Executive summary
jgabrielfreitas/ktor-hexagonal-benchmark falls short of our standard for production because two passwords or keys sit in the current code and we found no automated security scanning of the code, its secrets or its dependencies. It scores 49 out of 100 and is rated Weak, and seven of its eight critical findings are security problems.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 8 points. Recording design decisions comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 54.
Three settings leave the servers or containers unsafe. Two passwords or keys are open to anyone who can read the repository, and two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings, replacing each exposed password or key and pinning each tool to an exact version would close these risks. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 1,162 lines, about €1,300 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 49 to about 54.
New since the last survey: 1 finding
- Data Protection · No data-protection/encryption secondary/database-layer/src/main/resources/db/migration/V002__create_user.sql
Fixed since the last survey: 1 finding
- Data Protection · No data-protection/encryption secondary/database-layer/src/main/kotlin/com/quick/tor/database/dbo/Users.kt
Rebuild cost: about €1,300 · Estimate
| Cost to rebuild | €420 to €2,100, for 7 to 22 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, 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 49. 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,162 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 tor | 2 tor.common | 3 tor.common.exceptions | 4 tor.commons.exceptions | 5 tor.config | 6 tor.database | 7 tor.database.commons.extentions | 8 tor.infrastructure | 9 tor.log | 10 tor.producer | 11 tor.producer.dto | 12 tor.usecases.user.model | 13 tor.controller | 14 tor.controller.user.dto | 15 tor.database.commons | 16 tor.database.dbo | 17 tor.infrastructure.Acks | 18 tor.infrastructure.BatchSize | 19 tor.infrastructure.CommandStatus | 20 tor.infrastructure.Compression | 21 tor.infrastructure.OffsetBehaviour | 22 tor.infrastructure.consumer | 23 tor.infrastructure.producer | 24 tor.kafka | 25 tor.usecases.user.port.primary | 26 tor.usecases.user.port.secondary | 27 tor.controller.health | 28 tor.controller.user | 29 tor.database.repository | 30 tor.hello.controller | 31 tor.kafka.consumer | 32 tor.producer.adapter | 33 tor.usecases.user | 34 tor.database.adapters | 35 tor.database.repository.impl |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 tor | |||||||||||||||||||||||||||||||||||
| 2 tor.common | |||||||||||||||||||||||||||||||||||
| 3 tor.common.exceptions | |||||||||||||||||||||||||||||||||||
| 4 tor.commons.exceptions | |||||||||||||||||||||||||||||||||||
| 5 tor.config | |||||||||||||||||||||||||||||||||||
| 6 tor.database | |||||||||||||||||||||||||||||||||||
| 7 tor.database.commons.extentions | |||||||||||||||||||||||||||||||||||
| 8 tor.infrastructure | |||||||||||||||||||||||||||||||||||
| 9 tor.log | |||||||||||||||||||||||||||||||||||
| 10 tor.producer | |||||||||||||||||||||||||||||||||||
| 11 tor.producer.dto | |||||||||||||||||||||||||||||||||||
| 12 tor.usecases.user.model | |||||||||||||||||||||||||||||||||||
| 13 tor.controller | 1 | ||||||||||||||||||||||||||||||||||
| 14 tor.controller.user.dto | 1 | ||||||||||||||||||||||||||||||||||
| 15 tor.database.commons | 1 | ||||||||||||||||||||||||||||||||||
| 16 tor.database.dbo | 2 | 2 | |||||||||||||||||||||||||||||||||
| 17 tor.infrastructure.Acks | 3 | ||||||||||||||||||||||||||||||||||
| 18 tor.infrastructure.BatchSize | 4 | ||||||||||||||||||||||||||||||||||
| 19 tor.infrastructure.CommandStatus | 4 | ||||||||||||||||||||||||||||||||||
| 20 tor.infrastructure.Compression | 5 | ||||||||||||||||||||||||||||||||||
| 21 tor.infrastructure.OffsetBehaviour | 3 | ||||||||||||||||||||||||||||||||||
| 22 tor.infrastructure.consumer | 1 | ||||||||||||||||||||||||||||||||||
| 23 tor.infrastructure.producer | 3 | ||||||||||||||||||||||||||||||||||
| 24 tor.kafka | 1 | ||||||||||||||||||||||||||||||||||
| 25 tor.usecases.user.port.primary | 1 | ||||||||||||||||||||||||||||||||||
| 26 tor.usecases.user.port.secondary | 3 | ||||||||||||||||||||||||||||||||||
| 27 tor.controller.health | 1 | 1 | |||||||||||||||||||||||||||||||||
| 28 tor.controller.user | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 tor.database.repository | 2 | ||||||||||||||||||||||||||||||||||
| 30 tor.hello.controller | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 tor.kafka.consumer | 1 | 1 | |||||||||||||||||||||||||||||||||
| 32 tor.producer.adapter | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 tor.usecases.user | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||
| 34 tor.database.adapters | 2 | 2 | 2 | 2 | |||||||||||||||||||||||||||||||
| 35 tor.database.repository.impl | 2 | 2 | 2 | 2 |
13→9 tor.controller uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.controller uses a type in tor.log.
- The types involved
com.quick.tor.controller.BaseController→com.quick.tor.log.Logger
- Direction
- tor.controller uses tor.log, so a change to tor.log can break tor.controller, while a change to tor.controller can't break tor.log.
- Position
- Below the diagonal: tor.controller uses a module listed above it, which is the healthy direction.
14→12 tor.controller.user.dto uses tor.usecases.user.model✕
- Connections
- 1 pair of types, where a type in tor.controller.user.dto uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.controller.user.dto.UserDTO→com.quick.tor.usecases.user.model.User
- Direction
- tor.controller.user.dto uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.controller.user.dto, while a change to tor.controller.user.dto can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.controller.user.dto uses a module listed above it, which is the healthy direction.
15→1 tor.database.commons uses tor✕
- Connections
- 1 pair of types, where a type in tor.database.commons uses a type in tor.
- The types involved
com.quick.tor.database.commons.TransactionServiceImpl→com.quick.tor.TransactionService
- Direction
- tor.database.commons uses tor, so a change to tor can break tor.database.commons, while a change to tor.database.commons can't break tor.
- Position
- Below the diagonal: tor.database.commons uses a module listed above it, which is the healthy direction.
16→7 tor.database.dbo uses tor.database.commons.extentions✕
- Connections
- 2 pairs of types, where a type in tor.database.dbo uses a type in tor.database.commons.extentions.
- The types involved
com.quick.tor.database.dbo.Events→com.quick.tor.database.commons.extentions.StringIdTablecom.quick.tor.database.dbo.Users→com.quick.tor.database.commons.extentions.StringIdTable
- Direction
- tor.database.dbo uses tor.database.commons.extentions, so a change to tor.database.commons.extentions can break tor.database.dbo, while a change to tor.database.dbo can't break tor.database.commons.extentions.
- Position
- Below the diagonal: tor.database.dbo uses a module listed above it, which is the healthy direction.
16→12 tor.database.dbo uses tor.usecases.user.model✕
- Connections
- 2 pairs of types, where a type in tor.database.dbo uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.database.dbo.EventDBO→com.quick.tor.usecases.user.model.UserEventcom.quick.tor.database.dbo.UserDBO→com.quick.tor.usecases.user.model.User
- Direction
- tor.database.dbo uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.database.dbo, while a change to tor.database.dbo can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.database.dbo uses a module listed above it, which is the healthy direction.
17→8 tor.infrastructure.Acks uses tor.infrastructure✕
- Connections
- 3 pairs of types, where a type in tor.infrastructure.Acks uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.Acks.All→com.quick.tor.infrastructure.Ackscom.quick.tor.infrastructure.Acks.One→com.quick.tor.infrastructure.Ackscom.quick.tor.infrastructure.Acks.Zero→com.quick.tor.infrastructure.Acks
- Direction
- tor.infrastructure.Acks uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.Acks, while a change to tor.infrastructure.Acks can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.Acks uses a module listed above it, which is the healthy direction.
18→8 tor.infrastructure.BatchSize uses tor.infrastructure✕
- Connections
- 4 pairs of types, where a type in tor.infrastructure.BatchSize uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.BatchSize.OneHundredAndTwentyEight→com.quick.tor.infrastructure.BatchSizecom.quick.tor.infrastructure.BatchSize.Sixteen→com.quick.tor.infrastructure.BatchSizecom.quick.tor.infrastructure.BatchSize.SixtyFour→com.quick.tor.infrastructure.BatchSizecom.quick.tor.infrastructure.BatchSize.ThirtyTwo→com.quick.tor.infrastructure.BatchSize
- Direction
- tor.infrastructure.BatchSize uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.BatchSize, while a change to tor.infrastructure.BatchSize can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.BatchSize uses a module listed above it, which is the healthy direction.
19→8 tor.infrastructure.CommandStatus uses tor.infrastructure✕
- Connections
- 4 pairs of types, where a type in tor.infrastructure.CommandStatus uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.CommandStatus.Closed→com.quick.tor.infrastructure.CommandStatuscom.quick.tor.infrastructure.CommandStatus.Error→com.quick.tor.infrastructure.CommandStatuscom.quick.tor.infrastructure.CommandStatus.Open→com.quick.tor.infrastructure.CommandStatuscom.quick.tor.infrastructure.CommandStatus.Processing→com.quick.tor.infrastructure.CommandStatus
- Direction
- tor.infrastructure.CommandStatus uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.CommandStatus, while a change to tor.infrastructure.CommandStatus can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.CommandStatus uses a module listed above it, which is the healthy direction.
20→8 tor.infrastructure.Compression uses tor.infrastructure✕
- Connections
- 5 pairs of types, where a type in tor.infrastructure.Compression uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.Compression.Gzip→com.quick.tor.infrastructure.Compressioncom.quick.tor.infrastructure.Compression.None→com.quick.tor.infrastructure.Compressioncom.quick.tor.infrastructure.Compression.Snappy→com.quick.tor.infrastructure.Compressioncom.quick.tor.infrastructure.Compression.lz4→com.quick.tor.infrastructure.Compressioncom.quick.tor.infrastructure.Compression.zstd→com.quick.tor.infrastructure.Compression
- Direction
- tor.infrastructure.Compression uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.Compression, while a change to tor.infrastructure.Compression can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.Compression uses a module listed above it, which is the healthy direction.
21→8 tor.infrastructure.OffsetBehaviour uses tor.infrastructure✕
- Connections
- 3 pairs of types, where a type in tor.infrastructure.OffsetBehaviour uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.OffsetBehaviour.Earliest→com.quick.tor.infrastructure.OffsetBehaviourcom.quick.tor.infrastructure.OffsetBehaviour.Latest→com.quick.tor.infrastructure.OffsetBehaviourcom.quick.tor.infrastructure.OffsetBehaviour.None→com.quick.tor.infrastructure.OffsetBehaviour
- Direction
- tor.infrastructure.OffsetBehaviour uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.OffsetBehaviour, while a change to tor.infrastructure.OffsetBehaviour can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.OffsetBehaviour uses a module listed above it, which is the healthy direction.
22→8 tor.infrastructure.consumer uses tor.infrastructure✕
- Connections
- 1 pair of types, where a type in tor.infrastructure.consumer uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.consumer.KafkaConsumerKt→com.quick.tor.infrastructure.OffsetBehaviour
- Direction
- tor.infrastructure.consumer uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.consumer, while a change to tor.infrastructure.consumer can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.consumer uses a module listed above it, which is the healthy direction.
23→8 tor.infrastructure.producer uses tor.infrastructure✕
- Connections
- 3 pairs of types, where a type in tor.infrastructure.producer uses a type in tor.infrastructure.
- The types involved
com.quick.tor.infrastructure.producer.KafkaProducerKt→com.quick.tor.infrastructure.Ackscom.quick.tor.infrastructure.producer.KafkaProducerKt→com.quick.tor.infrastructure.BatchSizecom.quick.tor.infrastructure.producer.KafkaProducerKt→com.quick.tor.infrastructure.Compression
- Direction
- tor.infrastructure.producer uses tor.infrastructure, so a change to tor.infrastructure can break tor.infrastructure.producer, while a change to tor.infrastructure.producer can't break tor.infrastructure.
- Position
- Below the diagonal: tor.infrastructure.producer uses a module listed above it, which is the healthy direction.
24→12 tor.kafka uses tor.usecases.user.model✕
- Connections
- 1 pair of types, where a type in tor.kafka uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.kafka.UserMessageDto→com.quick.tor.usecases.user.model.User
- Direction
- tor.kafka uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.kafka, while a change to tor.kafka can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.kafka uses a module listed above it, which is the healthy direction.
25→12 tor.usecases.user.port.primary uses tor.usecases.user.model✕
- Connections
- 1 pair of types, where a type in tor.usecases.user.port.primary uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.usecases.user.port.primary.UserPort→com.quick.tor.usecases.user.model.User
- Direction
- tor.usecases.user.port.primary uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.usecases.user.port.primary, while a change to tor.usecases.user.port.primary can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.usecases.user.port.primary uses a module listed above it, which is the healthy direction.
26→12 tor.usecases.user.port.secondary uses tor.usecases.user.model✕
- Connections
- 3 pairs of types, where a type in tor.usecases.user.port.secondary uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.usecases.user.port.secondary.UserDataAccessPort→com.quick.tor.usecases.user.model.Usercom.quick.tor.usecases.user.port.secondary.UserEventDataAccessPort→com.quick.tor.usecases.user.model.UserEventcom.quick.tor.usecases.user.port.secondary.UserNotificationPort→com.quick.tor.usecases.user.model.UserEvent
- Direction
- tor.usecases.user.port.secondary uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.usecases.user.port.secondary, while a change to tor.usecases.user.port.secondary can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.usecases.user.port.secondary uses a module listed above it, which is the healthy direction.
27→9 tor.controller.health uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.controller.health uses a type in tor.log.
- The types involved
com.quick.tor.controller.health.HealthCheckerController→com.quick.tor.log.Logger
- Direction
- tor.controller.health uses tor.log, so a change to tor.log can break tor.controller.health, while a change to tor.controller.health can't break tor.log.
- Position
- Below the diagonal: tor.controller.health uses a module listed above it, which is the healthy direction.
27→13 tor.controller.health uses tor.controller✕
- Connections
- 1 pair of types, where a type in tor.controller.health uses a type in tor.controller.
- The types involved
com.quick.tor.controller.health.HealthCheckerController→com.quick.tor.controller.BaseController
- Direction
- tor.controller.health uses tor.controller, so a change to tor.controller can break tor.controller.health, while a change to tor.controller.health can't break tor.controller.
- Position
- Below the diagonal: tor.controller.health uses a module listed above it, which is the healthy direction.
28→9 tor.controller.user uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.controller.user uses a type in tor.log.
- The types involved
com.quick.tor.controller.user.UserController→com.quick.tor.log.Logger
- Direction
- tor.controller.user uses tor.log, so a change to tor.log can break tor.controller.user, while a change to tor.controller.user can't break tor.log.
- Position
- Below the diagonal: tor.controller.user uses a module listed above it, which is the healthy direction.
28→13 tor.controller.user uses tor.controller✕
- Connections
- 1 pair of types, where a type in tor.controller.user uses a type in tor.controller.
- The types involved
com.quick.tor.controller.user.UserController→com.quick.tor.controller.BaseController
- Direction
- tor.controller.user uses tor.controller, so a change to tor.controller can break tor.controller.user, while a change to tor.controller.user can't break tor.controller.
- Position
- Below the diagonal: tor.controller.user uses a module listed above it, which is the healthy direction.
29→16 tor.database.repository uses tor.database.dbo✕
- Connections
- 2 pairs of types, where a type in tor.database.repository uses a type in tor.database.dbo.
- The types involved
com.quick.tor.database.repository.EventRepositoryPort→com.quick.tor.database.dbo.EventDBOcom.quick.tor.database.repository.UserRepositoryPort→com.quick.tor.database.dbo.UserDBO
- Direction
- tor.database.repository uses tor.database.dbo, so a change to tor.database.dbo can break tor.database.repository, while a change to tor.database.repository can't break tor.database.dbo.
- Position
- Below the diagonal: tor.database.repository uses a module listed above it, which is the healthy direction.
30→9 tor.hello.controller uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.hello.controller uses a type in tor.log.
- The types involved
com.quick.tor.hello.controller.HelloWorldController→com.quick.tor.log.Logger
- Direction
- tor.hello.controller uses tor.log, so a change to tor.log can break tor.hello.controller, while a change to tor.hello.controller can't break tor.log.
- Position
- Below the diagonal: tor.hello.controller uses a module listed above it, which is the healthy direction.
30→13 tor.hello.controller uses tor.controller✕
- Connections
- 1 pair of types, where a type in tor.hello.controller uses a type in tor.controller.
- The types involved
com.quick.tor.hello.controller.HelloWorldController→com.quick.tor.controller.BaseController
- Direction
- tor.hello.controller uses tor.controller, so a change to tor.controller can break tor.hello.controller, while a change to tor.hello.controller can't break tor.controller.
- Position
- Below the diagonal: tor.hello.controller uses a module listed above it, which is the healthy direction.
31→9 tor.kafka.consumer uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.kafka.consumer uses a type in tor.log.
- The types involved
com.quick.tor.kafka.consumer.UserRegisterKafkaConsumerKt→com.quick.tor.log.Logger
- Direction
- tor.kafka.consumer uses tor.log, so a change to tor.log can break tor.kafka.consumer, while a change to tor.kafka.consumer can't break tor.log.
- Position
- Below the diagonal: tor.kafka.consumer uses a module listed above it, which is the healthy direction.
31→25 tor.kafka.consumer uses tor.usecases.user.port.primary✕
- Connections
- 1 pair of types, where a type in tor.kafka.consumer uses a type in tor.usecases.user.port.primary.
- The types involved
com.quick.tor.kafka.consumer.UserRegisterKafkaConsumerKt→com.quick.tor.usecases.user.port.primary.UserPort
- Direction
- tor.kafka.consumer uses tor.usecases.user.port.primary, so a change to tor.usecases.user.port.primary can break tor.kafka.consumer, while a change to tor.kafka.consumer can't break tor.usecases.user.port.primary.
- Position
- Below the diagonal: tor.kafka.consumer uses a module listed above it, which is the healthy direction.
32→9 tor.producer.adapter uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.producer.adapter uses a type in tor.log.
- The types involved
com.quick.tor.producer.adapter.UserNotificationAdapter→com.quick.tor.log.Logger
- Direction
- tor.producer.adapter uses tor.log, so a change to tor.log can break tor.producer.adapter, while a change to tor.producer.adapter can't break tor.log.
- Position
- Below the diagonal: tor.producer.adapter uses a module listed above it, which is the healthy direction.
32→10 tor.producer.adapter uses tor.producer✕
- Connections
- 1 pair of types, where a type in tor.producer.adapter uses a type in tor.producer.
- The types involved
com.quick.tor.producer.adapter.UserNotificationAdapter→com.quick.tor.producer.KafkaProducerAdapter
- Direction
- tor.producer.adapter uses tor.producer, so a change to tor.producer can break tor.producer.adapter, while a change to tor.producer.adapter can't break tor.producer.
- Position
- Below the diagonal: tor.producer.adapter uses a module listed above it, which is the healthy direction.
32→12 tor.producer.adapter uses tor.usecases.user.model✕
- Connections
- 1 pair of types, where a type in tor.producer.adapter uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.producer.adapter.UserNotificationAdapter→com.quick.tor.usecases.user.model.UserEvent
- Direction
- tor.producer.adapter uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.producer.adapter, while a change to tor.producer.adapter can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.producer.adapter uses a module listed above it, which is the healthy direction.
32→26 tor.producer.adapter uses tor.usecases.user.port.secondary✕
- Connections
- 1 pair of types, where a type in tor.producer.adapter uses a type in tor.usecases.user.port.secondary.
- The types involved
com.quick.tor.producer.adapter.UserNotificationAdapter→com.quick.tor.usecases.user.port.secondary.UserNotificationPort
- Direction
- tor.producer.adapter uses tor.usecases.user.port.secondary, so a change to tor.usecases.user.port.secondary can break tor.producer.adapter, while a change to tor.producer.adapter can't break tor.usecases.user.port.secondary.
- Position
- Below the diagonal: tor.producer.adapter uses a module listed above it, which is the healthy direction.
33→1 tor.usecases.user uses tor✕
- Connections
- 1 pair of types, where a type in tor.usecases.user uses a type in tor.
- The types involved
com.quick.tor.usecases.user.UserUseCase→com.quick.tor.TransactionService
- Direction
- tor.usecases.user uses tor, so a change to tor can break tor.usecases.user, while a change to tor.usecases.user can't break tor.
- Position
- Below the diagonal: tor.usecases.user uses a module listed above it, which is the healthy direction.
33→9 tor.usecases.user uses tor.log✕
- Connections
- 1 pair of types, where a type in tor.usecases.user uses a type in tor.log.
- The types involved
com.quick.tor.usecases.user.UserUseCase→com.quick.tor.log.Logger
- Direction
- tor.usecases.user uses tor.log, so a change to tor.log can break tor.usecases.user, while a change to tor.usecases.user can't break tor.log.
- Position
- Below the diagonal: tor.usecases.user uses a module listed above it, which is the healthy direction.
33→12 tor.usecases.user uses tor.usecases.user.model✕
- Connections
- 1 pair of types, where a type in tor.usecases.user uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.usecases.user.UserUseCase→com.quick.tor.usecases.user.model.User
- Direction
- tor.usecases.user uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.usecases.user, while a change to tor.usecases.user can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.usecases.user uses a module listed above it, which is the healthy direction.
33→25 tor.usecases.user uses tor.usecases.user.port.primary✕
- Connections
- 1 pair of types, where a type in tor.usecases.user uses a type in tor.usecases.user.port.primary.
- The types involved
com.quick.tor.usecases.user.UserUseCase→com.quick.tor.usecases.user.port.primary.UserPort
- Direction
- tor.usecases.user uses tor.usecases.user.port.primary, so a change to tor.usecases.user.port.primary can break tor.usecases.user, while a change to tor.usecases.user can't break tor.usecases.user.port.primary.
- Position
- Below the diagonal: tor.usecases.user uses a module listed above it, which is the healthy direction.
33→26 tor.usecases.user uses tor.usecases.user.port.secondary✕
- Connections
- 3 pairs of types, where a type in tor.usecases.user uses a type in tor.usecases.user.port.secondary.
- The types involved
com.quick.tor.usecases.user.UserUseCase→com.quick.tor.usecases.user.port.secondary.UserDataAccessPortcom.quick.tor.usecases.user.UserUseCase→com.quick.tor.usecases.user.port.secondary.UserEventDataAccessPortcom.quick.tor.usecases.user.UserUseCase→com.quick.tor.usecases.user.port.secondary.UserNotificationPort
- Direction
- tor.usecases.user uses tor.usecases.user.port.secondary, so a change to tor.usecases.user.port.secondary can break tor.usecases.user, while a change to tor.usecases.user can't break tor.usecases.user.port.secondary.
- Position
- Below the diagonal: tor.usecases.user uses a module listed above it, which is the healthy direction.
34→9 tor.database.adapters uses tor.log✕
- Connections
- 2 pairs of types, where a type in tor.database.adapters uses a type in tor.log.
- The types involved
com.quick.tor.database.adapters.UserDataAccessAdapter→com.quick.tor.log.Loggercom.quick.tor.database.adapters.UserEventDataAccessAdapter→com.quick.tor.log.Logger
- Direction
- tor.database.adapters uses tor.log, so a change to tor.log can break tor.database.adapters, while a change to tor.database.adapters can't break tor.log.
- Position
- Below the diagonal: tor.database.adapters uses a module listed above it, which is the healthy direction.
34→12 tor.database.adapters uses tor.usecases.user.model✕
- Connections
- 2 pairs of types, where a type in tor.database.adapters uses a type in tor.usecases.user.model.
- The types involved
com.quick.tor.database.adapters.UserDataAccessAdapter→com.quick.tor.usecases.user.model.Usercom.quick.tor.database.adapters.UserEventDataAccessAdapter→com.quick.tor.usecases.user.model.UserEvent
- Direction
- tor.database.adapters uses tor.usecases.user.model, so a change to tor.usecases.user.model can break tor.database.adapters, while a change to tor.database.adapters can't break tor.usecases.user.model.
- Position
- Below the diagonal: tor.database.adapters uses a module listed above it, which is the healthy direction.
34→26 tor.database.adapters uses tor.usecases.user.port.secondary✕
- Connections
- 2 pairs of types, where a type in tor.database.adapters uses a type in tor.usecases.user.port.secondary.
- The types involved
com.quick.tor.database.adapters.UserDataAccessAdapter→com.quick.tor.usecases.user.port.secondary.UserDataAccessPortcom.quick.tor.database.adapters.UserEventDataAccessAdapter→com.quick.tor.usecases.user.port.secondary.UserEventDataAccessPort
- Direction
- tor.database.adapters uses tor.usecases.user.port.secondary, so a change to tor.usecases.user.port.secondary can break tor.database.adapters, while a change to tor.database.adapters can't break tor.usecases.user.port.secondary.
- Position
- Below the diagonal: tor.database.adapters uses a module listed above it, which is the healthy direction.
34→29 tor.database.adapters uses tor.database.repository✕
- Connections
- 2 pairs of types, where a type in tor.database.adapters uses a type in tor.database.repository.
- The types involved
com.quick.tor.database.adapters.UserDataAccessAdapter→com.quick.tor.database.repository.UserRepositoryPortcom.quick.tor.database.adapters.UserEventDataAccessAdapter→com.quick.tor.database.repository.EventRepositoryPort
- Direction
- tor.database.adapters uses tor.database.repository, so a change to tor.database.repository can break tor.database.adapters, while a change to tor.database.adapters can't break tor.database.repository.
- Position
- Below the diagonal: tor.database.adapters uses a module listed above it, which is the healthy direction.
35→1 tor.database.repository.impl uses tor✕
- Connections
- 2 pairs of types, where a type in tor.database.repository.impl uses a type in tor.
- The types involved
com.quick.tor.database.repository.impl.EventRepositoryMysqlAdapter→com.quick.tor.TransactionServicecom.quick.tor.database.repository.impl.UserRepositoryMysqlAdapter→com.quick.tor.TransactionService
- Direction
- tor.database.repository.impl uses tor, so a change to tor can break tor.database.repository.impl, while a change to tor.database.repository.impl can't break tor.
- Position
- Below the diagonal: tor.database.repository.impl uses a module listed above it, which is the healthy direction.
35→9 tor.database.repository.impl uses tor.log✕
- Connections
- 2 pairs of types, where a type in tor.database.repository.impl uses a type in tor.log.
- The types involved
com.quick.tor.database.repository.impl.EventRepositoryMysqlAdapter→com.quick.tor.log.Loggercom.quick.tor.database.repository.impl.UserRepositoryMysqlAdapter→com.quick.tor.log.Logger
- Direction
- tor.database.repository.impl uses tor.log, so a change to tor.log can break tor.database.repository.impl, while a change to tor.database.repository.impl can't break tor.log.
- Position
- Below the diagonal: tor.database.repository.impl uses a module listed above it, which is the healthy direction.
35→16 tor.database.repository.impl uses tor.database.dbo✕
- Connections
- 2 pairs of types, where a type in tor.database.repository.impl uses a type in tor.database.dbo.
- The types involved
com.quick.tor.database.repository.impl.EventRepositoryMysqlAdapter→com.quick.tor.database.dbo.EventDBOcom.quick.tor.database.repository.impl.UserRepositoryMysqlAdapter→com.quick.tor.database.dbo.UserDBO
- Direction
- tor.database.repository.impl uses tor.database.dbo, so a change to tor.database.dbo can break tor.database.repository.impl, while a change to tor.database.repository.impl can't break tor.database.dbo.
- Position
- Below the diagonal: tor.database.repository.impl uses a module listed above it, which is the healthy direction.
35→29 tor.database.repository.impl uses tor.database.repository✕
- Connections
- 2 pairs of types, where a type in tor.database.repository.impl uses a type in tor.database.repository.
- The types involved
com.quick.tor.database.repository.impl.EventRepositoryMysqlAdapter→com.quick.tor.database.repository.EventRepositoryPortcom.quick.tor.database.repository.impl.UserRepositoryMysqlAdapter→com.quick.tor.database.repository.UserRepositoryPort
- Direction
- tor.database.repository.impl uses tor.database.repository, so a change to tor.database.repository can break tor.database.repository.impl, while a change to tor.database.repository.impl can't break tor.database.repository.
- Position
- Below the diagonal: tor.database.repository.impl 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
| A05:2025 — Injection | 4 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2); Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +8.3 pts | Low | Secret Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.2 pts | Low | ADR Quality |
| Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with UserUseCase.kt, DatabaseModule.kt, build.gradle. | +5.5 pts | Low | Knowledge Freshness |
| Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.). | +8.6 pts | Medium | Data Protection |
| Resolve the 1 Banned license finding(s) in License Compliance. | +2.7 pts | Low | License Compliance |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.9 pts | Medium | Security & performance tooling |
| 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. | +3.1 pts | Medium | Architecture documentation |
| 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 |
|---|---|---|---|
| REDACTED | 0.7 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.7 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 2.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| domain/src/main/kotlin/com/quick/tor/usecases/user/UserUseCase.kt | 7.3 | Mixed | Explicit Debt: TodoComment |
| primary/rest/src/main/kotlin/com/quick/tor/common/ApplicationExtensions.kt | 8.2 | Near-clean | Explicit Debt: TodoComment |
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 56 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 — 56 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, 27 of 35 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — 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 (.kt) 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. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because jcenter.bintray.com — the registry that answers it — was asked and did not reply (the build stopped because jcenter.bintray.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add jcenter.bintray.com to the allowlist and re-run — not to build anything.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 76 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: 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.
- D32 Data Compliance (PII/GDPR) — 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. `secondary/database-layer/src/main/kotlin/com/quick/tor/database/repository/impl/UserRepositoryMysqlAdapter.kt` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Koin, whose lifetimes are not modelled 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.
- AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- 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.
- 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 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.
- IC1 Incompleteness & stubs — 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, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's 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.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (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.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
D5 · Coupling
9 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 8 of the 9 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
1 of 13 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 9 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 3 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 7 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
- Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 1162 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 UserUseCase.kt (2), ApplicationExtensions.kt. — One of this dimension's main actionable groups (3 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 8 build units (Gradle) flagged as possibly oversized/incoherent.
D27 · Navigability
92 % of calls cross a namespace and 78 % 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)
4 finding(s): 0 critical, 2 high, 2 medium, 0 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 144–145, line 146, line 147, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).
D31 · IaC & Container Security
11 finding(s): 0 critical, 3 high, 8 medium, 0 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 8 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
D34 · Knowledge Freshness
4 of 4 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is domain/src/main/kotlin/com/quick/tor/usecases/user/UserUseCase.kt. Counted over 4 of the 61 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 4 Orphaned file finding(s) in Knowledge Freshness — start with UserUseCase.kt, DatabaseModule.kt, build.gradle. — One of this dimension's main actionable groups (4 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 22 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
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX7 · Slice cohesion
C1 · Data Protection
- No encryption usage (javax.crypto's Cipher in ENCRYPT_MODE, Tink, Jasypt, Spring Security's Encryptors, Jetpack Security's EncryptedSharedPreferences or EncryptedFile, the Android Keystore, SQLCipher, pgcrypto) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — secondary/database-layer/src/main/resources/db/migration/V002__create_user.sql:4
What to do
- Encrypt sensitive data at rest (open the store encrypted — SQLCipher's SupportFactory for Room, a Realm encryptionKey — or encrypt the fields with Tink's AEAD or an AES/GCM Cipher, or use Jetpack Security's EncryptedSharedPreferences on Android) keeping its key in the Android Keystore or a vault, and manage server-side keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
- Enforce HTTPS on the server that receives this data: terminate TLS in it (Ktor's sslConnector, Spring's server.ssl and requiresSecure, Netty's SslContextBuilder.forServer) and send Strict-Transport-Security (Ktor's HttpsRedirect), or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
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.
- Add a README to the 8 of 8 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- Only 6/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `main`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry-java or Micrometer) and a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 664 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. — REDACTED:9
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P8 · Schema migrations
PF3 · Async & latency hygiene
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
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
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 99% | Exemplary | Solid. |
| Architecture | 88% | Strong | Solid. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 39% | Weak — gated by D13, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 40% | Weak — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — an Exposed table, a data class, a Room entity or a SQL migration's table named for it — Hibernate Envers' @Audited, a JPA entity listener, Hibernate event listener or jOOQ RecordListener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- D10 Test Quality — ~91 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Dependency currency not established — jcenter.bintray.com did not answer
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; 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. 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 .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
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 value object(s))
- 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.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM source (service entry point: main/src/main/kotlin/com/quick/tor/ApplicationMain.kt:21 (embeddedServer())
- 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.
- 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 Kotlin was 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 Kotlin request outside a suspend function has no caller's cancellation to honour
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: mysql:mysql-connector-java
Serious — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment primary/rest/src/main/kotlin/com/quick/tor/common/ApplicationExtensions.kt:14
- TodoComment domain/src/main/kotlin/com/quick/tor/usecases/user/UserUseCase.kt:38
- TodoComment domain/src/main/kotlin/com/quick/tor/usecases/user/UserUseCase.kt:68
- REDACTED
- REDACTED
- No data-protection/encryption secondary/database-layer/src/main/resources/db/migration/V002__create_user.sql:4
- REDACTED
Minor — 12 finding(s)
- Orphaned file domain/src/main/kotlin/com/quick/tor/usecases/user/UserUseCase.kt:1
- Orphaned file secondary/database-layer/src/main/kotlin/com/quick/tor/database/DatabaseModule.kt:1
- Orphaned file build.gradle:1
- Orphaned file infrastructure/kafka/src/main/kotlin/com/quick/tor/infrastructure/producer/KafkaProducer.kt:1
- No ADRs found
- High interface indirection
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- Logging is not universal
- No SAST REDACTED:9
- No rollback/health safety
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-920fd5f2b13b499aa74b312743b19ed7/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-920fd5f2b13b499aa74b312743b19ed7/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 . | 4 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `secondary/database-layer/src/main/kotlin/com/quick/tor/database/repository/impl/UserRepositoryMysqlAdapter.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure 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 | — |