Public report of AxonIQ/AxonFramework, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 18:39 UTC · Survey ID cd_7cef26ac4d554486b1f7a9c935a633a0

AxonIQ/AxonFramework

Measured 22 October 2026, 18:31 UTC, at code version 3bf89ef

CAI score 60out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 6 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Event Sourcing 100 Exemplary Code Health 84 Strong Architecture 78 Strong Performance 77 Strong Security and Compliance 72 Adequate Maturity 54 Adequate Production Readiness 53 Adequate

A large codebase: 176,354 lines of product code in 23 projects, tests not counted · Estimated rebuild effort: about 3.6 person-years · Weakest lens: Production Readiness, 53

Findings by how serious they are

45 critical 520 serious 660 minor

15 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 18:31 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

70of 76 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
1205of 1225 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
76dimensions across 7 lenses, read from 176,354 lines of product code in 23 projects.
Chapters

Executive summary

AxonIQ/AxonFramework scores 60 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Event Sourcing at 100, rated Exemplary, Code Health at 84, Architecture at 78 and Performance at 77, all rated Strong, and Security and Compliance at 72, rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Production Readiness, which scores 53 and is rated Adequate. Its Security & performance tooling dimension scores 3 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 ADR not followed finding(s) in ADR Conformance and to reconcile the README with reality: Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project; README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists; docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it; docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists, and if Production Readiness rose to 70, the score would rise from 60 to about 64.

45 findings are critical: 44 in Static Analysis (SAST) and one in ADR Conformance.

Watchdog couldn't measure 14 dimensions in this code, among them Code Coverage, Dependency Hygiene and Internal API Consistency, so they are left out of the score. The product code is 176,354 lines, which would take an estimated 3.6 person-years, around €530,000, to rebuild.

Code Health 84 Strong Architecture 78 Strong Maturity 54 Adequate, capped by Documentation accuracy Production Readiness 53 Adequate, capped by Security & performance tooling and Schema migrations Security and Compliance 72 Adequate, capped by Static Analysis (SAST) and Supply-chain Provenance & Signing Event Sourcing 100 ★ Exemplary Performance 77 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 53 · counts for 46%Maturity 54 · counts for 25%Security and Compliance 72 · counts for 14%Performance 77 · counts for 8%Architecture 78 · counts for 4%Code Health 84 · counts for 2%Event Sourcing 100 · counts for 1%

If Production Readiness rose from 53 to 70, the lowest score rated Strong, the score would rise from 60 to about 64.

Code composition: what the lines of code are
Product code 52%Tests 48%
New since the last survey: 158 findings

These 158 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java
  • Cyclomatic Complexity · 15003.visitClassDeclaration (cyclomatic 20) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Cyclomatic Complexity · 17091.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cyclomatic Complexity · 11940.visitClassDeclaration (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cyclomatic Complexity · 1.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java
  • Cyclomatic Complexity · AddAggregateScopeToDeadlineCalls.commandIdentifier (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cyclomatic Complexity · Aggregate.of (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cyclomatic Complexity · 5.visitMethodInvocation (cyclomatic 16) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • Cognitive Complexity · MoveSagaFieldToHandlerParameter.planFor (cognitive 40) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java
  • Cognitive Complexity · 15003.visitClassDeclaration (cognitive 28) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Cognitive Complexity · 11940.visitClassDeclaration (cognitive 26) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · Aggregate.of (cognitive 25) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cognitive Complexity · 20014.classFields (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · 20014.resolveIndent (cognitive 23) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · 1.unitOfWorkFactoryInScope (cognitive 23) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • Cognitive Complexity · 5.visitMethodInvocation (cognitive 22) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • Cognitive Complexity · 17091.visitMethodInvocation (cognitive 20) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cognitive Complexity · AddAggregateScopeToDeadlineCalls.commandIdentifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cognitive Complexity · AddAggregateScopeToDeadlineCalls.identifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Cognitive Complexity · MigrateAggregateDeadlineHandler.aggregateTypeOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Cognitive Complexity · MigrateAggregateDeadlineHandler.commandNamesOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Cognitive Complexity · 1.visitNewClass (cognitive 17) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java
  • Cognitive Complexity · 1.extractClassLiteralType (cognitive 16) migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java
  • God Classes · MethodTooLong: MigrateAxonTestFixtureFluentApi.getVisitor migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java
  • God Classes · MethodTooLong: MigrateDeadlineManagerBuilders.getVisitor migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • God Classes · ClassTooLong: MigrateDeadlineManagerBuilders migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • God Classes · ClassTooLong: AddAggregateScopeToDeadlineCalls migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • God Classes · TooManyMethods: AnnotatedEntityMetamodel modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java
  • God Classes · FileTooLong: migration/MigrateDeadlineManagerBuilders.java migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • God Classes · ClassTooLong: MigrateAggregateDeadlineHandler migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • God Classes · FileTooLong: config/SpringComponentRegistry.java extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java
  • Code Duplication · Duplicated block (6–13 lines × 3) extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java
  • Code Duplication · Duplicated block (12 lines × 2) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java
  • Code Duplication · Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java
  • Code Duplication · Duplicated block (9 lines × 4) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java
  • Code Duplication · Duplicated block (9 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java
  • Code Duplication · Duplicated block (7 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java
  • Code Duplication · Duplicated block (6 lines × 6) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Code Duplication · Duplicated block (6 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java
  • Code Duplication · Duplicated block (6 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MethodParameters.java
  • Code Duplication · Duplicated block (5 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java
  • Code Duplication · Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java
  • Code Duplication · Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java
  • Code Duplication · Duplicated block (9 lines × 4) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java
  • Churn × Complexity Hotspots · Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Churn × Complexity Hotspots · Hotspot: migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Churn × Complexity Hotspots · Hotspot: migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Churn × Complexity Hotspots · Hotspot: migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/StatementTodoMarker.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdas.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MarkUnsupportedSagaTestFixtureCalls.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/MarkAggregateTestFixtureDeadlineCalls.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypes.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypes.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotationTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotationKotlinTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdasTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateAggregateDeadlineHandlerTest.java

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 42 findings

These 42 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.

  • Cyclomatic Complexity · 8892.visitClassDeclaration (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · 8892.visitClassDeclaration (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · 15831.classFields (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Cognitive Complexity · 15831.resolveIndent (cognitive 23) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • God Classes · ClassTooLong: MigrateCommandGatewayInSagaEventHandler migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java
  • Code Duplication · Duplicated block (55–61 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java
  • Code Duplication · Duplicated block (20 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Duplicated block (11–12 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Duplicated block (11–12 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Duplicated block (10 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
  • Code Duplication · Duplicated block (10 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AnnotationBasedTagResolver.java
  • Code Duplication · Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java
  • Code Duplication · Duplicated block (9 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java
  • Code Duplication · Duplicated block (7–8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java
  • Code Duplication · Duplicated block (7 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java
  • Code Duplication · Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java
  • Code Duplication · Duplicated block (13 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/springboot/DropwizardMetricsAutoConfiguration.java
  • Explicit Debt · TodoComment examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/legacy/PaymentSaga.java
  • Explicit Debt · TodoComment examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/legacy/PaymentSaga.java
  • Explicit Debt · TodoComment examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/legacy/PaymentSaga.java
  • Explicit Debt · TodoComment examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/legacy/PaymentSaga.java
  • Explicit Debt · TodoComment examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/legacy/PaymentSaga.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotationTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotationKotlinTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Explicit Debt · TodoComment migration/src/test/java/org/axonframework/migration/MarkSagaResourceInjectionTest.java
  • Static Analysis (SAST) · High: watchdog-mutable-docker-action-tag REDACTED
  • Change Coupling · Change coupling: DefaultProcessorModuleFactory.java ↔ MessageHandlerConfigurer.java extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/DefaultProcessorModuleFactory.java
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Exception handling · Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java
  • Exception handling · Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java
Rebuild cost: about €530,000 · Estimate
Cost to rebuild€180,000 to €880,000, for 2,920 to 9,263 hours of work, about 3.6 person-years for 2 to 7 engineers
Difficulty of the problemHigh, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 176,354 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 0001-jackson-converter-jackson2-handling.md.
Raises the score by about 5 points · Low effort · ADR Conformance
2
Reconcile the README with reality: Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project; README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists; docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it; docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists.
Raises the score by about 6 points · Medium effort · Documentation accuracy
3
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 2 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €530,000 to build again, about 3.6 person-years of work. Its weakest lens is Production Readiness, at 53 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 ADR not followed finding(s) in ADR Conformance. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Conformance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch axon-common axon-common axon-conversion axon-conversion axon-conversion->axon-common axon-coverage-report axon-coverage-report axon-coverage-report->axon-common axon-coverage-report->axon-conversion axon-eventsourcing axon-eventsourcing axon-coverage-report->axon-eventsourcing axon-messaging axon-messaging axon-coverage-report->axon-messaging axon-metrics-dropwizard axon-metrics-dropwizard axon-coverage-report->axon-metrics-dropwizard axon-metrics-micrometer axon-metrics-micrometer axon-coverage-report->axon-metrics-micrometer axon-modelling axon-modelling axon-coverage-report->axon-modelling axon-spring axon-spring axon-coverage-report->axon-spring axon-spring-boot-autoconfigure axon-spring-boot-autoconfigure axon-coverage-report->axon-spring-boot-autoconfigure axon-test axon-test axon-coverage-report->axon-test axon-eventsourcing->axon-messaging axon-eventsourcing->axon-modelling axon-kotlin axon-kotlin axon-kotlin->axon-eventsourcing axon-kotlin->axon-messaging axon-kotlin->axon-modelling axon-kotlin-test axon-kotlin-test axon-kotlin-test->axon-test axon-messaging->axon-common axon-messaging->axon-conversion axon-update axon-update axon-messaging->axon-update axon-metrics-dropwizard->axon-messaging axon-metrics-dropwizard->axon-spring-boot-autoconfigure axon-metrics-micrometer->axon-messaging axon-metrics-micrometer->axon-spring-boot-autoconfigure axon-modelling->axon-messaging axon-reactor axon-reactor axon-reactor->axon-messaging axon-spring->axon-eventsourcing axon-spring->axon-messaging axon-spring->axon-modelling axon-spring-boot-autoconfigure->axon-reactor axon-spring-boot-autoconfigure->axon-spring axon-spring-boot-autoconfigure->axon-test axon-spring-boot-compatibility-tests-3 axon-spring-boot-compatibility-tests-3 axon-spring-boot-compatibility-tests-common axon-spring-boot-compatibility-tests-common axon-spring-boot-compatibility-tests-3->axon-spring-boot-compatibility-tests-common axon-spring-boot-compatibility-tests-4 axon-spring-boot-compatibility-tests-4 axon-spring-boot-compatibility-tests-4->axon-spring-boot-compatibility-tests-common axon-spring-boot-starter axon-spring-boot-starter axon-spring-boot-compatibility-tests-common->axon-spring-boot-starter axon-spring-boot-starter->axon-eventsourcing axon-spring-boot-starter->axon-messaging axon-spring-boot-starter->axon-modelling axon-spring-boot-starter->axon-spring axon-spring-boot-starter->axon-spring-boot-autoconfigure axon-spring-boot-starter-test axon-spring-boot-starter-test axon-spring-boot-starter-test->axon-test axon-test->axon-eventsourcing axon-update->axon-common __more__ +3 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

182 modules, with 749 dependencies between them. 4 loops run through 21 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 142 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 common2 common.infra3 messaging.core.unitofwork4 common.configuration5 conversion6 messaging.commandhandling7 messaging.core.conversion8 messaging.eventhandling.replay9 messaging.eventhandling10 messaging.core.sequencing11 messaging.core.annotation12 messaging.core13 messaging.commandhandling.gateway14 messaging.eventhandling.gateway15 messaging.eventhandling.processing.streaming.token16 messaging.queryhandling17 messaging.tracing18 modelling.repository19 messaging.core.interception20 messaging.eventhandling.annotation21 messaging.eventhandling.processing.streaming.segmenting22 messaging.eventstreaming23 modelling24 eventsourcing.eventstore25 messaging.eventhandling.processing26 modelling.entity27 eventsourcing.eventstore.jpa28 eventsourcing.eventstore.tracing29 eventsourcing.handler30 messaging.eventhandling.processing.streaming.pooled31 messaging.eventhandling.processing.subscribing32 modelling.annotation33 eventsourcing34 extension.springboot.autoconfig35 messaging.eventhandling.configuration36 modelling.entity.annotation37 messaging.core.configuration38 eventsourcing.configuration39 integrationtests.testsuite.administration40 integrationtests.testsuite.student
1 common
2 common.infra1
3 messaging.core.unitofwork10
4 common.configuration616
5 conversion14
6 messaging.commandhandling446519
7 messaging.core.conversion12
8 messaging.eventhandling.replay334215
9 messaging.eventhandling61012212126
10 messaging.core.sequencing10115
11 messaging.core.annotation2121125
12 messaging.core1391811
13 messaging.commandhandling.gateway55429
14 messaging.eventhandling.gateway4447
15 messaging.eventhandling.processing.streaming.token12
16 messaging.queryhandling5610171430
17 messaging.tracing2510
18 modelling.repository1361
19 messaging.core.interception17431444296
20 messaging.eventhandling.annotation1624522353
21 messaging.eventhandling.processing.streaming.segmenting1328195
22 messaging.eventstreaming21134
23 modelling191021369
24 eventsourcing.eventstore55122222524
25 messaging.eventhandling.processing1311241
26 modelling.entity772121936
27 eventsourcing.eventstore.jpa3111335217
28 eventsourcing.eventstore.tracing1221222429
29 eventsourcing.handler551113153
30 messaging.eventhandling.processing.streaming.pooled220815117122012211
31 messaging.eventhandling.processing.subscribing122845211
32 modelling.annotation3617482
33 eventsourcing131131111
34 extension.springboot.autoconfig1211252434121
35 messaging.eventhandling.configuration2117751331
36 modelling.entity.annotation45132259281
37 messaging.core.configuration29151211511421
38 eventsourcing.configuration10212311214631611
39 integrationtests.testsuite.administration131146
40 integrationtests.testsuite.student6223214231141111
Uses a module listed above itPart of a loopThe module itself
1 common2 common.infra3 messaging.core.unitofwork4 common.configuration5 conversion6 messaging.commandhandling7 messaging.core.conversion8 messaging.eventhandling.replay9 messaging.eventhandling10 messaging.core.sequencing11 messaging.core.annotation12 messaging.core13 messaging.commandhandling.gateway14 messaging.eventhandling.gateway15 messaging.eventhandling.processing.streaming.token16 messaging.queryhandling17 messaging.tracing18 modelling.repository19 messaging.core.interception20 messaging.eventhandling.annotation21 messaging.eventhandling.processing.streaming.segmenting22 messaging.eventstreaming23 modelling24 eventsourcing.eventstore25 messaging.eventhandling.processing26 modelling.entity27 eventsourcing.eventstore.jpa28 eventsourcing.eventstore.tracing29 eventsourcing.handler30 messaging.eventhandling.processing.streaming.pooled31 messaging.eventhandling.processing.subscribing32 modelling.annotation33 eventsourcing34 extension.springboot.autoconfig35 messaging.eventhandling.configuration36 modelling.entity.annotation37 messaging.core.configuration38 eventsourcing.configuration39 integrationtests.testsuite.administration40 integrationtests.testsuite.studentcommon1common.infra2messaging.core.unitofwork3common.configuration4conversion5messaging.commandhandling6messaging.core.conversion7messaging.eventhandling.replay8messaging.eventhandling9messaging.core.sequencing10messaging.core.annotation11messaging.core12messaging.commandhandling.gateway13messaging.eventhandling.gateway14messaging.eventhandling.processing.streaming.token15messaging.queryhandling16messaging.tracing17modelling.repository18messaging.core.interception19messaging.eventhandling.annotation20messaging.eventhandling.processing.streaming.segmenting21messaging.eventstreaming22modelling23eventsourcing.eventstore24messaging.eventhandling.processing25modelling.entity26eventsourcing.eventstore.jpa27eventsourcing.eventstore.tracing28eventsourcing.handler29messaging.eventhandling.processing.streaming.pooled30messaging.eventhandling.processing.subscribing31modelling.annotation32eventsourcing33extension.springboot.autoconfig34messaging.eventhandling.configuration35modelling.entity.annotation36messaging.core.configuration37eventsourcing.configuration38integrationtests.testsuite.administration39integrationtests.testsuite.student40110616144465191233421561012212126101152121125139181155429444712561017143025101361174314442961624522353132819521134191021369551222225241311241772121936311133521712212224295511131532208151171220122111228452113617482131131111121125243412121177513314513225928129151211511421102123112146316111311466223214231141111+142 more modules (most-connected shown)

At a glance — Code Health · 84% · Strong ·

The Good
D1 · .NET / C# Cyclomatic Complexity 8.3 D3 · .NET / C# God Classes 9.3 D4 · .NET / C# Code Duplication 9.5 D17 · .NET / C# Explicit Debt 9.9 IC1 · Repo Incompleteness & stubs 9.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.4 X30 · Repo Support guard that admits what it rejects 10.0 X4 · Repo Structured logging 7.9 X5 · Repo Nullable reference types 9.9
The Bad
D2 · .NET / C# Cognitive Complexity 7.0

At a glance — Architecture · 78% · Strong ·

The Good
D5 · .NET / C# Coupling 9.6 D6 · .NET / C# Cohesion (LCOM4) 9.8 D7 · .NET / C# Architectural Integrity 8.0 D35 · .NET / C# Change Coupling 9.9 AX1 · Repo Captive dependencies 10.0 AX2 · Repo Stateful singletons 7.2 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0
The Bad
D26 · .NET / C# Project Cohesion 6.0 AX10 · Repo Code composition 5.5

At a glance — Maturity · 54% · Adequate · gated by M4 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 8.3 D19 · .NET / C# Documentation Quality 9.0 D20 · .NET / C# ADR Quality 10.0 D21 · .NET / C# Naming Consistency 10.0 D34 · .NET / C# Knowledge Freshness 9.8 M1 · Repo Documentation (README) 7.1 M2 · Repo Architecture documentation 7.0 M3 · Repo Folder & project structure 10.0
The Ugly
D25 · .NET / C# ADR Conformance 0.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 53% · Adequate · gated by P3, P8 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.1 D11 · .NET / C# Test Reliability 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 9.4 P4 · Repo Deployment & Rollback 7.0 P7 · Repo Outbound HTTP resilience 10.0
The Bad
P10 · Repo Library API & versioning 6.0 P6 · Repo Release Hygiene 5.0
The Ugly
P3 · Repo Security & performance tooling 3.0 P8 · Repo Schema migrations 3.0

At a glance — Security · 72% · Adequate · gated by D29, D36 ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D30 · .NET / C# Dependency Vulnerabilities 10.0 D31 · .NET / C# IaC & Container Security 10.0 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.7 D36 · .NET / C# Supply-chain Provenance & Signing 2.5

At a glance — Event Sourcing · 100% · Exemplary ·

The Good
ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0 ES3 · Repo PII in the event store 10.0

At a glance — Performance · 77% · Strong ·

The Good
PF3 · Repo Async & latency hygiene 10.0
The Bad
PF2 · Repo Allocation hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection51High / Critical
A03:2025 — Software Supply Chain Failures13Medium

Roadmap

First, reconcile the documentation with the actual codebase to eliminate contradictions and remove references to non-existent files or configurations. Next, address the single ADR conformance issue and implement a SAST step in CI to prevent security regressions from reaching production. Finally, replace Hibernate's automatic schema management with a versioned migration tool like Flyway or Liquibase to ensure safe database evolution, and establish a changelog to clearly record what ships in each release.

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

Do thisHelpsEffortDimension
Resolve the 1 ADR not followed finding(s) in ADR Conformance — start with 0001-jackson-converter-jackson2-handling.md.+5.4 ptsLowADR Conformance
Reconcile the README with reality: Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project; README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists; docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it; docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists.+5.6 ptsMediumDocumentation accuracy
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+2.5 ptsMediumSecurity & performance tooling
Replace Hibernate ddl-auto with Flyway or Liquibase, with `ddl-auto` set to `validate` so the production schema can evolve safely and reproducibly.+2.5 ptsMediumSchema migrations
Resolve the 6 Off-boarding risk finding(s) in Bus Factor.+1.2 ptsLowBus Factor
Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.+0.8 ptsLowSupply-chain Provenance & Signing
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+1.5 ptsMediumRelease Hygiene
Grow the ADR log (currently 1) — reach 8 to raise the maturity tier; document significant decisions as they're made.+1.3 ptsMediumArchitecture documentation

File quality

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

FileScoreBandWorst signal
REDACTED0.9SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java5.6MixedCyclomatic Complexity: CoordinationTask.run (cyclomatic 20)
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java6.0MixedExplicit Debt: TodoComment
migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java6.0MixedExplicit Debt: TodoComment
migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java6.0MixedExplicit Debt: TodoComment
migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java6.0MixedExplicit Debt: TodoComment
migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java6.0MixedExplicit Debt: TodoComment
migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java6.0MixedExplicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 45

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 520

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 660

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 15

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 70 of 76 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — 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 — 76 dimensions across the health lenses
D1D2D3D4D5D6D7D9D10D11D13D14D15D16D17D19D20D21D25D26D28D29D30D31D34D35D36D43D44AX1AX10AX2AX3AX5AX6ES1ES2ES3IC1M1M2M3M4P1P10P2P3P4P6P7P8PF2PF3X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X4X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a164e2-188d-701b-82b7-fd0631a3eaaf.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,325 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 22 test source file(s) (.kt) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because central.sonatype.com — the registry that answers it — was asked and did not reply (the build stopped because central.sonatype.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it; 59 dependencies were resolved and graded first, but the graph is partial so the result is reported and not scored). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add central.sonatype.com to the allowlist and re-run — not to build anything.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `common/src/main/java/org/axonframework/common/ReflectionUtils.java`, `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java`, … (+9 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D43 Malicious Dependencies — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; npm was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that npm is free of known-vulnerable dependencies.
  • AX9 CQS / query purity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 1 query handler was classified, but the query-purity walk could not open its body: it recognises a value-returning entry point named Execute/Handle/Consume (±Async), or one implementing a member of the handler interface the type was classified on, and the handlers in this repository have neither. Scoring the set anyway would report every unopened handler as pure, so AX9 abstains instead of publishing a perfect score it did not measure.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/docker-compose.yaml). compose up failed (exit 18 — an image could not be pulled) — axon-server Pulling axon-server Error Get "https://docker.axoniq.io/v2/": Forbidden Error response from daemon: Get "https://docker.axoniq.io/v2/": Forbidden; the earlier `compose pull` step reported: axon-server Pulling axon-server Error Get "https://docker.axoniq.io/v2/": Forbidden Error response from daemon: Get "https://docker.axoniq.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.

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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • 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. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • 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.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • 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.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (6): D19, D20, D21, D25, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

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

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

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

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

13 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MoveSagaFieldToHandlerParameter.planFor at 27. 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. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/MethodSequencingPolicyEventHandlerDefinition.java (SequencingPolicyEventMessageHandlingMember.parseParameter at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27)migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257
15003.visitClassDeclaration (cyclomatic 20)migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245
CoordinationTask.run (cyclomatic 20)messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:767
17091.visitMethodInvocation (cyclomatic 19)migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333
11940.visitClassDeclaration (cyclomatic 19)migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234

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

What to do

  1. Bring the 13 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27), 15003.visitClassDeclaration (cyclomatic 20), CoordinationTask.run (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cyclomatic Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity7.0 / 10Adequate✓ Tool-verified

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

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

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

31 method(s) exceeded the cognitive complexity threshold of 15; the worst was MoveSagaFieldToHandlerParameter.planFor at 40.

MoveSagaFieldToHandlerParameter.planFor (cognitive 40)migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257
MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37)migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:367
1.removeGatewayFromConstructors (cognitive 36)migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:760
15003.visitClassDeclaration (cognitive 28)migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245
AddCommandAnnotation.hasRoutingKeyAttribute (cognitive 27)migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:338

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with MoveSagaFieldToHandlerParameter.planFor (cognitive 40), MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37), 1.removeGatewayFromConstructors (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 7.0 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.3 / 10Stronggated by 36 serious findings✓ Tool-verified

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

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

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

36 god class(es) detected.

MethodTooLong: MigrateCommandGatewayInEventHandler.getVisitor · ×12migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:96
TooManyMethods: PooledStreamingEventProcessorConfiguration · ×11messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorConfiguration.java:100
ClassTooLong: Coordinator · ×8messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:86
FileTooLong: pooled/Coordinator.java · ×5messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java

What to do

  1. Resolve the 12 MethodTooLong finding(s) in God Classes — start with MigrateCommandGatewayInEventHandler.java, MigrateCommandGatewayInSagaEventHandler.java, AddEventTagAnnotation.java. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 11 TooManyMethods finding(s) in God Classes — start with PooledStreamingEventProcessorConfiguration.java, JdbcTokenStore.java, MessagingConfigurer.java. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 8 ClassTooLong finding(s) in God Classes — start with Coordinator.java, AddEventTagAnnotation.java, MigrateCommandGatewayInEventHandler.java. — One of this dimension's main actionable groups (8 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication9.5 / 10Stronggated by 191 serious findings✓ Tool-verified

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

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

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

177 duplicated block group(s) detected. A further 14 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 62 of the 191 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (9 lines × 2) · ×13common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:202
Duplicated block (5 lines × 2) · ×12common/src/main/java/org/axonframework/common/ReflectionUtils.java:389
Duplicated block (8 lines × 2) · ×11messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:449
Duplicated block (7 lines × 2) · ×11examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:290
Duplicated block (6 lines × 2) · ×11common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:58

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

What to do

  1. Resolve the 13 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AddCommandAnnotation.java (2), DefaultComponentRegistry.java, MetricsConfigurationEnhancer.java. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 12 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with SimpleEventSourcedEntityModule.java (3), ReflectionUtils.java, JacksonConverter.java. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 11 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MigrateCommandGatewayInEventHandler.java (2), JdbcTokenStore.java, SimpleQueryBus.java. — One of this dimension's main actionable groups (11 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.6 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

23 production modules (Maven), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 15 of the 23 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Unstable project axon-spring-boot-starter

What to do

  1. Resolve the 1 Unstable project axon-spring-boot-starter finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

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

5 of 379 classes have LCOM4 above 3.

Low cohesion: Builder (LCOM4 19) · ×5messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:417

What to do

  1. Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with Coordinator.java, WorkPackage.java, TokenSchema.java. — One of this dimension's main actionable groups (5 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D7 · Architectural Integrity8.0 / 10Strong✓ Tool-verified

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.

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

All 1 mechanizable ADR(s) are enforced: 0 by analyzers, 1 by tests. 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

  1. Enforce Architectural Integrity in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified toward Prevented — provenance only; does not change the score.

Detailed fixes: d7_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.1 / 10Stronggated by 83 serious findings✓ Tool-verified

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

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

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

4 skipped (4 with a documented reason), 654 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1325 tests (6 harness-style project(s) excluded from the assertion penalty). Measured on the .java suite only — at least 22 test source file(s) (.kt) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: closesTheSpanAtContextCompletionWhenTheTransactionIsAbandoned · ×83eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStorageEngineTest.java:107
No direct assertions: givenPreparedPaymentWhenCancelPaymentThenPaymentCancelled · ×571examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:45
Skipped (documented): nextThenMapTest · ×4messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:226

What to do

  1. Resolve the 571 No direct assertions finding(s) in Test Quality — start with MigrateAggregateDeadlineHandlerTest.java (37), Axon4ToAxoniq5LegacySagaTest.java (31), MoveSagaFieldToHandlerParameterTest.java (29). — One of this dimension's main actionable groups (571 recommendation-level).
  2. Resolve the 83 No assertions finding(s) in Test Quality — start with TracingEventHandlingComponentTest.java (17), AxonTestFixtureExcludesWhenInputsTest.java (8), TracingQueryBusTest.java (7). — One of this dimension's main actionable groups (83 warning-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Maven): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 37 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 56 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 592 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 7 serious findings✓ Tool-verified

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

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

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

Top hotspots: messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java (10×20=200); migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java (7×20=140); migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java (6×19=114)

Hotspot: messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java · ×7messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:767

What to do

  1. Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with Coordinator.java, MigrateAggregateDeadlineHandler.java, AddAggregateScopeToDeadlineCalls.java. — One of this dimension's main actionable groups (7 warning-level).

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

D16 · Bus Factor8.3 / 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.

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

119 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/MigrateSagaLifecycle.java. Counted over 698 of the 1161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×6
Further sole-owners (lower concentration)

What to do

  1. Resolve the 6 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (6 recommendation-level).
  2. 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.

D17 · Explicit Debt9.9 / 10Stronggated by 111 serious findings✓ Tool-verified

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

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

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

111 deducted task-comment markers across 176354 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×110eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ContinuousMessageStream.java:95
FixmeCommentintegrationtests/src/test/java/org/axonframework/integrationtests/queryhandling/SimpleQueryBusSubscriptionQueryTest.java:52

What to do

  1. Resolve the 110 TodoComment finding(s) in Explicit Debt — start with MigrateAggregateDeadlineHandlerTest.java (21), AddAggregateScopeToDeadlineCallsTest.java (9), MarkUnsupportedSagaTestFixtureCallsTest.java (7). — One of this dimension's main actionable groups (110 warning-level).
  2. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with SimpleQueryBusSubscriptionQueryTest.java. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation QualityExemplary◐ Sampled · advisory

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

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

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

The repository's root README and the docs/README are both excellent: the root one is a clear overview of Axon Framework with product links, an Axon IQ transfer note, and a strong architecture section; the docs/README documents the AxonIQ Docs project as a standalone Antora repo (with migration, getting started, identifier-generation guides, and contribution instructions). The READMEs are each complete for their directories: the root one is the repository overview, the docs/README is the docs directory's own documentation, and the examples/* READMEs are per-directory. All visible documents are well-structured with headings, an overview, and clear usage/contribution guidance. The repository is well documented with a strong README for each directory (e.g. university-multi-tenancy-examples/README.md), an architecture/design docs set of 141 markdown files, and the root CLAUDE.md covering migration, project overview, and getting started. The documentation is comprehensive and well-structured across directories: the university multi-tenancy examples show what the demo demonstrates (one enrollment per tenant, per-tenant event storage, tenant-aware processing), while the Axon 5 reference guide migration instructions describe the architectural changes and a detailed changes-to-process.md workflow. All visible documents are present in the outline; no missing section is flagged.

Documentation: no project overviewdocs/CLAUDE.md

✓ On the Gold path — maintain.

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

D20 · ADR QualityExemplary◐ Sampled · advisory

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.

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

Evaluated 1 ADR(s) individually; mean quality 10.0/10 (consistently complete and clear). 0 flagged with a specific gap.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D25 · ADR ConformanceCritical◐ Sampled · advisory

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.

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

0 conform / 1 violate across 1 ADRs.

ADR not followed: 1. JacksonConverter rejects Jackson 2 tree nodes (fail loud)specs/137-message-transformation/0001-jackson-converter-jackson2-handling.md

What to do

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

D26 · Project Cohesion6.0 / 10Adequate✓ Tool-verified

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

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

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

3 of 15 build units (Maven, npm) flagged as possibly oversized/incoherent.

Split messaging

What to do

  1. Resolve the 1 Split messaging finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.7 / 10Critical✓ Tool-verified

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

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

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

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

51 finding(s): 0 critical, 44 high, 7 medium, 0 low. 31 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 15 file(s) — `common/src/main/java/org/axonframework/common/ReflectionUtils.java` (line 539, line 542), `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java` (line 275, line 279, line 280, …), `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java` (line 466, line 467), `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java` (line 41, line 42, lines 66–69, …), `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java` (line 61), … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 31 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (31 issue-level, 0 of them charged here).

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

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

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness9.8 / 10Exemplary✓ Tool-verified

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

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

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

13 of 698 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java. Counted over 698 of the 1161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×13extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.9 / 10Stronggated by 10 serious findings✓ Tool-verified

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

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

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: MappedMessageStream.java↔OnErrorContinueMessageStream.java 80%; OnErrorContinueMessageStream.java↔OnNextMessageStream.java 75%; ConcatenatingMessageStream.java↔OnNextMessageStream.java 75%

Change coupling: MessageStreamUtils.java ↔ SingleValueMessageStream.java · ×8messaging/src/main/java/org/axonframework/messaging/core/MessageStreamUtils.java:1
Change-coupling hub: MappedMessageStream.java → ConcatenatingMessageStream.java, EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java · ×2messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java

What to do

  1. Resolve the 8 Change coupling finding(s) in Change Coupling — start with MessageStreamUtils.java, ConcatenatingMessageStream.java, MergedMessageStream.java. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with MappedMessageStream.java, OnNextMessageStream.java. — One of this dimension's main actionable groups (2 warning-level).

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

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

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. npm was not scanned (npm: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 4 platform declaration(s) and 84 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

AX10 · Code composition5.5 / 10Adequate✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons7.2 / 10Strong✓ Tool-verified

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

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

  • `SpringParameterResolverFactoryBean` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (factories; e.g. `factories` in `setAdditionalFactories` at line 85). — extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/annotation/SpringParameterResolverFactoryBean.java:42
  • `SpringComponentRegistry` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (disableEnhancerScanning, beanFactory, factories; e.g. `disableEnhancerScanning` in `disableEnhancerScanning` at line 266). — extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104

What to do

  • Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

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.

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

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.

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.

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `position` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ConsistencyMarkers.java:79
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×17) — common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:668, common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:699, eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStoreTestSuite.java:249, …

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
  • Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)7.1 / 10Strong✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying 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 43 of 55 project(s) that lack one — worth up to 1.6 pts.
M2 · Architecture documentation7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Grow the ADR log (currently 1) — reach 8 to raise the maturity tier; document significant decisions as they're made.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

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

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

  • Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project — searched for: `code-samples`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:1
  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:32
  • docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/README.md:49
  • docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/ROOT/pages/conversion.adoc:214
  • docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/configuration/pages/spring.adoc:194
  • docs/reference-guide/modules/messaging-concepts/pages/anatomy-message.adoc names `module-info.java`, but no file or folder `module-info.java` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/messaging-concepts/pages/anatomy-message.adoc:75
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `org.axonframework.config`, but no file or folder `org.axonframework.config` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:93
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring`, but no file or folder `extensions/axon-spring` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:251
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring-boot-autoconfigure`, but no file or folder `extensions/axon-spring-boot-autoconfigure` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:255
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring-boot-starter`, but no file or folder `extensions/axon-spring-boot-starter` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:259
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-metrics-dropwizard`, but no file or folder `extensions/axon-metrics-dropwizard` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:263
  • docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-metrics-micrometer`, but no file or folder `extensions/axon-metrics-micrometer` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference-guide/modules/migration/pages/paths/index.adoc:267

What to do

  • Reconcile the README with reality: Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project; README advertises a microservices architecture, but the repo is a single project with no service manifests; docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists; docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it; docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

  • 1045/1386 types (75%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

What to do

  • Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`) so internals can change without breaking consumers.
P2 · Observability9.4 / 10Exemplary✓ Tool-verified

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

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

  • Only 8/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/_playbook`, `extensions/spring/spring-boot-compatibility-tests/common`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 33781 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

P8 · Schema migrations3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

  • Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment. (×4) — examples/university-java-springboot-3/src/main/resources/application.yml:14, examples/university-java-springboot-4/src/main/resources/application.yml:14, examples/workflow-bike-rental/src/main/resources/application.yaml:24, …

What to do

  • Replace Hibernate ddl-auto with Flyway or Liquibase, with `ddl-auto` set to `validate` so the production schema can evolve safely and reproducibly.
PF2 · Allocation hygiene6.0 / 10Adequate✓ Tool-verified

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

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 11 use(s) across 138,351 production line(s) (~0.1/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
  • Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

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

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

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

  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — extensions/spring/spring/src/main/java/org/axonframework/extension/spring/conversion/avro/SpecificRecordBaseClasspathAvroSchemaLoader.java:76, update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:158, update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49
  • `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:274, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:481, migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:213

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging7.9 / 10Strong✓ Tool-verified

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

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `info` at line 138 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/JpaPollingEventCoordinator.java:138

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 144/145 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

Reference — by lens

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

LensScoreRatingImpact
Code Health84%StrongSolid.
Architecture78%StrongSolid.
Maturity54%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness53%Adequate — gated by P3, P8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security72%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Event Sourcing100%ExemplaryStrongest area.
Performance77%StrongSolid.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • P12 CI test-gate honesty — 1 observation(s) recorded · 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.
  • X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 40 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.
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — 1 query handler detected, but its entry-point body could not be walked — the query-purity oracle recognises a value-returning Execute/Handle/Consume (±Async) entry point or one that implements the classifying handler interface's member, and this codebase's handlers were classified but never read. This is an engine limitation, not a finding about the repository.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — axon-server Pulling axon-server Error Get "https://docker.axoniq.io/v2/": Forbidden Error response from daemon: Get "https://docker.axoniq.io/v2/": Forbidden; the earlier `compose pull` step reported: axon-server Pulling axon-server Error Get "https://docker.axoniq.io/v2/": Forbidden Error response from daemon: Get "https://docker.axoniq.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • 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.
  • D12 Dependency Hygiene — Dependency currency not established — central.sonatype.com did not answer
  • 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 — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (examples), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.java), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 14 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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.
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (5 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 391 value object(s); 37 domain event(s); its domain events are published by services or handlers — no domain entity raises one; 3 repository port(s) loading or saving an aggregate/entity; a DDD annotation stack (jMolecules/Axon @AggregateRoot/@Aggregate/@ValueObject — persistence @Entity does not count); a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
  • ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 31 event handler(s); 7 CQRS handler(s)
  • ED5 Idempotency — Not assessed, and this one is on us: 37 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • 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.
  • X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

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.

Critical — 45 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 6 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D25 · ADR Conformance · ADR not followed · ×1
  • ADR not followed: 1. JacksonConverter rejects Jackson 2 tree nodes (fail loud) specs/137-message-transformation/0001-jackson-converter-jackson2-handling.md — JacksonConverter derives from ObjectMapper (tools.jackson.databind.ObjectMapper), which is Jackson 3, but the summary shows no rejection of Jackson 2 JsonNode in favour of a Map<String,Object>. (specs/137-message-transformation/0001-jackson-converter-jackson2-handling.md)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 520 finding(s)
D17 · Explicit Debt · TodoComment · ×110
  • TodoComment eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ContinuousMessageStream.java:95 — // TODO #3854 - ContinuousMessageStream may block in its MessageStream::peek call (and methods that rely on it) which is not allowed
  • TodoComment eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStoreTestSuite.java:250 — // TODO #3997 - it looks like they return a token that's one position too low? Postgres does not do this
  • TodoComment integrationtests/src/test/java/org/axonframework/integrationtests/queryhandling/AbstractSubscriptionQueryTestSuite.java:441 — // TODO #4422 this test was/is flakey sometimes, will hang indefinitely, needs further investigation
  • TodoComment integrationtests/src/test/java/org/axonframework/integrationtests/queryhandling/AbstractSubscriptionQueryTestSuite.java:759 — // todo: there is a difference between Distributed (we convert: null -> bytes[0] -> string) we ends with empty string and the Local (we just pass null) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment messaging/src/test/java/org/axonframework/messaging/core/AsyncMessageHandlerTest.java:373 — // TODO #3392 - Once EventSink is created, can adds declartive tests here which subscribe with a QualifiedName
  • TodoComment migration/src/main/java/org/axonframework/migration/StatementTodoMarker.java:34 — // TODO(axon4to5):} markers on the statements of a block that contain a method invocation needing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:513 — // TODO(axon4to5):} line comment above the {@code @Aggregate}/{@code @EventSourced} — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:534 — // TODO(axon4to5):} line comment above the bean method for custom trigger types. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:63 — // TODO(axon4to5):} comment for a manual migration, as each of its — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:65 — // TODO(axon4to5):} comment is prepended to the class with a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:141 — // Two passes: rewrite the matching `handle` method, then add the class-level TODO. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateLegacyFixtureInterceptorLambdas.java:74 — // TODO(axon4to5):} marker on its — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java:61 — // TODO(axon4to5):} marker on the statement: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:83 — // TODO(axon4to5):} marker on the statement that — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:67 — // TODO(axon4to5):} marker asks to name the command after the deadline instead. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:74 — // TODO(axon4to5):} marker and keeps the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MarkUnsupportedSagaTestFixtureCalls.java:34 — // TODO(axon4to5):} marker on the Axon Framework 4 {@code SagaTestFixture} usage that the fixture — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:39 — // TODO(axon4to5):} marker wherever an Axon Framework 4 Saga relies on resource injection, which — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/MarkAggregateTestFixtureDeadlineCalls.java:34 — // TODO(axon4to5):} marker on the statements that use the deadline and time support of the Axon — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java:33 — // TODO(axon4to5):} comment. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypes.java:62 — // TODO(axon4to5):} comment pointing at the new shape: AF5 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/Axon4ToAxon5QueryResponseTypes.java:171 — // TODO(axon4to5):} comment to a {@code subscriptionQuery(...)} call — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:73 — // TODO(axon4to5):} comment asking a human reviewer to verify the choice;</li> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:77 — // TODO(axon4to5):} comment;</li> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:79 — // TODO(axon4to5):} comment.</li> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 85 more in this group — see findings.md.
D10 · Test Quality · No assertions · ×83
  • No assertions: closesTheSpanAtContextCompletionWhenTheTransactionIsAbandoned eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStorageEngineTest.java:107 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: addsResolvedTagsToTheActiveSpan eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/annotation/TracingEventTagsHandlerEnhancerDefinitionTest.java:64 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: resolvesEventTagAnnotationsFromTheHandlersDeclaredPayloadType eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/annotation/TracingEventTagsHandlerEnhancerDefinitionTest.java:82 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensASourcingSpanCarryingEntityTypeAndIdentifier eventsourcing/src/test/java/org/axonframework/eventsourcing/handler/tracing/TracingEntityLifecycleHandlerTest.java:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensAnInternalSpanWithQualifiedNameAndIdentifier eventsourcing/src/test/java/org/axonframework/eventsourcing/snapshot/store/tracing/TracingSnapshotStoreTest.java:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensAnInternalSpanForLoad eventsourcing/src/test/java/org/axonframework/eventsourcing/snapshot/store/tracing/TracingSnapshotStoreTest.java:94 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: leavesTheStorageEngineUndecoratedWhenEventStoreTracingIsDisabled eventsourcing/src/test/java/org/axonframework/eventsourcing/tracing/configuration/EventStorageEngineTracingConfigurationTest.java:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: tracesTheConfiguredStorageEngineUntilTheAppendTransactionRollsBack eventsourcing/src/test/java/org/axonframework/eventsourcing/tracing/configuration/EventStorageEngineTracingConfigurationTest.java:52 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensAnInternalSpanWithEntityTypeAndIdentifier modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensAnInternalSpanForPersist modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:73 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: attachBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:141 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: loadBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:94 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: loadOrCreateBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:110 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: persistBranchesContextSoDownstreamSpansNestUnderIt modelling/src/test/java/org/axonframework/modelling/repository/tracing/TracingRepositoryTest.java:126 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: publishNoEvents extensions/reactor/axon-reactor/src/test/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGatewayTest.java:124 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: subscriptionQueryExceptionReportedInFlux extensions/reactor/axon-reactor/src/test/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGatewayTest.java:230 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opensCompletesAndPropagatesADispatchSpan messaging/src/test/java/org/axonframework/messaging/commandhandling/tracing/TracingCommandBusTest.java:72 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: asynchronousActionsRegisteredByShufflingThePhasesAreExecutedInTheIntendedPhaseOrder messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:217 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: asynchronousActionsRegisteredInReversePhaseOrderAreExecutedInTheIntendedPhaseOrder messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:158 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: asynchronousActionsRegisteredInReversePhaseOrderWithDifferingTimeoutsAreExecutedInTheIntendedPhaseOrder messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:187 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: asynchronousActionsRegisteredInTheSamePhaseAlwaysCompleteBeforeEnteringTheSubsequentPhase messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:129 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: synchronousActionsRegisteredInReversePhaseOrderAreExecutedInTheIntendedPhaseOrder messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:100 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: synchronousActionsRegisteredInTheSamePhaseAlwaysCompleteBeforeEnteringTheSubsequentPhase messaging/src/test/java/org/axonframework/messaging/core/unitofwork/ProcessingLifecycleTest.java:71 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: sequenceNumberParameterResolverHandlesPrimitive messaging/src/test/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedParameterResolverFactoryTest.java:47 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: sequenceNumberParameterResolverIsReturnedOnlyWhenAppropriate messaging/src/test/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedParameterResolverFactoryTest.java:40 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 58 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×13
  • Duplicated block (9 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:202 — common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:202-210 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:237-245 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:91 — extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:91-99 | extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:111-119 — 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 `extensions/metrics/metrics-dropwizard/src/main/java/org/axonframework/extension/metrics/dropwizard/MetricsConfigurationEnhancer.java:91` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:233 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:233-241 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java:204-212 — before extracting anything, compare `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java` and `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:340 — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:340-348 | migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:393-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.
  • 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, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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) modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java:54 — modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java:54-62 | modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyEventTargetMatcherDefinition.java:52-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:204 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:204-212 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorModule.java:143-151 — 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 (9 lines × 2) extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfiguration.java:71 — extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfiguration.java:71-79 | extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/ReactorAutoConfiguration.java:72-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfiguration.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `commandInterceptors` to `Optional<List<MessageDispatchInterceptor<? super CommandMessage>>>` in one and `Optional<List<ReactorMessageDispatchInterceptor<? super CommandMessage>>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:167 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:167-175 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorsConfigurer.java:164-172 — 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/PooledStreamingEventProcessorsConfigurer.java:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:150 — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:150-158 | migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:107-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (9 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:66 — modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:66-74 | modelling/src/main/java/org/axonframework/modelling/entity/annotation/SingleEntityChildModelDefinition.java:61-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:66` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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-3/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java:28 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java:28-36 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java:28-36 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/automation/NotificationAutomationConfiguration.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandler.java:57 — examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandler.java:57-65 | examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/rejectpayment/RejectPaymentCommandHandler.java:55-63 — before extracting anything, compare `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandler.java` and `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/payment/write/rejectpayment/RejectPaymentCommandHandler.java` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `ConfirmPayment` in one and `RejectPayment` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D3 · God Classes · MethodTooLong · ×12
  • MethodTooLong: MigrateCommandGatewayInEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:96 — MethodTooLong — getVisitor runs 494 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 394 over it, 4.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateCommandGatewayInSagaEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:85 — MethodTooLong — getVisitor runs 353 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 253 over it, 3.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AddEventTagAnnotation.getVisitor migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:369 — MethodTooLong — getVisitor runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateSagaLifecycle.getVisitor migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:106 — MethodTooLong — getVisitor runs 273 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 173 over it, 2.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateEventGatewayPublishInEventHandler.getVisitor migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:93 — MethodTooLong — getVisitor runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateAxonTestFixtureFluentApi.getVisitor migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:90 — MethodTooLong — getVisitor runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateDeadlineManagerBuilders.getVisitor migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:171 — MethodTooLong — getVisitor runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MigrateMessageInterceptorSignatures.getVisitor migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:129 — MethodTooLong — getVisitor runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CoordinationTask.run messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:767 — MethodTooLong — run runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ReplaceAggregateLifecycleApply.getVisitor migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:92 — MethodTooLong — getVisitor runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ConvertCommandHandlerConstructorToCompanionObject.getVisitor migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:86 — MethodTooLong — getVisitor runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AddEntityCreatorAnnotation.getVisitor migration/src/main/java/org/axonframework/migration/AddEntityCreatorAnnotation.java:72 — MethodTooLong — getVisitor runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×12
  • Duplicated block (5 lines × 2) common/src/main/java/org/axonframework/common/ReflectionUtils.java:389 — common/src/main/java/org/axonframework/common/ReflectionUtils.java:389-393 | common/src/main/java/org/axonframework/common/ReflectionUtils.java:405-409 — 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/ReflectionUtils.java:389` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (5 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:99 — conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:99-103 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:83-87 — before extracting anything, compare `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java` and `conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:99` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: `ObjectMapper` names `com.fasterxml.jackson.databind.ObjectMapper` in one and `tools.jackson.databind.ObjectMapper` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:246 — eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:246-252 | modelling/src/main/java/org/axonframework/modelling/configuration/SimpleStateBasedEntityModule.java:192-196 — 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:246` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with 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 (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:336 — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:336-340 | eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/inmemory/InMemoryEventStorageEngine.java:352-356 — 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) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:966 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:966-970 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:991-995 — 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:966` 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 (5 lines × 2) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231 — migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:231-235 | migration/src/main/java/org/axonframework/migration/MigrateAggregateTestFixtureSetup.java:218-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `target` to `J.Annotation` in one and `J.NewClass` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MethodParameters.java:261 — migration/src/main/java/org/axonframework/migration/MethodParameters.java:261-265 | migration/src/main/java/org/axonframework/migration/MethodParameters.java:276-280 — 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/MethodParameters.java:261` 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 (5 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:665 — modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:665-669 | modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:682-686 — 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 (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:80 — eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:80-84 | modelling/src/main/java/org/axonframework/modelling/configuration/SimpleStateBasedEntityModule.java:65-69 — 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:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:88 — eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SimpleEventSourcedEntityModule.java:88-92 | modelling/src/main/java/org/axonframework/modelling/configuration/SimpleStateBasedEntityModule.java:96-100 — 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:88` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (5 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:309 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:309-313 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:324-328 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (5 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:56 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:56-60 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:56-60 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D3 · God Classes · TooManyMethods · ×11
  • TooManyMethods: PooledStreamingEventProcessorConfiguration messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorConfiguration.java:100 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. 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:64 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. 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:89 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. 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. The bar is 30 methods; this is 4 over it, 1.13× the bar. 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. The bar is 30 methods; this is 4 over it, 1.13× the bar. 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: UnitOfWorkProcessingContext messaging/src/main/java/org/axonframework/messaging/core/unitofwork/UnitOfWork.java:206 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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: WorkPackage messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java:89 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. 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: 1 migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:86 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. 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: AnnotatedEntityMetamodel modelling/src/main/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodel.java:108 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×11
  • Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:449 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:449-456 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:469-476 — 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:449` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryBus.java:258 — messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryBus.java:258-265 | messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryBus.java:298-305 — 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/queryhandling/SimpleQueryBus.java:258` 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) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:199 — migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:199-206 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:275-282 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/AddAxonTestFixtureTearDown.java:199` 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 (8 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:312 — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:312-319 | migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:322-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:312` 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) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:130 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:130-137 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:165-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. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:130` 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 (8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:373-380 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:218-225 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (8 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:356 — migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:356-363 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:432-439 — 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:356` 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/core/configuration/MessagingConfigurationDefaults.java:394 — messaging/src/main/java/org/axonframework/messaging/core/configuration/MessagingConfigurationDefaults.java:394-401 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/QueryGatewayConfigurer.java:250-257 — 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 (8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:185 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:185-192 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java:138-145 — before extracting anything, compare `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java` and `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java:121 — update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java:121-128 | update/src/main/java/org/axonframework/update/detection/MachineId.java:82-89 — 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 (8 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyConfiguration.java:10 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/enrollstudent/EnrollStudentInFacultyConfiguration.java:10-17 | examples/university-java/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyConfiguration.java:25-33 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×11
  • Duplicated block (7 lines × 2) examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:290 — examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/InteractiveShell.java:290-296 | update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:136-142 — 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:290` 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) 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `delegate` to `CompletableFuture<? extends MessageStream<M>>` in one and `CompletableFuture<MessageStream.Single<M>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:761 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:761-767 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:548-554 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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:761` 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) common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:178 — common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:178-184 | common/src/main/java/org/axonframework/common/configuration/DecoratorDefinition.java:140-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:178` 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 first that the copies are not typed on the same thing: the declarations holding them bind `handler` to `Consumer<C>` in one and `Consumer<D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:220 — common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:220-226 | common/src/main/java/org/axonframework/common/configuration/DecoratorDefinition.java:170-176 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `common/src/main/java/org/axonframework/common/configuration/ComponentDefinition.java:220` 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 first that the copies are not typed on the same thing: the declarations holding them bind `handler` to `Consumer<C>` in one and `Consumer<D>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:213 — common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:213-219 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:248-254 — 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 (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:217 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:217-223 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java:170-176 — before extracting anything, compare `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java` and `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/commandhandling/configuration/SimpleCommandHandlingModule.java:63 — messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/SimpleCommandHandlingModule.java:63-69 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/SimpleQueryHandlingModule.java:58-64 — 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 (7 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandHandlingComponent.java:61 — messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandHandlingComponent.java:61-67 | messaging/src/main/java/org/axonframework/messaging/queryhandling/interception/InterceptingQueryHandlingComponent.java:61-67 — 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/interception/InterceptingCommandHandlingComponent.java:61` 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 first that the copies are not typed on the same thing: the declarations holding them bind `delegate` to `CommandHandlingComponent` in one and `QueryHandlingComponent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandler.java:126 — examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandler.java:126-132 | examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandler.java:122-128 — before extracting anything, compare `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandler.java` and `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandler.java` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/eventsourced/AppendingPaymentProcess.java:208 — examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/eventsourced/AppendingPaymentProcess.java:208-214 | examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/eventsourced/PaymentProcess.java:197-203 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/eventsourced/AppendingPaymentProcess.java:208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×11
  • 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) messaging/src/main/java/org/axonframework/messaging/core/CloseCallbackMessageStream.java:50 — messaging/src/main/java/org/axonframework/messaging/core/CloseCallbackMessageStream.java:50-55 | messaging/src/main/java/org/axonframework/messaging/tracing/SpanScopedMessageStream.java:61-66 — 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/core/CloseCallbackMessageStream.java:50` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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) messaging/src/main/java/org/axonframework/messaging/core/FlatMappedMessageStream.java:59 — messaging/src/main/java/org/axonframework/messaging/core/FlatMappedMessageStream.java:59-64 | messaging/src/main/java/org/axonframework/messaging/core/MapMultiMessageStream.java:60-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/core/FlatMappedMessageStream.java:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: the declarations holding them bind `mapper` to `Function<? super Entry<M>, ? extends MessageStream<? extends N>>` in one and `BiConsumer<? super Entry<M>, ? super Consumer<Entry<N>>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • 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, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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.
  • Duplicated block (6 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:328 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:328-333 | migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:222-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:328` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:277 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorModule.java:277-282 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorModule.java:212-217 — 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:277` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:100 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:100-105 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java:119-124 — before extracting anything, compare `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java` and `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:77 — modelling/src/main/java/org/axonframework/modelling/entity/annotation/ListEntityChildModelDefinition.java:77-82 | modelling/src/main/java/org/axonframework/modelling/entity/annotation/MapEntityChildModelDefinition.java:75-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanup.java:60 — examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanup.java:60-65 | examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/catalog/transformations/WelcomeMessageBetaCleanupWithoutPreFilter.java:58-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (6 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:37 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:37-42 | examples/university-java/src/main/java/org/axonframework/examples/university/UniversityExampleApplication.java:76-82 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×9
  • Members sharing a duplicated core (4 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:198 — migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:198-212 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:274-296 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:421-439 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:482-500 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:112 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:112-124 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:133-145 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:133-145 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:131-143 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:127 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:127-139 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:148-160 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:148-160 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:146-158 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:142 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:142-162 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:163-183 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:163-183 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:161-181 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:98 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:98-105 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:94-101 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:94-101 | examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:92-99 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:68 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:68-82 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:124-145 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:68-82 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:124-145 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:42 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:42-61 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:58-76 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:42-61 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:58-76 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:47 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:47-68 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentToCourseController.java:47-66 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:47-68 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentToCourseController.java:47-68 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:50 — examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:50-63 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:66-79 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:82-95 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:98-111 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×9
  • Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:254 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:254-263 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:292-301 — 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:254` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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/MigrateCommandGatewayInSagaEventHandler.java:221 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:221-230 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:350-359 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:244 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:244-253 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:388-397 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:244` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:234 — modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:234-243 | modelling/src/main/java/org/axonframework/modelling/entity/PolymorphicEntityMetamodel.java:148-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:234` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:250 — modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:250-259 | modelling/src/main/java/org/axonframework/modelling/entity/PolymorphicEntityMetamodel.java:177-186 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:250` 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/core/SimpleContext.java:72 — messaging/src/main/java/org/axonframework/messaging/core/SimpleContext.java:72-81 | messaging/src/main/java/org/axonframework/messaging/core/SimpleHandlerAttributes.java:84-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/MergeTask.java:94 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/MergeTask.java:94-103 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/SplitTask.java:91-101 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/eventhandling/processing/streaming/pooled/MergeTask.java:94` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GapAwareTrackingToken.java:240 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GapAwareTrackingToken.java:240-249 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GlobalSequenceTrackingToken.java:112-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GapAwareTrackingToken.java:256` calls `hasGaps`, `isEmpty` and `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/GlobalSequenceTrackingToken.java:123` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) REDACTED:68 — REDACTED:68-77 | REDACTED:68-77 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D3 · God Classes · ClassTooLong · ×8
  • ClassTooLong: Coordinator messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:86 — ClassTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 468 over it, 2.17× the bar. 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.
  • ClassTooLong: AddEventTagAnnotation migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:103 — ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 210 over it, 1.53× the bar. 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.
  • ClassTooLong: MigrateCommandGatewayInEventHandler migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:69 — ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. 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.
  • ClassTooLong: MigrateDeadlineManagerBuilders migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:90 — ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 82 over it, 1.21× the bar. 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.
  • ClassTooLong: JdbcTokenStore messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:64 — ClassTooLong — 453 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 53 over it, 1.13× the bar. 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.
  • ClassTooLong: AddAggregateScopeToDeadlineCalls migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:101 — ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. 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.
  • ClassTooLong: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104 — ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. 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.
  • ClassTooLong: MigrateAggregateDeadlineHandler migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:99 — ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 8 over it, 1.02× the bar. 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.
D35 · Change Coupling · Change coupling · ×8
  • Change coupling: MessageStreamUtils.java ↔ SingleValueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MessageStreamUtils.java:1 — `messaging/src/main/java/org/axonframework/messaging/core/MessageStreamUtils.java` and `messaging/src/main/java/org/axonframework/messaging/core/SingleValueMessageStream.java` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `13eabaf7` Added `@Nullable` annotations where relevant; `44615e6f` Added `@Nullable` annotations where relevant; `7ecbe0a4` Added `@Nullable` annotations where relevant — run `git show` on any of them.
  • Change coupling: ConcatenatingMessageStream.java ↔ DelayedMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java:1 — `messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java` change together 56% of the time (9 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `1b1ca6b6` Move static factory methods for reactor types to MessageStreamUtils (… (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java`); `8ab69cfe` [#3459] feat: `MessageStream` - add `peek` method (#3463) (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java`); `c4d9fcc5` Rename asCompletableFuture to firstAsCompletableFuture (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/ConcatenatingMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java`) — run `git show` on any of them.
  • Change coupling: MergedMessageStream.java ↔ SingleValueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java:1 — `messaging/src/main/java/org/axonframework/messaging/core/MergedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/SingleValueMessageStream.java` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7f367c04` fix: provide AbstractMessageStream and implement correct callback beh…; `43a36851` fix: provide AbstractMessageStream and implement correct callback beh…; `58b90dab` fix: provide AbstractMessageStream and implement correct callback beh… — run `git show` on any of them.
  • Change coupling: DelayedMessageStream.java ↔ OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java:1 — `messaging/src/main/java/org/axonframework/messaging/core/DelayedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/core/OnErrorContinueMessageStream.java` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `8ab69cfe` [#3459] feat: `MessageStream` - add `peek` method (#3463) (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/OnErrorContinueMessageStream.java`); `c0d416f3` Resolved comments after PR (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/OnErrorContinueMessageStream.java`); `c4d9fcc5` Rename asCompletableFuture to firstAsCompletableFuture (at that commit the files were still `messaging/src/main/java/org/axonframework/messaging/DelayedMessageStream.java` and `messaging/src/main/java/org/axonframework/messaging/OnErrorContinueMessageStream.java`) — run `git show` on any of them.
  • Change coupling: RetryingCommandBus.java ↔ TracingCommandBus.java messaging/src/main/java/org/axonframework/messaging/commandhandling/retry/RetryingCommandBus.java:1 — `messaging/src/main/java/org/axonframework/messaging/commandhandling/retry/RetryingCommandBus.java` and `messaging/src/main/java/org/axonframework/messaging/commandhandling/tracing/TracingCommandBus.java` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c1bb192c` Ensure right type of command bus is returned from fluent-subscription.. (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/retry/RetryingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`); `5deb2908` Fine tune JavaDoc, indentation, and null checks on components (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/retry/RetryingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`); `980dafa2` Replace CommandBus#subscribe for MessageHandlerRegistry#subscribe (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/retry/RetryingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`) — run `git show` on any of them.
  • Change coupling: InterceptingCommandBus.java ↔ TracingCommandBus.java messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandBus.java:1 — `messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/InterceptingCommandBus.java` and `messaging/src/main/java/org/axonframework/messaging/commandhandling/tracing/TracingCommandBus.java` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d76151b1` Adjust the CommandHandler to return a MessageStream.Single (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/InterceptingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`); `c1bb192c` Ensure right type of command bus is returned from fluent-subscription.. (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/InterceptingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`); `980dafa2` Replace CommandBus#subscribe for MessageHandlerRegistry#subscribe (at that commit the files were still `messaging/src/main/java/org/axonframework/commandhandling/InterceptingCommandBus.java` and `messaging/src/main/java/org/axonframework/commandhandling/tracing/TracingCommandBus.java`) — run `git show` on any of them.
  • Change coupling: EventProcessorProperties.java ↔ SpringCustomizations.java extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/EventProcessorProperties.java:1 — `extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/EventProcessorProperties.java` and `extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringCustomizations.java` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `2d79bc02` Combination of migration improvements; `fc1b3a36` Extend token claims of segments waiting for a worker thread; `917d8031` [#4809] Name the token store bean that was looked for — run `git show` on any of them.
  • Change coupling: SimpleContext.java ↔ SimpleEntry.java messaging/src/main/java/org/axonframework/messaging/core/SimpleContext.java:1 — `messaging/src/main/java/org/axonframework/messaging/core/SimpleContext.java` and `messaging/src/main/java/org/axonframework/messaging/core/SimpleEntry.java` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `248d1516` MessageStream API improvements (at that commit the files were still `messaging/src/main/java/org/axonframework/common/SimpleContext.java` and `messaging/src/main/java/org/axonframework/messaging/SimpleEntry.java`); `c2dbe4af` Remove Context#putAll and Context#asMap since we do not need them (at that commit the files were still `messaging/src/main/java/org/axonframework/common/SimpleContext.java` and `messaging/src/main/java/org/axonframework/messaging/SimpleEntry.java`); `8b6ff3e8` Make the Context immutable and ProcessingContext mutable (at that commit the files were still `messaging/src/main/java/org/axonframework/common/SimpleContext.java` and `messaging/src/main/java/org/axonframework/messaging/SimpleEntry.java`) — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×8
  • Duplicated block (12 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SimpleEntityLifecycleHandler.java:85 — eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SimpleEntityLifecycleHandler.java:85-96 | eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SnapshottingEntityLifecycleHandler.java:137-148 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SimpleEntityLifecycleHandler.java:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SnapshottingEntityLifecycleHandler.java:152` calls `currentTimeMillis` and `eventsourcing/src/main/java/org/axonframework/eventsourcing/handler/SimpleEntityLifecycleHandler.java:100` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:113 — messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:113-124 | messaging/src/main/java/org/axonframework/messaging/core/interception/annotation/MessageHandlerInterceptorDefinition.java:183-194 — 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 (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/TransactionManager.java:82 — messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/TransactionManager.java:82-93 | messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/jpa/EntityManagerTransactionManager.java:114-125 — 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/core/unitofwork/transaction/TransactionManager.java:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/jpa/EntityManagerTransactionManager.java:113` calls `putResource`, `of`, `EntityManagerExecutor` and `messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/TransactionManager.java:80` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:470 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessor.java:470-481 | 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:470` 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/MarkSagaResourceInjection.java:138 — migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:138-149 | migration/src/main/java/org/axonframework/migration/SagaClasses.java:105-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:330 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:330-341 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:408-419 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) common/src/main/java/org/axonframework/common/caching/EhCacheAdapter.java:94 — common/src/main/java/org/axonframework/common/caching/EhCacheAdapter.java:94-105 | common/src/main/java/org/axonframework/common/caching/JCacheAdapter.java:84-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/src/main/java/org/axonframework/common/caching/EhCacheAdapter.java:92` calls `SuppressWarnings` and `common/src/main/java/org/axonframework/common/caching/JCacheAdapter.java:81` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:36 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:36-47 | examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java:52-63 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×8
  • Duplicated block (6 lines × 3) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291 — migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291-300 | migration/src/main/java/org/axonframework/migration/MigrateMessageInterceptorSignatures.java:361-366 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:562-567 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (6 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:140 — migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:140-145 | migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:516-521 | migration/src/main/java/org/axonframework/migration/SagaClasses.java:107-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, 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/MarkSagaResourceInjection.java:140` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:149 — messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:149-154 | messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedEventHandlingComponent.java:271-276 | messaging/src/main/java/org/axonframework/messaging/queryhandling/annotation/AnnotatedQueryHandlingComponent.java:156-161 — 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.
  • Duplicated block (6 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandResultMessage.java:148 — messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandResultMessage.java:148-153 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericQueryResponseMessage.java:156-161 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericSubscriptionQueryUpdateMessage.java:141-146 — 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. 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 × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:59 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:59-64 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:59-64 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:57-62 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:67 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:67-72 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:67-72 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:65-70 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:75 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:75-80 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:75-80 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:73-78 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:83 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:83-88 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:83-88 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:81-86 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D15 · Churn × Complexity Hotspots · Hotspot · ×7
  • 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:767 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CoordinationTask.run at line 767. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245 — migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in 15003.visitClassDeclaration at line 245. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333 — migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in 17091.visitMethodInvocation at line 333. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in 11940.visitClassDeclaration at line 234. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java:73 — messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in MessagingTracingConfigurationEnhancer.enhance at line 73. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingConfigurationEnhancer.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257 — migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in MoveSagaFieldToHandlerParameter.planFor at line 257. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:93 — migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in 1.visitMethodInvocation at line 93. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 09:13:34 +02:00' --until='2026-10-22 09:13:34 +02:00' --full-history --no-merges -- migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×6
  • Swallowed exception (caught, then discarded) extensions/spring/spring/src/main/java/org/axonframework/extension/spring/conversion/avro/SpecificRecordBaseClasspathAvroSchemaLoader.java:76 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:274 — `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:481 — `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:213 — `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) update/src/main/java/org/axonframework/update/api/UpdateCheckResponse.java:158 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D3 · God Classes · FileTooLong · ×5
  • FileTooLong: pooled/Coordinator.java messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java — FileTooLong — 917 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Coordinator (86-1620). The bar is 500 significant lines; this is 417 over it, 1.83× the bar. 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/AddEventTagAnnotation.java migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java — FileTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AddEventTagAnnotation (103-1208). The bar is 500 significant lines; this is 139 over it, 1.28× the bar. 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 — FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: MigrateCommandGatewayInEventHandler (69-836). The bar is 500 significant lines; this is 28 over it, 1.06× the bar. 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/MigrateDeadlineManagerBuilders.java migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java — FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: MigrateDeadlineManagerBuilders (90-821). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. 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: config/SpringComponentRegistry.java extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java — FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: SpringComponentRegistry (104-1009). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×5
  • Duplicated block (15 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:109 — conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:109-123 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:93-107 — before extracting anything, compare `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java` and `conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventstreaming/TagAndTypeFilteredEventCriteria.java:91 — messaging/src/main/java/org/axonframework/messaging/eventstreaming/TagAndTypeFilteredEventCriteria.java:91-105 | messaging/src/main/java/org/axonframework/messaging/eventstreaming/TagFilteredEventCriteria.java:81-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (15 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:19 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java:19-33 | examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java:35-49 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/ConfigurationProperties.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/ConfigurationProperties.java` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:59 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:59-73 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:59-73 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/renamecourse/RenameCourseController.java:59` 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 (15 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentConfiguration.java:9 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentConfiguration.java:9-23 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentConfiguration.java:25-39 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:137 — common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:137-147 | common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java:172-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:206 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:206-216 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:169-179 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:422 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:422-432 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:483-493 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:422` 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 (11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:438 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:438-448 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:414-424 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:438` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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) conversion/src/main/java/org/axonframework/conversion/jackson/ByteArrayToJsonNodeConverter.java:60 — conversion/src/main/java/org/axonframework/conversion/jackson/ByteArrayToJsonNodeConverter.java:60-70 | conversion/src/main/java/org/axonframework/conversion/jackson2/ByteArrayToJsonNodeConverter.java:60-70 — 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. Note first that the copies are not typed on the same thing: `JsonNode` names `com.fasterxml.jackson.databind.JsonNode` in one and `tools.jackson.databind.JsonNode` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D6 · Cohesion (LCOM4) · Low cohesion · ×5
  • Low cohesion: Builder (LCOM4 19) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:417 — Builder's methods fall into 19 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 19 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Builder (LCOM4 14) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/WorkPackage.java:760 — Builder's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Builder (LCOM4 8) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/TokenSchema.java:138 — Builder's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SubscribingEventProcessorConfiguration (LCOM4 7) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorConfiguration.java:52 — SubscribingEventProcessorConfiguration's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Builder (LCOM4 4) extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MessageTimerMonitor.java:136 — Builder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×4
  • Duplicated block (8 lines × 3) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:328 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:328-335 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:1123-1130 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:137-144 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. 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 × 3) 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-67 | examples/university-java/src/main/java/org/axonframework/examples/university/UniversityExampleApplication.java:98-105 | examples/university-message-transformation/src/main/java/org/axonframework/examples/demo/coursecatalog/CourseCatalogApplication.java:72-79 — 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 `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 (8 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:83 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:83-90 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:82-89 | examples/university-java/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:81-88 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/automation/WhenCourseFullyBookedThenSendNotification.java:83` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java:50 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java:50-57 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java:50-57 | examples/university-java/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java:45-52 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityCommandHandler.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:138 — migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:138-144 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:425-431 | migration/src/main/java/org/axonframework/migration/SagaClasses.java:105-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:75 — extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:75-81 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java:70-76 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java:64-70 — 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:75` 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 first that the copies are not typed on the same thing: the declarations holding them bind `dispatchInterceptors` to `List<ReactorMessageDispatchInterceptor<? super CommandMessage>>` in one and `List<ReactorMessageDispatchInterceptor<? super EventMessage>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/CommandMessageHandlerInterceptorChain.java:66 — messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/CommandMessageHandlerInterceptorChain.java:66-72 | messaging/src/main/java/org/axonframework/messaging/eventhandling/interception/EventMessageHandlerInterceptorChain.java:66-72 | messaging/src/main/java/org/axonframework/messaging/queryhandling/interception/QueryMessageHandlerInterceptorChain.java:66-72 — 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.
  • Duplicated block (7 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:157 — messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:157-163 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:148-154 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorsConfigurer.java:145-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 `messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:148` 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 first that the copies are not typed on the same thing: the declarations holding them bind `configureDefaults` to `UnaryOperator<EventProcessorConfiguration>` in one and `UnaryOperator<PooledStreamingEventProcessorConfiguration>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
P8 · Schema migrations · Schema created by Hibernate ddl-auto (no migration path) · ×4
  • Schema created by Hibernate ddl-auto (no migration path) examples/university-java-springboot-3/src/main/resources/application.yml:14 — Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment.
  • Schema created by Hibernate ddl-auto (no migration path) examples/university-java-springboot-4/src/main/resources/application.yml:14 — Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment.
  • Schema created by Hibernate ddl-auto (no migration path) examples/workflow-bike-rental/src/main/resources/application.yaml:24 — Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment.
  • Schema created by Hibernate ddl-auto (no migration path) extensions/spring/spring-boot-compatibility-tests/common/src/main/resources/application.yml:10 — Hibernate ddl-auto builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt Flyway or Liquibase, with `ddl-auto` set to `validate`, so every schema change is a versioned file applied the same way in every environment.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×3
  • Duplicated block (14 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:152 — conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:152-165 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:126-139 — before extracting anything, compare `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java` and `conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:152` 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 first that the copies are not typed on the same thing: `ObjectMapper` names `com.fasterxml.jackson.databind.ObjectMapper` in one and `tools.jackson.databind.ObjectMapper` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:156 — migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:156-169 | migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToStaticMethod.java:109-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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 (14 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:93 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:93-106 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:93-106 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:552 — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:552-564 | migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:158-170 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/SimpleCommandHandlingComponent.java:70 — messaging/src/main/java/org/axonframework/messaging/commandhandling/SimpleCommandHandlingComponent.java:70-82 | messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryHandlingComponent.java:66-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 `messaging/src/main/java/org/axonframework/messaging/commandhandling/SimpleCommandHandlingComponent.java:70` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:58 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/UniversityAxonApplication.java:58-70 | examples/university-java/src/main/java/org/axonframework/examples/university/UniversityExampleApplication.java:96-108 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • Duplicated block (11 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-147 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java:131-141 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java:144-154 — 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 runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: the declarations holding them bind `interceptors` to `List<ReactorMessageDispatchInterceptor<? super CommandMessage>>` in one and `List<ReactorMessageDispatchInterceptor<? super EventMessage>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (11 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:99 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:99-109 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:98-108 | examples/university-java/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java:97-107 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/automation/WhenCourseFullyBookedThenSendNotification.java` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:95 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:95-105 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:95-105 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:93-103 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×3
  • Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:325 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:325-335 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:135-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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:325` 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 (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java:92 — migration/src/main/java/org/axonframework/migration/FlagSerializerBeans.java:92-101 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:270-280 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10–11 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:303 — migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:303-312 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:371-381 — 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:303` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:84 — messaging/src/main/java/org/axonframework/messaging/commandhandling/annotation/AnnotatedCommandHandlingComponent.java:84-92 | messaging/src/main/java/org/axonframework/messaging/eventhandling/annotation/AnnotatedEventHandlingComponent.java:90-98 | messaging/src/main/java/org/axonframework/messaging/queryhandling/annotation/AnnotatedQueryHandlingComponent.java:85-93 — 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/annotation/AnnotatedCommandHandlingComponent.java:84` 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 first that the copies are not typed on the same thing: the declarations holding them bind `converter` to `MessageConverter` in one and `EventConverter` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (9 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:80 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:80-88 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:80-88 | examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:78-86 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:55 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:55-63 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:55-63 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:53-61 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×3
  • Duplicated block (5 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:374 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:374-378 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:447-451 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:219-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, 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:374` 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 (5 lines × 3) messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:141 — messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventProcessingConfigurer.java:141-145 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorsConfigurer.java:128-132 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/subscribing/SubscribingEventProcessorsConfigurer.java:125-129 — 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/eventhandling/configuration/EventProcessingConfigurer.java:141` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `configureDefaults` to `BiFunction<Configuration, EventProcessorConfiguration, EventProcessorConfiguration>` in one and `BiFunction<Configuration, PooledStreamingEventProcessorConfiguration, PooledStreamingEventProcessorConfiguration>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:53 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:53-57 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:53-57 | examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:51-55 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×3
  • Duplicated block (7 lines × 4) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:184 — extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:184-190 | messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultDispatchInterceptorRegistry.java:225-231 | messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java:186-192 | messaging/src/main/java/org/axonframework/messaging/monitoring/configuration/DefaultMessageMonitorRegistry.java:211-217 — before extracting anything, compare `extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java` and `messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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:184` 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 first that the copies are not typed on the same thing: the declarations holding them bind `interceptorDefinition` to `ComponentDefinition<ReactorMessageDispatchInterceptor<? super M>>` in one and `ComponentDefinition<MessageDispatchInterceptor<? super M>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (7 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:99 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:99-105 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:95-101 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:95-101 | examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java:93-99 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentFromCourseCommandHandler.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:58 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:58-64 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:79-85 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:79-85 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:77-83 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` and `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • Duplicated block (17 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:126 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:126-142 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:126-142 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/read/coursestats/controller/CourseStatsController.java:126` 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 (17 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityConfiguration.java:10 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/changecoursecapacity/ChangeCourseCapacityConfiguration.java:10-26 | examples/university-java/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityConfiguration.java:26-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: `CourseId` names `org.axonframework.examples.demo.university.shared.ids.CourseId` in one and `org.axonframework.examples.university.shared.CourseId` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (17 lines × 2) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentConfiguration.java:9 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/unsubscribestudent/UnsubscribeStudentConfiguration.java:9-25 | examples/university-java/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentConfiguration.java:25-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
AX2 · Stateful singletons · Stateful singleton · ×2
  • Stateful singleton: SpringParameterResolverFactoryBean extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/annotation/SpringParameterResolverFactoryBean.java:42 — `SpringParameterResolverFactoryBean` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (factories; e.g. `factories` in `setAdditionalFactories` at line 85).
  • Stateful singleton: SpringComponentRegistry extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:104 — `SpringComponentRegistry` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (disableEnhancerScanning, beanFactory, factories; e.g. `disableEnhancerScanning` in `disableEnhancerScanning` at line 266).
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×2
  • Change-coupling hub: MappedMessageStream.java → ConcatenatingMessageStream.java, EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java — `messaging/src/main/java/org/axonframework/messaging/core/MappedMessageStream.java` changes together with 5 other files — `messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/EmptyMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/FluxMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/OnErrorContinueMessageStream.java` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
  • Change-coupling hub: OnNextMessageStream.java → ConcatenatingMessageStream.java, EmptyMessageStream.java, FailedMessageStream.java, FluxMessageStream.java, OnErrorContinueMessageStream.java messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java — `messaging/src/main/java/org/axonframework/messaging/core/OnNextMessageStream.java` changes together with 5 other files — `messaging/src/main/java/org/axonframework/messaging/core/ConcatenatingMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/EmptyMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/FailedMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/FluxMessageStream.java`, `messaging/src/main/java/org/axonframework/messaging/core/OnErrorContinueMessageStream.java` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (6 members, 50+ identical tokens) messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:155 — messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandMessage.java:155-166 | messaging/src/main/java/org/axonframework/messaging/commandhandling/GenericCommandResultMessage.java:125-136 | messaging/src/main/java/org/axonframework/messaging/core/GenericResultMessage.java:112-123 | messaging/src/main/java/org/axonframework/messaging/eventhandling/GenericEventMessage.java:173-184 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericQueryMessage.java:108-119 | messaging/src/main/java/org/axonframework/messaging/queryhandling/GenericQueryResponseMessage.java:133-144 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:717 — migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:717-730 | migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:220-233 | migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:651-664 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:807-820 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java:307-320 | migration/src/main/java/org/axonframework/migration/StatementTodoMarker.java:112-125 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:55 — messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:55-67 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventDispatchInterceptor.java:52-64 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventHandlerInterceptor.java:53-65 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringQueryHandlerInterceptor.java:55-67 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringSubscriptionQueryUpdateDispatchInterceptor.java:52-64 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:235 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:235-364 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:327-349 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:1122-1139 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:96-170 | migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java:136-161 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:327 — common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:327-351 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:554-578 — 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/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:554` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:551` calls `getBeanNamesForType`, `doRegisterEnhancer`, `getBean` and `common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:326` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135 — conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:135-150 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:109-124 — before extracting anything, compare `conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java` and `conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. Note first that the copies are not typed on the same thing: `JavaType` names `com.fasterxml.jackson.databind.JavaType` in one and `tools.jackson.databind.JavaType` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (16 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:43 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:43-58 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:43-58 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/changecoursecapacity/ChangeCourseCapacityController.java:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:221 — migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:221-229 | migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:652-660 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:808-816 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java:308-316 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
  • Duplicated block (9 lines × 4) examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:55 — examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:55-63 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:71-79 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:87-95 | examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:103-111 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/workflow-bike-rental/src/main/java/org/axonframework/examples/workflow/bikerental/rental/BikeStatusProjector.java:55` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: the declarations holding them bind `event` to `BikeRequestedEvent` in one and `BikeInUseEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStore.java:68 — eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/tracing/TracingEventStore.java:68-115 | messaging/src/main/java/org/axonframework/messaging/eventhandling/tracing/TracingEventBus.java:61-83 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `delegate` to `EventStore` in one and `EventBus` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (23 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java:59 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java:59-81 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java:59-81 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (43 lines × 3) · ×2
  • Duplicated block (43 lines × 3) REDACTED:80 — REDACTED:80-122 | REDACTED:80-122 | REDACTED:53-95 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (43 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/read/coursestats/projection/InMemoryCourseStatsRepository.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×2
  • Duplicated block (12 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:113 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:113-124 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:134-145 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:134-145 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:132-143 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` and `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:128 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:128-139 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:149-160 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:149-160 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:147-158 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` and `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D1 · Cyclomatic Complexity · MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27) · ×1
  • MoveSagaFieldToHandlerParameter.planFor (cyclomatic 27) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257 — MoveSagaFieldToHandlerParameter.planFor has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 15003.visitClassDeclaration (cyclomatic 20) · ×1
  • 15003.visitClassDeclaration (cyclomatic 20) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245 — 15003.visitClassDeclaration has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CoordinationTask.run (cyclomatic 20) · ×1
  • CoordinationTask.run (cyclomatic 20) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:767 — 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.
D1 · Cyclomatic Complexity · 17091.visitMethodInvocation (cyclomatic 19) · ×1
  • 17091.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333 — 17091.visitMethodInvocation has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · 11940.visitClassDeclaration (cyclomatic 19) · ×1
  • 11940.visitClassDeclaration (cyclomatic 19) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234 — 11940.visitClassDeclaration has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · 1.visitMethodInvocation (cyclomatic 19) · ×1
  • 1.visitMethodInvocation (cyclomatic 19) migration/src/main/java/org/axonframework/migration/MigrateAxonTestFixtureFluentApi.java:93 — 1.visitMethodInvocation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · 1.methodsNeedingContext (cyclomatic 18) · ×1
  • 1.methodsNeedingContext (cyclomatic 18) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:154 — 1.methodsNeedingContext has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AddAggregateScopeToDeadlineCalls.commandIdentifier (cyclomatic 17) · ×1
  • AddAggregateScopeToDeadlineCalls.commandIdentifier (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:532 — AddAggregateScopeToDeadlineCalls.commandIdentifier has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Aggregate.of (cyclomatic 17) · ×1
  • Aggregate.of (cyclomatic 17) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:743 — Aggregate.of 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.
D1 · Cyclomatic Complexity · 1.removeGatewayFromConstructors (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · 5.visitMethodInvocation (cyclomatic 16) · ×1
  • 5.visitMethodInvocation (cyclomatic 16) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:738 — 5.visitMethodInvocation 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.
D1 · Cyclomatic Complexity · AvroConverter.convert (cyclomatic 16) · ×1
  • 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, 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.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment integrationtests/src/test/java/org/axonframework/integrationtests/queryhandling/SimpleQueryBusSubscriptionQueryTest.java:52 — //fixme: SimpleQueryBus throws for duplicated subscriptions, how it should work with AxonServer? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · MoveSagaFieldToHandlerParameter.planFor (cognitive 40) · ×1
  • MoveSagaFieldToHandlerParameter.planFor (cognitive 40) migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java:257 — MoveSagaFieldToHandlerParameter.planFor has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 9 (10 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateSnapshotTriggerDefinitionToAnnotation.detectTriggerType (cognitive 37) · ×1
  • 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 11 (32 pts), boolean chains 4, loops 1 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · 1.removeGatewayFromConstructors (cognitive 36) · ×1
  • 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 8 (21 pts), loops 3 (6 pts), ternaries 1 (5 pts), 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.
D2 · Cognitive Complexity · 15003.visitClassDeclaration (cognitive 28) · ×1
  • 15003.visitClassDeclaration (cognitive 28) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:245 — 15003.visitClassDeclaration has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 8, ternaries 2 (5 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AddCommandAnnotation.hasRoutingKeyAttribute (cognitive 27) · ×1
  • 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 8 (22 pts), loops 2 (3 pts), 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.
D2 · Cognitive Complexity · AddEventAnnotation.findRevisionValue (cognitive 27) · ×1
  • 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 7 (23 pts), boolean chains 3, loops 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · 1.removeGatewayFromConstructors (cognitive 27) · ×1
  • 1.removeGatewayFromConstructors (cognitive 27) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:546 — 1.removeGatewayFromConstructors has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 3 (6 pts), 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.
D2 · Cognitive Complexity · 11940.visitClassDeclaration (cognitive 26) · ×1
  • 11940.visitClassDeclaration (cognitive 26) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:234 — 11940.visitClassDeclaration has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 3, loops 2 (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.
D2 · Cognitive Complexity · 1.methodsNeedingContext (cognitive 26) · ×1
  • 1.methodsNeedingContext (cognitive 26) migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:154 — 1.methodsNeedingContext has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 7 (9 pts), boolean chains 5 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CoordinationTask.run (cognitive 26) · ×1
  • CoordinationTask.run (cognitive 26) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:767 — CoordinationTask.run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (18 pts), ternaries 3 (4 pts), 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.
D2 · Cognitive Complexity · Aggregate.of (cognitive 25) · ×1
  • Aggregate.of (cognitive 25) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:743 — Aggregate.of has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 5 (8 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 20014.classFields (cognitive 25) · ×1
  • 20014.classFields (cognitive 25) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:846 — 20014.classFields has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (8 pts), 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.
D2 · Cognitive Complexity · AvroConverter.convert (cognitive 24) · ×1
  • AvroConverter.convert (cognitive 24) conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java:123 — AvroConverter.convert has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · 20014.resolveIndent (cognitive 23) · ×1
  • 20014.resolveIndent (cognitive 23) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:773 — 20014.resolveIndent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (4 pts), 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.
D2 · Cognitive Complexity · 1.unitOfWorkFactoryInScope (cognitive 23) · ×1
  • 1.unitOfWorkFactoryInScope (cognitive 23) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:339 — 1.unitOfWorkFactoryInScope has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AddCommandAnnotation.findFieldName (cognitive 22) · ×1
  • 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 6 (16 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 5.visitMethodInvocation (cognitive 22) · ×1
  • 5.visitMethodInvocation (cognitive 22) migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:738 — 5.visitMethodInvocation has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MigrateSnapshotTriggerDefinitionToAnnotation.isSnapshotTriggerDefinitionMethod (cognitive 21) · ×1
  • 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 8 (16 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 17091.visitMethodInvocation (cognitive 20) · ×1
  • 17091.visitMethodInvocation (cognitive 20) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:333 — 17091.visitMethodInvocation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · 6861.visitAnnotation (cognitive 20) · ×1
  • 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 10 (13 pts), ternaries 4 (7 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SpringUtils.isQualifierMatch (cognitive 20) · ×1
  • SpringUtils.isQualifierMatch (cognitive 20) extensions/spring/spring/src/main/java/org/axonframework/extension/spring/SpringUtils.java:87 — SpringUtils.isQualifierMatch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), 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.
D2 · Cognitive Complexity · JacksonConverter.convert (cognitive 20) · ×1
  • JacksonConverter.convert (cognitive 20) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:107 — JacksonConverter.convert has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), 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.
D2 · Cognitive Complexity · AddAggregateScopeToDeadlineCalls.commandIdentifier (cognitive 19) · ×1
  • AddAggregateScopeToDeadlineCalls.commandIdentifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:532 — AddAggregateScopeToDeadlineCalls.commandIdentifier has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, boolean chains 6, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · AddAggregateScopeToDeadlineCalls.identifier (cognitive 19) · ×1
  • AddAggregateScopeToDeadlineCalls.identifier (cognitive 19) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:664 — AddAggregateScopeToDeadlineCalls.identifier has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 2 (3 pts) (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.
D2 · Cognitive Complexity · MigrateAggregateDeadlineHandler.aggregateTypeOf (cognitive 19) · ×1
  • MigrateAggregateDeadlineHandler.aggregateTypeOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:363 — MigrateAggregateDeadlineHandler.aggregateTypeOf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 3 (7 pts), boolean chains 3, loops 2 (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.
D2 · Cognitive Complexity · MigrateAggregateDeadlineHandler.commandNamesOf (cognitive 19) · ×1
  • MigrateAggregateDeadlineHandler.commandNamesOf (cognitive 19) migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:402 — MigrateAggregateDeadlineHandler.commandNamesOf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Jackson2Converter.convert (cognitive 19) · ×1
  • Jackson2Converter.convert (cognitive 19) conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:91 — Jackson2Converter.convert has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), 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.
D2 · Cognitive Complexity · CoordinationTask.coordinateWorkPackages (cognitive 18) · ×1
  • CoordinationTask.coordinateWorkPackages (cognitive 18) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/Coordinator.java:1343 — CoordinationTask.coordinateWorkPackages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), 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.
D2 · Cognitive Complexity · 1.visitNewClass (cognitive 17) · ×1
  • 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 6 (9 pts), 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.
D2 · Cognitive Complexity · AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable (cognitive 17) · ×1
  • AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable (cognitive 17) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:180 — AnnotationBasedEventSourcedEntityFactory.addEntityCreatorExecutable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), 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.
D2 · Cognitive Complexity · 1.extractClassLiteralType (cognitive 16) · ×1
  • 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 6 (15 pts), boolean chains 1 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (45 shared lines) · ×1
  • Near-duplicate member pair (45 shared lines) conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:108 — conversion/src/main/java/org/axonframework/conversion/jackson/JacksonConverter.java:108-172 | conversion/src/main/java/org/axonframework/conversion/jackson2/Jackson2Converter.java:92-146 — These two members are variants of one another: 45 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Duplicated block (18–21 lines × 2) · ×1
  • Duplicated block (18–21 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:286 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:286-306 | migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java:330-347 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:286` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:402 — common/src/main/java/org/axonframework/common/configuration/DefaultComponentRegistry.java:402-418 | extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringComponentRegistry.java:273-290 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:290 — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:290-307 | migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:1097-1114 — 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:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:69 — common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:69-83 | common/src/main/java/org/axonframework/common/jdbc/ConnectionWrapperFactory.java:103-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:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:149 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:149-163 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:131-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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/MigrateCommandGatewayInSagaEventHandler.java:149` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 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-56 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/RemovedTrackerStatus.java:44-56 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/TrackerStatus.java:261-273 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6–13 lines × 3) · ×1
  • Duplicated block (6–13 lines × 3) extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:131 — extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:131-144 | extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:165-177 | extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:197-202 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java:131` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
D4 · Code Duplication · Duplicated block (9–13 lines × 2) · ×1
  • Duplicated block (9–13 lines × 2) migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291 — migration/src/main/java/org/axonframework/migration/ConfigureEventSourcedAnnotation.java:291-303 | migration/src/main/java/org/axonframework/migration/MigrateSnapshotTriggerDefinitionToAnnotation.java:562-570 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:246 — messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:246-257 | messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:190-200 | messaging/src/main/java/org/axonframework/messaging/queryhandling/configuration/QueryHandlingModule.java:248-259 — 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:246` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `messaging/src/main/java/org/axonframework/messaging/eventhandling/configuration/EventHandlingComponentsConfigurer.java:207` calls `toMap` and `messaging/src/main/java/org/axonframework/messaging/commandhandling/configuration/CommandHandlingModule.java:258` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–12 lines × 2) · ×1
  • Duplicated block (9–12 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:503 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:503-514 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:628-636 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×1
  • Duplicated block (11 lines × 5) messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:57 — messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringCommandHandlerInterceptor.java:57-67 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventDispatchInterceptor.java:54-64 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringEventHandlerInterceptor.java:55-65 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringQueryHandlerInterceptor.java:57-67 | messaging/src/main/java/org/axonframework/messaging/monitoring/interception/MonitoringSubscriptionQueryUpdateDispatchInterceptor.java:54-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, 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/MonitoringCommandHandlerInterceptor.java:57` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: the declarations holding them bind `messageMonitor` to `MessageMonitor<? super CommandMessage>` in one and `MessageMonitor<? super EventMessage>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1
  • Duplicated block (8–10 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:276 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:276-283 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:423-432 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:484-493 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×1
  • Duplicated block (7–10 lines × 2) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:799 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:799-808 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:572-578 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, 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:799` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–10 lines × 3) · ×1
  • Duplicated block (4–10 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:775 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:775-778 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:452-461 | migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java:513-522 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, 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:775` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:386 — eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java:386-394 | messaging/src/main/java/org/axonframework/messaging/core/annotation/MethodInvokingMessageHandlingMember.java:204-210 — 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/core/annotation/MethodInvokingMessageHandlingMember.java:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:582 — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:582-588 | messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenStore.java:622-629 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:721 — migration/src/main/java/org/axonframework/migration/AddAggregateScopeToDeadlineCalls.java:721-726 | migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:224-229 | migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java:655-660 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java:811-816 | migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java:311-316 | migration/src/main/java/org/axonframework/migration/StatementTodoMarker.java:116-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, 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/AddAggregateScopeToDeadlineCalls.java:721` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×1
  • Duplicated block (4–5 lines × 3) migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:510 — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:510-514 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:527-530 | migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:561-565 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:510` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • 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 — before extracting anything, compare `extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java` and `messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `interceptorBuilder` to `ComponentBuilder<ReactorMessageDispatchInterceptor<Message>>` in one and `ComponentBuilder<MessageHandlerInterceptor<Message>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) conversion/src/main/java/org/axonframework/conversion/DelegatingGeneralConverter.java:44 — conversion/src/main/java/org/axonframework/conversion/DelegatingGeneralConverter.java:44-69 | messaging/src/main/java/org/axonframework/messaging/core/conversion/DelegatingMessageConverter.java:45-82 — 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.
D4 · Code Duplication · Duplicated block (63 lines × 2) · ×1
  • Duplicated block (63 lines × 2) conversion/src/main/java/org/axonframework/conversion/jackson/JsonNodeToObjectNodeConverter.java:1 — conversion/src/main/java/org/axonframework/conversion/jackson/JsonNodeToObjectNodeConverter.java:1-63 | conversion/src/main/java/org/axonframework/conversion/jackson2/JsonNodeToObjectNodeConverter.java:1-64 — `conversion/src/main/java/org/axonframework/conversion/jackson/JsonNodeToObjectNodeConverter.java` and `conversion/src/main/java/org/axonframework/conversion/jackson2/JsonNodeToObjectNodeConverter.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 64 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `conversion/src/main/java/org/axonframework/conversion/jackson/JsonNodeToObjectNodeConverter.java:1` 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 first that the copies are not typed on the same thing: `JsonNode` names `com.fasterxml.jackson.databind.JsonNode` in one and `tools.jackson.databind.JsonNode` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (144 lines × 2) · ×1
  • Duplicated block (144 lines × 2) extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/CBORConverterAutoConfiguration.java:1 — extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/CBORConverterAutoConfiguration.java:1-144 | extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/JacksonConverterAutoConfiguration.java:1-161 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/CBORConverterAutoConfiguration.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (59 lines × 2) · ×1
  • Duplicated block (59 lines × 2) messaging/src/main/java/org/axonframework/messaging/commandhandling/CommandExecutionException.java:42 — messaging/src/main/java/org/axonframework/messaging/commandhandling/CommandExecutionException.java:42-101 | messaging/src/main/java/org/axonframework/messaging/queryhandling/QueryExecutionException.java:41-99 — 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/queryhandling/QueryExecutionException.java:41` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:107 — extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:107-111 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:124-128 | extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:141-145 | messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java:107-111 | messaging/src/main/java/org/axonframework/messaging/monitoring/configuration/DefaultMessageMonitorRegistry.java:102-106 — before extracting anything, compare `extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java` and `messaging/src/main/java/org/axonframework/messaging/core/interception/DefaultHandlerInterceptorRegistry.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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:107` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `interceptorBuilder` to `ComponentBuilder<ReactorMessageDispatchInterceptor<? super CommandMessage>>` in one and `ComponentBuilder<ReactorMessageDispatchInterceptor<? super EventMessage>>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java:64 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java:64-87 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java:57-79 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/createcourse/CreateCourseController.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) 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-162 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:166-183 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:166-183 | examples/university-java/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java:164-181 — before extracting anything, compare `examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` and `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseCommandHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: `FacultyTags` names `org.axonframework.examples.demo.university.faculty.FacultyTags` in one and `org.axonframework.examples.university.shared.FacultyTags` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14–16 lines × 4) · ×1
  • Duplicated block (14–16 lines × 4) 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-68 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentToCourseController.java:53-66 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java:53-68 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/unsubscribestudent/UnsubscribeStudentToCourseController.java:53-68 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/subscribestudent/SubscribeStudentToCourseController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `SubscribeStudentToCourseRequest` in one and `UnsubscribeStudentToCourseRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48-61 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:63-76 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java:48-61 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/RenameCourseController.java:63-76 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/changecoursecapacity/ChangeCourseCapacityController.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/changecoursecapacity/ChangeCourseCapacityController.java:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–11 lines × 4) · ×1
  • Duplicated block (10–11 lines × 4) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73-82 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:135-145 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:73-82 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java:135-145 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/controller/CourseStatsController.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/read/coursestats/controller/CourseStatsController.java:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 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-28 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CourseStatsConfiguration.java:48-58 — 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.
D4 · Code Duplication · Duplicated block (116 lines × 2) · ×1
  • Duplicated block (116 lines × 2) examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentcancelledthenrejectrequest/WhenPaymentCancelledThenRejectRequest.java:1 — examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentcancelledthenrejectrequest/WhenPaymentCancelledThenRejectRequest.java:1-116 | examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentrejectedthenrejectrequest/WhenPaymentRejectedThenRejectRequest.java:1-116 — `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentcancelledthenrejectrequest/WhenPaymentCancelledThenRejectRequest.java` and `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentrejectedthenrejectrequest/WhenPaymentRejectedThenRejectRequest.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 116 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `examples/saga-recipes/src/main/java/org/axonframework/examples/sagarecipes/saga/verticalslices/whenpaymentcancelledthenrejectrequest/WhenPaymentCancelledThenRejectRequest.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×1
  • Duplicated block (21 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/InMemoryCourseStatsRepository.java:1 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/faculty/read/coursestats/InMemoryCourseStatsRepository.java:1-21 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java:1-43 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/InMemoryCourseStatsRepository.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/InMemoryCourseStatsRepository.java:1` 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. Note first that the copies are not typed on the same thing: `CourseId` names `org.axonframework.examples.demo.university.shared.ids.CourseId` in one and `org.axonframework.examples.university.shared.CourseId` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (31 lines × 4) · ×1
  • Duplicated block (31 lines × 4) examples/university-demo/src/main/java/org/axonframework/examples/demo/university/shared/ids/CourseId.java:1 — examples/university-demo/src/main/java/org/axonframework/examples/demo/university/shared/ids/CourseId.java:1-31 | examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/shared/CourseId.java:1-55 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/shared/CourseId.java:1-55 | examples/university-java/src/main/java/org/axonframework/examples/university/shared/CourseId.java:1-55 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/shared/CourseId.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/shared/CourseId.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/shared/ids/CourseId.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (41 lines × 3) · ×1
  • Duplicated block (41 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java:1 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java:1-41 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java:1-41 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java:1-41 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java` and `examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStats.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/read/coursestats/projection/CoursesStats.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java:1 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java:1-43 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java:1-43 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjectionConfiguration.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/read/coursestats/projection/CoursesStatsProjectionConfiguration.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java:41 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java:41-56 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java:41-56 | examples/university-java/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java:40-60 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/createcourse/CourseCreation.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (55 lines × 3) · ×1
  • Duplicated block (55 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1-57 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1-57 | examples/university-java/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1-55 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/enrollstudent/EnrollStudentInFacultyCommandHandler.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/enrollstudent/EnrollStudentInFacultyCommandHandler.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java:39 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java:39-59 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java:39-59 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/write/renamecourse/CourseRenaming.java` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:47 — examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:47-56 | examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:47-56 | examples/university-java/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java:45-54 — before extracting anything, compare `examples/university-java-springboot-3/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` and `examples/university-java-springboot-4/src/main/java/org/axonframework/examples/university/read/coursestats/projection/CoursesStatsProjector.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D5 · Coupling · Unstable project axon-spring-boot-starter · ×1
  • Unstable project axon-spring-boot-starter — axon-spring-boot-starter has instability 0.83 with 1 dependents.
IC1 · Incompleteness & stubs · Unfinished stub · ×1
  • Unfinished stub — throws a "not implemented" exception eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/ConsistencyMarkers.java:79 — `position` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Minor — 656 finding(s)
D10 · Test Quality · No direct assertions · ×571
  • No direct assertions: givenPreparedPaymentWhenCancelPaymentThenPaymentCancelled examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:45 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenNoPaymentAtAllWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:115 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyCancelledWhenCancelPaymentAgainThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:98 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyConfirmedWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:64 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyRejectedWhenCancelPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/cancelpayment/CancelPaymentCommandHandlerTest.java:81 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenNoPaymentWhenConfirmPaymentThenRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:56 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPreparedPaymentWhenConfirmPaymentThenPaymentConfirmed examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:40 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyCancelledWhenConfirmPaymentThenIgnoredSilently examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:89 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyConfirmedWhenConfirmPaymentAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/confirmpayment/ConfirmPaymentCommandHandlerTest.java:72 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPaymentAlreadyPreparedWhenPreparePaymentForSameReferenceThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/write/preparepayment/PreparePaymentCommandHandlerTest.java:72 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: paymentContextKnowsNothingAboutRentingOrTheSaga examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/PaymentContextIsolationTest.java:44 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: rentalContextKnowsNothingAboutPaymentOrTheSaga examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/payment/PaymentContextIsolationTest.java:54 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPendingRequestWhenApproveRequestThenBikeInUse examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:51 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenBikeReservedByAnotherRenterWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:107 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenNeverRequestedBikeWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:127 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenRequestAlreadyApprovedWhenApproveRequestAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:71 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenRequestAlreadyRejectedWhenApproveRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/approverequest/ApproveRequestCommandHandlerTest.java:89 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenNoBikeWhenRegisterBikeThenBikeRegistered examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/registerbike/RegisterBikeCommandHandlerTest.java:37 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenRegisteredBikeWhenRegisterBikeAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/registerbike/RegisterBikeCommandHandlerTest.java:52 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenPendingRequestWhenRejectRequestThenRequestRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:46 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenNeverRequestedBikeWhenRejectRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:106 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenRequestAlreadyApprovedWhenRejectRequestThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:88 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenRequestAlreadyRejectedWhenRejectRequestAgainThenNoEventsAndSuccess examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/rejectrequest/RejectRequestCommandHandlerTest.java:66 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenAvailableBikeWhenRequestBikeThenBikeRequested examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/requestbike/RequestBikeCommandHandlerTest.java:48 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: givenUnregisteredBikeWhenRequestBikeThenRejected examples/saga-recipes/src/test/java/org/axonframework/examples/sagarecipes/rental/write/requestbike/RequestBikeCommandHandlerTest.java:64 — No conventional assertion call was detected, and 67 of 80 tests in `saga-recipes` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • + 546 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×24
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:329 — `!APPLY_AF4.matches(invocation) && !APPLY_AF5.matches(invocation)` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java, migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:454 — `!declarations.getVariables().isEmpty() && declarations.getVariables().get(0).getSimpleName().equals(name)` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:135 — `!params.isEmpty() && params.get(0) instanceof J.VariableDeclarations` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java, migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java:113 — `!parentDir.exists() && !parentDir.mkdirs()` appears character-identically in 2 files — update/src/main/java/org/axonframework/update/configuration/PropertyFileUsagePropertyProvider.java, update/src/main/java/org/axonframework/update/detection/MachineId.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java:55 — `Iterable.class.isAssignableFrom(memberValueType) || Map.class.isAssignableFrom(memberValueType)` appears character-identically in 2 files — modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyCommandTargetResolverDefinition.java, modelling/src/main/java/org/axonframework/modelling/entity/annotation/RoutingKeyEventTargetMatcherDefinition.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:152 — `TypeUtils.isOfClassType(ann.getType(), COMMAND_HANDLER_AF4) || TypeUtils.isOfClassType(ann.getType(), COMMAND_HANDLER_AF5)` appears character-identically in 3 files — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java, migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java, migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToStaticMethod.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java:109 — `TypeUtils.isOfClassType(ann.getType(), ESH_AF4) || TypeUtils.isOfClassType(ann.getType(), ESH_AF5)` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java, migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java:162 — `ann.getAnnotationType() instanceof J.Identifier && "CommandHandler".equals( ((J.Identifier) ann.getAnnotationType()).getSimpleName())` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToCompanionObject.java, migration/src/main/java/org/axonframework/migration/ConvertCommandHandlerConstructorToStaticMethod.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:254 — `arguments.size() == 1 && arguments.get(0) instanceof J.Empty` appears character-identically in 3 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java, migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:427 — `declarations.getTypeExpression() == null || declarations.getVariables().isEmpty()` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:372 — `existing.size() == 1 && existing.get(0) instanceof J.Empty` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java, migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java:140 — `fqType != null && !fqType.getFullyQualifiedName().startsWith("org.axonframework")` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddCommandAnnotation.java, migration/src/main/java/org/axonframework/migration/AddEventAnnotation.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java:332 — `invocation.getArguments().isEmpty() || invocation.getArguments().get(0) instanceof J.Empty` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddEventTagAnnotation.java, migration/src/main/java/org/axonframework/migration/ReplaceAggregateLifecycleApply.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:159 — `isCreationalCommand(message) && !isInstanceCommand(message)` appears character-identically in 2 files — modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java, modelling/src/main/java/org/axonframework/modelling/entity/PolymorphicEntityMetamodel.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java:143 — `isInstanceCommand(message) && !isCreationalCommand(message)` appears character-identically in 2 files — modelling/src/main/java/org/axonframework/modelling/entity/ConcreteEntityMetamodel.java, modelling/src/main/java/org/axonframework/modelling/entity/PolymorphicEntityMetamodel.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:298 — `isOwnMethodCall(invocation) && callKeys.contains(callKeyOf(invocation.getSimpleName(), argumentCount(invocation)))` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:290 — `method.getBody() == null || callKeys.isEmpty()` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java:249 — `parameters.size() == 1 && parameters.get(0) instanceof J.Empty` appears character-identically in 3 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateEventGatewayPublishInEventHandler.java, migration/src/main/java/org/axonframework/migration/MoveSagaFieldToHandlerParameter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate common/src/main/java/org/axonframework/common/util/PriorityCallable.java:79 — `priority == that.priority && sequence == that.sequence && Objects.equals(task, that.task)` appears character-identically in 2 files — common/src/main/java/org/axonframework/common/util/PriorityCallable.java, common/src/main/java/org/axonframework/common/util/PriorityRunnable.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java:203 — `this.owner == null || owner.equals(this.owner) || expired(claimTimeout)` appears character-identically in 2 files — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jdbc/JdbcTokenEntry.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/TokenEntry.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java:143 — `token.isPresent() && ReplayToken.isReplay(token.get())` appears character-identically in 2 files — messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/ProcessorEventHandlingComponents.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/replay/ReplayBlockingEventHandlingComponent.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java:214 — `type == null || type instanceof JavaType.Unknown` appears character-identically in 7 files — migration/src/main/java/org/axonframework/migration/MarkSagaResourceInjection.java, migration/src/main/java/org/axonframework/migration/MigrateAggregateDeadlineHandler.java, migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerBuilders.java, migration/src/main/java/org/axonframework/migration/MigrateDeadlineManagerConfiguration.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java:831 — `variable instanceof J.Identifier && ((J.Identifier) variable).getSimpleName().equals(fieldName)` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java, migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInSagaEventHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java:204 — `vd.getTypeExpression() == null || vd.getVariables().isEmpty()` appears character-identically in 2 files — migration/src/main/java/org/axonframework/migration/AddAxonTestFixtureTearDown.java, migration/src/main/java/org/axonframework/migration/MigrateCommandGatewayInEventHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
IC1 · Incompleteness & stubs · Disabled test · ×17
  • Disabled test common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:668 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test common/src/test/java/org/axonframework/common/configuration/ApplicationConfigurerTestSuite.java:699 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test eventsourcing/src/test/java/org/axonframework/eventsourcing/eventstore/StorageEngineBackedEventStoreTestSuite.java:249 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/AxonHandlerConfigurationTest.java:49 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:73 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:97 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/InterceptorAutoConfigurationTest.java:122 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test extensions/spring/spring-boot-autoconfigure/src/test/java/org/axonframework/extension/springboot/autoconfig/RepositoryWiringTest.java:40 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/core/ConcatenatingMessageStreamTest.java:126 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/core/OnErrorContinueMessageStreamTest.java:68 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/core/annotation/AnnotatedHandlerAttributesTest.java:143 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/core/interception/ExceptionHandlerTest.java:141 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/eventhandling/processing/streaming/pooled/PooledStreamingEventProcessorTest.java:613 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/FutureAsResponseTypeToQueryHandlersTest.java:140 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/FutureAsResponseTypeToQueryHandlersTest.java:154 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test messaging/src/test/java/org/axonframework/messaging/queryhandling/annotation/InterceptingAnnotatedQueryHandlingComponentTest.java:51 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test modelling/src/test/java/org/axonframework/modelling/entity/annotation/AnnotatedEntityMetamodelCommandHandlerInheritanceTest.java:114 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D34 · Knowledge Freshness · Orphaned file · ×13
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorRegistry.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/DefaultReactorDispatchInterceptorRegistry.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/DefaultReactorCommandGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/DefaultReactorQueryGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/queryhandling/gateway/ReactorQueryGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/DefaultReactorEventGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/autoconfig/ReactorAutoConfiguration.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/configuration/ReactorConfigurationDefaults.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/jpa/JpaTokenStoreConfiguration.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/commandhandling/gateway/ReactorCommandGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/eventhandling/gateway/ReactorEventGateway.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/spring/spring/src/main/java/org/axonframework/extension/spring/data/JacksonPageDeserializer.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file extensions/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/interception/ReactorDispatchInterceptorFactory.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
M4 · Documentation accuracy · README/code drift · ×12
  • README/code drift README.md:1 — Axon Framework README claims AxonIQ code-samples repo but the evidence shows a separate AxonIQ/hotel-demo project — searched for: `code-samples`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift README.md:32 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift docs/README.md:49 — docs/README.md names `antory.yml`, but no file or folder `antory.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/ROOT/pages/conversion.adoc:214 — docs/reference-guide/modules/ROOT/pages/conversion.adoc documents the environment variable `ALLOW_FINAL_FIELDS_AS_MUTATORS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/configuration/pages/spring.adoc:194 — docs/reference-guide/modules/configuration/pages/spring.adoc names `module-info.java`, but no file or folder `module-info.java` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/messaging-concepts/pages/anatomy-message.adoc:75 — docs/reference-guide/modules/messaging-concepts/pages/anatomy-message.adoc names `module-info.java`, but no file or folder `module-info.java` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:93 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `org.axonframework.config`, but no file or folder `org.axonframework.config` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:251 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring`, but no file or folder `extensions/axon-spring` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:255 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring-boot-autoconfigure`, but no file or folder `extensions/axon-spring-boot-autoconfigure` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:259 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-spring-boot-starter`, but no file or folder `extensions/axon-spring-boot-starter` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:263 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-metrics-dropwizard`, but no file or folder `extensions/axon-metrics-dropwizard` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference-guide/modules/migration/pages/paths/index.adoc:267 — docs/reference-guide/modules/migration/pages/paths/index.adoc names `extensions/axon-metrics-micrometer`, but no file or folder `extensions/axon-metrics-micrometer` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D16 · Bus Factor · Off-boarding risk · ×6
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 47 significant file(s) lose their only recent owner: eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/AggregateBasedJpaEventStorageEngineConfiguration.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryBus.java, extensions/spring/spring/src/main/java/org/axonframework/extension/spring/config/SpringEventSourcedEntityLookup.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/QueryBus.java, messaging/src/main/java/org/axonframework/messaging/core/HandlerExecutionException.java, messaging/src/main/java/org/axonframework/messaging/core/Message.java, extensions/metrics/metrics-micrometer/src/main/java/org/axonframework/extension/metrics/micrometer/MetricsConfigurationEnhancer.java, messaging/src/main/java/org/axonframework/messaging/queryhandling/SimpleQueryUpdateEmitter.java (+39 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 41 significant file(s) lose their only recent owner: migration/src/main/java/org/axonframework/migration/MigrateSagaLifecycle.java, extensions/spring/spring-boot-autoconfigure/src/main/java/org/axonframework/extension/springboot/TracingProperties.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/ReplaceAggregateLifecycleApply.java, migration/src/main/java/org/axonframework/migration/AddEntityCreatorAnnotation.java, messaging/src/main/java/org/axonframework/messaging/tracing/configuration/MessagingTracingSettings.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/tracing/TracingEventHandlingComponent.java (+33 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 6 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/core/unitofwork/transaction/TransactionalExecutorProvider.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/EventCoordinator.java, common/src/main/java/org/axonframework/common/jpa/EntityManagerExecutor.java, common/src/main/java/org/axonframework/common/jdbc/ConnectionExecutor.java, common/src/main/java/org/axonframework/common/configuration/DecoratingComponent.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, 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 #5 — If anonymized user #5 becomes unavailable, 6 significant file(s) lose their only recent owner: messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/progress/SegmentProgressStrategy.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/progress/SegmentProgressContext.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/segmenting/annotation/SegmentParameterResolverFactory.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/progress/TokenStoringProgressStrategy.java, messaging/src/main/java/org/axonframework/messaging/commandhandling/CommandHandlingExceptionHandler.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/progress/SegmentProgressStrategyFactory.java. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: conversion/src/main/java/org/axonframework/conversion/avro/AvroConverter.java, conversion/src/main/java/org/axonframework/conversion/avro/SpecificRecordBaseConverterStrategy.java, conversion/src/main/java/org/axonframework/conversion/avro/AvroConverterStrategy.java. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 5 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 (119 single-owned of 698 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 698 of the 1161 production source files in this repository met that bar). They are anonymized user #7 (3 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (1 file(s)), anonymized user #11 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: messaging/src/main/java/org/axonframework/messaging/commandhandling/gateway/CommandGateway.java, messaging/src/main/java/org/axonframework/messaging/commandhandling/interception/CommandSequencingInterceptor.java, messaging/src/main/java/org/axonframework/messaging/core/sequencing/ExtractionSequencingPolicy.java, messaging/src/main/java/org/axonframework/messaging/eventhandling/processing/streaming/token/store/LegacyTokenTypes.java, eventsourcing/src/main/java/org/axonframework/eventsourcing/configuration/SnapshotSourcingConfigurationEnhancer.java, messaging/src/main/java/org/axonframework/messaging/core/SimpleVersionedType.java, messaging/src/main/java/org/axonframework/messaging/core/VersionedType.java, modelling/src/main/java/org/axonframework/modelling/entity/child/ChildEntityFieldDefinition.java (+1 more).
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no project overview docs/CLAUDE.md — The project overview states 'This directory contains the Axon Framework 5 Getting Started Guide', but it never explains what the guide itself does or what the Axon University Registration Application is about. Add a one-paragraph overview of the tutorial's purpose and the Axon University registration application it builds.
D26 · Project Cohesion · Split messaging · ×1
  • Split messaging — The messaging project is huge at 57k LoC and sprawls across 65 namespaces, far exceeding both size and spread thresholds. Suggested: split into messaging/core, queryhandling, commandhandling, eventhandling with the listed core/annotation/processing/streaming/segmenting namespaces
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 13 of 698 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 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 698 of the 1161 production source files in this repository met that bar). 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 — most significant first: 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, 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/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/reactor/axon-reactor/src/main/java/org/axonframework/extension/reactor/messaging/core/configuration/ReactorConfigurationDefaults.java (and 5 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 1045/1386 types (75%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 8/10 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `docs/_playbook`, `extensions/spring/spring-boot-compatibility-tests/common`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 33781 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — 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.)
X4 · Structured logging · Interpolated log message defeats structured logging · ×1
  • Interpolated log message defeats structured logging eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/jpa/JpaPollingEventCoordinator.java:138 — `info` at line 138 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 144/145 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch update/src/main/java/org/axonframework/update/detection/KotlinVersion.java:49 — `detect` swallows every exception into `return "none"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
Minor — 4 finding(s)
D10 · Test Quality · Skipped (documented) · ×4
  • Skipped (documented): nextThenMapTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:226 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): nextThenReduceTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:217 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): peekThenMapTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:235 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
  • Skipped (documented): peekThenReduceTest messaging/src/test/java/org/axonframework/messaging/core/MessageStreamTestSuite.java:244 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a1a98779d8034e0c9973998388e8755f/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a1a98779d8034e0c9973998388e8755f/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .51artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 14 file(s) — `common/src/main/java/org/axonframework/common/ReflectionUtils.java`, `common/src/main/java/org/axonframework/common/infra/FilesystemStyleComponentDescriptor.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/annotation/reflection/AnnotationBasedEventSourcedEntityFactory.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/AggregateSequenceNumberPosition.java`, `eventsourcing/src/main/java/org/axonframework/eventsourcing/eventstore/DefaultSourcingCondition.java`, … (+9 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0—

Run 01a164e2-188d-701b-82b7-fd0631a3eaaf · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 45 · Warnings: 520 · Recommendations: 656 · Info: 4 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 18: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.

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