Executive summary
valentinajemuovic/banking-kata-java falls short of our standard for a template or a sample because 12 passwords or keys sit in the current code and we found no logging, tracing or health checks in the code. It scores 45 out of 100 and is rated Adequate, and 34 of its 36 critical findings are security problems.
Production Readiness, at 26, is the weakest lens and counts most in the score. The best first step is replacing the 12 exposed passwords or keys and switching the old ones off, worth about 17 points. Fixing the package under a licence on your banned list comes next, worth about 5 points. Raising Production Readiness to 52 would lift the score to about 57.
Sixteen passwords or keys in the code's history and 12 in the code are open to anyone who can read the repository. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one package carries licence risk. Replacing each exposed password or key, pinning each tool to an exact version and replacing or clearing the banned-licence packages would close these risks. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 3,173 lines, about €7,300 to rebuild.
If Production Readiness rose from 26 to 52, the lowest score rated Strong, the score would rise from 45 to about 57.
New since the last survey: 1 finding
- License Compliance · Banned license: de.mkammerer.snowflake-id:snowflake-id
Fixed since the last survey: 4 findings
- Test Quality · No assertions: should_find_multiple_added_bank_accounts adapter-base/src/test/java/com/optivem/kata/banking/adapter/driven/base/BankAccountStorageTest.java
- Test Quality · No assertions: should_return_added_bank_account adapter-base/src/test/java/com/optivem/kata/banking/adapter/driven/base/BankAccountStorageTest.java
- Test Quality · No assertions: should_return_current_date_time adapter-time-fake/src/test/java/com/optivem/kata/banking/adapter/driven/time/fake/FakeDateTimeServiceTest.java
- Test Quality · Test project verifies nothing: adapter-time-fake adapter-time-fake/src/test/java/com/optivem/kata/banking/adapter/driven/time/fake/FakeDateTimeServiceTest.java
Rebuild cost: about €7,300 · Estimate
| Cost to rebuild | €2,400 to €12,000, for 40 to 128 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 45. 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: 3,173 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 adapter.driven.generation.fake.internal | 2 adapter.driven.persistence.jpa.internal | 3 adapter.driven.persistence.mongo.internal | 4 adapter.driven.persistence.redis.internal | 5 adapter.driver.restapi.spring.controllers.base | 6 core.internal.cleanarch.domain.common.events | 7 core.ports.driven.events | 8 core.ports.driver.accounts.depositfunds | 9 core.ports.driver.accounts.openaccount | 10 core.internal.cleanarch.domain.accounts | 11 core.ports.driven | 12 com.optivem.kata.banking | 13 adapter.driven.generation.fake | 14 adapter.driven.generation.random | 15 adapter.driven.messaging.fake | 16 adapter.driven.messaging.inmemory | 17 adapter.driven.microservice.fake | 18 adapter.driven.microservice.real | 19 adapter.driven.persistence.fake | 20 adapter.driven.persistence.jdbc | 21 adapter.driven.persistence.jpa.mapper | 22 adapter.driven.persistence.mongo | 23 adapter.driven.persistence.redis.mapper | 24 adapter.driven.thirdparty.fake | 25 adapter.driven.thirdparty.real | 26 adapter.driven.time.fake | 27 core.internal.cleanarch.acl | 28 core.internal.cleanarch.domain.common.guards | 29 core.internal.cleanarch.domain.scoring | 30 core.internal.crud.usecases | 31 adapter.driven.persistence.jpa | 32 adapter.driven.persistence.redis | 33 adapter.driver.restapi.spring.configurations | 34 core.internal.cleanarch.domain.common | 35 core.internal.crud.common | 36 core.ports.driver.accounts.viewaccount | 37 adapter.driver.restapi.spring.clients | 38 adapter.driver.restapi.spring.controllers | 39 core.internal.cleanarch.usecases | 40 core |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 adapter.driven.generation.fake.internal | ||||||||||||||||||||||||||||||||||||||||
| 2 adapter.driven.persistence.jpa.internal | ||||||||||||||||||||||||||||||||||||||||
| 3 adapter.driven.persistence.mongo.internal | ||||||||||||||||||||||||||||||||||||||||
| 4 adapter.driven.persistence.redis.internal | ||||||||||||||||||||||||||||||||||||||||
| 5 adapter.driver.restapi.spring.controllers.base | ||||||||||||||||||||||||||||||||||||||||
| 6 core.internal.cleanarch.domain.common.events | ||||||||||||||||||||||||||||||||||||||||
| 7 core.ports.driven.events | ||||||||||||||||||||||||||||||||||||||||
| 8 core.ports.driver.accounts.depositfunds | ||||||||||||||||||||||||||||||||||||||||
| 9 core.ports.driver.accounts.openaccount | ||||||||||||||||||||||||||||||||||||||||
| 10 core.internal.cleanarch.domain.accounts | 3 | |||||||||||||||||||||||||||||||||||||||
| 11 core.ports.driven | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 com.optivem.kata.banking | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 adapter.driven.generation.fake | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 adapter.driven.generation.random | 2 | |||||||||||||||||||||||||||||||||||||||
| 15 adapter.driven.messaging.fake | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 adapter.driven.messaging.inmemory | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 adapter.driven.microservice.fake | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 adapter.driven.microservice.real | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 adapter.driven.persistence.fake | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 adapter.driven.persistence.jdbc | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 adapter.driven.persistence.jpa.mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 adapter.driven.persistence.mongo | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 23 adapter.driven.persistence.redis.mapper | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 adapter.driven.thirdparty.fake | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 adapter.driven.thirdparty.real | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 adapter.driven.time.fake | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 core.internal.cleanarch.acl | 2 | 4 | 8 | 5 | ||||||||||||||||||||||||||||||||||||
| 28 core.internal.cleanarch.domain.common.guards | 2 | |||||||||||||||||||||||||||||||||||||||
| 29 core.internal.cleanarch.domain.scoring | 8 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 core.internal.crud.usecases | 2 | 7 | ||||||||||||||||||||||||||||||||||||||
| 31 adapter.driven.persistence.jpa | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 adapter.driven.persistence.redis | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 adapter.driver.restapi.spring.configurations | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 core.internal.cleanarch.domain.common | 2 | 4 | ||||||||||||||||||||||||||||||||||||||
| 35 core.internal.crud.common | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 core.ports.driver.accounts.viewaccount | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 adapter.driver.restapi.spring.clients | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 adapter.driver.restapi.spring.controllers | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 core.internal.cleanarch.usecases | 3 | 1 | 2 | 14 | 5 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 40 core | 1 | 2 | 7 | 2 | 3 |
10→6 core.internal.cleanarch.domain.accounts uses core.internal.cleanarch.domain.common.events✕
- Connections
- 3 pairs of types, where a type in core.internal.cleanarch.domain.accounts uses a type in core.internal.cleanarch.domain.common.events.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountOpened→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.BaseDomainEventcom.optivem.kata.banking.core.internal.cleanarch.domain.accounts.FundsDeposited→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.BaseDomainEventcom.optivem.kata.banking.core.internal.cleanarch.domain.accounts.FundsWithdrawn→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.BaseDomainEvent
- Direction
- core.internal.cleanarch.domain.accounts uses core.internal.cleanarch.domain.common.events, so a change to core.internal.cleanarch.domain.common.events can break core.internal.cleanarch.domain.accounts, while a change to core.internal.cleanarch.domain.accounts can't break core.internal.cleanarch.domain.common.events.
- Position
- Below the diagonal: core.internal.cleanarch.domain.accounts uses a module listed above it, which is the healthy direction.
11→7 core.ports.driven uses core.ports.driven.events✕
- Connections
- 1 pair of types, where a type in core.ports.driven uses a type in core.ports.driven.events.
- The types involved
com.optivem.kata.banking.core.ports.driven.EventBus→com.optivem.kata.banking.core.ports.driven.events.EventDto
- Direction
- core.ports.driven uses core.ports.driven.events, so a change to core.ports.driven.events can break core.ports.driven, while a change to core.ports.driven can't break core.ports.driven.events.
- Position
- Below the diagonal: core.ports.driven uses a module listed above it, which is the healthy direction.
12→7 com.optivem.kata.banking uses core.ports.driven.events✕
- Connections
- 1 pair of types, where a type in com.optivem.kata.banking uses a type in core.ports.driven.events.
- The types involved
com.optivem.kata.banking.RabbitMQEventBus→com.optivem.kata.banking.core.ports.driven.events.EventDto
- Direction
- com.optivem.kata.banking uses core.ports.driven.events, so a change to core.ports.driven.events can break com.optivem.kata.banking, while a change to com.optivem.kata.banking can't break core.ports.driven.events.
- Position
- Below the diagonal: com.optivem.kata.banking uses a module listed above it, which is the healthy direction.
12→11 com.optivem.kata.banking uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in com.optivem.kata.banking uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.RabbitMQEventBus→com.optivem.kata.banking.core.ports.driven.EventBus
- Direction
- com.optivem.kata.banking uses core.ports.driven, so a change to core.ports.driven can break com.optivem.kata.banking, while a change to com.optivem.kata.banking can't break core.ports.driven.
- Position
- Below the diagonal: com.optivem.kata.banking uses a module listed above it, which is the healthy direction.
13→1 adapter.driven.generation.fake uses adapter.driven.generation.fake.internal✕
- Connections
- 2 pairs of types, where a type in adapter.driven.generation.fake uses a type in adapter.driven.generation.fake.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.generation.fake.FakeAccountIdGenerator→com.optivem.kata.banking.adapter.driven.generation.fake.internal.FakeGeneratorcom.optivem.kata.banking.adapter.driven.generation.fake.FakeAccountNumberGenerator→com.optivem.kata.banking.adapter.driven.generation.fake.internal.FakeGenerator
- Direction
- adapter.driven.generation.fake uses adapter.driven.generation.fake.internal, so a change to adapter.driven.generation.fake.internal can break adapter.driven.generation.fake, while a change to adapter.driven.generation.fake can't break adapter.driven.generation.fake.internal.
- Position
- Below the diagonal: adapter.driven.generation.fake uses a module listed above it, which is the healthy direction.
13→11 adapter.driven.generation.fake uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.generation.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.generation.fake.FakeAccountIdGenerator→com.optivem.kata.banking.core.ports.driven.AccountIdGeneratorcom.optivem.kata.banking.adapter.driven.generation.fake.FakeAccountNumberGenerator→com.optivem.kata.banking.core.ports.driven.AccountNumberGenerator
- Direction
- adapter.driven.generation.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.generation.fake, while a change to adapter.driven.generation.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.generation.fake uses a module listed above it, which is the healthy direction.
14→11 adapter.driven.generation.random uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.generation.random uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.generation.random.RandomAccountIdGenerator→com.optivem.kata.banking.core.ports.driven.AccountIdGeneratorcom.optivem.kata.banking.adapter.driven.generation.random.RandomAccountNumberGenerator→com.optivem.kata.banking.core.ports.driven.AccountNumberGenerator
- Direction
- adapter.driven.generation.random uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.generation.random, while a change to adapter.driven.generation.random can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.generation.random uses a module listed above it, which is the healthy direction.
15→7 adapter.driven.messaging.fake uses core.ports.driven.events✕
- Connections
- 1 pair of types, where a type in adapter.driven.messaging.fake uses a type in core.ports.driven.events.
- The types involved
com.optivem.kata.banking.adapter.driven.messaging.fake.FakeEventBus→com.optivem.kata.banking.core.ports.driven.events.EventDto
- Direction
- adapter.driven.messaging.fake uses core.ports.driven.events, so a change to core.ports.driven.events can break adapter.driven.messaging.fake, while a change to adapter.driven.messaging.fake can't break core.ports.driven.events.
- Position
- Below the diagonal: adapter.driven.messaging.fake uses a module listed above it, which is the healthy direction.
15→11 adapter.driven.messaging.fake uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.messaging.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.messaging.fake.FakeEventBus→com.optivem.kata.banking.core.ports.driven.EventBus
- Direction
- adapter.driven.messaging.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.messaging.fake, while a change to adapter.driven.messaging.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.messaging.fake uses a module listed above it, which is the healthy direction.
16→7 adapter.driven.messaging.inmemory uses core.ports.driven.events✕
- Connections
- 1 pair of types, where a type in adapter.driven.messaging.inmemory uses a type in core.ports.driven.events.
- The types involved
com.optivem.kata.banking.adapter.driven.messaging.inmemory.ApplicationEventBus→com.optivem.kata.banking.core.ports.driven.events.EventDto
- Direction
- adapter.driven.messaging.inmemory uses core.ports.driven.events, so a change to core.ports.driven.events can break adapter.driven.messaging.inmemory, while a change to adapter.driven.messaging.inmemory can't break core.ports.driven.events.
- Position
- Below the diagonal: adapter.driven.messaging.inmemory uses a module listed above it, which is the healthy direction.
16→11 adapter.driven.messaging.inmemory uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.messaging.inmemory uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.messaging.inmemory.ApplicationEventBus→com.optivem.kata.banking.core.ports.driven.EventBus
- Direction
- adapter.driven.messaging.inmemory uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.messaging.inmemory, while a change to adapter.driven.messaging.inmemory can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.messaging.inmemory uses a module listed above it, which is the healthy direction.
17→11 adapter.driven.microservice.fake uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.microservice.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.microservice.fake.FakeCustomerGateway→com.optivem.kata.banking.core.ports.driven.CustomerGatewaycom.optivem.kata.banking.adapter.driven.microservice.fake.FakeCustomerGatewaySimulator→com.optivem.kata.banking.core.ports.driven.CustomerGateway
- Direction
- adapter.driven.microservice.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.microservice.fake, while a change to adapter.driven.microservice.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.microservice.fake uses a module listed above it, which is the healthy direction.
18→11 adapter.driven.microservice.real uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.microservice.real uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.microservice.real.RealCustomerGateway→com.optivem.kata.banking.core.ports.driven.CustomerGateway
- Direction
- adapter.driven.microservice.real uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.microservice.real, while a change to adapter.driven.microservice.real can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.microservice.real uses a module listed above it, which is the healthy direction.
19→11 adapter.driven.persistence.fake uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.fake.FakeBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.adapter.driven.persistence.fake.FakeBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountStorage
- Direction
- adapter.driven.persistence.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.fake, while a change to adapter.driven.persistence.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.fake uses a module listed above it, which is the healthy direction.
20→11 adapter.driven.persistence.jdbc uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.jdbc uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jdbc.JdbcBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.adapter.driven.persistence.jdbc.JdbcBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountStorage
- Direction
- adapter.driven.persistence.jdbc uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.jdbc, while a change to adapter.driven.persistence.jdbc can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.jdbc uses a module listed above it, which is the healthy direction.
21→2 adapter.driven.persistence.jpa.mapper uses adapter.driven.persistence.jpa.internal✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.jpa.mapper uses a type in adapter.driven.persistence.jpa.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jpa.mapper.BankAccountJpaMapper→com.optivem.kata.banking.adapter.driven.persistence.jpa.internal.BankAccountRecord
- Direction
- adapter.driven.persistence.jpa.mapper uses adapter.driven.persistence.jpa.internal, so a change to adapter.driven.persistence.jpa.internal can break adapter.driven.persistence.jpa.mapper, while a change to adapter.driven.persistence.jpa.mapper can't break adapter.driven.persistence.jpa.internal.
- Position
- Below the diagonal: adapter.driven.persistence.jpa.mapper uses a module listed above it, which is the healthy direction.
21→11 adapter.driven.persistence.jpa.mapper uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.jpa.mapper uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jpa.mapper.BankAccountJpaMapper→com.optivem.kata.banking.core.ports.driven.BankAccountDto
- Direction
- adapter.driven.persistence.jpa.mapper uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.jpa.mapper, while a change to adapter.driven.persistence.jpa.mapper can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.jpa.mapper uses a module listed above it, which is the healthy direction.
22→3 adapter.driven.persistence.mongo uses adapter.driven.persistence.mongo.internal✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.mongo uses a type in adapter.driven.persistence.mongo.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.mongo.MongoBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.mongo.internal.MongoTemplateCustomDataAccessor
- Direction
- adapter.driven.persistence.mongo uses adapter.driven.persistence.mongo.internal, so a change to adapter.driven.persistence.mongo.internal can break adapter.driven.persistence.mongo, while a change to adapter.driven.persistence.mongo can't break adapter.driven.persistence.mongo.internal.
- Position
- Below the diagonal: adapter.driven.persistence.mongo uses a module listed above it, which is the healthy direction.
22→11 adapter.driven.persistence.mongo uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.mongo uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.mongo.MongoBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.adapter.driven.persistence.mongo.MongoBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountStorage
- Direction
- adapter.driven.persistence.mongo uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.mongo, while a change to adapter.driven.persistence.mongo can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.mongo uses a module listed above it, which is the healthy direction.
23→4 adapter.driven.persistence.redis.mapper uses adapter.driven.persistence.redis.internal✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.redis.mapper uses a type in adapter.driven.persistence.redis.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.redis.mapper.BankAccountMapper→com.optivem.kata.banking.adapter.driven.persistence.redis.internal.BankAccountModel
- Direction
- adapter.driven.persistence.redis.mapper uses adapter.driven.persistence.redis.internal, so a change to adapter.driven.persistence.redis.internal can break adapter.driven.persistence.redis.mapper, while a change to adapter.driven.persistence.redis.mapper can't break adapter.driven.persistence.redis.internal.
- Position
- Below the diagonal: adapter.driven.persistence.redis.mapper uses a module listed above it, which is the healthy direction.
23→11 adapter.driven.persistence.redis.mapper uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.redis.mapper uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.redis.mapper.BankAccountMapper→com.optivem.kata.banking.core.ports.driven.BankAccountDto
- Direction
- adapter.driven.persistence.redis.mapper uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.redis.mapper, while a change to adapter.driven.persistence.redis.mapper can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.redis.mapper uses a module listed above it, which is the healthy direction.
24→11 adapter.driven.thirdparty.fake uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.thirdparty.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.thirdparty.fake.FakeNationalIdentityGateway→com.optivem.kata.banking.core.ports.driven.NationalIdentityGatewaycom.optivem.kata.banking.adapter.driven.thirdparty.fake.FakeNationalIdentityGatewaySimulator→com.optivem.kata.banking.core.ports.driven.NationalIdentityGateway
- Direction
- adapter.driven.thirdparty.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.thirdparty.fake, while a change to adapter.driven.thirdparty.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.thirdparty.fake uses a module listed above it, which is the healthy direction.
25→11 adapter.driven.thirdparty.real uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.thirdparty.real uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.thirdparty.real.RealNationalIdentityGateway→com.optivem.kata.banking.core.ports.driven.NationalIdentityGateway
- Direction
- adapter.driven.thirdparty.real uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.thirdparty.real, while a change to adapter.driven.thirdparty.real can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.thirdparty.real uses a module listed above it, which is the healthy direction.
26→11 adapter.driven.time.fake uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driven.time.fake uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.time.fake.FakeDateTimeService→com.optivem.kata.banking.core.ports.driven.DateTimeService
- Direction
- adapter.driven.time.fake uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.time.fake, while a change to adapter.driven.time.fake can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.time.fake uses a module listed above it, which is the healthy direction.
27→6 core.internal.cleanarch.acl uses core.internal.cleanarch.domain.common.events✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.acl uses a type in core.internal.cleanarch.domain.common.events.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.acl.EventPublisherImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.DomainEventcom.optivem.kata.banking.core.internal.cleanarch.acl.EventPublisherImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.EventPublisher
- Direction
- core.internal.cleanarch.acl uses core.internal.cleanarch.domain.common.events, so a change to core.internal.cleanarch.domain.common.events can break core.internal.cleanarch.acl, while a change to core.internal.cleanarch.acl can't break core.internal.cleanarch.domain.common.events.
- Position
- Below the diagonal: core.internal.cleanarch.acl uses a module listed above it, which is the healthy direction.
27→7 core.internal.cleanarch.acl uses core.ports.driven.events✕
- Connections
- 4 pairs of types, where a type in core.internal.cleanarch.acl uses a type in core.ports.driven.events.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.acl.AccountOpenedConverter→com.optivem.kata.banking.core.ports.driven.events.AccountOpenedDtocom.optivem.kata.banking.core.internal.cleanarch.acl.EventPublisherImpl→com.optivem.kata.banking.core.ports.driven.events.EventDtocom.optivem.kata.banking.core.internal.cleanarch.acl.FundsDepositedConverter→com.optivem.kata.banking.core.ports.driven.events.FundsDepositedDtocom.optivem.kata.banking.core.internal.cleanarch.acl.FundsWithdrawnConverter→com.optivem.kata.banking.core.ports.driven.events.FundsWithdrawnDto
- Direction
- core.internal.cleanarch.acl uses core.ports.driven.events, so a change to core.ports.driven.events can break core.internal.cleanarch.acl, while a change to core.internal.cleanarch.acl can't break core.ports.driven.events.
- Position
- Below the diagonal: core.internal.cleanarch.acl uses a module listed above it, which is the healthy direction.
27→10 core.internal.cleanarch.acl uses core.internal.cleanarch.domain.accounts✕
- Connections
- 8 pairs of types, where a type in core.internal.cleanarch.acl uses a type in core.internal.cleanarch.domain.accounts.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.acl.AccountOpenedConverter→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountOpenedcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountConverter→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountIdcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountNumbercom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountRepositorycom.optivem.kata.banking.core.internal.cleanarch.acl.FundsDepositedConverter→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.FundsDepositedcom.optivem.kata.banking.core.internal.cleanarch.acl.FundsWithdrawnConverter→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.FundsWithdrawn
- Direction
- core.internal.cleanarch.acl uses core.internal.cleanarch.domain.accounts, so a change to core.internal.cleanarch.domain.accounts can break core.internal.cleanarch.acl, while a change to core.internal.cleanarch.acl can't break core.internal.cleanarch.domain.accounts.
- Position
- Below the diagonal: core.internal.cleanarch.acl uses a module listed above it, which is the healthy direction.
27→11 core.internal.cleanarch.acl uses core.ports.driven✕
- Connections
- 5 pairs of types, where a type in core.internal.cleanarch.acl uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountConverter→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.ports.driven.AccountIdGeneratorcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.ports.driven.AccountNumberGeneratorcom.optivem.kata.banking.core.internal.cleanarch.acl.BankAccountRepositoryImpl→com.optivem.kata.banking.core.ports.driven.BankAccountStoragecom.optivem.kata.banking.core.internal.cleanarch.acl.EventPublisherImpl→com.optivem.kata.banking.core.ports.driven.EventBus
- Direction
- core.internal.cleanarch.acl uses core.ports.driven, so a change to core.ports.driven can break core.internal.cleanarch.acl, while a change to core.internal.cleanarch.acl can't break core.ports.driven.
- Position
- Below the diagonal: core.internal.cleanarch.acl uses a module listed above it, which is the healthy direction.
28→10 core.internal.cleanarch.domain.common.guards uses core.internal.cleanarch.domain.accounts✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.domain.common.guards uses a type in core.internal.cleanarch.domain.accounts.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.MoneyGuard→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.Moneycom.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.TextGuard→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.Text
- Direction
- core.internal.cleanarch.domain.common.guards uses core.internal.cleanarch.domain.accounts, so a change to core.internal.cleanarch.domain.accounts can break core.internal.cleanarch.domain.common.guards, while a change to core.internal.cleanarch.domain.common.guards can't break core.internal.cleanarch.domain.accounts.
- Position
- Below the diagonal: core.internal.cleanarch.domain.common.guards uses a module listed above it, which is the healthy direction.
29→10 core.internal.cleanarch.domain.scoring uses core.internal.cleanarch.domain.accounts✕
- Connections
- 8 pairs of types, where a type in core.internal.cleanarch.domain.scoring uses a type in core.internal.cleanarch.domain.accounts.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.scoring.BalanceFactorCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.DefaultScoreCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.FactorAggregator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.FactorCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.LinearFactorAggregator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.NameFactorCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.ScoreCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.TimeFactorCalculator→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccount
- Direction
- core.internal.cleanarch.domain.scoring uses core.internal.cleanarch.domain.accounts, so a change to core.internal.cleanarch.domain.accounts can break core.internal.cleanarch.domain.scoring, while a change to core.internal.cleanarch.domain.scoring can't break core.internal.cleanarch.domain.accounts.
- Position
- Below the diagonal: core.internal.cleanarch.domain.scoring uses a module listed above it, which is the healthy direction.
29→11 core.internal.cleanarch.domain.scoring uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.domain.scoring uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.scoring.DefaultScoreCalculator→com.optivem.kata.banking.core.ports.driven.DateTimeServicecom.optivem.kata.banking.core.internal.cleanarch.domain.scoring.TimeFactorCalculator→com.optivem.kata.banking.core.ports.driven.DateTimeService
- Direction
- core.internal.cleanarch.domain.scoring uses core.ports.driven, so a change to core.ports.driven can break core.internal.cleanarch.domain.scoring, while a change to core.internal.cleanarch.domain.scoring can't break core.ports.driven.
- Position
- Below the diagonal: core.internal.cleanarch.domain.scoring uses a module listed above it, which is the healthy direction.
30→9 core.internal.crud.usecases uses core.ports.driver.accounts.openaccount✕
- Connections
- 2 pairs of types, where a type in core.internal.crud.usecases uses a type in core.ports.driver.accounts.openaccount.
- The types involved
com.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountRequestcom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountResponse
- Direction
- core.internal.crud.usecases uses core.ports.driver.accounts.openaccount, so a change to core.ports.driver.accounts.openaccount can break core.internal.crud.usecases, while a change to core.internal.crud.usecases can't break core.ports.driver.accounts.openaccount.
- Position
- Below the diagonal: core.internal.crud.usecases uses a module listed above it, which is the healthy direction.
30→11 core.internal.crud.usecases uses core.ports.driven✕
- Connections
- 7 pairs of types, where a type in core.internal.crud.usecases uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.AccountIdGeneratorcom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.AccountNumberGeneratorcom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.BankAccountStoragecom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.CustomerGatewaycom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.DateTimeServicecom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.EventBuscom.optivem.kata.banking.core.internal.crud.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.NationalIdentityGateway
- Direction
- core.internal.crud.usecases uses core.ports.driven, so a change to core.ports.driven can break core.internal.crud.usecases, while a change to core.internal.crud.usecases can't break core.ports.driven.
- Position
- Below the diagonal: core.internal.crud.usecases uses a module listed above it, which is the healthy direction.
31→2 adapter.driven.persistence.jpa uses adapter.driven.persistence.jpa.internal✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.jpa uses a type in adapter.driven.persistence.jpa.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jpa.JpaBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.jpa.internal.BankAccountRecordcom.optivem.kata.banking.adapter.driven.persistence.jpa.JpaBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.jpa.internal.JpaBankAccountDataAccessor
- Direction
- adapter.driven.persistence.jpa uses adapter.driven.persistence.jpa.internal, so a change to adapter.driven.persistence.jpa.internal can break adapter.driven.persistence.jpa, while a change to adapter.driven.persistence.jpa can't break adapter.driven.persistence.jpa.internal.
- Position
- Below the diagonal: adapter.driven.persistence.jpa uses a module listed above it, which is the healthy direction.
31→11 adapter.driven.persistence.jpa uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.jpa uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jpa.JpaBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.adapter.driven.persistence.jpa.JpaBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountStorage
- Direction
- adapter.driven.persistence.jpa uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.jpa, while a change to adapter.driven.persistence.jpa can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.jpa uses a module listed above it, which is the healthy direction.
31→21 adapter.driven.persistence.jpa uses adapter.driven.persistence.jpa.mapper✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.jpa uses a type in adapter.driven.persistence.jpa.mapper.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.jpa.JpaBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.jpa.mapper.BankAccountJpaMapper
- Direction
- adapter.driven.persistence.jpa uses adapter.driven.persistence.jpa.mapper, so a change to adapter.driven.persistence.jpa.mapper can break adapter.driven.persistence.jpa, while a change to adapter.driven.persistence.jpa can't break adapter.driven.persistence.jpa.mapper.
- Position
- Below the diagonal: adapter.driven.persistence.jpa uses a module listed above it, which is the healthy direction.
32→4 adapter.driven.persistence.redis uses adapter.driven.persistence.redis.internal✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.redis uses a type in adapter.driven.persistence.redis.internal.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.redis.RedisBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.redis.internal.BankAccountModelcom.optivem.kata.banking.adapter.driven.persistence.redis.RedisBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.redis.internal.RedisBankAccountDataAccessor
- Direction
- adapter.driven.persistence.redis uses adapter.driven.persistence.redis.internal, so a change to adapter.driven.persistence.redis.internal can break adapter.driven.persistence.redis, while a change to adapter.driven.persistence.redis can't break adapter.driven.persistence.redis.internal.
- Position
- Below the diagonal: adapter.driven.persistence.redis uses a module listed above it, which is the healthy direction.
32→11 adapter.driven.persistence.redis uses core.ports.driven✕
- Connections
- 2 pairs of types, where a type in adapter.driven.persistence.redis uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.redis.RedisBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountDtocom.optivem.kata.banking.adapter.driven.persistence.redis.RedisBankAccountStorage→com.optivem.kata.banking.core.ports.driven.BankAccountStorage
- Direction
- adapter.driven.persistence.redis uses core.ports.driven, so a change to core.ports.driven can break adapter.driven.persistence.redis, while a change to adapter.driven.persistence.redis can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driven.persistence.redis uses a module listed above it, which is the healthy direction.
32→23 adapter.driven.persistence.redis uses adapter.driven.persistence.redis.mapper✕
- Connections
- 1 pair of types, where a type in adapter.driven.persistence.redis uses a type in adapter.driven.persistence.redis.mapper.
- The types involved
com.optivem.kata.banking.adapter.driven.persistence.redis.RedisBankAccountStorage→com.optivem.kata.banking.adapter.driven.persistence.redis.mapper.BankAccountMapper
- Direction
- adapter.driven.persistence.redis uses adapter.driven.persistence.redis.mapper, so a change to adapter.driven.persistence.redis.mapper can break adapter.driven.persistence.redis, while a change to adapter.driven.persistence.redis can't break adapter.driven.persistence.redis.mapper.
- Position
- Below the diagonal: adapter.driven.persistence.redis uses a module listed above it, which is the healthy direction.
33→11 adapter.driver.restapi.spring.configurations uses core.ports.driven✕
- Connections
- 1 pair of types, where a type in adapter.driver.restapi.spring.configurations uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.configurations.DomainConfiguration→com.optivem.kata.banking.core.ports.driven.DateTimeService
- Direction
- adapter.driver.restapi.spring.configurations uses core.ports.driven, so a change to core.ports.driven can break adapter.driver.restapi.spring.configurations, while a change to adapter.driver.restapi.spring.configurations can't break core.ports.driven.
- Position
- Below the diagonal: adapter.driver.restapi.spring.configurations uses a module listed above it, which is the healthy direction.
33→29 adapter.driver.restapi.spring.configurations uses core.internal.cleanarch.domain.scoring✕
- Connections
- 1 pair of types, where a type in adapter.driver.restapi.spring.configurations uses a type in core.internal.cleanarch.domain.scoring.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.configurations.DomainConfiguration→com.optivem.kata.banking.core.internal.cleanarch.domain.scoring.ScoreCalculator
- Direction
- adapter.driver.restapi.spring.configurations uses core.internal.cleanarch.domain.scoring, so a change to core.internal.cleanarch.domain.scoring can break adapter.driver.restapi.spring.configurations, while a change to adapter.driver.restapi.spring.configurations can't break core.internal.cleanarch.domain.scoring.
- Position
- Below the diagonal: adapter.driver.restapi.spring.configurations uses a module listed above it, which is the healthy direction.
34→10 core.internal.cleanarch.domain.common uses core.internal.cleanarch.domain.accounts✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.domain.common uses a type in core.internal.cleanarch.domain.accounts.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.Moneycom.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.Text
- Direction
- core.internal.cleanarch.domain.common uses core.internal.cleanarch.domain.accounts, so a change to core.internal.cleanarch.domain.accounts can break core.internal.cleanarch.domain.common, while a change to core.internal.cleanarch.domain.common can't break core.internal.cleanarch.domain.accounts.
- Position
- Below the diagonal: core.internal.cleanarch.domain.common uses a module listed above it, which is the healthy direction.
34→28 core.internal.cleanarch.domain.common uses core.internal.cleanarch.domain.common.guards✕
- Connections
- 4 pairs of types, where a type in core.internal.cleanarch.domain.common uses a type in core.internal.cleanarch.domain.common.guards.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.LongGuardcom.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.MoneyGuardcom.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.ObjectGuardcom.optivem.kata.banking.core.internal.cleanarch.domain.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.TextGuard
- Direction
- core.internal.cleanarch.domain.common uses core.internal.cleanarch.domain.common.guards, so a change to core.internal.cleanarch.domain.common.guards can break core.internal.cleanarch.domain.common, while a change to core.internal.cleanarch.domain.common can't break core.internal.cleanarch.domain.common.guards.
- Position
- Below the diagonal: core.internal.cleanarch.domain.common uses a module listed above it, which is the healthy direction.
35→28 core.internal.crud.common uses core.internal.cleanarch.domain.common.guards✕
- Connections
- 2 pairs of types, where a type in core.internal.crud.common uses a type in core.internal.cleanarch.domain.common.guards.
- The types involved
com.optivem.kata.banking.core.internal.crud.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.LongGuardcom.optivem.kata.banking.core.internal.crud.common.Guard→com.optivem.kata.banking.core.internal.cleanarch.domain.common.guards.ObjectGuard
- Direction
- core.internal.crud.common uses core.internal.cleanarch.domain.common.guards, so a change to core.internal.cleanarch.domain.common.guards can break core.internal.crud.common, while a change to core.internal.crud.common can't break core.internal.cleanarch.domain.common.guards.
- Position
- Below the diagonal: core.internal.crud.common uses a module listed above it, which is the healthy direction.
36→29 core.ports.driver.accounts.viewaccount uses core.internal.cleanarch.domain.scoring✕
- Connections
- 1 pair of types, where a type in core.ports.driver.accounts.viewaccount uses a type in core.internal.cleanarch.domain.scoring.
- The types involved
com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountResponse→com.optivem.kata.banking.core.internal.cleanarch.domain.scoring.Score
- Direction
- core.ports.driver.accounts.viewaccount uses core.internal.cleanarch.domain.scoring, so a change to core.internal.cleanarch.domain.scoring can break core.ports.driver.accounts.viewaccount, while a change to core.ports.driver.accounts.viewaccount can't break core.internal.cleanarch.domain.scoring.
- Position
- Below the diagonal: core.ports.driver.accounts.viewaccount uses a module listed above it, which is the healthy direction.
37→9 adapter.driver.restapi.spring.clients uses core.ports.driver.accounts.openaccount✕
- Connections
- 2 pairs of types, where a type in adapter.driver.restapi.spring.clients uses a type in core.ports.driver.accounts.openaccount.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.clients.BankingClient→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountRequestcom.optivem.kata.banking.adapter.driver.restapi.spring.clients.BankingClient→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountResponse
- Direction
- adapter.driver.restapi.spring.clients uses core.ports.driver.accounts.openaccount, so a change to core.ports.driver.accounts.openaccount can break adapter.driver.restapi.spring.clients, while a change to adapter.driver.restapi.spring.clients can't break core.ports.driver.accounts.openaccount.
- Position
- Below the diagonal: adapter.driver.restapi.spring.clients uses a module listed above it, which is the healthy direction.
37→36 adapter.driver.restapi.spring.clients uses core.ports.driver.accounts.viewaccount✕
- Connections
- 1 pair of types, where a type in adapter.driver.restapi.spring.clients uses a type in core.ports.driver.accounts.viewaccount.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.clients.BankingClient→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountResponse
- Direction
- adapter.driver.restapi.spring.clients uses core.ports.driver.accounts.viewaccount, so a change to core.ports.driver.accounts.viewaccount can break adapter.driver.restapi.spring.clients, while a change to adapter.driver.restapi.spring.clients can't break core.ports.driver.accounts.viewaccount.
- Position
- Below the diagonal: adapter.driver.restapi.spring.clients uses a module listed above it, which is the healthy direction.
38→5 adapter.driver.restapi.spring.controllers uses adapter.driver.restapi.spring.controllers.base✕
- Connections
- 1 pair of types, where a type in adapter.driver.restapi.spring.controllers uses a type in adapter.driver.restapi.spring.controllers.base.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.controllers.BankAccountController→com.optivem.kata.banking.adapter.driver.restapi.spring.controllers.base.BaseController
- Direction
- adapter.driver.restapi.spring.controllers uses adapter.driver.restapi.spring.controllers.base, so a change to adapter.driver.restapi.spring.controllers.base can break adapter.driver.restapi.spring.controllers, while a change to adapter.driver.restapi.spring.controllers can't break adapter.driver.restapi.spring.controllers.base.
- Position
- Below the diagonal: adapter.driver.restapi.spring.controllers uses a module listed above it, which is the healthy direction.
38→9 adapter.driver.restapi.spring.controllers uses core.ports.driver.accounts.openaccount✕
- Connections
- 2 pairs of types, where a type in adapter.driver.restapi.spring.controllers uses a type in core.ports.driver.accounts.openaccount.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.controllers.BankAccountController→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountRequestcom.optivem.kata.banking.adapter.driver.restapi.spring.controllers.BankAccountController→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountResponse
- Direction
- adapter.driver.restapi.spring.controllers uses core.ports.driver.accounts.openaccount, so a change to core.ports.driver.accounts.openaccount can break adapter.driver.restapi.spring.controllers, while a change to adapter.driver.restapi.spring.controllers can't break core.ports.driver.accounts.openaccount.
- Position
- Below the diagonal: adapter.driver.restapi.spring.controllers uses a module listed above it, which is the healthy direction.
38→36 adapter.driver.restapi.spring.controllers uses core.ports.driver.accounts.viewaccount✕
- Connections
- 1 pair of types, where a type in adapter.driver.restapi.spring.controllers uses a type in core.ports.driver.accounts.viewaccount.
- The types involved
com.optivem.kata.banking.adapter.driver.restapi.spring.controllers.BankAccountController→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountResponse
- Direction
- adapter.driver.restapi.spring.controllers uses core.ports.driver.accounts.viewaccount, so a change to core.ports.driver.accounts.viewaccount can break adapter.driver.restapi.spring.controllers, while a change to adapter.driver.restapi.spring.controllers can't break core.ports.driver.accounts.viewaccount.
- Position
- Below the diagonal: adapter.driver.restapi.spring.controllers uses a module listed above it, which is the healthy direction.
39→6 core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.common.events✕
- Connections
- 3 pairs of types, where a type in core.internal.cleanarch.usecases uses a type in core.internal.cleanarch.domain.common.events.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.EventPublishercom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.EventPublishercom.optivem.kata.banking.core.internal.cleanarch.usecases.WithdrawFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.common.events.EventPublisher
- Direction
- core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.common.events, so a change to core.internal.cleanarch.domain.common.events can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.internal.cleanarch.domain.common.events.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→8 core.internal.cleanarch.usecases uses core.ports.driver.accounts.depositfunds✕
- Connections
- 1 pair of types, where a type in core.internal.cleanarch.usecases uses a type in core.ports.driver.accounts.depositfunds.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.ports.driver.accounts.depositfunds.DepositFundsRequest
- Direction
- core.internal.cleanarch.usecases uses core.ports.driver.accounts.depositfunds, so a change to core.ports.driver.accounts.depositfunds can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.ports.driver.accounts.depositfunds.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→9 core.internal.cleanarch.usecases uses core.ports.driver.accounts.openaccount✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.usecases uses a type in core.ports.driver.accounts.openaccount.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountRequestcom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountResponse
- Direction
- core.internal.cleanarch.usecases uses core.ports.driver.accounts.openaccount, so a change to core.ports.driver.accounts.openaccount can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.ports.driver.accounts.openaccount.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→10 core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.accounts✕
- Connections
- 14 pairs of types, where a type in core.internal.cleanarch.usecases uses a type in core.internal.cleanarch.domain.accounts.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountNumbercom.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountRepositorycom.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.TransactionAmountcom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountHolderNamecom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountOpenedcom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.Balancecom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountRepositorycom.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountNumbercom.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountcom.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountRepositorycom.optivem.kata.banking.core.internal.cleanarch.usecases.WithdrawFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.AccountNumbercom.optivem.kata.banking.core.internal.cleanarch.usecases.WithdrawFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.BankAccountRepositorycom.optivem.kata.banking.core.internal.cleanarch.usecases.WithdrawFundsUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.accounts.TransactionAmount
- Direction
- core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.accounts, so a change to core.internal.cleanarch.domain.accounts can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.internal.cleanarch.domain.accounts.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→11 core.internal.cleanarch.usecases uses core.ports.driven✕
- Connections
- 5 pairs of types, where a type in core.internal.cleanarch.usecases uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCase→com.optivem.kata.banking.core.ports.driven.DateTimeServicecom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.CustomerGatewaycom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.DateTimeServicecom.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCase→com.optivem.kata.banking.core.ports.driven.NationalIdentityGatewaycom.optivem.kata.banking.core.internal.cleanarch.usecases.WithdrawFundsUseCase→com.optivem.kata.banking.core.ports.driven.DateTimeService
- Direction
- core.internal.cleanarch.usecases uses core.ports.driven, so a change to core.ports.driven can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.ports.driven.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→29 core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.scoring✕
- Connections
- 1 pair of types, where a type in core.internal.cleanarch.usecases uses a type in core.internal.cleanarch.domain.scoring.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.internal.cleanarch.domain.scoring.ScoreCalculator
- Direction
- core.internal.cleanarch.usecases uses core.internal.cleanarch.domain.scoring, so a change to core.internal.cleanarch.domain.scoring can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.internal.cleanarch.domain.scoring.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
39→36 core.internal.cleanarch.usecases uses core.ports.driver.accounts.viewaccount✕
- Connections
- 2 pairs of types, where a type in core.internal.cleanarch.usecases uses a type in core.ports.driver.accounts.viewaccount.
- The types involved
com.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountRequestcom.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountResponse
- Direction
- core.internal.cleanarch.usecases uses core.ports.driver.accounts.viewaccount, so a change to core.ports.driver.accounts.viewaccount can break core.internal.cleanarch.usecases, while a change to core.internal.cleanarch.usecases can't break core.ports.driver.accounts.viewaccount.
- Position
- Below the diagonal: core.internal.cleanarch.usecases uses a module listed above it, which is the healthy direction.
40→8 core uses core.ports.driver.accounts.depositfunds✕
- Connections
- 1 pair of types, where a type in core uses a type in core.ports.driver.accounts.depositfunds.
- The types involved
com.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driver.accounts.depositfunds.DepositFundsRequest
- Direction
- core uses core.ports.driver.accounts.depositfunds, so a change to core.ports.driver.accounts.depositfunds can break core, while a change to core can't break core.ports.driver.accounts.depositfunds.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
40→9 core uses core.ports.driver.accounts.openaccount✕
- Connections
- 2 pairs of types, where a type in core uses a type in core.ports.driver.accounts.openaccount.
- The types involved
com.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountRequestcom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driver.accounts.openaccount.OpenAccountResponse
- Direction
- core uses core.ports.driver.accounts.openaccount, so a change to core.ports.driver.accounts.openaccount can break core, while a change to core can't break core.ports.driver.accounts.openaccount.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
40→11 core uses core.ports.driven✕
- Connections
- 7 pairs of types, where a type in core uses a type in core.ports.driven.
- The types involved
com.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.AccountIdGeneratorcom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.AccountNumberGeneratorcom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.BankAccountStoragecom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.CustomerGatewaycom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.DateTimeServicecom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.EventBuscom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driven.NationalIdentityGateway
- Direction
- core uses core.ports.driven, so a change to core.ports.driven can break core, while a change to core can't break core.ports.driven.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
40→36 core uses core.ports.driver.accounts.viewaccount✕
- Connections
- 2 pairs of types, where a type in core uses a type in core.ports.driver.accounts.viewaccount.
- The types involved
com.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountRequestcom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.ports.driver.accounts.viewaccount.ViewAccountResponse
- Direction
- core uses core.ports.driver.accounts.viewaccount, so a change to core.ports.driver.accounts.viewaccount can break core, while a change to core can't break core.ports.driver.accounts.viewaccount.
- Position
- Below the diagonal: core uses a module listed above it, which is the healthy direction.
40→39 core uses core.internal.cleanarch.usecases✕
- Connections
- 3 pairs of types, where a type in core uses a type in core.internal.cleanarch.usecases.
- The types involved
com.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.internal.cleanarch.usecases.DepositFundsUseCasecom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.internal.cleanarch.usecases.OpenAccountUseCasecom.optivem.kata.banking.core.Facade→com.optivem.kata.banking.core.internal.cleanarch.usecases.ViewAccountUseCase
- Direction
- core uses core.internal.cleanarch.usecases, so a change to core.internal.cleanarch.usecases can break core, while a change to core can't break core.internal.cleanarch.usecases.
- Position
- Below the diagonal: core 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 29 | High / Critical |
| A05:2025 — Injection | 11 | High / Critical |
| A02:2025 — Security Misconfiguration | 7 | Medium |
Roadmap
Top priorities: Resolve the 12 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (2), REDACTED (2); Resolve the 15 Orphaned file finding(s) in Knowledge Freshness — start with OpenAccountUseCase.java (2), build.gradle, JpaBankAccountStorage.java; Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 12 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (2), REDACTED (2). | +16.6 pts | Medium | REDACTED Scanning |
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.6 pts | Low | License Compliance |
| Resolve the 15 Orphaned file finding(s) in Knowledge Freshness — start with OpenAccountUseCase.java (2), build.gradle, JpaBankAccountStorage.java. | +5.0 pts | Medium | Knowledge Freshness |
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +4.7 pts | Medium | Observability |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.7 pts | Medium | DR & Backup |
| 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.2 pts | Medium | Architecture documentation |
| Resolve the 34 No direct assertions finding(s) in Test Quality — start with FakeBankAccountStorageExtendedTest.java (8), OpenAccountUseCaseTest.java (7), BankAccountTest.java (6). | +3.4 pts | Medium | Test Quality |
| Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry). | +2.0 pts | Medium | Outbound HTTP resilience |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.1 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 1.3 | Slop | Secrets (history): REDACTED: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java | 6.0 | Near-clean | Explicit Debt: TodoComment |
| z-thirdparty-provider-contracts/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayProviderTest.java | 6.0 | Near-clean | Explicit Debt: TodoComment |
| startup/src/test/java/com/optivem/kata/banking/adapter/restapi/spring/BankingProviderContractTest.java | 6.7 | Near-clean | Explicit Debt: TodoComment |
| startup/src/test/java/com/optivem/kata/banking/startup/BankAccountControllerSystemTest.java | 6.9 | Near-clean | Explicit Debt: TodoComment |
| adapter-microservice-real/src/test/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGatewayConsumerTest.java | 7.2 | Near-clean | Test Quality: No assertions: should_return_false_when_customer_not_exists |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java | 7.2 | Near-clean | Explicit Debt: TodoComment |
| adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/adminrabbitmq/AdminAMQPTest.java | 7.3 | Near-clean | Explicit Debt: TodoComment |
| adapter-thirdparty-real/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayConsumerTest.java | 7.4 | Near-clean | Test Quality: No assertions: should_return_false_when_user_not_exists |
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 68 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 68 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, 155 of 412 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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-maintainer repository — bus factor is not applicable (8 contributor(s) across 546 commit(s) sampled, automation and bot accounts excluded). One of them holds 90% of the history; the other 7 hold 1.4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and 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: 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.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — mongo-express Error context canceled rabbitmq Error context canceled adminer Error context canceled redis Error context canceled mongodb Error context canceled postgres Error context canceled Error response from daemon: pull access denied for jboss/keycloak, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: adminer Error context canceled mongo-express Error context canceled postgres Error context canceled mongodb Error context canceled redis Error context canceled rabbitmq Error context canceled Error response from daemon: pull access denied for jboss/keycloak, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
- C1 Data Protection — not measured this run — 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.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — 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 REDACTED Scanning: REDACTED 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.
- 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").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
0 god class(es) detected.
D4 · Code Duplication
5 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with BankAccount.java, LongGuard.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with BankAccount.java, FundsDepositedConverter.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with JpaBankAccountStorage.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
25 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; 2 module(s) off the main sequence, with abstractness counted on 24 of the 25 (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 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 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 31 classes have LCOM4 above 3.
D9 · Test Distribution
80 test methods: 80 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 46 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 80 tests (2 harness-style project(s) excluded from the assertion penalty).
What to do
- Resolve the 34 No direct assertions finding(s) in Test Quality — start with FakeBankAccountStorageExtendedTest.java (8), OpenAccountUseCaseTest.java (7), BankAccountTest.java (6). — One of this dimension's main actionable groups (34 recommendation-level).
- Resolve the 12 No assertions finding(s) in Test Quality — start with RealCustomerGatewayConsumerTest.java (3), RealNationalIdentityGatewayConsumerTest.java (2), RabbitMQEventBusTest.java (2). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 5 Test project verifies nothing finding(s) in Test Quality — start with RabbitMQEventBusTest.java, RealCustomerGatewayConsumerTest.java, RealNationalIdentityGatewayConsumerTest.java. — One of this dimension's main actionable groups (5 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: 273 artifact(s) resolved, 273 of them gradable against Maven Central, and 243 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 · REDACTED Scanning
8 secret(s) detected.
What to do
- Resolve the 12 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (5), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
1 of 23 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 25 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
21 deducted task-comment markers across 3173 LoC (0.4/KLoC) → score 9.2. 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.
What to do
- Resolve the 21 TodoComment finding(s) in Explicit Debt — start with BankAccountControllerSystemTest.java (3), FakeBankAccountStorageExtendedTest.java (3), AdminAMQPTest.java (2). — One of this dimension's main actionable groups (21 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 22 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
56 % of calls cross a namespace and 19 % go through an interface, but 100 % 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)
16 finding(s): 0 critical, 16 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 16 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 6 high, 5 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 173) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D31 · IaC & Container Security
7 finding(s): 0 critical, 0 high, 7 medium, 0 low.
What to do
- Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
D34 · Knowledge Freshness
15 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is build.gradle. Counted over 15 of the 181 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 15 Orphaned file finding(s) in Knowledge Freshness — start with OpenAccountUseCase.java (2), build.gradle, JpaBankAccountStorage.java. — One of this dimension's main actionable groups (15 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: DepositFundsUseCase.java↔WithdrawFundsUseCase.java 62%; RandomAccountIdGenerator.java↔RandomAccountNumberGenerator.java 60%; DepositFundsRequestBuilder.java↔OpenAccountRequestBuilder.java 60%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ApplicationEventBus.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with DepositFundsUseCase.java, RandomAccountIdGenerator.java, DepositFundsRequestBuilder.java. — One of this dimension's main actionable groups (4 warning-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 34 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
AX2 · Stateful singletons
- `EventQueue` is a singleton (@Component: the container shares one instance across every request thread) but mutates instance state outside any lock (queue; e.g. `queue` in `addEvent` at line 19). — adapter-messaging-inmemory/src/main/java/com/optivem/kata/banking/adapter/driven/messaging/inmemory/internal/EventQueue.java:11
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
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `JpaBankAccountDataAccessor` is a repository over `BankAccountRecord`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `BankAccountRecord` through its owning aggregate instead. — adapter-persistence-jpa/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/jpa/internal/JpaBankAccountDataAccessor.java:9
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a README to the 24 of 24 project(s) that lack one — worth up to 2 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
P1 · CI/CD gates
P2 · Observability
- No logging call was found in the 135 JVM production file(s) this check read across 22 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
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
P7 · Outbound HTTP resilience
- `WebClient.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×5) — adapter-microservice-real/src/main/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGateway.java:26, adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/BankingClient.java:27, adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/BankingClient.java:45, …
What to do
- Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
P8 · Schema migrations
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/58 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 | 72% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 81% | Strong | Strongest area. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26% | Weak — gated by D13, P2, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 64% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 82% | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 56 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — mongo-express Error context canceled rabbitmq Error context canceled adminer Error context canceled redis Error context canceled mongodb Error context canceled postgres Error context canceled Error response from daemon: pull access denied for jboss/keycloak, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the earlier `compose pull` step reported: adminer Error context canceled mongo-express Error context canceled postgres Error context canceled mongodb Error context canceled redis Error context canceled rabbitmq Error context canceled Error response from daemon: pull access denied for jboss/keycloak, repository does not exist or may require 'docker login': denied: requested access to the resource is denied; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D16 Bus Factor — single-maintainer 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.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- 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. Aggregate roots were found in only one source directory (core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — 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).
- 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
- 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
- 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 — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 event handler(s); 5 CQRS handler(s)
- ED5 Idempotency — Not assessed, and this one is on us: 6 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- 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.
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (command argument 1); M4 checks only links and versions and artefact counts.
- 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
- 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 — 36 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: de.mkammerer.snowflake-id:snowflake-id
- Boundary-crossing change coupling: ApplicationEventBus.java ↔ FacadeFactory.java adapter-messaging-inmemory/src/main/java/com/optivem/kata/banking/adapter/driven/messaging/inmemory/ApplicationEventBus.java:1
Serious — 75 finding(s)
- TodoComment z-thirdparty-provider-contracts/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayProviderTest.java:21
- TodoComment z-customer-microservice/src/main/java/com/optivem/kata/banking/CustomerApplication.java:7
- TodoComment test-fixtures/src/main/java/com/optivem/kata/banking/core/common/builders/ports/driven/BankAccountDtoTestBuilder.java:80
- TodoComment startup/src/test/java/com/optivem/kata/banking/startup/BankAccountControllerSystemTest.java:63
- TodoComment startup/src/test/java/com/optivem/kata/banking/startup/BankAccountControllerSystemTest.java:105
- TodoComment startup/src/test/java/com/optivem/kata/banking/startup/BankAccountControllerSystemTest.java:106
- TodoComment startup/src/test/java/com/optivem/kata/banking/adapter/restapi/spring/BankingProviderContractTest.java:34
- TodoComment core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:59
- TodoComment core/src/test/java/com/optivem/kata/banking/core/facade/DepositFundsUseCaseFacadeTest.java:25
- TodoComment core/src/test/java/com/optivem/kata/banking/core/facade/common/TestFacade.java:26
- TodoComment core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/usecases/OpenAccountUseCase.java:54
- TodoComment adapter-thirdparty-real/src/main/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/UserDto.java:8
- TodoComment adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/fake/FakeAuthenticationProvider.java:14
- TodoComment adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/controllers/BankAccountController.java:33
- TodoComment adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/BankingClient.java:12
- TodoComment adapter-persistence-redis/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/redis/RedisBankAccountStorageTest.java:16
- TodoComment adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:8
- TodoComment adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:150
- TodoComment adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:162
- TodoComment adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/adminrabbitmq/AdminAMQPTest.java:31
- TodoComment adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/adminrabbitmq/AdminAMQPTest.java:46
- No assertions: should_execute_without_error adapter-base/src/test/java/com/optivem/kata/banking/adapter/driven/base/EventBusTest.java:20
- No assertions: should_return_false_when_customer_not_exists adapter-microservice-real/src/test/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGatewayConsumerTest.java:115
- No assertions: should_return_true_when_user_is_blacklisted adapter-microservice-real/src/test/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGatewayConsumerTest.java:101
- No assertions: should_return_true_when_user_is_whitelisted adapter-microservice-real/src/test/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGatewayConsumerTest.java:108
- No assertions: should_return_false_when_user_not_exists adapter-thirdparty-real/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayConsumerTest.java:80
- No assertions: should_return_true_when_user_exists adapter-thirdparty-real/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayConsumerTest.java:74
- No assertions: pactVerificationTestTemplate z-thirdparty-provider-contracts/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayProviderTest.java:25
- No assertions: pactVerificationTestTemplate startup/src/test/java/com/optivem/kata/banking/adapter/restapi/spring/BankingProviderContractTest.java:51
- No assertions: contextLoads startup/src/test/java/com/optivem/kata/banking/startup/BankingApplicationTests.java:16
- No assertions: should_consume_message_from_queue adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/RabbitMQEventBusTest.java:56
- No assertions: should_send_dto_to_default_queue adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/RabbitMQEventBusTest.java:51
- No assertions: pactVerificationTestTemplate z-customer-microservice/src/test/java/RealCustomerGatewayProviderTest.java:35
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test project verifies nothing: adapter-messaging-rabbitmq adapter-messaging-rabbitmq/src/test/java/com/optivem/kata/banking/RabbitMQEventBusTest.java:56
- Test project verifies nothing: adapter-microservice-real adapter-microservice-real/src/test/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGatewayConsumerTest.java:115
- Test project verifies nothing: adapter-thirdparty-real adapter-thirdparty-real/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayConsumerTest.java:80
- Test project verifies nothing: z-customer-microservice z-customer-microservice/src/test/java/RealCustomerGatewayProviderTest.java:35
- Test project verifies nothing: z-thirdparty-provider-contracts z-thirdparty-provider-contracts/src/test/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGatewayProviderTest.java:25
- Outbound HTTP without resilience adapter-microservice-real/src/main/java/com/optivem/kata/banking/adapter/driven/microservice/real/RealCustomerGateway.java:26
- Outbound HTTP without resilience adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/BankingClient.java:27
- Outbound HTTP without resilience adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/BankingClient.java:45
- Outbound HTTP without resilience adapter-restapi-spring/src/main/java/com/optivem/kata/banking/adapter/driver/restapi/spring/clients/RealTokenProvider.java:21
- Outbound HTTP without resilience adapter-thirdparty-real/src/main/java/com/optivem/kata/banking/adapter/driven/thirdparty/real/RealNationalIdentityGateway.java:24
- Change coupling: DepositFundsUseCase.java ↔ WithdrawFundsUseCase.java core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/usecases/DepositFundsUseCase.java:1
- Change coupling: RandomAccountIdGenerator.java ↔ RandomAccountNumberGenerator.java adapter-generation-random/src/main/java/com/optivem/kata/banking/adapter/driven/generation/random/RandomAccountIdGenerator.java:1
- Change coupling: DepositFundsRequestBuilder.java ↔ OpenAccountRequestBuilder.java test-fixtures/src/main/java/com/optivem/kata/banking/core/common/builders/requests/DepositFundsRequestBuilder.java:1
- Change coupling: OpenAccountUseCase.java ↔ FacadeFactory.java core/src/main/java/com/optivem/kata/banking/core/internal/crud/usecases/OpenAccountUseCase.java:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/accounts/BankAccount.java:24
- Duplicated block (12 lines × 2) core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/common/guards/LongGuard.java:4
- Duplicated block (7 lines × 2) core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/accounts/BankAccount.java:65
- Duplicated block (7 lines × 2) core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/acl/FundsDepositedConverter.java:7
- Off the main sequence: :adapter-base
- Off the main sequence: :core
- Stateful singleton: EventQueue adapter-messaging-inmemory/src/main/java/com/optivem/kata/banking/adapter/driven/messaging/inmemory/internal/EventQueue.java:11
- REDACTED
- Duplicated block (8 lines × 2) adapter-persistence-jpa/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/jpa/JpaBankAccountStorage.java:56
- End-of-life framework: Spring Boot 2 build.gradle:1
- Repository for a non-root entity: JpaBankAccountDataAccessor → BankAccountRecord adapter-persistence-jpa/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/jpa/internal/JpaBankAccountDataAccessor.java:9
- Coverage collected but not gated
- No structured logging
- No DR/backup evidence
Minor — 58 finding(s)
- No direct assertions: should_not_be_able_to_change_bank_account_after_add adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:63
- No direct assertions: should_not_be_able_to_change_bank_account_after_find adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:84
- No direct assertions: should_not_be_able_to_change_bank_account_after_update adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:107
- No direct assertions: should_retrieve_updated_bank_account_after_update adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:38
- No direct assertions: should_return_bank_account_when_account_number_exists adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:26
- No direct assertions: should_return_empty_result_when_account_number_does_not_exist adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:19
- No direct assertions: should_throw_exception_when_attempt_add_bank_account_with_same_account_number_twice adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:133
- No direct assertions: should_throw_exception_when_attempt_to_update_non_existent_bank_account adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:155
- No direct assertions: should_throw_exception_given_non_positive_value core/src/test/java/com/optivem/kata/banking/core/domain/AccountIdTest.java:14
- No direct assertions: should_throw_exception_given_null_account_holder_name core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:38
- No direct assertions: should_throw_exception_given_null_account_id core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:20
- No direct assertions: should_throw_exception_given_null_account_number core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:26
- No direct assertions: should_throw_exception_given_null_balance core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:51
- No direct assertions: should_throw_exception_given_null_national_identity_number core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:32
- No direct assertions: should_throw_exception_given_null_opening_date core/src/test/java/com/optivem/kata/banking/core/domain/BankAccountTest.java:44
- No direct assertions: should_deposit_funds_given_valid_request core/src/test/java/com/optivem/kata/banking/core/usecases/DepositFundsUseCaseTest.java:62
- No direct assertions: should_throw_exception_given_empty_account_number core/src/test/java/com/optivem/kata/banking/core/usecases/DepositFundsUseCaseTest.java:102
- No direct assertions: should_throw_exception_given_non_existent_account_number core/src/test/java/com/optivem/kata/banking/core/usecases/DepositFundsUseCaseTest.java:113
- No direct assertions: should_throw_exception_given_non_positive_amount core/src/test/java/com/optivem/kata/banking/core/usecases/DepositFundsUseCaseTest.java:124
- No direct assertions: should_open_account_given_valid_request core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:67
- No direct assertions: should_throw_exception_given_blacklisted_national_identity_number core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:135
- No direct assertions: should_throw_exception_given_empty_first_name core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:152
- No direct assertions: should_throw_exception_given_empty_last_name core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:162
- No direct assertions: should_throw_exception_given_empty_national_identity_number core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:110
- No direct assertions: should_throw_exception_given_negative_balance core/src/test/java/com/optivem/kata/banking/core/usecases/OpenAccountUseCaseTest.java:172
- Orphaned file build.gradle:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/usecases/OpenAccountUseCase.java:1
- Orphaned file adapter-persistence-jpa/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/jpa/JpaBankAccountStorage.java:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/internal/crud/usecases/OpenAccountUseCase.java:1
- Orphaned file adapter-persistence-fake/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorage.java:1
- Orphaned file adapter-messaging-rabbitmq/src/main/java/com/optivem/kata/banking/configuration/RabbitMQConfig.java:1
- Orphaned file test-fixtures/src/main/java/com/optivem/kata/banking/core/common/factories/CleanArchUseCaseFactory.java:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/accounts/ESBankAccount.java:1
- Orphaned file test-fixtures/src/main/java/com/optivem/kata/banking/core/common/builders/ports/driven/BankAccountDtoTestBuilder.java:1
- Orphaned file adapter-persistence-jdbc/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/jdbc/JdbcBankAccountStorage.java:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/acl/BankAccountRepositoryImpl.java:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/accounts/BankAccount.java:1
- Orphaned file core/src/main/java/com/optivem/kata/banking/core/Facade.java:1
- Orphaned file adapter-persistence-redis/src/main/java/com/optivem/kata/banking/adapter/driven/persistence/redis/RedisBankAccountStorage.java:1
- Orphaned file test-facade/src/main/java/com/optivem/kata/banking/core/common/factories/FacadeFactory.java:1
- Test project verifies nothing: adapter-persistence-fake adapter-persistence-fake/src/test/java/com/optivem/kata/banking/adapter/driven/persistence/fake/FakeBankAccountStorageExtendedTest.java:63
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No rollback/health safety
- No changelog
- Duplicated predicate core/src/main/java/com/optivem/kata/banking/core/internal/cleanarch/domain/accounts/Text.java:7
- Java packages are not null-marked everywhere
Minor — 243 finding(s)
- Outdated (compile): org.projectlombok:lombok
- Outdated (compile): org.springframework.boot:spring-boot-starter-webflux
- Outdated (compile): org.springframework.boot:spring-boot-starter
- Outdated (compile): org.springframework.boot:spring-boot
- Outdated (compile): org.springframework:spring-core
- Outdated (compile): org.springframework:spring-jcl
- Outdated (compile): org.springframework:spring-context
- Outdated (compile): org.springframework:spring-aop
- Outdated (compile): org.springframework:spring-beans
- Outdated (compile): org.springframework:spring-expression
- Outdated (compile): org.springframework.boot:spring-boot-autoconfigure
- Outdated (compile): org.springframework.boot:spring-boot-starter-logging
- Outdated (compile): ch.qos.logback:logback-classic
- Outdated (compile): ch.qos.logback:logback-core
- Outdated (compile): org.slf4j:slf4j-api
- Outdated (compile): org.apache.logging.log4j:log4j-to-slf4j
- Outdated (compile): org.apache.logging.log4j:log4j-api
- Outdated (compile): org.slf4j:jul-to-slf4j
- Outdated (compile): jakarta.annotation:jakarta.annotation-api
- Outdated (compile): org.yaml:snakeyaml
- Outdated (compile): org.springframework.boot:spring-boot-starter-json
- Outdated (compile): org.springframework:spring-web
- Outdated (compile): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): com.fasterxml.jackson:jackson-bom
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-90ec1930a5544c0abc33762e979d2786/history.json --exit-code 0 --source . | 26 | 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-90ec1930a5544c0abc33762e979d2786/tree.json --exit-code 0 --source . | 18 | 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 . | 11 | 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 config --format json --quiet . | 7 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 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 | — |