Executive summary
bertilmuth/requirementsascode falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100 and is rated Adequate, and its one critical finding doesn't concern security.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 5 points. Adopting a logging library would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 65.
Referring to the other business object by its identifier would take care of the business object holding another business object directly.
The product code is 6,291 lines, about €14,000 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 51 to about 65.
Fixed since the last survey: 75 findings
- Test Quality · No assertions: actorDoesnReactIfActorInModelIsDifferent requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: actorReactsIfActorInModelMatches requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: actorReactsIfActorInModelMatchesForSecondEvent requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: actorReactsToEvent requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: actorReactsToFulfilledCondition requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: actorReactsToTwoEvents requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: customActorReactsToFulfilledCondition requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: twoActorsInteract requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: twoActorsInteractWhenSourceActorIsSpecifiedInTargetStepAs requirementsascodecore/src/test/java/org/requirementsascode/ActorWithBehaviorTest.java
- Test Quality · No assertions: doesNotHandleExceptionIfNoExceptionOccurs requirementsascodecore/src/test/java/org/requirementsascode/ExceptionHandlingTest.java
- Test Quality · No assertions: doesNotHandleExceptionIfSystemReactionDoesNotThrowException requirementsascodecore/src/test/java/org/requirementsascode/ExceptionHandlingTest.java
- Test Quality · No assertions: handlesExceptionAtAnyTime requirementsascodecore/src/test/java/org/requirementsascode/ExceptionHandlingTest.java
- Test Quality · No assertions: continuesAfterCalledFromFirstStepOfAlternativeFlowWithRightActor requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAfterCalledFromMultipleMutuallyExclusiveAlternativeFlows requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAfterCalledFromSecondStepOfAlternativeFlow requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAfterNotCalledWhenActorIsWrong requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAfterSecondStepCalledFromFirstStepOfAlternativeFlowWithoutEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtCalledFromFirstStepOfAlternativeFlowWithRightActor requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtCalledFromMultipleMutuallyExclusiveAlternativeFlows requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtCalledFromSecondStepOfAlternativeFlow requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtFirstStepCalledFromFirstStepOfAlternativeFlowWithEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtFirstStepCalledFromFirstStepOfAlternativeFlowWithoutEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtNotCalledWhenActorIsWrong requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtThirdStepCalledFromFirstStepOfAlternativeFlowWithEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesAtThirdStepCalledFromFirstStepOfAlternativeFlowWithoutEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continuesWithPreferredFlow requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesNotReactToAlreadyRunStep requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesNotReactToEmptyCommands requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesNotReactWhileConditionNotFulfilled requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesNotReenterAlternativeFlowEvenIfItHasTrueCondition requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntContinueAtFirstStepCalledFromFirstStepOfAlternativeFlowWithWrongEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntContinueAtThirdStepCalledFromFirstStepOfAlternativeFlowWithWrongEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntContinueWithIgnoredFlowIfConditionFalse requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntContinueWithIgnoredFlowIfItIsAnAfterFlow requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntPrintsTextAutonomouslyForActorCalledSystem requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: doesntReactWhenDefaultActorIsWrong requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: interruptsReactWhileAfter requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: interruptsReactWhileBefore requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: oneStepInFlowReactsWithConstantText requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: oneStepInFlowReactsWithConstantTextWhenModelIsRebuiltAndRerun requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: oneStepInFlowReactsWithEnteredText requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: onlyStepWithTrueConditionReacts requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: printsTextAutonomously requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: printsTextAutonomouslyOnlyIfActorIsRightInFirstStep requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: printsTextAutonomouslyOnlyIfActorIsRightInSecondStep requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: printsTextAutonomouslyTwice requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactToStepOnce requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactToStepThreeTimes requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactToStepTwice requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactsToAlternativeAfterFirstStep requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactsToAlternativeOfAlternative requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactsToFirstStepAlternativeWhen requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: reactsToSecondStepAlternativeWhen requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: startsOneOfTwoParallelUseCasesByDifferentEvent requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: startsTwoUseCasesSequentially requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: stepThasHasTrueConditionReactsEvenIfOtherStepWouldBePerformedBySystem requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactOnlyWhenActorIsRight requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactToEventsOfDifferentType requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactToEventsOfDifferentTypeAsList requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactToEventsOfSameType requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactToEventsOfSameTypeAsList requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenActorIsChanged requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenDefaultActorIsRight requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenNoActorHasBeenSpecified requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenRunningWithDifferentActors requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenSeveralActorsContainRightActorAtFirstPosition requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactWhenSeveralActorsContainRightActorAtSecondPosition requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoSequentialStepsReactyOnlyWhenActorHasSameName requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoStepReactWhenFirstStepPublishesTwoEventsAsArray requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: twoStepReactWhenFirstStepPublishesTwoEventsAsCollection requirementsascodecore/src/test/java/org/requirementsascode/FlowTest.java
- Test Quality · No assertions: continueRecordingAfterRestart requirementsascodecore/src/test/java/org/requirementsascode/RecordingTest.java
- Test Quality · No assertions: recordIsEmptyForFreshlyRunModel requirementsascodecore/src/test/java/org/requirementsascode/RecordingTest.java
- Test Quality · No assertions: recordMultipleEvents requirementsascodecore/src/test/java/org/requirementsascode/RecordingTest.java
- Test Quality · No assertions: recordMultipleEvents_startRecordingAfterRunning requirementsascodecore/src/test/java/org/requirementsascode/RecordingTest.java
- Test Quality · No assertions: recordSingleEvent requirementsascodecore/src/test/java/org/requirementsascode/RecordingTest.java
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 77 to 243 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, 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.7 at a score of 51. 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. |
| Size | Small: 6,291 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 creditcard_eventsourcing.model.command | 2 creditcard_eventsourcing.model.event | 3 helloworld.command | 4 helloworld.domain | 5 helloworld.infrastructure | 6 message | 7 org.requirementsascode.queue | 8 pizzavolumecalculator.actor.command | 9 creditcard_eventsourcing.persistence | 10 helloworld.commandhandler | 11 org.requirementsascode.flowposition | 12 pizzavolumecalculator.console | 13 creditcard_eventsourcing | 14 org.requirementsascode.builder | 15 org.requirementsascode | 16 actor | 17 akka | 18 cleanarchitecture | 19 creditcard_eventsourcing.model | 20 crosscuttingconcerns | 21 helloworld | 22 helloworld.actor | 23 org.requirementsascode.exception | 24 org.requirementsascode.extract.freemarker | 25 org.requirementsascode.extract.freemarker.methodmodel | 26 org.requirementsascode.extract.freemarker.methodmodel.util | 27 org.requirementsascode.systemreaction | 28 pizzavolumecalculator.actor | 29 creditcard_eventsourcing.controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 creditcard_eventsourcing.model.command | |||||||||||||||||||||||||||||
| 2 creditcard_eventsourcing.model.event | |||||||||||||||||||||||||||||
| 3 helloworld.command | |||||||||||||||||||||||||||||
| 4 helloworld.domain | |||||||||||||||||||||||||||||
| 5 helloworld.infrastructure | |||||||||||||||||||||||||||||
| 6 message | |||||||||||||||||||||||||||||
| 7 org.requirementsascode.queue | |||||||||||||||||||||||||||||
| 8 pizzavolumecalculator.actor.command | |||||||||||||||||||||||||||||
| 9 creditcard_eventsourcing.persistence | 1 | ||||||||||||||||||||||||||||
| 10 helloworld.commandhandler | 3 | 4 | 4 | ||||||||||||||||||||||||||
| 11 org.requirementsascode.flowposition | 12 | ||||||||||||||||||||||||||||
| 12 pizzavolumecalculator.console | 2 | ||||||||||||||||||||||||||||
| 13 creditcard_eventsourcing | 1 | ||||||||||||||||||||||||||||
| 14 org.requirementsascode.builder | 3 | 42 | |||||||||||||||||||||||||||
| 15 org.requirementsascode | 4 | 1 | |||||||||||||||||||||||||||
| 16 actor | 4 | 6 | |||||||||||||||||||||||||||
| 17 akka | 2 | ||||||||||||||||||||||||||||
| 18 cleanarchitecture | 2 | ||||||||||||||||||||||||||||
| 19 creditcard_eventsourcing.model | 4 | 2 | 1 | 7 | |||||||||||||||||||||||||
| 20 crosscuttingconcerns | 3 | ||||||||||||||||||||||||||||
| 21 helloworld | 5 | 22 | |||||||||||||||||||||||||||
| 22 helloworld.actor | 6 | ||||||||||||||||||||||||||||
| 23 org.requirementsascode.exception | 3 | ||||||||||||||||||||||||||||
| 24 org.requirementsascode.extract.freemarker | 1 | ||||||||||||||||||||||||||||
| 25 org.requirementsascode.extract.freemarker.methodmodel | 1 | 8 | |||||||||||||||||||||||||||
| 26 org.requirementsascode.extract.freemarker.methodmodel.util | 3 | ||||||||||||||||||||||||||||
| 27 org.requirementsascode.systemreaction | 5 | ||||||||||||||||||||||||||||
| 28 pizzavolumecalculator.actor | 2 | 3 | |||||||||||||||||||||||||||
| 29 creditcard_eventsourcing.controller | 1 | 1 |
9→2 creditcard_eventsourcing.persistence uses creditcard_eventsourcing.model.event✕
- Connections
- 1 pair of types, where a type in creditcard_eventsourcing.persistence uses a type in creditcard_eventsourcing.model.event.
- The types involved
creditcard_eventsourcing.persistence.EventStore→creditcard_eventsourcing.model.event.DomainEvent
- Direction
- creditcard_eventsourcing.persistence uses creditcard_eventsourcing.model.event, so a change to creditcard_eventsourcing.model.event can break creditcard_eventsourcing.persistence, while a change to creditcard_eventsourcing.persistence can't break creditcard_eventsourcing.model.event.
- Position
- Below the diagonal: creditcard_eventsourcing.persistence uses a module listed above it, which is the healthy direction.
10→3 helloworld.commandhandler uses helloworld.command✕
- Connections
- 3 pairs of types, where a type in helloworld.commandhandler uses a type in helloworld.command.
- The types involved
helloworld.commandhandler.GreetWithEnteredName→helloworld.command.EnterTexthelloworld.commandhandler.SaveAge→helloworld.command.EnterTexthelloworld.commandhandler.SaveName→helloworld.command.EnterText
- Direction
- helloworld.commandhandler uses helloworld.command, so a change to helloworld.command can break helloworld.commandhandler, while a change to helloworld.commandhandler can't break helloworld.command.
- Position
- Below the diagonal: helloworld.commandhandler uses a module listed above it, which is the healthy direction.
10→4 helloworld.commandhandler uses helloworld.domain✕
- Connections
- 4 pairs of types, where a type in helloworld.commandhandler uses a type in helloworld.domain.
- The types involved
helloworld.commandhandler.GreetPersonWithAge→helloworld.domain.Personhelloworld.commandhandler.GreetPersonWithName→helloworld.domain.Personhelloworld.commandhandler.SaveAge→helloworld.domain.Personhelloworld.commandhandler.SaveName→helloworld.domain.Person
- Direction
- helloworld.commandhandler uses helloworld.domain, so a change to helloworld.domain can break helloworld.commandhandler, while a change to helloworld.commandhandler can't break helloworld.domain.
- Position
- Below the diagonal: helloworld.commandhandler uses a module listed above it, which is the healthy direction.
10→5 helloworld.commandhandler uses helloworld.infrastructure✕
- Connections
- 4 pairs of types, where a type in helloworld.commandhandler uses a type in helloworld.infrastructure.
- The types involved
helloworld.commandhandler.GreetPersonWithAge→helloworld.infrastructure.OutputAdapterhelloworld.commandhandler.GreetPersonWithName→helloworld.infrastructure.OutputAdapterhelloworld.commandhandler.GreetWithDefaultName→helloworld.infrastructure.OutputAdapterhelloworld.commandhandler.GreetWithEnteredName→helloworld.infrastructure.OutputAdapter
- Direction
- helloworld.commandhandler uses helloworld.infrastructure, so a change to helloworld.infrastructure can break helloworld.commandhandler, while a change to helloworld.commandhandler can't break helloworld.infrastructure.
- Position
- Below the diagonal: helloworld.commandhandler uses a module listed above it, which is the healthy direction.
11→15 org.requirementsascode.flowposition uses org.requirementsascode part of a loop✕
- Connections
- 12 pairs of types, where a type in org.requirementsascode.flowposition uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.flowposition.After→org.requirementsascode.FlowSteporg.requirementsascode.flowposition.After→org.requirementsascode.ModelRunnerorg.requirementsascode.flowposition.After→org.requirementsascode.UseCaseorg.requirementsascode.flowposition.AfterSingleStep→org.requirementsascode.FlowSteporg.requirementsascode.flowposition.AfterSingleStep→org.requirementsascode.ModelRunnerorg.requirementsascode.flowposition.AfterSingleStep→org.requirementsascode.UseCaseorg.requirementsascode.flowposition.Anytime→org.requirementsascode.ModelRunnerorg.requirementsascode.flowposition.FlowPosition→org.requirementsascode.ModelRunnerorg.requirementsascode.flowposition.FlowPosition→org.requirementsascode.UseCaseorg.requirementsascode.flowposition.InsteadOf→org.requirementsascode.FlowSteporg.requirementsascode.flowposition.InsteadOf→org.requirementsascode.ModelRunnerorg.requirementsascode.flowposition.InsteadOf→org.requirementsascode.UseCase
- Direction
- org.requirementsascode.flowposition uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.flowposition, while a change to org.requirementsascode.flowposition can't break org.requirementsascode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→8 pizzavolumecalculator.console uses pizzavolumecalculator.actor.command✕
- Connections
- 2 pairs of types, where a type in pizzavolumecalculator.console uses a type in pizzavolumecalculator.actor.command.
- The types involved
pizzavolumecalculator.console.PizzaVolumeCalculatorConsole→pizzavolumecalculator.actor.command.EnterHeightpizzavolumecalculator.console.PizzaVolumeCalculatorConsole→pizzavolumecalculator.actor.command.EnterRadius
- Direction
- pizzavolumecalculator.console uses pizzavolumecalculator.actor.command, so a change to pizzavolumecalculator.actor.command can break pizzavolumecalculator.console, while a change to pizzavolumecalculator.console can't break pizzavolumecalculator.actor.command.
- Position
- Below the diagonal: pizzavolumecalculator.console uses a module listed above it, which is the healthy direction.
13→9 creditcard_eventsourcing uses creditcard_eventsourcing.persistence✕
- Connections
- 1 pair of types, where a type in creditcard_eventsourcing uses a type in creditcard_eventsourcing.persistence.
- The types involved
creditcard_eventsourcing.EventsourcingApplication→creditcard_eventsourcing.persistence.EventStore
- Direction
- creditcard_eventsourcing uses creditcard_eventsourcing.persistence, so a change to creditcard_eventsourcing.persistence can break creditcard_eventsourcing, while a change to creditcard_eventsourcing can't break creditcard_eventsourcing.persistence.
- Position
- Below the diagonal: creditcard_eventsourcing uses a module listed above it, which is the healthy direction.
14→11 org.requirementsascode.builder uses org.requirementsascode.flowposition✕
- Connections
- 3 pairs of types, where a type in org.requirementsascode.builder uses a type in org.requirementsascode.flowposition.
- The types involved
org.requirementsascode.builder.FlowConditionPart→org.requirementsascode.flowposition.FlowPositionorg.requirementsascode.builder.FlowPositionPart→org.requirementsascode.flowposition.FlowPositionorg.requirementsascode.builder.StepPart→org.requirementsascode.flowposition.FlowPosition
- Direction
- org.requirementsascode.builder uses org.requirementsascode.flowposition, so a change to org.requirementsascode.flowposition can break org.requirementsascode.builder, while a change to org.requirementsascode.builder can't break org.requirementsascode.flowposition.
- Position
- Below the diagonal: org.requirementsascode.builder uses a module listed above it, which is the healthy direction.
14→15 org.requirementsascode.builder uses org.requirementsascode part of a loop✕
- Connections
- 42 pairs of types, where a type in org.requirementsascode.builder uses a type in org.requirementsascode. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
org.requirementsascode.builder.FlowConditionPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowPart→org.requirementsascode.Floworg.requirementsascode.builder.FlowPart→org.requirementsascode.UseCaseorg.requirementsascode.builder.FlowPositionPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowlessConditionPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowlessConditionPart→org.requirementsascode.ModelRunnerorg.requirementsascode.builder.FlowlessStepPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowlessStepPart→org.requirementsascode.ModelRunnerorg.requirementsascode.builder.FlowlessSystemPart→org.requirementsascode.Behaviororg.requirementsascode.builder.FlowlessSystemPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowlessSystemPart→org.requirementsascode.Modelorg.requirementsascode.builder.FlowlessToPart→org.requirementsascode.Behaviororg.requirementsascode.builder.FlowlessToPart→org.requirementsascode.Conditionorg.requirementsascode.builder.FlowlessToPart→org.requirementsascode.Modelorg.requirementsascode.builder.FlowlessUseCasePart→org.requirementsascode.Conditionorg.requirementsascode.builder.ModelBuilder→org.requirementsascode.Conditionorg.requirementsascode.builder.ModelBuilder→org.requirementsascode.Modelorg.requirementsascode.builder.StepAsPart→org.requirementsascode.AbstractActororg.requirementsascode.builder.StepAsPart→org.requirementsascode.ModelRunnerorg.requirementsascode.builder.StepAsPart→org.requirementsascode.Steporg.requirementsascode.builder.StepConditionPart→org.requirementsascode.Conditionorg.requirementsascode.builder.StepInCasePart→org.requirementsascode.Conditionorg.requirementsascode.builder.StepPart→org.requirementsascode.AbstractActororg.requirementsascode.builder.StepPart→org.requirementsascode.Condition
- Direction
- org.requirementsascode.builder uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.builder, while a change to org.requirementsascode.builder can't break org.requirementsascode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→11 org.requirementsascode uses org.requirementsascode.flowposition✕
- Connections
- 4 pairs of types, where a type in org.requirementsascode uses a type in org.requirementsascode.flowposition.
- The types involved
org.requirementsascode.Flow→org.requirementsascode.flowposition.FlowPositionorg.requirementsascode.FlowStep→org.requirementsascode.flowposition.FlowPositionorg.requirementsascode.InterruptingFlowStep→org.requirementsascode.flowposition.FlowPositionorg.requirementsascode.UseCase→org.requirementsascode.flowposition.FlowPosition
- Direction
- org.requirementsascode uses org.requirementsascode.flowposition, so a change to org.requirementsascode.flowposition can break org.requirementsascode, while a change to org.requirementsascode can't break org.requirementsascode.flowposition.
- Position
- Below the diagonal: org.requirementsascode uses a module listed above it, which is the healthy direction.
15→14 org.requirementsascode uses org.requirementsascode.builder✕
- Connections
- 1 pair of types, where a type in org.requirementsascode uses a type in org.requirementsascode.builder.
- The types involved
org.requirementsascode.Model→org.requirementsascode.builder.ModelBuilder
- Direction
- org.requirementsascode uses org.requirementsascode.builder, so a change to org.requirementsascode.builder can break org.requirementsascode, while a change to org.requirementsascode can't break org.requirementsascode.builder.
- Position
- Below the diagonal: org.requirementsascode uses a module listed above it, which is the healthy direction.
16→6 actor uses message✕
- Connections
- 4 pairs of types, where a type in actor uses a type in message.
- The types involved
actor.MessageConsumer→message.NameEnteredactor.MessageProducer→message.EnterNameactor.MessageProducer→message.NameEnteredactor.PublishingActor→message.EnterName
- Direction
- actor uses message, so a change to message can break actor, while a change to actor can't break message.
- Position
- Below the diagonal: actor uses a module listed above it, which is the healthy direction.
16→15 actor uses org.requirementsascode✕
- Connections
- 6 pairs of types, where a type in actor uses a type in org.requirementsascode.
- The types involved
actor.MessageConsumer→org.requirementsascode.AbstractActoractor.MessageConsumer→org.requirementsascode.Modelactor.MessageProducer→org.requirementsascode.AbstractActoractor.MessageProducer→org.requirementsascode.Modelactor.PublishingActor→org.requirementsascode.AbstractActoractor.PublishingActor→org.requirementsascode.Model
- Direction
- actor uses org.requirementsascode, so a change to org.requirementsascode can break actor, while a change to actor can't break org.requirementsascode.
- Position
- Below the diagonal: actor uses a module listed above it, which is the healthy direction.
17→15 akka uses org.requirementsascode✕
- Connections
- 2 pairs of types, where a type in akka uses a type in org.requirementsascode.
- The types involved
akka.Akka→org.requirementsascode.Modelakka.SayHelloActor→org.requirementsascode.ModelRunner
- Direction
- akka uses org.requirementsascode, so a change to org.requirementsascode can break akka, while a change to akka can't break org.requirementsascode.
- Position
- Below the diagonal: akka uses a module listed above it, which is the healthy direction.
18→15 cleanarchitecture uses org.requirementsascode✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture uses a type in org.requirementsascode.
- The types involved
cleanarchitecture.GreetingServiceModel→org.requirementsascode.BehaviorModelcleanarchitecture.GreetingServiceModel→org.requirementsascode.Model
- Direction
- cleanarchitecture uses org.requirementsascode, so a change to org.requirementsascode can break cleanarchitecture, while a change to cleanarchitecture can't break org.requirementsascode.
- Position
- Below the diagonal: cleanarchitecture uses a module listed above it, which is the healthy direction.
19→1 creditcard_eventsourcing.model uses creditcard_eventsourcing.model.command✕
- Connections
- 4 pairs of types, where a type in creditcard_eventsourcing.model uses a type in creditcard_eventsourcing.model.command.
- The types involved
creditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.model.command.RequestRepaycreditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.model.command.RequestToAssignLimitcreditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.model.command.RequestToCloseCyclecreditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.model.command.RequestWithdrawal
- Direction
- creditcard_eventsourcing.model uses creditcard_eventsourcing.model.command, so a change to creditcard_eventsourcing.model.command can break creditcard_eventsourcing.model, while a change to creditcard_eventsourcing.model can't break creditcard_eventsourcing.model.command.
- Position
- Below the diagonal: creditcard_eventsourcing.model uses a module listed above it, which is the healthy direction.
19→2 creditcard_eventsourcing.model uses creditcard_eventsourcing.model.event✕
- Connections
- 2 pairs of types, where a type in creditcard_eventsourcing.model uses a type in creditcard_eventsourcing.model.event.
- The types involved
creditcard_eventsourcing.model.CreditCard→creditcard_eventsourcing.model.event.DomainEventcreditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.model.event.DomainEvent
- Direction
- creditcard_eventsourcing.model uses creditcard_eventsourcing.model.event, so a change to creditcard_eventsourcing.model.event can break creditcard_eventsourcing.model, while a change to creditcard_eventsourcing.model can't break creditcard_eventsourcing.model.event.
- Position
- Below the diagonal: creditcard_eventsourcing.model uses a module listed above it, which is the healthy direction.
19→9 creditcard_eventsourcing.model uses creditcard_eventsourcing.persistence✕
- Connections
- 1 pair of types, where a type in creditcard_eventsourcing.model uses a type in creditcard_eventsourcing.persistence.
- The types involved
creditcard_eventsourcing.model.CreditCardAggregateRoot→creditcard_eventsourcing.persistence.EventStore
- Direction
- creditcard_eventsourcing.model uses creditcard_eventsourcing.persistence, so a change to creditcard_eventsourcing.persistence can break creditcard_eventsourcing.model, while a change to creditcard_eventsourcing.model can't break creditcard_eventsourcing.persistence.
- Position
- Below the diagonal: creditcard_eventsourcing.model uses a module listed above it, which is the healthy direction.
19→15 creditcard_eventsourcing.model uses org.requirementsascode✕
- Connections
- 7 pairs of types, where a type in creditcard_eventsourcing.model uses a type in org.requirementsascode.
- The types involved
creditcard_eventsourcing.model.CreditCard→org.requirementsascode.Modelcreditcard_eventsourcing.model.CreditCard→org.requirementsascode.ModelRunnercreditcard_eventsourcing.model.CreditCard→org.requirementsascode.Stepcreditcard_eventsourcing.model.CreditCardAggregateRoot→org.requirementsascode.Conditioncreditcard_eventsourcing.model.CreditCardAggregateRoot→org.requirementsascode.Modelcreditcard_eventsourcing.model.CreditCardAggregateRoot→org.requirementsascode.ModelRunnercreditcard_eventsourcing.model.CreditCardAggregateRoot→org.requirementsascode.Step
- Direction
- creditcard_eventsourcing.model uses org.requirementsascode, so a change to org.requirementsascode can break creditcard_eventsourcing.model, while a change to creditcard_eventsourcing.model can't break org.requirementsascode.
- Position
- Below the diagonal: creditcard_eventsourcing.model uses a module listed above it, which is the healthy direction.
20→15 crosscuttingconcerns uses org.requirementsascode✕
- Connections
- 3 pairs of types, where a type in crosscuttingconcerns uses a type in org.requirementsascode.
- The types involved
crosscuttingconcerns.CrossCuttingConcernsActor01→org.requirementsascode.AbstractActorcrosscuttingconcerns.CrossCuttingConcernsActor01→org.requirementsascode.Modelcrosscuttingconcerns.CrossCuttingConcernsActor01→org.requirementsascode.StepToBeRun
- Direction
- crosscuttingconcerns uses org.requirementsascode, so a change to org.requirementsascode can break crosscuttingconcerns, while a change to crosscuttingconcerns can't break org.requirementsascode.
- Position
- Below the diagonal: crosscuttingconcerns uses a module listed above it, which is the healthy direction.
21→3 helloworld uses helloworld.command✕
- Connections
- 5 pairs of types, where a type in helloworld uses a type in helloworld.command.
- The types involved
helloworld.HelloWorldActor03→helloworld.command.EnterTexthelloworld.HelloWorldActor03a→helloworld.command.EnterTexthelloworld.HelloWorldActor04→helloworld.command.EnterTexthelloworld.HelloWorldActor05→helloworld.command.EnterTexthelloworld.HelloWorldActor06→helloworld.command.EnterText
- Direction
- helloworld uses helloworld.command, so a change to helloworld.command can break helloworld, while a change to helloworld can't break helloworld.command.
- Position
- Below the diagonal: helloworld uses a module listed above it, which is the healthy direction.
21→15 helloworld uses org.requirementsascode✕
- Connections
- 22 pairs of types, where a type in helloworld uses a type in org.requirementsascode.
- The types involved
helloworld.GreeterModel→org.requirementsascode.BehaviorModelhelloworld.GreeterModel→org.requirementsascode.Modelhelloworld.HelloWorldActor01→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor01→org.requirementsascode.Modelhelloworld.HelloWorldActor02→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor02→org.requirementsascode.Conditionhelloworld.HelloWorldActor02→org.requirementsascode.Modelhelloworld.HelloWorldActor03→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor03→org.requirementsascode.Modelhelloworld.HelloWorldActor03a→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor03a→org.requirementsascode.Modelhelloworld.HelloWorldActor04→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor04→org.requirementsascode.Modelhelloworld.HelloWorldActor05→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor05→org.requirementsascode.Conditionhelloworld.HelloWorldActor05→org.requirementsascode.Modelhelloworld.HelloWorldActor06→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor06→org.requirementsascode.Conditionhelloworld.HelloWorldActor06→org.requirementsascode.Modelhelloworld.HelloWorldActor07→org.requirementsascode.AbstractActorhelloworld.HelloWorldActor07→org.requirementsascode.Conditionhelloworld.HelloWorldActor07→org.requirementsascode.Model
- Direction
- helloworld uses org.requirementsascode, so a change to org.requirementsascode can break helloworld, while a change to helloworld can't break org.requirementsascode.
- Position
- Below the diagonal: helloworld uses a module listed above it, which is the healthy direction.
22→15 helloworld.actor uses org.requirementsascode✕
- Connections
- 6 pairs of types, where a type in helloworld.actor uses a type in org.requirementsascode.
- The types involved
helloworld.actor.AnonymousUser→org.requirementsascode.AbstractActorhelloworld.actor.AnonymousUser→org.requirementsascode.Modelhelloworld.actor.NormalUser→org.requirementsascode.AbstractActorhelloworld.actor.NormalUser→org.requirementsascode.Modelhelloworld.actor.ValidUser→org.requirementsascode.AbstractActorhelloworld.actor.ValidUser→org.requirementsascode.Model
- Direction
- helloworld.actor uses org.requirementsascode, so a change to org.requirementsascode can break helloworld.actor, while a change to helloworld.actor can't break org.requirementsascode.
- Position
- Below the diagonal: helloworld.actor uses a module listed above it, which is the healthy direction.
23→15 org.requirementsascode.exception uses org.requirementsascode✕
- Connections
- 3 pairs of types, where a type in org.requirementsascode.exception uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.exception.InfiniteRepetition→org.requirementsascode.Steporg.requirementsascode.exception.MissingUseCaseStepPart→org.requirementsascode.Steporg.requirementsascode.exception.MoreThanOneStepCanReact→org.requirementsascode.Step
- Direction
- org.requirementsascode.exception uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.exception, while a change to org.requirementsascode.exception can't break org.requirementsascode.
- Position
- Below the diagonal: org.requirementsascode.exception uses a module listed above it, which is the healthy direction.
24→15 org.requirementsascode.extract.freemarker uses org.requirementsascode✕
- Connections
- 1 pair of types, where a type in org.requirementsascode.extract.freemarker uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.extract.freemarker.FreeMarkerEngine→org.requirementsascode.Model
- Direction
- org.requirementsascode.extract.freemarker uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.extract.freemarker, while a change to org.requirementsascode.extract.freemarker can't break org.requirementsascode.
- Position
- Below the diagonal: org.requirementsascode.extract.freemarker uses a module listed above it, which is the healthy direction.
25→11 org.requirementsascode.extract.freemarker.methodmodel uses org.requirementsascode.flowposition✕
- Connections
- 1 pair of types, where a type in org.requirementsascode.extract.freemarker.methodmodel uses a type in org.requirementsascode.flowposition.
- The types involved
org.requirementsascode.extract.freemarker.methodmodel.FlowCondition→org.requirementsascode.flowposition.FlowPosition
- Direction
- org.requirementsascode.extract.freemarker.methodmodel uses org.requirementsascode.flowposition, so a change to org.requirementsascode.flowposition can break org.requirementsascode.extract.freemarker.methodmodel, while a change to org.requirementsascode.extract.freemarker.methodmodel can't break org.requirementsascode.flowposition.
- Position
- Below the diagonal: org.requirementsascode.extract.freemarker.methodmodel uses a module listed above it, which is the healthy direction.
25→15 org.requirementsascode.extract.freemarker.methodmodel uses org.requirementsascode✕
- Connections
- 8 pairs of types, where a type in org.requirementsascode.extract.freemarker.methodmodel uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.extract.freemarker.methodmodel.ActorPartOfStep→org.requirementsascode.Steporg.requirementsascode.extract.freemarker.methodmodel.FlowCondition→org.requirementsascode.Floworg.requirementsascode.extract.freemarker.methodmodel.FlowlessCondition→org.requirementsascode.Steporg.requirementsascode.extract.freemarker.methodmodel.InCasePartOfStep→org.requirementsascode.Conditionorg.requirementsascode.extract.freemarker.methodmodel.InCasePartOfStep→org.requirementsascode.Steporg.requirementsascode.extract.freemarker.methodmodel.SystemPartOfStep→org.requirementsascode.Behaviororg.requirementsascode.extract.freemarker.methodmodel.SystemPartOfStep→org.requirementsascode.Steporg.requirementsascode.extract.freemarker.methodmodel.UserPartOfStep→org.requirementsascode.Step
- Direction
- org.requirementsascode.extract.freemarker.methodmodel uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.extract.freemarker.methodmodel, while a change to org.requirementsascode.extract.freemarker.methodmodel can't break org.requirementsascode.
- Position
- Below the diagonal: org.requirementsascode.extract.freemarker.methodmodel uses a module listed above it, which is the healthy direction.
26→15 org.requirementsascode.extract.freemarker.methodmodel.util uses org.requirementsascode✕
- Connections
- 3 pairs of types, where a type in org.requirementsascode.extract.freemarker.methodmodel.util uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.extract.freemarker.methodmodel.util.Steps→org.requirementsascode.AbstractActororg.requirementsascode.extract.freemarker.methodmodel.util.Steps→org.requirementsascode.Floworg.requirementsascode.extract.freemarker.methodmodel.util.Steps→org.requirementsascode.Step
- Direction
- org.requirementsascode.extract.freemarker.methodmodel.util uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.extract.freemarker.methodmodel.util, while a change to org.requirementsascode.extract.freemarker.methodmodel.util can't break org.requirementsascode.
- Position
- Below the diagonal: org.requirementsascode.extract.freemarker.methodmodel.util uses a module listed above it, which is the healthy direction.
27→15 org.requirementsascode.systemreaction uses org.requirementsascode✕
- Connections
- 5 pairs of types, where a type in org.requirementsascode.systemreaction uses a type in org.requirementsascode.
- The types involved
org.requirementsascode.systemreaction.AbstractContinuesAfter→org.requirementsascode.FlowSteporg.requirementsascode.systemreaction.AbstractContinuesAfter→org.requirementsascode.ModelRunnerorg.requirementsascode.systemreaction.ContinuesAfter→org.requirementsascode.FlowSteporg.requirementsascode.systemreaction.ContinuesAfter→org.requirementsascode.UseCaseorg.requirementsascode.systemreaction.ContinuesAt→org.requirementsascode.FlowStep
- Direction
- org.requirementsascode.systemreaction uses org.requirementsascode, so a change to org.requirementsascode can break org.requirementsascode.systemreaction, while a change to org.requirementsascode.systemreaction can't break org.requirementsascode.
- Position
- Below the diagonal: org.requirementsascode.systemreaction uses a module listed above it, which is the healthy direction.
28→8 pizzavolumecalculator.actor uses pizzavolumecalculator.actor.command✕
- Connections
- 2 pairs of types, where a type in pizzavolumecalculator.actor uses a type in pizzavolumecalculator.actor.command.
- The types involved
pizzavolumecalculator.actor.PizzaVolumeCalculator→pizzavolumecalculator.actor.command.EnterHeightpizzavolumecalculator.actor.PizzaVolumeCalculator→pizzavolumecalculator.actor.command.EnterRadius
- Direction
- pizzavolumecalculator.actor uses pizzavolumecalculator.actor.command, so a change to pizzavolumecalculator.actor.command can break pizzavolumecalculator.actor, while a change to pizzavolumecalculator.actor can't break pizzavolumecalculator.actor.command.
- Position
- Below the diagonal: pizzavolumecalculator.actor uses a module listed above it, which is the healthy direction.
28→15 pizzavolumecalculator.actor uses org.requirementsascode✕
- Connections
- 3 pairs of types, where a type in pizzavolumecalculator.actor uses a type in org.requirementsascode.
- The types involved
pizzavolumecalculator.actor.PizzaVolumeCalculator→org.requirementsascode.AbstractActorpizzavolumecalculator.actor.PizzaVolumeCalculator→org.requirementsascode.Conditionpizzavolumecalculator.actor.PizzaVolumeCalculator→org.requirementsascode.Model
- Direction
- pizzavolumecalculator.actor uses org.requirementsascode, so a change to org.requirementsascode can break pizzavolumecalculator.actor, while a change to pizzavolumecalculator.actor can't break org.requirementsascode.
- Position
- Below the diagonal: pizzavolumecalculator.actor uses a module listed above it, which is the healthy direction.
29→9 creditcard_eventsourcing.controller uses creditcard_eventsourcing.persistence✕
- Connections
- 1 pair of types, where a type in creditcard_eventsourcing.controller uses a type in creditcard_eventsourcing.persistence.
- The types involved
creditcard_eventsourcing.controller.CreditCardController→creditcard_eventsourcing.persistence.EventStore
- Direction
- creditcard_eventsourcing.controller uses creditcard_eventsourcing.persistence, so a change to creditcard_eventsourcing.persistence can break creditcard_eventsourcing.controller, while a change to creditcard_eventsourcing.controller can't break creditcard_eventsourcing.persistence.
- Position
- Below the diagonal: creditcard_eventsourcing.controller uses a module listed above it, which is the healthy direction.
29→19 creditcard_eventsourcing.controller uses creditcard_eventsourcing.model✕
- Connections
- 1 pair of types, where a type in creditcard_eventsourcing.controller uses a type in creditcard_eventsourcing.model.
- The types involved
creditcard_eventsourcing.controller.CreditCardController→creditcard_eventsourcing.model.CreditCardAggregateRoot
- Direction
- creditcard_eventsourcing.controller uses creditcard_eventsourcing.model, so a change to creditcard_eventsourcing.model can break creditcard_eventsourcing.controller, while a change to creditcard_eventsourcing.controller can't break creditcard_eventsourcing.model.
- Position
- Below the diagonal: creditcard_eventsourcing.controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 3 | Medium |
Roadmap
Top priorities: Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run; Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with ModelRunner.java, CreditCardAggregateRoot.java, StepPart.java.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +5.4 pts | Low | ADR Quality |
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +6.8 pts | Medium | Observability |
| Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with ModelRunner.java, CreditCardAggregateRoot.java, StepPart.java. | +5.4 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.7 pts | Medium | Architecture documentation |
| Run the test suite in CI via an explicit runner step for your stack, and gate merges on it. | +2.0 pts | Medium | CI/CD gates |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.0 pts | Medium | Release Hygiene |
| Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers. | +1.4 pts | Medium | Library API & versioning |
| 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. | +1.2 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/methodmodel/FlowCondition.java | 7.8 | Mixed | Code Duplication: Duplicated block (5 lines × 2) |
| requirementsascodeexamples/creditcard_eventsourcing/build.gradle | 7.9 | Mixed | Platform End-of-Life: End-of-life framework: Spring Boot 2 |
| requirementsascodecore/src/main/java/org/requirementsascode/ModelRunner.java | 8.5 | Near-clean | God Classes: TooManyMethods: ModelRunner |
| requirementsascodecore/src/main/java/org/requirementsascode/builder/ModelBuilder.java | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/model/event/CardRepaid.java | 8.5 | Near-clean | Code Duplication: Duplicated block (22 lines × 3) |
| requirementsascodeexamples/helloworld/src/main/java/helloworld/commandhandler/GreetWithDefaultName.java | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessSystemPart.java | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| requirementsascodeexamples/creditcard_eventsourcing/src/test/java/creditcard_eventsourcing/model/CreditCardAggregateRootTest.java | 8.5 | Near-clean | Test Quality: No assertions: withdrawingOftenWorksWhenCycleIsClosed |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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
This survey 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. All 63 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 63 dimensions across the health lenses
- 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, 38 of 124 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We 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) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) 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 — the Gradle `jacocoTestReport` task) 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.
- D11 Test Reliability — not measured this run — We 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. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 1722 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We 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 (build.gradle), 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.
- D24 Comment Value — not measured this run — We 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- C1 Data Protection — not measured this run — We 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 — We 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 — We 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 — We 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 — We 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.
- DM8 Value-object opportunities — not measured this run — We 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
- GD1 Unfinished & placeholder code — not measured this run — We 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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java 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 — We 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.
- X1 Async correctness — not measured this run — We 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
- X12 Unreachable branch — not measured this run — We 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X13 Undrained process stream — not measured this run — We 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We 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, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- 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.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ModelRunner.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ModelBuilder.java, FlowCondition.java, FlowlessSystemPart.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Duplicated block (22 lines × 3) finding(s) in Code Duplication — start with CardRepaid.java. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with GreetWithDefaultName.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
9 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 8 of the 9 (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).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 44 classes have LCOM4 above 3.
D9 · Test Distribution
303 test methods: 303 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 303 tests.
What to do
- Resolve the 1 No assertions finding(s) in Test Quality — start with CreditCardAggregateRootTest.java. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 73 artifact(s) resolved, 73 of them gradable against Maven Central, and 71 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 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. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 6291 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
57 % of calls cross a namespace and 0 % go through an interface, but 94 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
28 of 28 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is requirementsascodecore/src/main/java/org/requirementsascode/ModelRunner.java. Counted over 28 of the 130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 28 Orphaned file finding(s) in Knowledge Freshness — start with ModelRunner.java, CreditCardAggregateRoot.java, StepPart.java. — One of this dimension's main actionable groups (28 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/3 supply-chain integrity signals present (provenance, signing, SBOM).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 1 platform declaration(s) and 8 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.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with build.gradle. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
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 singletons
- `EventStore` is a singleton (@Repository: the container shares one instance across every request thread) but mutates instance state outside any lock (eventStream; e.g. `eventStream` in `save` at line 25). — requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/persistence/EventStore.java:22
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 cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM1 · Aggregate boundaries
- `CreditCardAggregateRoot` references the aggregate root `CreditCard` directly (via `creditCard`) — hold its `CreditCardId` instead.
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM10 · One transaction, one aggregate
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
M1 · Documentation (README)
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 5 of 8 project(s) that lack one — worth up to 1.3 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no test-runner invocation (your stack's test command, or a test job) was found — changes may merge without the suite running.
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
- 113/144 types (78%) 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) so internals can change without breaking consumers.
P2 · Observability
- No logging call was found in the 120 JVM production file(s) this check read across 8 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- 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 1 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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- 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.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/29 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
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 81% | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 57% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 80% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 76% | Adequate — gated by DM1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 5 control(s) we could not find positive evidence for
- 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.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java not measured.
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- 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.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/EventsourcingApplication.java:21 (@SpringBootApplication))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) 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.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — 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
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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)
Critical — 1 finding(s)
- Aggregate holds a reference to another aggregate: CreditCardAggregateRoot.creditCard
Serious — 12 finding(s)
- Duplicated block (5 lines × 2) requirementsascodecore/src/main/java/org/requirementsascode/builder/ModelBuilder.java:120
- Duplicated block (5 lines × 2) requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/methodmodel/FlowCondition.java:101
- Duplicated block (5 lines × 2) requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessSystemPart.java:131
- Stateful singleton: EventStore requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/persistence/EventStore.java:22
- No assertions: withdrawingOftenWorksWhenCycleIsClosed requirementsascodeexamples/creditcard_eventsourcing/src/test/java/creditcard_eventsourcing/model/CreditCardAggregateRootTest.java:111
- TooManyMethods: ModelRunner requirementsascodecore/src/main/java/org/requirementsascode/ModelRunner.java:26
- Duplicated block (22 lines × 3) requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/model/event/CardRepaid.java:17
- Duplicated block (13 lines × 2) requirementsascodeexamples/helloworld/src/main/java/helloworld/commandhandler/GreetWithDefaultName.java:9
- Duplicated block (11 lines × 4) requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/methodmodel/FlowCondition.java:28
- End-of-life framework: Spring Boot 2 requirementsascodeexamples/creditcard_eventsourcing/build.gradle:1
- Off the main sequence: :requirementsascodecore
- No structured logging
Minor — 40 finding(s)
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/ModelRunner.java:1
- Orphaned file requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/model/CreditCardAggregateRoot.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/UseCase.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/AbstractActor.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessSystemPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/Model.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepUserPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepSystemPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/UseCasePart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepAsPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepInCasePart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/ModelBuilder.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessConditionPart.java:1
- Orphaned file requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/methodmodel/SystemPartOfStep.java:1
- Orphaned file requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/methodmodel/FlowCondition.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessStepPart.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessUserPart.java:1
- Orphaned file requirementsascodeexamples/creditcard_eventsourcing/src/main/java/creditcard_eventsourcing/model/CreditCard.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/FlowlessToPart.java:1
- Orphaned file requirementsascodeexamples/helloworld/src/main/java/helloworld/HelloWorld06.java:1
- Orphaned file requirementsascodeextract/src/main/java/org/requirementsascode/extract/freemarker/FreeMarkerEngine.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/StepToBeRun.java:1
- Orphaned file requirementsascodecore/src/main/java/org/requirementsascode/builder/StepToPart.java:1
- No ADRs found
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- CI test execution not evidenced
- CI build step not evidenced
- Large public API surface
- No SAST
- No changelog
- Java packages are not null-marked everywhere
Minor — 71 finding(s)
- Outdated (compile): org.junit.jupiter:junit-jupiter-api
- Outdated (compile): org.junit:junit-bom
- Outdated (compile): org.junit.platform:junit-platform-commons
- Outdated (compile): org.apiguardian:apiguardian-api
- Outdated (compile): org.opentest4j:opentest4j
- Outdated (compile): org.junit.jupiter:junit-jupiter-engine
- Outdated (compile): org.junit.platform:junit-platform-engine
- Outdated (compile): com.typesafe.akka:akka-actor_2.11
- Outdated (compile): org.scala-lang:scala-library
- Outdated (compile): com.typesafe:config
- Outdated (compile): org.scala-lang.modules:scala-java8-compat_2.11
- Outdated (compile): com.typesafe.akka:akka-remote_2.11
- Outdated (compile): com.typesafe.akka:akka-stream_2.11
- Outdated (compile): org.reactivestreams:reactive-streams
- Outdated (compile): com.typesafe:ssl-config-core_2.11
- Outdated (compile): org.scala-lang.modules:scala-parser-combinators_2.11
- Outdated (compile): com.typesafe.akka:akka-protobuf_2.11
- Outdated (compile): io.aeron:aeron-driver
- Outdated (compile): io.aeron:aeron-client
- Outdated (compile): org.agrona:agrona
- Outdated (compile): org.springframework.boot:spring-boot-starter-data-rest
- Outdated (compile): org.springframework.boot:spring-boot-starter-web
- Outdated (compile): org.springframework.boot:spring-boot-starter
- Outdated (compile): org.springframework.boot:spring-boot
- Outdated (compile): org.springframework:spring-core
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f6ab16a1481a43fa812f2f75f1bac7ef/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f6ab16a1481a43fa812f2f75f1bac7ef/tree.json --exit-code 0 --source . | 0 | artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |