Executive summary
getSoftware/clean-architecture-hexagonal-my-approach falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 43 out of 100 and is rated Weak, and it has no critical findings.
Production Readiness, at 20, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 7 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 62.
The seven serious findings are spread across the lenses, with the most in Production Readiness.
The product code is 1,424 lines, about €2,000 to rebuild.
If Production Readiness rose from 20 to 70, the lowest score rated Strong, the score would rise from 43 to about 62.
Rebuild cost: about €2,000 · Estimate
| Cost to rebuild | €680 to €3,400, for 11 to 36 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 43. 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 | Very small: 1,424 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: which parts of the code depend on which
| uses → | 1 cleanarchitecture | 2 cleanarchitecture.adapter.common.error | 3 cleanarchitecture.application.domain.model.address | 4 cleanarchitecture.application.domain.model.domain | 5 cleanarchitecture.application.domain.model.mapper | 6 cleanarchitecture.application.domain.model.modelinnerservice | 7 cleanarchitecture.application.port.in.user.iprocessor | 8 cleanarchitecture.application.port.out.user.iportservice | 9 cleanarchitecture.main.config | 10 cleanarchitecture.application.domain.model.user | 11 cleanarchitecture.application.domain.usecase.user.service | 12 cleanarchitecture.adapter.out.persistence.model | 13 cleanarchitecture.application.port.in.user.dto | 14 cleanarchitecture.application.port.out.user | 15 cleanarchitecture.adapter.out | 16 cleanarchitecture.adapter.out.persistence.mapper | 17 cleanarchitecture.adapter.out.persistence.repository | 18 cleanarchitecture.application.domain.usecase | 19 cleanarchitecture.application.port.in.user.iqueryservice | 20 cleanarchitecture.application.port.in.user.iusecase | 21 cleanarchitecture.adapter.in.web.controller | 22 cleanarchitecture.adapter.out.persistence.service | 23 cleanarchitecture.adapter.in.service | 24 cleanarchitecture.application.domain.usecase.user |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cleanarchitecture | ||||||||||||||||||||||||
| 2 cleanarchitecture.adapter.common.error | ||||||||||||||||||||||||
| 3 cleanarchitecture.application.domain.model.address | ||||||||||||||||||||||||
| 4 cleanarchitecture.application.domain.model.domain | ||||||||||||||||||||||||
| 5 cleanarchitecture.application.domain.model.mapper | ||||||||||||||||||||||||
| 6 cleanarchitecture.application.domain.model.modelinnerservice | ||||||||||||||||||||||||
| 7 cleanarchitecture.application.port.in.user.iprocessor | ||||||||||||||||||||||||
| 8 cleanarchitecture.application.port.out.user.iportservice | ||||||||||||||||||||||||
| 9 cleanarchitecture.main.config | ||||||||||||||||||||||||
| 10 cleanarchitecture.application.domain.model.user | 2 | |||||||||||||||||||||||
| 11 cleanarchitecture.application.domain.usecase.user.service | 2 | 2 | ||||||||||||||||||||||
| 12 cleanarchitecture.adapter.out.persistence.model | 1 | 1 | ||||||||||||||||||||||
| 13 cleanarchitecture.application.port.in.user.dto | 5 | |||||||||||||||||||||||
| 14 cleanarchitecture.application.port.out.user | 1 | |||||||||||||||||||||||
| 15 cleanarchitecture.adapter.out | 1 | 1 | ||||||||||||||||||||||
| 16 cleanarchitecture.adapter.out.persistence.mapper | 1 | 3 | 2 | 2 | 1 | |||||||||||||||||||
| 17 cleanarchitecture.adapter.out.persistence.repository | 1 | 1 | ||||||||||||||||||||||
| 18 cleanarchitecture.application.domain.usecase | 1 | |||||||||||||||||||||||
| 19 cleanarchitecture.application.port.in.user.iqueryservice | 1 | 1 | ||||||||||||||||||||||
| 20 cleanarchitecture.application.port.in.user.iusecase | 1 | 1 | 4 | |||||||||||||||||||||
| 21 cleanarchitecture.adapter.in.web.controller | 1 | 1 | 1 | 1 | 3 | 1 | 2 | |||||||||||||||||
| 22 cleanarchitecture.adapter.out.persistence.service | 2 | 2 | 2 | |||||||||||||||||||||
| 23 cleanarchitecture.adapter.in.service | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||
| 24 cleanarchitecture.application.domain.usecase.user | 1 | 1 | 2 | 4 | 2 | 2 | 2 | 4 |
10→3 cleanarchitecture.application.domain.model.user uses cleanarchitecture.application.domain.model.address✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.model.user uses a type in cleanarchitecture.application.domain.model.address.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainFactory→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObjecteu.getsoftware.cleanarchitecture.application.domain.model.user.UserRootDomainEntity→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObject
- Direction
- cleanarchitecture.application.domain.model.user uses cleanarchitecture.application.domain.model.address, so a change to cleanarchitecture.application.domain.model.address can break cleanarchitecture.application.domain.model.user, while a change to cleanarchitecture.application.domain.model.user can't break cleanarchitecture.application.domain.model.address.
- Position
- Below the diagonal: cleanarchitecture.application.domain.model.user uses a module listed above it, which is the healthy direction.
11→5 cleanarchitecture.application.domain.usecase.user.service uses cleanarchitecture.application.domain.model.mapper✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user.service uses a type in cleanarchitecture.application.domain.model.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutRepositoryQueryAdapter→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.EntityGenericMappereu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutUpdateAdapter→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.EntityGenericMapper
- Direction
- cleanarchitecture.application.domain.usecase.user.service uses cleanarchitecture.application.domain.model.mapper, so a change to cleanarchitecture.application.domain.model.mapper can break cleanarchitecture.application.domain.usecase.user.service, while a change to cleanarchitecture.application.domain.usecase.user.service can't break cleanarchitecture.application.domain.model.mapper.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user.service uses a module listed above it, which is the healthy direction.
11→8 cleanarchitecture.application.domain.usecase.user.service uses cleanarchitecture.application.port.out.user.iportservice✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user.service uses a type in cleanarchitecture.application.port.out.user.iportservice.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutRepositoryQueryAdapter→eu.getsoftware.cleanarchitecture.application.port.out.user.iportservice.GenericOutRepositoryQueryServiceeu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutUpdateAdapter→eu.getsoftware.cleanarchitecture.application.port.out.user.iportservice.GenericOutPersistService
- Direction
- cleanarchitecture.application.domain.usecase.user.service uses cleanarchitecture.application.port.out.user.iportservice, so a change to cleanarchitecture.application.port.out.user.iportservice can break cleanarchitecture.application.domain.usecase.user.service, while a change to cleanarchitecture.application.domain.usecase.user.service can't break cleanarchitecture.application.port.out.user.iportservice.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user.service uses a module listed above it, which is the healthy direction.
12→5 cleanarchitecture.adapter.out.persistence.model uses cleanarchitecture.application.domain.model.mapper✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.model uses a type in cleanarchitecture.application.domain.model.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.model.UserMappedDBEntity→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.IMappedDBEntity
- Direction
- cleanarchitecture.adapter.out.persistence.model uses cleanarchitecture.application.domain.model.mapper, so a change to cleanarchitecture.application.domain.model.mapper can break cleanarchitecture.adapter.out.persistence.model, while a change to cleanarchitecture.adapter.out.persistence.model can't break cleanarchitecture.application.domain.model.mapper.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.model uses a module listed above it, which is the healthy direction.
12→10 cleanarchitecture.adapter.out.persistence.model uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.model uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.model.UserMappedDBEntity→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.adapter.out.persistence.model uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.out.persistence.model, while a change to cleanarchitecture.adapter.out.persistence.model can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.model uses a module listed above it, which is the healthy direction.
13→10 cleanarchitecture.application.port.in.user.dto uses cleanarchitecture.application.domain.model.user✕
- Connections
- 5 pairs of types, where a type in cleanarchitecture.application.port.in.user.dto uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTO→eu.getsoftware.cleanarchitecture.application.domain.model.user.IUserDomainResponseDTOeu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTO→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainIdeu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserRegisterRequestUseCaseDTO→eu.getsoftware.cleanarchitecture.application.domain.model.user.IDomainRequestDTOeu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserUpdateRequestUseCaseDTO→eu.getsoftware.cleanarchitecture.application.domain.model.user.IDomainRequestDTOeu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserUpdateRequestUseCaseDTO→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.application.port.in.user.dto uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.application.port.in.user.dto, while a change to cleanarchitecture.application.port.in.user.dto can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.dto uses a module listed above it, which is the healthy direction.
14→10 cleanarchitecture.application.port.out.user uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.port.out.user uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresenter→eu.getsoftware.cleanarchitecture.application.domain.model.user.IUserDomainResponseDTO
- Direction
- cleanarchitecture.application.port.out.user uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.application.port.out.user, while a change to cleanarchitecture.application.port.out.user can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.application.port.out.user uses a module listed above it, which is the healthy direction.
15→10 cleanarchitecture.adapter.out uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.UserResponseDTOPortFormatter→eu.getsoftware.cleanarchitecture.application.domain.model.user.IUserDomainResponseDTO
- Direction
- cleanarchitecture.adapter.out uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.out, while a change to cleanarchitecture.adapter.out can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.out uses a module listed above it, which is the healthy direction.
15→14 cleanarchitecture.adapter.out uses cleanarchitecture.application.port.out.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out uses a type in cleanarchitecture.application.port.out.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.UserResponseDTOPortFormatter→eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresenter
- Direction
- cleanarchitecture.adapter.out uses cleanarchitecture.application.port.out.user, so a change to cleanarchitecture.application.port.out.user can break cleanarchitecture.adapter.out, while a change to cleanarchitecture.adapter.out can't break cleanarchitecture.application.port.out.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.out uses a module listed above it, which is the healthy direction.
16→3 cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.address✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.mapper uses a type in cleanarchitecture.application.domain.model.address.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.AddressValueObjectMapper→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObject
- Direction
- cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.address, so a change to cleanarchitecture.application.domain.model.address can break cleanarchitecture.adapter.out.persistence.mapper, while a change to cleanarchitecture.adapter.out.persistence.mapper can't break cleanarchitecture.application.domain.model.address.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.mapper uses a module listed above it, which is the healthy direction.
16→5 cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.mapper✕
- Connections
- 3 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.mapper uses a type in cleanarchitecture.application.domain.model.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.AddressValueObjectMapper→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.EntityGenericMappereu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserDtoMapper→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.DtoGenericMappereu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserEntityMapper→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.EntityGenericMapper
- Direction
- cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.mapper, so a change to cleanarchitecture.application.domain.model.mapper can break cleanarchitecture.adapter.out.persistence.mapper, while a change to cleanarchitecture.adapter.out.persistence.mapper can't break cleanarchitecture.application.domain.model.mapper.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.mapper uses a module listed above it, which is the healthy direction.
16→10 cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.user✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.mapper uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserDtoMapper→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserRootDomainEntityeu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserEntityMapper→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserRootDomainEntity
- Direction
- cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.out.persistence.mapper, while a change to cleanarchitecture.adapter.out.persistence.mapper can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.mapper uses a module listed above it, which is the healthy direction.
16→12 cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.adapter.out.persistence.model✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.mapper uses a type in cleanarchitecture.adapter.out.persistence.model.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.AddressValueObjectMapper→eu.getsoftware.cleanarchitecture.adapter.out.persistence.model.AddressDBEmbeddableeu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserEntityMapper→eu.getsoftware.cleanarchitecture.adapter.out.persistence.model.UserMappedDBEntity
- Direction
- cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.adapter.out.persistence.model, so a change to cleanarchitecture.adapter.out.persistence.model can break cleanarchitecture.adapter.out.persistence.mapper, while a change to cleanarchitecture.adapter.out.persistence.mapper can't break cleanarchitecture.adapter.out.persistence.model.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.mapper uses a module listed above it, which is the healthy direction.
16→13 cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.mapper uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserDtoMapper→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTO
- Direction
- cleanarchitecture.adapter.out.persistence.mapper uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.adapter.out.persistence.mapper, while a change to cleanarchitecture.adapter.out.persistence.mapper can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.mapper uses a module listed above it, which is the healthy direction.
17→10 cleanarchitecture.adapter.out.persistence.repository uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.repository uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.repository.UserJpaRepository→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.adapter.out.persistence.repository uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.out.persistence.repository, while a change to cleanarchitecture.adapter.out.persistence.repository can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.repository uses a module listed above it, which is the healthy direction.
17→12 cleanarchitecture.adapter.out.persistence.repository uses cleanarchitecture.adapter.out.persistence.model✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.out.persistence.repository uses a type in cleanarchitecture.adapter.out.persistence.model.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.repository.UserJpaRepository→eu.getsoftware.cleanarchitecture.adapter.out.persistence.model.UserMappedDBEntity
- Direction
- cleanarchitecture.adapter.out.persistence.repository uses cleanarchitecture.adapter.out.persistence.model, so a change to cleanarchitecture.adapter.out.persistence.model can break cleanarchitecture.adapter.out.persistence.repository, while a change to cleanarchitecture.adapter.out.persistence.repository can't break cleanarchitecture.adapter.out.persistence.model.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.repository uses a module listed above it, which is the healthy direction.
18→14 cleanarchitecture.application.domain.usecase uses cleanarchitecture.application.port.out.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.domain.usecase uses a type in cleanarchitecture.application.port.out.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.UseCasePresenterHandlerAspect→eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresenter
- Direction
- cleanarchitecture.application.domain.usecase uses cleanarchitecture.application.port.out.user, so a change to cleanarchitecture.application.port.out.user can break cleanarchitecture.application.domain.usecase, while a change to cleanarchitecture.application.domain.usecase can't break cleanarchitecture.application.port.out.user.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase uses a module listed above it, which is the healthy direction.
19→10 cleanarchitecture.application.port.in.user.iqueryservice uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.port.in.user.iqueryservice uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.iqueryservice.UserInDTOQueryService→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.application.port.in.user.iqueryservice uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.application.port.in.user.iqueryservice, while a change to cleanarchitecture.application.port.in.user.iqueryservice can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.iqueryservice uses a module listed above it, which is the healthy direction.
19→13 cleanarchitecture.application.port.in.user.iqueryservice uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.port.in.user.iqueryservice uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.iqueryservice.UserInDTOQueryService→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTO
- Direction
- cleanarchitecture.application.port.in.user.iqueryservice uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.application.port.in.user.iqueryservice, while a change to cleanarchitecture.application.port.in.user.iqueryservice can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.iqueryservice uses a module listed above it, which is the healthy direction.
20→3 cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.domain.model.address✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.port.in.user.iusecase uses a type in cleanarchitecture.application.domain.model.address.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObject
- Direction
- cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.domain.model.address, so a change to cleanarchitecture.application.domain.model.address can break cleanarchitecture.application.port.in.user.iusecase, while a change to cleanarchitecture.application.port.in.user.iusecase can't break cleanarchitecture.application.domain.model.address.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.iusecase uses a module listed above it, which is the healthy direction.
20→10 cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.port.in.user.iusecase uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.application.port.in.user.iusecase, while a change to cleanarchitecture.application.port.in.user.iusecase can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.iusecase uses a module listed above it, which is the healthy direction.
20→13 cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 4 pairs of types, where a type in cleanarchitecture.application.port.in.user.iusecase uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserRegisterUseCase→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTOeu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserRegisterUseCase→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserRegisterRequestUseCaseDTOeu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTOeu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserUpdateRequestUseCaseDTO
- Direction
- cleanarchitecture.application.port.in.user.iusecase uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.application.port.in.user.iusecase, while a change to cleanarchitecture.application.port.in.user.iusecase can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.application.port.in.user.iusecase uses a module listed above it, which is the healthy direction.
21→2 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.adapter.common.error✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.adapter.common.error.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.ApiExceptionHandler→eu.getsoftware.cleanarchitecture.adapter.common.error.JsonErrorResponse
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.adapter.common.error, so a change to cleanarchitecture.adapter.common.error can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.adapter.common.error.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→3 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.address✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.domain.model.address.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObject
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.address, so a change to cleanarchitecture.application.domain.model.address can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.domain.model.address.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→4 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.domain✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.domain.model.domain.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.ApiExceptionHandler→eu.getsoftware.cleanarchitecture.application.domain.model.domain.BusinessException
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.domain, so a change to cleanarchitecture.application.domain.model.domain can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.domain.model.domain.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→10 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainId
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→13 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 3 pairs of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTOeu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserRegisterRequestUseCaseDTOeu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserUpdateRequestUseCaseDTO
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→19 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.iqueryservice✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.port.in.user.iqueryservice.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.iqueryservice.UserInDTOQueryService
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.iqueryservice, so a change to cleanarchitecture.application.port.in.user.iqueryservice can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.port.in.user.iqueryservice.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
21→20 cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.iusecase✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.in.web.controller uses a type in cleanarchitecture.application.port.in.user.iusecase.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserRegisterUseCaseeu.getsoftware.cleanarchitecture.adapter.in.web.controller.UserCrudController→eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase
- Direction
- cleanarchitecture.adapter.in.web.controller uses cleanarchitecture.application.port.in.user.iusecase, so a change to cleanarchitecture.application.port.in.user.iusecase can break cleanarchitecture.adapter.in.web.controller, while a change to cleanarchitecture.adapter.in.web.controller can't break cleanarchitecture.application.port.in.user.iusecase.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.web.controller uses a module listed above it, which is the healthy direction.
22→11 cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.application.domain.usecase.user.service✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.service uses a type in cleanarchitecture.application.domain.usecase.user.service.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdapter→eu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutRepositoryQueryAdaptereu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryUpdateAdapter→eu.getsoftware.cleanarchitecture.application.domain.usecase.user.service.GenericOutUpdateAdapter
- Direction
- cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.application.domain.usecase.user.service, so a change to cleanarchitecture.application.domain.usecase.user.service can break cleanarchitecture.adapter.out.persistence.service, while a change to cleanarchitecture.adapter.out.persistence.service can't break cleanarchitecture.application.domain.usecase.user.service.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.service uses a module listed above it, which is the healthy direction.
22→16 cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.adapter.out.persistence.mapper✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.service uses a type in cleanarchitecture.adapter.out.persistence.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdapter→eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserEntityMappereu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryUpdateAdapter→eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserEntityMapper
- Direction
- cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.adapter.out.persistence.mapper, so a change to cleanarchitecture.adapter.out.persistence.mapper can break cleanarchitecture.adapter.out.persistence.service, while a change to cleanarchitecture.adapter.out.persistence.service can't break cleanarchitecture.adapter.out.persistence.mapper.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.service uses a module listed above it, which is the healthy direction.
22→17 cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.adapter.out.persistence.repository✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.out.persistence.service uses a type in cleanarchitecture.adapter.out.persistence.repository.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdapter→eu.getsoftware.cleanarchitecture.adapter.out.persistence.repository.UserJpaRepositoryeu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryUpdateAdapter→eu.getsoftware.cleanarchitecture.adapter.out.persistence.repository.UserJpaRepository
- Direction
- cleanarchitecture.adapter.out.persistence.service uses cleanarchitecture.adapter.out.persistence.repository, so a change to cleanarchitecture.adapter.out.persistence.repository can break cleanarchitecture.adapter.out.persistence.service, while a change to cleanarchitecture.adapter.out.persistence.service can't break cleanarchitecture.adapter.out.persistence.repository.
- Position
- Below the diagonal: cleanarchitecture.adapter.out.persistence.service uses a module listed above it, which is the healthy direction.
23→5 cleanarchitecture.adapter.in.service uses cleanarchitecture.application.domain.model.mapper✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.application.domain.model.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.DtoGenericMapper
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.application.domain.model.mapper, so a change to cleanarchitecture.application.domain.model.mapper can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.application.domain.model.mapper.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
23→10 cleanarchitecture.adapter.in.service uses cleanarchitecture.application.domain.model.user✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainIdeu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserRootDomainEntity
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
23→13 cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTO
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
23→14 cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.out.user✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.application.port.out.user.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresenter
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.out.user, so a change to cleanarchitecture.application.port.out.user can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.application.port.out.user.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
23→19 cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.in.user.iqueryservice✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.application.port.in.user.iqueryservice.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.iqueryservice.UserInDTOQueryService
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.application.port.in.user.iqueryservice, so a change to cleanarchitecture.application.port.in.user.iqueryservice can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.application.port.in.user.iqueryservice.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
23→22 cleanarchitecture.adapter.in.service uses cleanarchitecture.adapter.out.persistence.service✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.adapter.in.service uses a type in cleanarchitecture.adapter.out.persistence.service.
- The types involved
eu.getsoftware.cleanarchitecture.adapter.in.service.UserInDTOQueryServiceImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdapter
- Direction
- cleanarchitecture.adapter.in.service uses cleanarchitecture.adapter.out.persistence.service, so a change to cleanarchitecture.adapter.out.persistence.service can break cleanarchitecture.adapter.in.service, while a change to cleanarchitecture.adapter.in.service can't break cleanarchitecture.adapter.out.persistence.service.
- Position
- Below the diagonal: cleanarchitecture.adapter.in.service uses a module listed above it, which is the healthy direction.
24→3 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.address✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.domain.model.address.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.domain.model.address.AddressValueObject
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.address, so a change to cleanarchitecture.application.domain.model.address can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.domain.model.address.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→5 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.mapper✕
- Connections
- 1 pair of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.domain.model.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.domain.model.mapper.DtoGenericMapper
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.mapper, so a change to cleanarchitecture.application.domain.model.mapper can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.domain.model.mapper.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→10 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.user✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.domain.model.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserDomainIdeu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.domain.model.user.UserRootDomainEntity
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.domain.model.user, so a change to cleanarchitecture.application.domain.model.user can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.domain.model.user.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→13 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.in.user.dto✕
- Connections
- 4 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.port.in.user.dto.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTOeu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserRegisterRequestUseCaseDTOeu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserClientDTOeu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.dto.UserUpdateRequestUseCaseDTO
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.in.user.dto, so a change to cleanarchitecture.application.port.in.user.dto can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.port.in.user.dto.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→14 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.out.user✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.port.out.user.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresentereu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.out.user.IUserResponseDTOPortPresenter
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.out.user, so a change to cleanarchitecture.application.port.out.user can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.port.out.user.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→16 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.adapter.out.persistence.mapper✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.adapter.out.persistence.mapper.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.AddressValueObjectMappereu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.mapper.UserDtoMapper
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.adapter.out.persistence.mapper, so a change to cleanarchitecture.adapter.out.persistence.mapper can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.adapter.out.persistence.mapper.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→20 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.in.user.iusecase✕
- Connections
- 2 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.application.port.in.user.iusecase.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserRegisterUseCaseeu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.application.port.in.user.iusecase.UserUpdateUseCase
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.application.port.in.user.iusecase, so a change to cleanarchitecture.application.port.in.user.iusecase can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.application.port.in.user.iusecase.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user uses a module listed above it, which is the healthy direction.
24→22 cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.adapter.out.persistence.service✕
- Connections
- 4 pairs of types, where a type in cleanarchitecture.application.domain.usecase.user uses a type in cleanarchitecture.adapter.out.persistence.service.
- The types involved
eu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdaptereu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserRegisterUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryUpdateAdaptereu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryQueryAdaptereu.getsoftware.cleanarchitecture.application.domain.usecase.user.UserUpdateUseCaseImpl→eu.getsoftware.cleanarchitecture.adapter.out.persistence.service.UserOutRepositoryUpdateAdapter
- Direction
- cleanarchitecture.application.domain.usecase.user uses cleanarchitecture.adapter.out.persistence.service, so a change to cleanarchitecture.adapter.out.persistence.service can break cleanarchitecture.application.domain.usecase.user, while a change to cleanarchitecture.application.domain.usecase.user can't break cleanarchitecture.adapter.out.persistence.service.
- Position
- Below the diagonal: cleanarchitecture.application.domain.usecase.user 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
Roadmap
Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with UserCrudController.java, UserRegisterUseCaseImpl.java, UserRootDomainEntity.java.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +6.7 pts | Low | Documentation Quality |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.7 pts | Low | ADR Quality |
| Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with UserCrudController.java, UserRegisterUseCaseImpl.java, UserRootDomainEntity.java. | +6.5 pts | Low | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.5 pts | Medium | CI/CD gates |
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +5.5 pts | Medium | Observability |
| 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. | +5.3 pts | Medium | Architecture documentation |
| Turn off Hibernate ddl-auto in production and let the versioned migrations own the schema. | +3.2 pts | Medium | Schema migrations |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.4 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/main/java/eu/getsoftware/cleanarchitecture/adapter/out/UserResponseDTOPortFormatter.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/java/eu/getsoftware/cleanarchitecture/application/domain/model/user/UserRootDomainEntity.java | 8.2 | Near-clean | Explicit Debt: TodoComment |
| src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerIntegrationTest.java | 9.1 | Near-clean | Test Quality: No direct assertions: testCreateUser |
| src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerMVCTest.java | 9.1 | Near-clean | Test Quality: No direct assertions: testCreateUser |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
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 66 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 — 66 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, 21 of 30 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 (2 contributor(s) across 177 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% 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 ToolchainServer (.). the service did not build — `sh ./gradlew --no-daemon -q classes` exited 1: Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain Caused by: java.lang.ClassNotFoundException: org.gradle.wrapper.GradleWrapperMain; runtime evidence skipped (launch chosen because build.gradle.kts applies the Spring Boot plugin and declares spring-boot-starter-web).
- 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.
- 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. Some of this repository's production types come from a frontend that does not declare whether a construction is produced or passed, which arm two needs to tell a producer from a mapping, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- 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, Kotlin 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.
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.
- 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.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D9 · Test Distribution
6 test methods: 6 unit, 0 integration, 0 BDD, 0 e2e.
D10 · Test Quality
0 skipped, 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6 tests (1 harness-style project(s) excluded from the assertion penalty).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 1424 LoC (0.1/KLoC) → score 9.8. 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 3 TodoComment finding(s) in Explicit Debt — start with UserResponseDTOPortFormatter.java (2), UserRootDomainEntity.java. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 11 document(s) read across 1 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
78 % of calls cross a namespace and 40 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D34 · Knowledge Freshness
8 of 8 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserCrudController.java. Counted over 8 of the 53 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 8 Orphaned file finding(s) in Knowledge Freshness — start with UserCrudController.java, UserRegisterUseCaseImpl.java, UserRootDomainEntity.java. — One of this dimension's main actionable groups (8 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
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 7 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.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
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
- `UserJpaRepository` is a repository over `UserMappedDBEntity`, 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 `UserMappedDBEntity` through its owning aggregate instead. — src/main/java/eu/getsoftware/cleanarchitecture/adapter/out/persistence/repository/UserJpaRepository.java:11
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 build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability
- No logging call was found in the 51 JVM production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
- This repository versions its schema (Liquibase), but Hibernate ddl-auto here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let Liquibase own the schema. — src/main/resources/application.yml:16
What to do
- Turn off Hibernate ddl-auto in production and let the versioned migrations own the schema.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
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/26 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 | 75% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 20% | Critical — gated by P1, P2, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 100% | Checked 3 of 9 | Strongest area. |
| Domain Modelling | 75% | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 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 — the service did not build — `sh ./gradlew --no-daemon -q classes` exited 1: Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain Caused by: java.lang.ClassNotFoundException: org.gradle.wrapper.GradleWrapperMain; runtime evidence skipped (launch chosen because build.gradle.kts applies the Spring Boot plugin and declares spring-boot-starter-web) 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
- D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Kotlin 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 (application), 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, .kt, 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (1424 LoC, 46 module-visible types across 24 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- M4 Documentation accuracy — Not applicable: the 11 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: src/main/java/eu/getsoftware/cleanarchitecture/Application.java:7 (@SpringBootApplication))
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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)
Serious — 7 finding(s)
- TodoComment src/main/java/eu/getsoftware/cleanarchitecture/application/domain/model/user/UserRootDomainEntity.java:100
- TodoComment src/main/java/eu/getsoftware/cleanarchitecture/adapter/out/UserResponseDTOPortFormatter.java:15
- TodoComment src/main/java/eu/getsoftware/cleanarchitecture/adapter/out/UserResponseDTOPortFormatter.java:31
- Repository for a non-root entity: UserJpaRepository → UserMappedDBEntity src/main/java/eu/getsoftware/cleanarchitecture/adapter/out/persistence/repository/UserJpaRepository.java:11
- No CI pipeline
- No structured logging
- Schema created by Hibernate ddl-auto outside the migrations src/main/resources/application.yml:16
Minor — 23 finding(s)
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserCrudController.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/usecase/user/UserRegisterUseCaseImpl.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/model/user/UserRootDomainEntity.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/usecase/user/UserUpdateUseCaseImpl.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/usecase/user/service/GenericOutRepositoryQueryAdapter.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/main/config/InfrastructureAdapterConfiguration.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/usecase/UseCasePresenterHandlerAspect.java:1
- Orphaned file src/main/java/eu/getsoftware/cleanarchitecture/application/domain/model/modelinnerservice/GenericRepositoryServiceAbstr.kt:1
- No direct assertions: testCreateUser src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerIntegrationTest.java:44
- No direct assertions: testFindById src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerIntegrationTest.java:58
- No direct assertions: testUpdateAddress src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerIntegrationTest.java:66
- No direct assertions: testCreateUser src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerMVCTest.java:33
- No direct assertions: testFindById src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerMVCTest.java:49
- No direct assertions: testUpdateAddress src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerMVCTest.java:66
- Test project verifies nothing: eu.getsoftware.cleanarchitecture src/test/java/eu/getsoftware/cleanarchitecture/adapter/in/web/controller/UserRegisterControllerIntegrationTest.java:44
- Documentation: no build, run or usage example README.md:1
- No ADRs found
- High interface indirection
- Orphaned files with no living knowledge
- No ADRs
- No SAST
- No changelog
- Java packages are not null-marked everywhere
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-d86c3d6365f645e1b426b408aaf9cb6d/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d86c3d6365f645e1b426b408aaf9cb6d/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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 | — |