Executive summary
lovung/GoCleanArchitecture is rated At risk because critical security findings are open. It scores 60 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 52, is the weakest lens and counts most in the score. The best first step for the work it takes is pinning the dependencies to tagged releases, worth about 4 points. Documenting the recovery plan would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 65.
Four known security holes in the packages the code depends on can be used by attackers. Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two pipeline steps run downloads nobody checks. Updating the vulnerable packages, pinning each tool to an exact version and checking each download against a checksum would close these risks. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 1,629 lines, about €3,900 to rebuild.
If Production Readiness rose from 52 to 70, the lowest score rated Strong, the score would rise from 60 to about 65.
Rebuild cost: about €3,900 · Estimate
| Cost to rebuild | €1,300 to €6,500, for 22 to 69 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 60. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Very small: 1,629 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 com/lovung/GoCleanArchitecture/app/config | 2 com/lovung/GoCleanArchitecture/app/internal/appctx | 3 com/lovung/GoCleanArchitecture/app/internal/apperror | 4 com/lovung/GoCleanArchitecture/app/internal/domain/entity | 5 com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter | 6 com/lovung/GoCleanArchitecture/app/internal/pkg/gormutil | 7 com/lovung/GoCleanArchitecture/app/internal/transaction | 8 com/lovung/GoCleanArchitecture/app/internal/usecase/dto | 9 com/lovung/GoCleanArchitecture/pkg/copier | 10 com/lovung/GoCleanArchitecture/pkg/gormer | 11 com/lovung/GoCleanArchitecture/pkg/hasher | 12 com/lovung/GoCleanArchitecture/pkg/jwtutil | 13 com/lovung/GoCleanArchitecture/pkg/logger | 14 com/lovung/GoCleanArchitecture/pkg/storage | 15 com/lovung/GoCleanArchitecture/pkg/testhelper | 16 com/lovung/GoCleanArchitecture/app/external/api | 17 com/lovung/GoCleanArchitecture/app/internal/domain/repository | 18 com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware | 19 com/lovung/GoCleanArchitecture/app/internal/usecase | 20 com/lovung/GoCleanArchitecture/cmd/services/core | 21 com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo | 22 com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler | 23 com/lovung/GoCleanArchitecture/app/internal/usecase/interactor | 24 com/lovung/GoCleanArchitecture/app/registry |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/lovung/GoCleanArchitecture/app/config | ||||||||||||||||||||||||
| 2 com/lovung/GoCleanArchitecture/app/internal/appctx | ||||||||||||||||||||||||
| 3 com/lovung/GoCleanArchitecture/app/internal/apperror | ||||||||||||||||||||||||
| 4 com/lovung/GoCleanArchitecture/app/internal/domain/entity | ||||||||||||||||||||||||
| 5 com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter | ||||||||||||||||||||||||
| 6 com/lovung/GoCleanArchitecture/app/internal/pkg/gormutil | ||||||||||||||||||||||||
| 7 com/lovung/GoCleanArchitecture/app/internal/transaction | ||||||||||||||||||||||||
| 8 com/lovung/GoCleanArchitecture/app/internal/usecase/dto | ||||||||||||||||||||||||
| 9 com/lovung/GoCleanArchitecture/pkg/copier | ||||||||||||||||||||||||
| 10 com/lovung/GoCleanArchitecture/pkg/gormer | ||||||||||||||||||||||||
| 11 com/lovung/GoCleanArchitecture/pkg/hasher | ||||||||||||||||||||||||
| 12 com/lovung/GoCleanArchitecture/pkg/jwtutil | ||||||||||||||||||||||||
| 13 com/lovung/GoCleanArchitecture/pkg/logger | ||||||||||||||||||||||||
| 14 com/lovung/GoCleanArchitecture/pkg/storage | ||||||||||||||||||||||||
| 15 com/lovung/GoCleanArchitecture/pkg/testhelper | ||||||||||||||||||||||||
| 16 com/lovung/GoCleanArchitecture/app/external/api | 1 | |||||||||||||||||||||||
| 17 com/lovung/GoCleanArchitecture/app/internal/domain/repository | 1 | |||||||||||||||||||||||
| 18 com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware | 1 | 2 | ||||||||||||||||||||||
| 19 com/lovung/GoCleanArchitecture/app/internal/usecase | 2 | |||||||||||||||||||||||
| 20 com/lovung/GoCleanArchitecture/cmd/services/core | 2 | |||||||||||||||||||||||
| 21 com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo | 1 | 1 | 1 | |||||||||||||||||||||
| 22 com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler | 1 | 2 | ||||||||||||||||||||||
| 23 com/lovung/GoCleanArchitecture/app/internal/usecase/interactor | 2 | 2 | 1 | |||||||||||||||||||||
| 24 com/lovung/GoCleanArchitecture/app/registry | 1 | 1 |
16→1 com/lovung/GoCleanArchitecture/app/external/api uses com/lovung/GoCleanArchitecture/app/config✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/external/api uses a type in com/lovung/GoCleanArchitecture/app/config.
- The types involved
github.com/lovung/GoCleanArchitecture/app/external/api.api→github.com/lovung/GoCleanArchitecture/app/config.Config
- Direction
- com/lovung/GoCleanArchitecture/app/external/api uses com/lovung/GoCleanArchitecture/app/config, so a change to com/lovung/GoCleanArchitecture/app/config can break com/lovung/GoCleanArchitecture/app/external/api, while a change to com/lovung/GoCleanArchitecture/app/external/api can't break com/lovung/GoCleanArchitecture/app/config.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/external/api uses a module listed above it, which is the healthy direction.
17→4 com/lovung/GoCleanArchitecture/app/internal/domain/repository uses com/lovung/GoCleanArchitecture/app/internal/domain/entity✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/domain/repository uses a type in com/lovung/GoCleanArchitecture/app/internal/domain/entity.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/domain/repository.UserRepository→github.com/lovung/GoCleanArchitecture/app/internal/domain/entity.User
- Direction
- com/lovung/GoCleanArchitecture/app/internal/domain/repository uses com/lovung/GoCleanArchitecture/app/internal/domain/entity, so a change to com/lovung/GoCleanArchitecture/app/internal/domain/entity can break com/lovung/GoCleanArchitecture/app/internal/domain/repository, while a change to com/lovung/GoCleanArchitecture/app/internal/domain/repository can't break com/lovung/GoCleanArchitecture/app/internal/domain/entity.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/domain/repository uses a module listed above it, which is the healthy direction.
18→5 com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.middleware→github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.Response
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter, so a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter can break com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware can't break com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses a module listed above it, which is the healthy direction.
18→7 com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses com/lovung/GoCleanArchitecture/app/internal/transaction✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses a type in com/lovung/GoCleanArchitecture/app/internal/transaction.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.TransactionMiddleware→github.com/lovung/GoCleanArchitecture/app/internal/transaction.Managergithub.com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.middleware→github.com/lovung/GoCleanArchitecture/app/internal/transaction.Manager
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses com/lovung/GoCleanArchitecture/app/internal/transaction, so a change to com/lovung/GoCleanArchitecture/app/internal/transaction can break com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware can't break com/lovung/GoCleanArchitecture/app/internal/transaction.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware uses a module listed above it, which is the healthy direction.
19→8 com/lovung/GoCleanArchitecture/app/internal/usecase uses com/lovung/GoCleanArchitecture/app/internal/usecase/dto✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/app/internal/usecase uses a type in com/lovung/GoCleanArchitecture/app/internal/usecase/dto.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/usecase.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/usecase/dto.CreateUserRequestgithub.com/lovung/GoCleanArchitecture/app/internal/usecase.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/usecase/dto.OneUserResponse
- Direction
- com/lovung/GoCleanArchitecture/app/internal/usecase uses com/lovung/GoCleanArchitecture/app/internal/usecase/dto, so a change to com/lovung/GoCleanArchitecture/app/internal/usecase/dto can break com/lovung/GoCleanArchitecture/app/internal/usecase, while a change to com/lovung/GoCleanArchitecture/app/internal/usecase can't break com/lovung/GoCleanArchitecture/app/internal/usecase/dto.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/usecase uses a module listed above it, which is the healthy direction.
20→1 com/lovung/GoCleanArchitecture/cmd/services/core uses com/lovung/GoCleanArchitecture/app/config✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/cmd/services/core uses a type in com/lovung/GoCleanArchitecture/app/config.
- The types involved
github.com/lovung/GoCleanArchitecture/cmd/services/core.application→github.com/lovung/GoCleanArchitecture/app/config.Configgithub.com/lovung/GoCleanArchitecture/cmd/services/core.application→github.com/lovung/GoCleanArchitecture/app/config.MySQL
- Direction
- com/lovung/GoCleanArchitecture/cmd/services/core uses com/lovung/GoCleanArchitecture/app/config, so a change to com/lovung/GoCleanArchitecture/app/config can break com/lovung/GoCleanArchitecture/cmd/services/core, while a change to com/lovung/GoCleanArchitecture/cmd/services/core can't break com/lovung/GoCleanArchitecture/app/config.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/cmd/services/core uses a module listed above it, which is the healthy direction.
21→4 com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/domain/entity✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a type in com/lovung/GoCleanArchitecture/app/internal/domain/entity.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo.UserRepository→github.com/lovung/GoCleanArchitecture/app/internal/domain/entity.User
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/domain/entity, so a change to com/lovung/GoCleanArchitecture/app/internal/domain/entity can break com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo can't break com/lovung/GoCleanArchitecture/app/internal/domain/entity.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a module listed above it, which is the healthy direction.
21→7 com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/transaction✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a type in com/lovung/GoCleanArchitecture/app/internal/transaction.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo.TxnDataSQL→github.com/lovung/GoCleanArchitecture/app/internal/transaction.Manager
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/transaction, so a change to com/lovung/GoCleanArchitecture/app/internal/transaction can break com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo can't break com/lovung/GoCleanArchitecture/app/internal/transaction.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a module listed above it, which is the healthy direction.
21→17 com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/domain/repository✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a type in com/lovung/GoCleanArchitecture/app/internal/domain/repository.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo.UserRepository→github.com/lovung/GoCleanArchitecture/app/internal/domain/repository.UserRepository
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses com/lovung/GoCleanArchitecture/app/internal/domain/repository, so a change to com/lovung/GoCleanArchitecture/app/internal/domain/repository can break com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo can't break com/lovung/GoCleanArchitecture/app/internal/domain/repository.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/persistence/rdbms/gormrepo uses a module listed above it, which is the healthy direction.
22→5 com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.BaseHandler→github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.MetaResponse
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter, so a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter can break com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler can't break com/lovung/GoCleanArchitecture/app/internal/interface/restful/presenter.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses a module listed above it, which is the healthy direction.
22→19 com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses com/lovung/GoCleanArchitecture/app/internal/usecase✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses a type in com/lovung/GoCleanArchitecture/app/internal/usecase.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.AuthHandler→github.com/lovung/GoCleanArchitecture/app/internal/usecase.UserUseCasegithub.com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.handler→github.com/lovung/GoCleanArchitecture/app/internal/usecase.UserUseCase
- Direction
- com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses com/lovung/GoCleanArchitecture/app/internal/usecase, so a change to com/lovung/GoCleanArchitecture/app/internal/usecase can break com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler, while a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler can't break com/lovung/GoCleanArchitecture/app/internal/usecase.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler uses a module listed above it, which is the healthy direction.
23→8 com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/usecase/dto✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a type in com/lovung/GoCleanArchitecture/app/internal/usecase/dto.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/usecase/interactor.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/usecase/dto.CreateUserRequestgithub.com/lovung/GoCleanArchitecture/app/internal/usecase/interactor.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/usecase/dto.OneUserResponse
- Direction
- com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/usecase/dto, so a change to com/lovung/GoCleanArchitecture/app/internal/usecase/dto can break com/lovung/GoCleanArchitecture/app/internal/usecase/interactor, while a change to com/lovung/GoCleanArchitecture/app/internal/usecase/interactor can't break com/lovung/GoCleanArchitecture/app/internal/usecase/dto.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a module listed above it, which is the healthy direction.
23→17 com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/domain/repository✕
- Connections
- 2 pairs of types, where a type in com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a type in com/lovung/GoCleanArchitecture/app/internal/domain/repository.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/usecase/interactor.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/domain/repository.UserRepositorygithub.com/lovung/GoCleanArchitecture/app/internal/usecase/interactor.interactor→github.com/lovung/GoCleanArchitecture/app/internal/domain/repository.UserRepository
- Direction
- com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/domain/repository, so a change to com/lovung/GoCleanArchitecture/app/internal/domain/repository can break com/lovung/GoCleanArchitecture/app/internal/usecase/interactor, while a change to com/lovung/GoCleanArchitecture/app/internal/usecase/interactor can't break com/lovung/GoCleanArchitecture/app/internal/domain/repository.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a module listed above it, which is the healthy direction.
23→19 com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/usecase✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a type in com/lovung/GoCleanArchitecture/app/internal/usecase.
- The types involved
github.com/lovung/GoCleanArchitecture/app/internal/usecase/interactor.UserUseCase→github.com/lovung/GoCleanArchitecture/app/internal/usecase.UserUseCase
- Direction
- com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses com/lovung/GoCleanArchitecture/app/internal/usecase, so a change to com/lovung/GoCleanArchitecture/app/internal/usecase can break com/lovung/GoCleanArchitecture/app/internal/usecase/interactor, while a change to com/lovung/GoCleanArchitecture/app/internal/usecase/interactor can't break com/lovung/GoCleanArchitecture/app/internal/usecase.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/internal/usecase/interactor uses a module listed above it, which is the healthy direction.
24→18 com/lovung/GoCleanArchitecture/app/registry uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/registry uses a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.
- The types involved
github.com/lovung/GoCleanArchitecture/app/registry.registry→github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.TransactionMiddleware
- Direction
- com/lovung/GoCleanArchitecture/app/registry uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware, so a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware can break com/lovung/GoCleanArchitecture/app/registry, while a change to com/lovung/GoCleanArchitecture/app/registry can't break com/lovung/GoCleanArchitecture/app/internal/interface/restful/middleware.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/registry uses a module listed above it, which is the healthy direction.
24→22 com/lovung/GoCleanArchitecture/app/registry uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler✕
- Connections
- 1 pair of types, where a type in com/lovung/GoCleanArchitecture/app/registry uses a type in com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.
- The types involved
github.com/lovung/GoCleanArchitecture/app/registry.registry→github.com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.AuthHandler
- Direction
- com/lovung/GoCleanArchitecture/app/registry uses com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler, so a change to com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler can break com/lovung/GoCleanArchitecture/app/registry, while a change to com/lovung/GoCleanArchitecture/app/registry can't break com/lovung/GoCleanArchitecture/app/internal/interface/restful/handler.
- Position
- Below the diagonal: com/lovung/GoCleanArchitecture/app/registry uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene; Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +4.4 pts | Low | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.0 pts | Low | ADR Quality |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +5.3 pts | Medium | DR & Backup |
| Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters). | +3.2 pts | Medium | Encapsulated state |
| Enable Dependabot/Renovate or a dependency-review gate. | +3.0 pts | Medium | Security & performance tooling |
| 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. | +3.0 pts | Medium | Deployment & Rollback |
| 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. | +2.8 pts | Medium | Architecture documentation |
| Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs. | +2.4 pts | Medium | Strongly-typed ids |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| app/internal/interface/restful/handler/auth_handler_test.go | 7.3 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| pkg/jwtutil/jwt.go | 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 50 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 — 50 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 52 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 READ here — but this repository measures it: a coverage step in CI (`go test -v -coverpkg=./... -covermode=count ${PKG_LIST} -cov…`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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 (`go test -coverprofile=coverage.out ./...`) 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.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's REDACTED declares a Go language version older than 1.17 (or none), and before 1.17 a REDACTED lists only the modules version selection needs, not every module the build compiles. The licences are resolved per module version, so grading the modules that file happens to list would be a verdict over part of the dependency graph. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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. Too few commits for a meaningful bus factor (32 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- 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 a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (32 commit(s) sampled).
- 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- 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 Go 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 Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
- X19 Unrestored process-global state — 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, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP 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.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- X22 Contradicted release guard — 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Go 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.
- X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP 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.
- 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.
- X25 Inert configuration knob — 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, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby 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.
- X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go 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.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — 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, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust 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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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 function(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 function(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 over-large unit(s) detected — types, modules or files that carry too much.
D4 · Code Duplication
0 duplicated block group(s) detected.
D6 · Cohesion (LCOM4)
0 of 5 classes have LCOM4 above 3.
D9 · Test Distribution
18 test methods: 18 unit, 0 integration, 0 BDD, 0 e2e. The Go suite contributes 18 test case(s) across 11 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/lovung/GoCleanArchitecture): measured (0 flaky).
D12 · Dependency Hygiene
16 outdated, 0 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and REDACTED there.
What to do
- Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
3 deducted task-comment markers across 1629 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 auth_handler_test.go (2), jwt.go. — 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. 2 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 1 build units (Go) flagged as possibly oversized/incoherent.
D27 · Navigability
68 % of calls cross a namespace and 12 % go through an interface, but 58 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 5 high, 3 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.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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).
D30 · Dependency Vulnerabilities
7 finding(s): 2 critical, 2 high, 3 medium, 0 low.
What to do
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
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 0 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
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM2 · Strongly-typed ids
- `User.ID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — app/internal/domain/entity/user_entity.go:14
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `User` exposes publicly writable state (ID, Username, Password). — app/internal/domain/entity/user_entity.go:13
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM7 · Repository granularity
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
What to do
- Add OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, and the service already exposes health probe endpoints (healthz/livez/readyz or a container healthcheck), but no compose service declares a `healthcheck:` that uses them and nothing pins a previous image to fall back to — so a release that starts but does not serve looks healthy, and reversing it is a manual step.
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
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P8 · Schema migrations
PF1 · Benchmark discipline
- A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — pkg/hasher/bcrypt_test.go
What to do
- Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — pkg/testhelper/panic.go:8
- `if err = ctx.ShouldBindJSON(&req); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/internal/interface/restful/handler/auth_handler.go:51
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — app/internal/interface/restful/handler/auth_handler.go:57
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 80% | Strong | Solid. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85% | Checked 5 of 11 | Solid. |
| Domain Modelling | 59% | Adequate — gated by DM2, DM5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 80% | Strong | Solid. |
Unscored — 2 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.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 76 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 applicable: Go's wire constructs every dependency once for the life of the application, so there is no shorter lifetime to capture.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — 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.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~1084 lines of test source are present (.go) 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.
- D14 License Compliance — Go module licences not graded — a REDACTED predates Go 1.17 and does not list its whole module graph
- D16 Bus Factor — too few commits for a meaningful bus factor
- 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; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, 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
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- 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.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- 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 2 current-state document(s) make no claim of a kind M4 checks.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go source (service entry point: app/external/api/route.go:35 (gin.Default())
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — 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
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- 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
- X25 Inert configuration knob — 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
- X27 Collection changed while being enumerated — 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
- X29 Per-element action decided by a fixed element — 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 — 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
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 10 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 18 finding(s)
- TodoComment pkg/jwtutil/jwt.go:44
- TodoComment app/internal/interface/restful/handler/auth_handler_test.go:145
- TodoComment app/internal/interface/restful/handler/auth_handler_test.go:285
- REDACTED
- REDACTED
- REDACTED
- Dependency pinned to a stale untagged commit: github.com/jinzhu/copier
- Dependency pinned to a stale untagged commit: golang.org/x/crypto
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) app/internal/interface/restful/handler/auth_handler.go:51
- Swallowed exception (caught, then discarded) app/internal/interface/restful/handler/auth_handler.go:57
- REDACTED
- REDACTED
- REDACTED
- Coverage collected but not gated
- No DR/backup evidence
- Swallowed exception (empty catch) pkg/testhelper/panic.go:8
Minor — 8 finding(s)
- No ADRs found
- Scattered collaborators
- REDACTED
- Primitive id on a domain type: User.ID app/internal/domain/entity/user_entity.go:14
- Mutable entity: User app/internal/domain/entity/user_entity.go:13
- No ADRs
- No rollback/health safety
- Benchmarks don't track allocations pkg/hasher/bcrypt_test.go
Minor — 16 finding(s)
- Outdated: github.com/DATA-DOG/go-sqlmock
- Outdated: github.com/gin-contrib/cors
- Outdated: github.com/gin-contrib/pprof
- Outdated: github.com/gin-contrib/zap
- Outdated: github.com/gin-gonic/gin
- Outdated: github.com/go-playground/validator/v10
- Outdated: github.com/golang/mock
- Outdated: github.com/google/go-cmp
- Outdated: github.com/google/wire
- Outdated: github.com/jinzhu/copier
- Outdated: github.com/stretchr/testify
- Outdated: github.com/urfave/cli/v2
- Outdated: go.uber.org/zap
- Outdated: golang.org/x/crypto
- Outdated: gorm.io/driver/mysql
- Outdated: gorm.io/gorm
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-c4a37116667d404b9f9afd53ea6d35ba/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-c4a37116667d404b9f9afd53ea6d35ba/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 --exclude app/internal/domain/repository/mockrepo --exclude app/internal/usecase/mockusecase . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-346170dc39ed45488900bb22a2a2ddd5 | 7 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-346170dc39ed45488900bb22a2a2ddd5 | 0 | artifacts/raw/osv-scanner.json |