Executive summary
Caknoooo/go-gin-clean-starter is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 42 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step for the work it takes is having someone learn and document the seven files no active contributor knows, worth about 4 points. Adding automated security scanning would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 52 would lift the score to about 49.
Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three settings leave the servers or containers unsafe, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, correcting the unsafe settings and limiting each secret to its own step would close these risks. Updating the vulnerable packages would fix the package with a known security hole, and the password or key in the code's history needs replacing, with the old one switched off. The form field without a label needs a label.
The product code is 2,293 lines, about €2,400 to rebuild.
If Production Readiness rose from 30 to 52, the lowest score rated Strong, the score would rise from 42 to about 49.
New since the last survey: 1 finding
- Visual & motion safety · Low contrast colour pair (3.2:1) REDACTED
Rebuild cost: about €2,400 · Estimate
| Cost to rebuild | €790 to €4,000, for 13 to 42 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 2,293 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 (global) | 2 github.com/Caknoooo/go-gin-clean-starter/cmd | 3 github.com/Caknoooo/go-gin-clean-starter/config | 4 github.com/Caknoooo/go-gin-clean-starter/database/entities | 5 github.com/Caknoooo/go-gin-clean-starter/database/migrations | 6 github.com/Caknoooo/go-gin-clean-starter/database/seeders/seeds | 7 github.com/Caknoooo/go-gin-clean-starter/modules/auth | 8 github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto | 9 github.com/Caknoooo/go-gin-clean-starter/modules/user | 10 github.com/Caknoooo/go-gin-clean-starter/modules/user/dto | 11 github.com/Caknoooo/go-gin-clean-starter/modules/user/query | 12 github.com/Caknoooo/go-gin-clean-starter/pkg/constants | 13 github.com/Caknoooo/go-gin-clean-starter/pkg/helpers | 14 github.com/Caknoooo/go-gin-clean-starter/pkg/utils | 15 github.com/Caknoooo/go-gin-clean-starter/providers | 16 github.com/Caknoooo/go-gin-clean-starter/script | 17 github.com/Caknoooo/go-gin-clean-starter/database | 18 github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository | 19 github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation | 20 github.com/Caknoooo/go-gin-clean-starter/modules/user/repository | 21 github.com/Caknoooo/go-gin-clean-starter/modules/user/validation | 22 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service | 23 github.com/Caknoooo/go-gin-clean-starter/modules/user/service | 24 github.com/Caknoooo/go-gin-clean-starter/middlewares | 25 github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller | 26 github.com/Caknoooo/go-gin-clean-starter/modules/user/controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||
| 2 github.com/Caknoooo/go-gin-clean-starter/cmd | ||||||||||||||||||||||||||
| 3 github.com/Caknoooo/go-gin-clean-starter/config | ||||||||||||||||||||||||||
| 4 github.com/Caknoooo/go-gin-clean-starter/database/entities | ||||||||||||||||||||||||||
| 5 github.com/Caknoooo/go-gin-clean-starter/database/migrations | ||||||||||||||||||||||||||
| 6 github.com/Caknoooo/go-gin-clean-starter/database/seeders/seeds | ||||||||||||||||||||||||||
| 7 github.com/Caknoooo/go-gin-clean-starter/modules/auth | ||||||||||||||||||||||||||
| 8 github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto | ||||||||||||||||||||||||||
| 9 github.com/Caknoooo/go-gin-clean-starter/modules/user | ||||||||||||||||||||||||||
| 10 github.com/Caknoooo/go-gin-clean-starter/modules/user/dto | ||||||||||||||||||||||||||
| 11 github.com/Caknoooo/go-gin-clean-starter/modules/user/query | ||||||||||||||||||||||||||
| 12 github.com/Caknoooo/go-gin-clean-starter/pkg/constants | ||||||||||||||||||||||||||
| 13 github.com/Caknoooo/go-gin-clean-starter/pkg/helpers | ||||||||||||||||||||||||||
| 14 github.com/Caknoooo/go-gin-clean-starter/pkg/utils | ||||||||||||||||||||||||||
| 15 github.com/Caknoooo/go-gin-clean-starter/providers | ||||||||||||||||||||||||||
| 16 github.com/Caknoooo/go-gin-clean-starter/script | ||||||||||||||||||||||||||
| 17 github.com/Caknoooo/go-gin-clean-starter/database | 1 | |||||||||||||||||||||||||
| 18 github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository | 2 | |||||||||||||||||||||||||
| 19 github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation | 3 | 4 | ||||||||||||||||||||||||
| 20 github.com/Caknoooo/go-gin-clean-starter/modules/user/repository | 2 | |||||||||||||||||||||||||
| 21 github.com/Caknoooo/go-gin-clean-starter/modules/user/validation | 2 | |||||||||||||||||||||||||
| 22 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service | 8 | 12 | 2 | 2 | ||||||||||||||||||||||
| 23 github.com/Caknoooo/go-gin-clean-starter/modules/user/service | 6 | 2 | ||||||||||||||||||||||||
| 24 github.com/Caknoooo/go-gin-clean-starter/middlewares | 1 | |||||||||||||||||||||||||
| 25 github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller | 1 | 2 | ||||||||||||||||||||||||
| 26 github.com/Caknoooo/go-gin-clean-starter/modules/user/controller | 1 | 2 |
17→4 github.com/Caknoooo/go-gin-clean-starter/database uses github.com/Caknoooo/go-gin-clean-starter/database/entities✕
- Connections
- 1 pair of types, where a type in github.com/Caknoooo/go-gin-clean-starter/database uses a type in github.com/Caknoooo/go-gin-clean-starter/database/entities.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/database.MigrationManager→github.com/Caknoooo/go-gin-clean-starter/database/entities.Migration
- Direction
- github.com/Caknoooo/go-gin-clean-starter/database uses github.com/Caknoooo/go-gin-clean-starter/database/entities, so a change to github.com/Caknoooo/go-gin-clean-starter/database/entities can break github.com/Caknoooo/go-gin-clean-starter/database, while a change to github.com/Caknoooo/go-gin-clean-starter/database can't break github.com/Caknoooo/go-gin-clean-starter/database/entities.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/database uses a module listed above it, which is the healthy direction.
18→4 github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository uses github.com/Caknoooo/go-gin-clean-starter/database/entities✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository uses a type in github.com/Caknoooo/go-gin-clean-starter/database/entities.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.RefreshTokenRepository→github.com/Caknoooo/go-gin-clean-starter/database/entities.RefreshTokengithub.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.refreshTokenRepository→github.com/Caknoooo/go-gin-clean-starter/database/entities.RefreshToken
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository uses github.com/Caknoooo/go-gin-clean-starter/database/entities, so a change to github.com/Caknoooo/go-gin-clean-starter/database/entities can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository can't break github.com/Caknoooo/go-gin-clean-starter/database/entities.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository uses a module listed above it, which is the healthy direction.
19→8 github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto✕
- Connections
- 3 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.RefreshTokenRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.ResetPasswordRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.SendPasswordResetRequest
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses a module listed above it, which is the healthy direction.
19→10 github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto✕
- Connections
- 4 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.SendVerificationEmailRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserCreateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserLoginRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.VerifyEmailRequest
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation uses a module listed above it, which is the healthy direction.
20→4 github.com/Caknoooo/go-gin-clean-starter/modules/user/repository uses github.com/Caknoooo/go-gin-clean-starter/database/entities✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/repository uses a type in github.com/Caknoooo/go-gin-clean-starter/database/entities.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.UserRepository→github.com/Caknoooo/go-gin-clean-starter/database/entities.Usergithub.com/Caknoooo/go-gin-clean-starter/modules/user/repository.userRepository→github.com/Caknoooo/go-gin-clean-starter/database/entities.User
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/repository uses github.com/Caknoooo/go-gin-clean-starter/database/entities, so a change to github.com/Caknoooo/go-gin-clean-starter/database/entities can break github.com/Caknoooo/go-gin-clean-starter/modules/user/repository, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/repository can't break github.com/Caknoooo/go-gin-clean-starter/database/entities.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/repository uses a module listed above it, which is the healthy direction.
21→10 github.com/Caknoooo/go-gin-clean-starter/modules/user/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/validation uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/validation.UserValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserCreateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/user/validation.UserValidation→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserUpdateRequest
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/validation uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/user/validation, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/validation can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/validation uses a module listed above it, which is the healthy direction.
22→8 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto✕
- Connections
- 8 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.RefreshTokenRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.ResetPasswordRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.SendPasswordResetRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.TokenResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.RefreshTokenRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.ResetPasswordRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.SendPasswordResetRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.TokenResponse
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a module listed above it, which is the healthy direction.
22→10 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto✕
- Connections
- 12 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.SendVerificationEmailRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserCreateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserLoginRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.VerifyEmailRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.VerifyEmailResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.SendVerificationEmailRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserCreateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserLoginRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.VerifyEmailRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.VerifyEmailResponse
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a module listed above it, which is the healthy direction.
22→18 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.RefreshTokenRepositorygithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.service→github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.RefreshTokenRepository
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/repository.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a module listed above it, which is the healthy direction.
22→20 github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/repository✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.authService→github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.UserRepositorygithub.com/Caknoooo/go-gin-clean-starter/modules/auth/service.service→github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.UserRepository
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/repository, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/repository can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/service uses a module listed above it, which is the healthy direction.
23→10 github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto✕
- Connections
- 6 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/service.UserService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.UserService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserUpdateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.UserService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserUpdateResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.userService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserResponsegithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.userService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserUpdateRequestgithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.userService→github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.UserUpdateResponse
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/dto, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/dto can break github.com/Caknoooo/go-gin-clean-starter/modules/user/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/dto.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses a module listed above it, which is the healthy direction.
23→20 github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/repository✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/service.service→github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.UserRepositorygithub.com/Caknoooo/go-gin-clean-starter/modules/user/service.userService→github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.UserRepository
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses github.com/Caknoooo/go-gin-clean-starter/modules/user/repository, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/repository can break github.com/Caknoooo/go-gin-clean-starter/modules/user/service, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/service can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/repository.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/service uses a module listed above it, which is the healthy direction.
24→22 github.com/Caknoooo/go-gin-clean-starter/middlewares uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/service✕
- Connections
- 1 pair of types, where a type in github.com/Caknoooo/go-gin-clean-starter/middlewares uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/middlewares.middlewares→github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.JWTService
- Direction
- github.com/Caknoooo/go-gin-clean-starter/middlewares uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can break github.com/Caknoooo/go-gin-clean-starter/middlewares, while a change to github.com/Caknoooo/go-gin-clean-starter/middlewares can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/middlewares uses a module listed above it, which is the healthy direction.
25→19 github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation✕
- Connections
- 1 pair of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller.authController→github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.AuthValidation
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/validation.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses a module listed above it, which is the healthy direction.
25→22 github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/service✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller.authController→github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthServicegithub.com/Caknoooo/go-gin-clean-starter/modules/auth/controller.controller→github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.AuthService
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/auth/service, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/service can break github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller can't break github.com/Caknoooo/go-gin-clean-starter/modules/auth/service.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/auth/controller uses a module listed above it, which is the healthy direction.
26→21 github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/user/validation✕
- Connections
- 1 pair of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/validation.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/controller.userController→github.com/Caknoooo/go-gin-clean-starter/modules/user/validation.UserValidation
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/user/validation, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/validation can break github.com/Caknoooo/go-gin-clean-starter/modules/user/controller, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/controller can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/validation.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses a module listed above it, which is the healthy direction.
26→23 github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/user/service✕
- Connections
- 2 pairs of types, where a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses a type in github.com/Caknoooo/go-gin-clean-starter/modules/user/service.
- The types involved
github.com/Caknoooo/go-gin-clean-starter/modules/user/controller.controller→github.com/Caknoooo/go-gin-clean-starter/modules/user/service.UserServicegithub.com/Caknoooo/go-gin-clean-starter/modules/user/controller.userController→github.com/Caknoooo/go-gin-clean-starter/modules/user/service.UserService
- Direction
- github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses github.com/Caknoooo/go-gin-clean-starter/modules/user/service, so a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/service can break github.com/Caknoooo/go-gin-clean-starter/modules/user/controller, while a change to github.com/Caknoooo/go-gin-clean-starter/modules/user/controller can't break github.com/Caknoooo/go-gin-clean-starter/modules/user/service.
- Position
- Below the diagonal: github.com/Caknoooo/go-gin-clean-starter/modules/user/controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 12 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | High / Critical |
| A02:2025 — Security Misconfiguration | 6 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery; Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with manager.go, auth_service.go, auth_controller.go.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with manager.go, auth_service.go, auth_controller.go. | +3.8 pts | Low | Knowledge Freshness |
| Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +3.0 pts | Low | Dependency Hygiene |
| Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +4.5 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +4.5 pts | Medium | DR & Backup |
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +3.5 pts | Medium | Visual & motion safety |
| 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.9 pts | Medium | Architecture documentation |
| Replace GORM AutoMigrate with a versioned migration tool such as golang-migrate, goose or Atlas so the production schema can evolve safely and reproducibly. | +2.8 pts | Medium | Schema migrations |
| Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge. | +2.5 pts | Medium | A11y enforcement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.1 | Mixed | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| database/manager.go | 7.2 | Near-clean | Cognitive Complexity: MigrationManager.addEntityToMigrationFile (cognitive 49) |
| REDACTED | 7.2 | Near-clean | Secrets (history): High secret: REDACTED |
| script/command.go | 7.8 | Near-clean | Cyclomatic Complexity: script.Commands (cyclomatic 37) |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| pkg/utils/aes.go | 8.2 | Near-clean | Explicit Debt: TodoComment |
| modules/auth/controller/auth_controller.go | 8.5 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| modules/auth/repository/refresh_token_repository.go | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| modules/user/repository/user_repository.go | 8.5 | Near-clean | Code Duplication: Duplicated block (11 lines × 2) |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
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 53 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 — 53 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, 61 of 77 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.go) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 231 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 3 hold 5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is 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.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is samber/do, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — time="2026-11-07T23:27:45Z" level=warning msg="The \"DB_PASS\" variable is not set. Defaulting to a blank string." time="2026-11-07T23:27:45Z" level=warning msg="The \"DB_NAME\" variable is not set. Defaulting to a blank string." failed to solve: process "/bin/sh -c go install github.com/air-verse/air@v1.65.1" did not complete successfully: exit code: 1; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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 REDACTED (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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was script.Commands at 37.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with script.Commands (cyclomatic 37). — Refactoring it lifts Cyclomatic Complexity from 9.0 to about 10.0/10.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was script.Commands at 59.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with script.Commands (cognitive 59), MigrationManager.addEntityToMigrationFile (cognitive 49), MigrationManager.Rollback (cognitive 25). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 7.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
4 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with refresh_token_repository.go, user_repository.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (34 lines × 2) finding(s) in Code Duplication — start with manager.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with auth_controller.go. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 8 classes have LCOM4 above 3.
D9 · Test Distribution
9 test methods: 9 unit, 0 integration, 0 BDD, 0 e2e. The Go suite contributes 9 test case(s) across 2 `_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/Caknoooo/go-gin-clean-starter): measured (0 flaky).
D12 · Dependency Hygiene
5 outdated, 0 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). 15 of 15 direct requirement(s) were graded against proxy.golang.org (0 not served there, 2 publishing no tagged release to be behind). 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 go.sum 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.
D14 · License Compliance
0 of 63 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 2293 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with aes.go. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 1 build units (Go) flagged as possibly oversized/incoherent.
D27 · Navigability
69 % of calls cross a namespace and 29 % go through an interface, but 20 % 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. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
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).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 6 high, 5 medium, 1 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `logs.html` (line 148, line 149, line 150, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
6 finding(s): 1 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
D31 · IaC & Container Security
6 finding(s): 0 critical, 3 high, 2 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
7 of 7 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is database/manager.go. Counted over 7 of the 40 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with manager.go, auth_service.go, auth_controller.go. — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
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
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — logs.html:147
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — logs.html:2, REDACTED:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC6 · Visual & motion safety
- `.refresh-button i` moves (`transition: transform 0.6s cubic-bezier(0.34, 1.56, 0.64, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — logs.html:118
- The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — REDACTED:47
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 2 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM7 · Repository granularity
- `RefreshTokenRepository` leaks the infrastructure/framework type `DB` through its contract. A repository should be a persistence PORT over an aggregate ROOT — expose intention-revealing whole-aggregate operations (Save/FindByID) and keep framework types, query specifications and business logic out of its contract so callers can't bypass the aggregate's invariants. — modules/auth/repository/refresh_token_repository.go:12
- `UserRepository` leaks the infrastructure/framework type `DB` through its contract. A repository should be a persistence PORT over an aggregate ROOT — expose intention-revealing whole-aggregate operations (Save/FindByID) and keep framework types, query specifications and business logic out of its contract so callers can't bypass the aggregate's invariants. — modules/user/repository/user_repository.go:12
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
What to do
- Run the test suite in CI via an explicit runner step (`go test ./...` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
What to do
- Consider OpenTelemetry tracing/metrics (go.opentelemetry.io/otel) and a health-check endpoint (a /healthz handler) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1117 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
What to do
- Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
- GORM AutoMigrate builds the schema from the model at startup and keeps no migration history, so there is no reviewed, repeatable upgrade path for an existing production database — a renamed column is dropped and re-added rather than migrated. Adopt a versioned migration tool such as golang-migrate, goose or Atlas, so every schema change is a versioned file applied the same way in every environment. (×5) — database/manager.go:51, database/manager.go:367, database/manager.go:421, …
What to do
- Replace GORM AutoMigrate with a versioned migration tool such as golang-migrate, goose or Atlas so the production schema can evolve safely and reproducibly.
S1 · Web-Security Posture
- `https://cdn.tailwindcss.com` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — logs.html:8
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:1
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
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
- `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. — pkg/utils/aes.go:91
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 87% | Exemplary | Solid. |
| Architecture | 94% | Exemplary | Strongest area. |
| Maturity | 50% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 30% | Weak — gated by P3, P5, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 70% | Strong | Solid. |
| Domain Modelling | 76% | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 37% | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 3 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 74 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- 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 — compose up failed (exit 17 — an image could not be built) — time="2026-11-07T23:27:45Z" level=warning msg="The \"DB_PASS\" variable is not set. Defaulting to a blank string." time="2026-11-07T23:27:45Z" level=warning msg="The \"DB_NAME\" variable is not set. Defaulting to a blank string." failed to solve: process "/bin/sh -c go install github.com/air-verse/air@v1.65.1" did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~115 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.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go, html 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 (database), 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.
- 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
- DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- 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)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 6 claim(s) of kinds M4 does not check were not checked (environment variable 6); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Go source (service entry point: cmd/main.go:61 (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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label logs.html:147
- REDACTED
- REDACTED
Serious — 42 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Schema created by GORM AutoMigrate (no migration path) database/manager.go:51
- Schema created by GORM AutoMigrate (no migration path) database/manager.go:367
- Schema created by GORM AutoMigrate (no migration path) database/manager.go:421
- Schema created by GORM AutoMigrate (no migration path) database/migrations/20240101000000_create_users_table.go:14
- Schema created by GORM AutoMigrate (no migration path) database/migrations/20240101000001_create_refresh_tokens_table.go:14
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark logs.html:2
- Page without a main landmark REDACTED:2
- Dependency pinned to a stale untagged commit: github.com/common-nighthawk/go-figure
- Dependency pinned to a stale untagged commit: gopkg.in/gomail.v2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) modules/auth/repository/refresh_token_repository.go:33
- Duplicated block (11 lines × 2) modules/user/repository/user_repository.go:44
- Leaky repository contract: RefreshTokenRepository modules/auth/repository/refresh_token_repository.go:12
- Leaky repository contract: UserRepository modules/user/repository/user_repository.go:12
- Animation without a prefers-reduced-motion guard logs.html:118
- Low contrast colour pair (3.2:1) REDACTED:47
- Accessibility enforcement below the top rung
- script.Commands (cyclomatic 37) script/command.go:16
- TodoComment pkg/utils/aes.go:14
- script.Commands (cognitive 59) script/command.go:16
- MigrationManager.addEntityToMigrationFile (cognitive 49) database/manager.go:407
- MigrationManager.Rollback (cognitive 25) database/manager.go:134
- MigrationManager.RollbackAll (cognitive 16) database/manager.go:200
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (34 lines × 2) database/manager.go:165
- Duplicated block (9 lines × 2) modules/auth/controller/auth_controller.go:36
- No DR/backup evidence
- Third-party script without Subresource Integrity logs.html:8
- Swallowed exception (caught, then discarded) pkg/utils/aes.go:91
Minor — 18 finding(s)
- Orphaned file database/manager.go:1
- Orphaned file modules/auth/service/auth_service.go:1
- Orphaned file modules/auth/controller/auth_controller.go:1
- Orphaned file modules/user/dto/user_dto.go:1
- Orphaned file modules/user/controller/user_controller.go:1
- Orphaned file script/command.go:1
- Orphaned file modules/user/repository/user_repository.go:1
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No SAST REDACTED:9
- No rollback/health safety
- No changelog
- No security response headers detected REDACTED:1
Minor — 5 finding(s)
- Outdated: github.com/go-playground/validator/v10
- Outdated: github.com/stretchr/testify
- Outdated: golang.org/x/crypto
- Outdated: gorm.io/driver/postgres
- 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-dca1d170731e418f92a20300acac265c/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-dca1d170731e418f92a20300acac265c/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 . | 12 | 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-eeecf080223645cc9bfff235335bb98f | 6 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | 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-eeecf080223645cc9bfff235335bb98f | 0 | artifacts/raw/osv-scanner.json |