Executive summary
luizomf/clean-architecture-api-boilerplate is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because two passwords or keys sit in the current code and we found no working pipeline that builds or tests changes to the code. It scores 48 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 22, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 22 points. Raising Production Readiness to 52 would lift the score to about 61.
Fifty-four known security holes in the packages the code depends on can be used by attackers. Four passwords or keys in the code's history and two in the code are open to anyone who can read the repository, and one weakness in the code could be used by an attacker. Updating the vulnerable packages, replacing each exposed password or key and fixing the weaknesses the scanner points to would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The two tests that check nothing need to check the result they produce.
The product code is 2,114 lines, about €6,200 to rebuild.
If Production Readiness rose from 22 to 52, the lowest score rated Strong, the score would rise from 48 to about 61.
New since the last survey: 7 findings
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 23 findings
- Code Coverage · Low coverage: src/application/use-cases/sign-in/sign-in.ts src/application/use-cases/sign-in/sign-in.ts
- Code Coverage · Low coverage: src/common/adapters/security/bcrypt-adapter.ts src/common/adapters/security/bcrypt-adapter.ts
- Code Coverage · Low coverage: src/infrastructure/express/adapters/express-middleware-adapter.ts src/infrastructure/express/adapters/express-middleware-adapter.ts
- Code Coverage · Low coverage: src/infrastructure/express/adapters/express-route-adapter.ts src/infrastructure/express/adapters/express-route-adapter.ts
- Code Coverage · Low coverage: src/infrastructure/express/middlewares/rate-limit.ts src/infrastructure/express/middlewares/rate-limit.ts
- Code Coverage · Low coverage: src/infrastructure/express/routes/refresh-token.ts src/infrastructure/express/routes/refresh-token.ts
- Code Coverage · Low coverage: src/infrastructure/express/routes/sign-in.ts src/infrastructure/express/routes/sign-in.ts
- Code Coverage · Low coverage: src/infrastructure/express/routes/user.ts src/infrastructure/express/routes/user.ts
- Code Coverage · Low coverage: src/infrastructure/express/setup/setup-app.ts src/infrastructure/express/setup/setup-app.ts
- Code Coverage · Low coverage: REDACTED REDACTED
- Code Coverage · Low coverage: src/infrastructure/express/setup/setup-global-middlewares.ts src/infrastructure/express/setup/setup-global-middlewares.ts
- Code Coverage · Low coverage: src/infrastructure/express/setup/setup-routes.ts src/infrastructure/express/setup/setup-routes.ts
- Code Coverage · Low coverage: src/infrastructure/repositories/token/sql/token-sql-repository.ts src/infrastructure/repositories/token/sql/token-sql-repository.ts
- Code Coverage · Low coverage: src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts
- Code Coverage · Low coverage: src/presentation/middlewares/authentication/logged-user-is-target-user.ts src/presentation/middlewares/authentication/logged-user-is-target-user.ts
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- DR & Backup · No DR/backup evidence
Rebuild cost: about €6,200 · Estimate
| Cost to rebuild | €2,100 to €10,000, for 35 to 110 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 48. 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,114 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 application.errors.default-application-error | 2 application.ports.repositories.token.create-token-repository | 3 application.ports.repositories.user.find-user-by-email-repository | 4 application.ports.repositories.user.find-user-by-id-repository | 5 application.ports.requests.middleware-request-model | 6 application.ports.requests.request-model | 7 application.ports.responses.response-model | 8 application.ports.security.jwt-token | 9 application.ports.security.password-hashing | 10 application.ports.validation.validation-composite | 11 domain.models.sign-in.sign-in-request-model | 12 domain.models.user.user | 13 domain.models.user.user-request-partial-fields | 14 application.ports.controllers.controller | 15 application.ports.middlewares.middleware | 16 application.ports.repositories.user.update-user-repository | 17 application.ports.responses.response-handler | 18 application.use-cases.token.refresh-token | 19 application.use-cases.user.create-user | 20 application.use-cases.user.delete-user-by-id | 21 application.use-cases.user.find-all-users | 22 application.validation.user.composite.user-composite-validation | 23 application.validation.user.leaf.user-email-validation | 24 domain.use-cases.sign-in.sign-in-use-case | 25 domain.use-cases.user.find-user-by-id-use-case | 26 domain.use-cases.user.update-user-use-case | 27 infrastructure.repositories.token.sql.token-sql-repository | 28 application.use-cases.sign-in.sign-in | 29 application.use-cases.user.find-user-by-id | 30 application.use-cases.user.update-user | 31 infrastructure.repositories.user.sql.repositories.user-sql-repository | 32 presentation.controllers.sign-in.sign-in-controller | 33 presentation.controllers.user.create-user-controller | 34 presentation.controllers.user.delete-user-by-id-controller | 35 presentation.controllers.user.find-all-users-controller | 36 presentation.controllers.user.find-by-id-controller | 37 presentation.controllers.user.update-user-controller | 38 presentation.middlewares.authentication.is-authenticated | 39 presentation.middlewares.authentication.logged-user-is-target-user | 40 presentation.controllers.token.refresh-token-controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application.errors.default-application-error | ||||||||||||||||||||||||||||||||||||||||
| 2 application.ports.repositories.token.create-token-repository | ||||||||||||||||||||||||||||||||||||||||
| 3 application.ports.repositories.user.find-user-by-email-repository | ||||||||||||||||||||||||||||||||||||||||
| 4 application.ports.repositories.user.find-user-by-id-repository | ||||||||||||||||||||||||||||||||||||||||
| 5 application.ports.requests.middleware-request-model | ||||||||||||||||||||||||||||||||||||||||
| 6 application.ports.requests.request-model | ||||||||||||||||||||||||||||||||||||||||
| 7 application.ports.responses.response-model | ||||||||||||||||||||||||||||||||||||||||
| 8 application.ports.security.jwt-token | ||||||||||||||||||||||||||||||||||||||||
| 9 application.ports.security.password-hashing | ||||||||||||||||||||||||||||||||||||||||
| 10 application.ports.validation.validation-composite | ||||||||||||||||||||||||||||||||||||||||
| 11 domain.models.sign-in.sign-in-request-model | ||||||||||||||||||||||||||||||||||||||||
| 12 domain.models.user.user | ||||||||||||||||||||||||||||||||||||||||
| 13 domain.models.user.user-request-partial-fields | ||||||||||||||||||||||||||||||||||||||||
| 14 application.ports.controllers.controller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 application.ports.middlewares.middleware | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 application.ports.repositories.user.update-user-repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 application.ports.responses.response-handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 application.use-cases.token.refresh-token | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 application.use-cases.user.create-user | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 application.use-cases.user.delete-user-by-id | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 application.use-cases.user.find-all-users | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 application.validation.user.composite.user-composite-validation | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 application.validation.user.leaf.user-email-validation | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 domain.use-cases.sign-in.sign-in-use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 domain.use-cases.user.find-user-by-id-use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 domain.use-cases.user.update-user-use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 infrastructure.repositories.token.sql.token-sql-repository | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 application.use-cases.sign-in.sign-in | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 29 application.use-cases.user.find-user-by-id | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 application.use-cases.user.update-user | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 31 infrastructure.repositories.user.sql.repositories.user-sql-repository | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 presentation.controllers.sign-in.sign-in-controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 presentation.controllers.user.create-user-controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 presentation.controllers.user.delete-user-by-id-controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 presentation.controllers.user.find-all-users-controller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 presentation.controllers.user.find-by-id-controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 presentation.controllers.user.update-user-controller | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 presentation.middlewares.authentication.is-authenticated | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 presentation.middlewares.authentication.logged-user-is-target-user | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 presentation.controllers.token.refresh-token-controller | 1 | 1 |
14→6 application.ports.controllers.controller uses application.ports.requests.request-model✕
- Connections
- 1 pair of types, where a type in application.ports.controllers.controller uses a type in application.ports.requests.request-model.
- The types involved
src.application.ports.controllers.controller.Controller→src.application.ports.requests.request-model.RequestModel
- Direction
- application.ports.controllers.controller uses application.ports.requests.request-model, so a change to application.ports.requests.request-model can break application.ports.controllers.controller, while a change to application.ports.controllers.controller can't break application.ports.requests.request-model.
- Position
- Below the diagonal: application.ports.controllers.controller uses a module listed above it, which is the healthy direction.
14→7 application.ports.controllers.controller uses application.ports.responses.response-model✕
- Connections
- 1 pair of types, where a type in application.ports.controllers.controller uses a type in application.ports.responses.response-model.
- The types involved
src.application.ports.controllers.controller.Controller→src.application.ports.responses.response-model.ResponseModel
- Direction
- application.ports.controllers.controller uses application.ports.responses.response-model, so a change to application.ports.responses.response-model can break application.ports.controllers.controller, while a change to application.ports.controllers.controller can't break application.ports.responses.response-model.
- Position
- Below the diagonal: application.ports.controllers.controller uses a module listed above it, which is the healthy direction.
15→5 application.ports.middlewares.middleware uses application.ports.requests.middleware-request-model✕
- Connections
- 1 pair of types, where a type in application.ports.middlewares.middleware uses a type in application.ports.requests.middleware-request-model.
- The types involved
src.application.ports.middlewares.middleware.Middleware→src.application.ports.requests.middleware-request-model.MiddlewareRequestModel
- Direction
- application.ports.middlewares.middleware uses application.ports.requests.middleware-request-model, so a change to application.ports.requests.middleware-request-model can break application.ports.middlewares.middleware, while a change to application.ports.middlewares.middleware can't break application.ports.requests.middleware-request-model.
- Position
- Below the diagonal: application.ports.middlewares.middleware uses a module listed above it, which is the healthy direction.
16→13 application.ports.repositories.user.update-user-repository uses domain.models.user.user-request-partial-fields✕
- Connections
- 1 pair of types, where a type in application.ports.repositories.user.update-user-repository uses a type in domain.models.user.user-request-partial-fields.
- The types involved
src.application.ports.repositories.user.update-user-repository.UpdateUserRepository→src.domain.models.user.user-request-partial-fields.UserRequestPartialFields
- Direction
- application.ports.repositories.user.update-user-repository uses domain.models.user.user-request-partial-fields, so a change to domain.models.user.user-request-partial-fields can break application.ports.repositories.user.update-user-repository, while a change to application.ports.repositories.user.update-user-repository can't break domain.models.user.user-request-partial-fields.
- Position
- Below the diagonal: application.ports.repositories.user.update-user-repository uses a module listed above it, which is the healthy direction.
17→7 application.ports.responses.response-handler uses application.ports.responses.response-model✕
- Connections
- 1 pair of types, where a type in application.ports.responses.response-handler uses a type in application.ports.responses.response-model.
- The types involved
src.application.ports.responses.response-handler.ResponseHandler→src.application.ports.responses.response-model.ResponseModel
- Direction
- application.ports.responses.response-handler uses application.ports.responses.response-model, so a change to application.ports.responses.response-model can break application.ports.responses.response-handler, while a change to application.ports.responses.response-handler can't break application.ports.responses.response-model.
- Position
- Below the diagonal: application.ports.responses.response-handler uses a module listed above it, which is the healthy direction.
18→2 application.use-cases.token.refresh-token uses application.ports.repositories.token.create-token-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.token.refresh-token uses a type in application.ports.repositories.token.create-token-repository.
- The types involved
src.application.use-cases.token.refresh-token.RefreshToken→src.application.ports.repositories.token.create-token-repository.CreateTokenRepository
- Direction
- application.use-cases.token.refresh-token uses application.ports.repositories.token.create-token-repository, so a change to application.ports.repositories.token.create-token-repository can break application.use-cases.token.refresh-token, while a change to application.use-cases.token.refresh-token can't break application.ports.repositories.token.create-token-repository.
- Position
- Below the diagonal: application.use-cases.token.refresh-token uses a module listed above it, which is the healthy direction.
18→8 application.use-cases.token.refresh-token uses application.ports.security.jwt-token✕
- Connections
- 1 pair of types, where a type in application.use-cases.token.refresh-token uses a type in application.ports.security.jwt-token.
- The types involved
src.application.use-cases.token.refresh-token.RefreshToken→src.application.ports.security.jwt-token.JwtToken
- Direction
- application.use-cases.token.refresh-token uses application.ports.security.jwt-token, so a change to application.ports.security.jwt-token can break application.use-cases.token.refresh-token, while a change to application.use-cases.token.refresh-token can't break application.ports.security.jwt-token.
- Position
- Below the diagonal: application.use-cases.token.refresh-token uses a module listed above it, which is the healthy direction.
19→3 application.use-cases.user.create-user uses application.ports.repositories.user.find-user-by-email-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.create-user uses a type in application.ports.repositories.user.find-user-by-email-repository.
- The types involved
src.application.use-cases.user.create-user.CreateUser→src.application.ports.repositories.user.find-user-by-email-repository.FindUserByEmailRepository
- Direction
- application.use-cases.user.create-user uses application.ports.repositories.user.find-user-by-email-repository, so a change to application.ports.repositories.user.find-user-by-email-repository can break application.use-cases.user.create-user, while a change to application.use-cases.user.create-user can't break application.ports.repositories.user.find-user-by-email-repository.
- Position
- Below the diagonal: application.use-cases.user.create-user uses a module listed above it, which is the healthy direction.
19→9 application.use-cases.user.create-user uses application.ports.security.password-hashing✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.create-user uses a type in application.ports.security.password-hashing.
- The types involved
src.application.use-cases.user.create-user.CreateUser→src.application.ports.security.password-hashing.PasswordHashing
- Direction
- application.use-cases.user.create-user uses application.ports.security.password-hashing, so a change to application.ports.security.password-hashing can break application.use-cases.user.create-user, while a change to application.use-cases.user.create-user can't break application.ports.security.password-hashing.
- Position
- Below the diagonal: application.use-cases.user.create-user uses a module listed above it, which is the healthy direction.
19→10 application.use-cases.user.create-user uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.create-user uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.user.create-user.CreateUser→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.user.create-user uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.user.create-user, while a change to application.use-cases.user.create-user can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.user.create-user uses a module listed above it, which is the healthy direction.
19→12 application.use-cases.user.create-user uses domain.models.user.user✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.create-user uses a type in domain.models.user.user.
- The types involved
src.application.use-cases.user.create-user.CreateUser→src.domain.models.user.user.User
- Direction
- application.use-cases.user.create-user uses domain.models.user.user, so a change to domain.models.user.user can break application.use-cases.user.create-user, while a change to application.use-cases.user.create-user can't break domain.models.user.user.
- Position
- Below the diagonal: application.use-cases.user.create-user uses a module listed above it, which is the healthy direction.
20→4 application.use-cases.user.delete-user-by-id uses application.ports.repositories.user.find-user-by-id-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.delete-user-by-id uses a type in application.ports.repositories.user.find-user-by-id-repository.
- The types involved
src.application.use-cases.user.delete-user-by-id.DeleteUserById→src.application.ports.repositories.user.find-user-by-id-repository.FindUserByIdRepository
- Direction
- application.use-cases.user.delete-user-by-id uses application.ports.repositories.user.find-user-by-id-repository, so a change to application.ports.repositories.user.find-user-by-id-repository can break application.use-cases.user.delete-user-by-id, while a change to application.use-cases.user.delete-user-by-id can't break application.ports.repositories.user.find-user-by-id-repository.
- Position
- Below the diagonal: application.use-cases.user.delete-user-by-id uses a module listed above it, which is the healthy direction.
20→10 application.use-cases.user.delete-user-by-id uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.delete-user-by-id uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.user.delete-user-by-id.DeleteUserById→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.user.delete-user-by-id uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.user.delete-user-by-id, while a change to application.use-cases.user.delete-user-by-id can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.user.delete-user-by-id uses a module listed above it, which is the healthy direction.
21→10 application.use-cases.user.find-all-users uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.find-all-users uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.user.find-all-users.FindAllUsers→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.user.find-all-users uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.user.find-all-users, while a change to application.use-cases.user.find-all-users can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.user.find-all-users uses a module listed above it, which is the healthy direction.
22→10 application.validation.user.composite.user-composite-validation uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.validation.user.composite.user-composite-validation uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.validation.user.composite.user-composite-validation.UserCompositeValidation→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.validation.user.composite.user-composite-validation uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.validation.user.composite.user-composite-validation, while a change to application.validation.user.composite.user-composite-validation can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.validation.user.composite.user-composite-validation uses a module listed above it, which is the healthy direction.
23→10 application.validation.user.leaf.user-email-validation uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.validation.user.leaf.user-email-validation uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.validation.user.leaf.user-email-validation.UserEmailValidation→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.validation.user.leaf.user-email-validation uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.validation.user.leaf.user-email-validation, while a change to application.validation.user.leaf.user-email-validation can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.validation.user.leaf.user-email-validation uses a module listed above it, which is the healthy direction.
23→13 application.validation.user.leaf.user-email-validation uses domain.models.user.user-request-partial-fields✕
- Connections
- 1 pair of types, where a type in application.validation.user.leaf.user-email-validation uses a type in domain.models.user.user-request-partial-fields.
- The types involved
src.application.validation.user.leaf.user-email-validation.UserEmailValidation→src.domain.models.user.user-request-partial-fields.UserRequestPartialFields
- Direction
- application.validation.user.leaf.user-email-validation uses domain.models.user.user-request-partial-fields, so a change to domain.models.user.user-request-partial-fields can break application.validation.user.leaf.user-email-validation, while a change to application.validation.user.leaf.user-email-validation can't break domain.models.user.user-request-partial-fields.
- Position
- Below the diagonal: application.validation.user.leaf.user-email-validation uses a module listed above it, which is the healthy direction.
24→11 domain.use-cases.sign-in.sign-in-use-case uses domain.models.sign-in.sign-in-request-model✕
- Connections
- 1 pair of types, where a type in domain.use-cases.sign-in.sign-in-use-case uses a type in domain.models.sign-in.sign-in-request-model.
- The types involved
src.domain.use-cases.sign-in.sign-in-use-case.SignInUseCase→src.domain.models.sign-in.sign-in-request-model.SignInRequestModel
- Direction
- domain.use-cases.sign-in.sign-in-use-case uses domain.models.sign-in.sign-in-request-model, so a change to domain.models.sign-in.sign-in-request-model can break domain.use-cases.sign-in.sign-in-use-case, while a change to domain.use-cases.sign-in.sign-in-use-case can't break domain.models.sign-in.sign-in-request-model.
- Position
- Below the diagonal: domain.use-cases.sign-in.sign-in-use-case uses a module listed above it, which is the healthy direction.
25→12 domain.use-cases.user.find-user-by-id-use-case uses domain.models.user.user✕
- Connections
- 1 pair of types, where a type in domain.use-cases.user.find-user-by-id-use-case uses a type in domain.models.user.user.
- The types involved
src.domain.use-cases.user.find-user-by-id-use-case.FindUserByIdUseCase→src.domain.models.user.user.User
- Direction
- domain.use-cases.user.find-user-by-id-use-case uses domain.models.user.user, so a change to domain.models.user.user can break domain.use-cases.user.find-user-by-id-use-case, while a change to domain.use-cases.user.find-user-by-id-use-case can't break domain.models.user.user.
- Position
- Below the diagonal: domain.use-cases.user.find-user-by-id-use-case uses a module listed above it, which is the healthy direction.
26→13 domain.use-cases.user.update-user-use-case uses domain.models.user.user-request-partial-fields✕
- Connections
- 1 pair of types, where a type in domain.use-cases.user.update-user-use-case uses a type in domain.models.user.user-request-partial-fields.
- The types involved
src.domain.use-cases.user.update-user-use-case.UpdateUserUseCase→src.domain.models.user.user-request-partial-fields.UserRequestPartialFields
- Direction
- domain.use-cases.user.update-user-use-case uses domain.models.user.user-request-partial-fields, so a change to domain.models.user.user-request-partial-fields can break domain.use-cases.user.update-user-use-case, while a change to domain.use-cases.user.update-user-use-case can't break domain.models.user.user-request-partial-fields.
- Position
- Below the diagonal: domain.use-cases.user.update-user-use-case uses a module listed above it, which is the healthy direction.
27→2 infrastructure.repositories.token.sql.token-sql-repository uses application.ports.repositories.token.create-token-repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.token.sql.token-sql-repository uses a type in application.ports.repositories.token.create-token-repository.
- The types involved
src.infrastructure.repositories.token.sql.token-sql-repository.TokenSqlRepository→src.application.ports.repositories.token.create-token-repository.CreateTokenRepository
- Direction
- infrastructure.repositories.token.sql.token-sql-repository uses application.ports.repositories.token.create-token-repository, so a change to application.ports.repositories.token.create-token-repository can break infrastructure.repositories.token.sql.token-sql-repository, while a change to infrastructure.repositories.token.sql.token-sql-repository can't break application.ports.repositories.token.create-token-repository.
- Position
- Below the diagonal: infrastructure.repositories.token.sql.token-sql-repository uses a module listed above it, which is the healthy direction.
28→2 application.use-cases.sign-in.sign-in uses application.ports.repositories.token.create-token-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in application.ports.repositories.token.create-token-repository.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.application.ports.repositories.token.create-token-repository.CreateTokenRepository
- Direction
- application.use-cases.sign-in.sign-in uses application.ports.repositories.token.create-token-repository, so a change to application.ports.repositories.token.create-token-repository can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break application.ports.repositories.token.create-token-repository.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→3 application.use-cases.sign-in.sign-in uses application.ports.repositories.user.find-user-by-email-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in application.ports.repositories.user.find-user-by-email-repository.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.application.ports.repositories.user.find-user-by-email-repository.FindUserByEmailRepository
- Direction
- application.use-cases.sign-in.sign-in uses application.ports.repositories.user.find-user-by-email-repository, so a change to application.ports.repositories.user.find-user-by-email-repository can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break application.ports.repositories.user.find-user-by-email-repository.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→8 application.use-cases.sign-in.sign-in uses application.ports.security.jwt-token✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in application.ports.security.jwt-token.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.application.ports.security.jwt-token.JwtToken
- Direction
- application.use-cases.sign-in.sign-in uses application.ports.security.jwt-token, so a change to application.ports.security.jwt-token can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break application.ports.security.jwt-token.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→9 application.use-cases.sign-in.sign-in uses application.ports.security.password-hashing✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in application.ports.security.password-hashing.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.application.ports.security.password-hashing.PasswordHashing
- Direction
- application.use-cases.sign-in.sign-in uses application.ports.security.password-hashing, so a change to application.ports.security.password-hashing can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break application.ports.security.password-hashing.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→10 application.use-cases.sign-in.sign-in uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.sign-in.sign-in uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→11 application.use-cases.sign-in.sign-in uses domain.models.sign-in.sign-in-request-model✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in domain.models.sign-in.sign-in-request-model.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.domain.models.sign-in.sign-in-request-model.SignInRequestModel
- Direction
- application.use-cases.sign-in.sign-in uses domain.models.sign-in.sign-in-request-model, so a change to domain.models.sign-in.sign-in-request-model can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break domain.models.sign-in.sign-in-request-model.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→12 application.use-cases.sign-in.sign-in uses domain.models.user.user✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in domain.models.user.user.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.domain.models.user.user.User
- Direction
- application.use-cases.sign-in.sign-in uses domain.models.user.user, so a change to domain.models.user.user can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break domain.models.user.user.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
28→24 application.use-cases.sign-in.sign-in uses domain.use-cases.sign-in.sign-in-use-case✕
- Connections
- 1 pair of types, where a type in application.use-cases.sign-in.sign-in uses a type in domain.use-cases.sign-in.sign-in-use-case.
- The types involved
src.application.use-cases.sign-in.sign-in.SignIn→src.domain.use-cases.sign-in.sign-in-use-case.SignInUseCase
- Direction
- application.use-cases.sign-in.sign-in uses domain.use-cases.sign-in.sign-in-use-case, so a change to domain.use-cases.sign-in.sign-in-use-case can break application.use-cases.sign-in.sign-in, while a change to application.use-cases.sign-in.sign-in can't break domain.use-cases.sign-in.sign-in-use-case.
- Position
- Below the diagonal: application.use-cases.sign-in.sign-in uses a module listed above it, which is the healthy direction.
29→4 application.use-cases.user.find-user-by-id uses application.ports.repositories.user.find-user-by-id-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.find-user-by-id uses a type in application.ports.repositories.user.find-user-by-id-repository.
- The types involved
src.application.use-cases.user.find-user-by-id.FindUserById→src.application.ports.repositories.user.find-user-by-id-repository.FindUserByIdRepository
- Direction
- application.use-cases.user.find-user-by-id uses application.ports.repositories.user.find-user-by-id-repository, so a change to application.ports.repositories.user.find-user-by-id-repository can break application.use-cases.user.find-user-by-id, while a change to application.use-cases.user.find-user-by-id can't break application.ports.repositories.user.find-user-by-id-repository.
- Position
- Below the diagonal: application.use-cases.user.find-user-by-id uses a module listed above it, which is the healthy direction.
29→10 application.use-cases.user.find-user-by-id uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.find-user-by-id uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.user.find-user-by-id.FindUserById→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.user.find-user-by-id uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.user.find-user-by-id, while a change to application.use-cases.user.find-user-by-id can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.user.find-user-by-id uses a module listed above it, which is the healthy direction.
29→25 application.use-cases.user.find-user-by-id uses domain.use-cases.user.find-user-by-id-use-case✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.find-user-by-id uses a type in domain.use-cases.user.find-user-by-id-use-case.
- The types involved
src.application.use-cases.user.find-user-by-id.FindUserById→src.domain.use-cases.user.find-user-by-id-use-case.FindUserByIdUseCase
- Direction
- application.use-cases.user.find-user-by-id uses domain.use-cases.user.find-user-by-id-use-case, so a change to domain.use-cases.user.find-user-by-id-use-case can break application.use-cases.user.find-user-by-id, while a change to application.use-cases.user.find-user-by-id can't break domain.use-cases.user.find-user-by-id-use-case.
- Position
- Below the diagonal: application.use-cases.user.find-user-by-id uses a module listed above it, which is the healthy direction.
30→3 application.use-cases.user.update-user uses application.ports.repositories.user.find-user-by-email-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in application.ports.repositories.user.find-user-by-email-repository.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.application.ports.repositories.user.find-user-by-email-repository.FindUserByEmailRepository
- Direction
- application.use-cases.user.update-user uses application.ports.repositories.user.find-user-by-email-repository, so a change to application.ports.repositories.user.find-user-by-email-repository can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break application.ports.repositories.user.find-user-by-email-repository.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→4 application.use-cases.user.update-user uses application.ports.repositories.user.find-user-by-id-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in application.ports.repositories.user.find-user-by-id-repository.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.application.ports.repositories.user.find-user-by-id-repository.FindUserByIdRepository
- Direction
- application.use-cases.user.update-user uses application.ports.repositories.user.find-user-by-id-repository, so a change to application.ports.repositories.user.find-user-by-id-repository can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break application.ports.repositories.user.find-user-by-id-repository.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→9 application.use-cases.user.update-user uses application.ports.security.password-hashing✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in application.ports.security.password-hashing.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.application.ports.security.password-hashing.PasswordHashing
- Direction
- application.use-cases.user.update-user uses application.ports.security.password-hashing, so a change to application.ports.security.password-hashing can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break application.ports.security.password-hashing.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→10 application.use-cases.user.update-user uses application.ports.validation.validation-composite✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in application.ports.validation.validation-composite.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.application.ports.validation.validation-composite.ValidationComposite
- Direction
- application.use-cases.user.update-user uses application.ports.validation.validation-composite, so a change to application.ports.validation.validation-composite can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break application.ports.validation.validation-composite.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→13 application.use-cases.user.update-user uses domain.models.user.user-request-partial-fields✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in domain.models.user.user-request-partial-fields.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.domain.models.user.user-request-partial-fields.UserRequestPartialFields
- Direction
- application.use-cases.user.update-user uses domain.models.user.user-request-partial-fields, so a change to domain.models.user.user-request-partial-fields can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break domain.models.user.user-request-partial-fields.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→16 application.use-cases.user.update-user uses application.ports.repositories.user.update-user-repository✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in application.ports.repositories.user.update-user-repository.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.application.ports.repositories.user.update-user-repository.UpdateUserRepository
- Direction
- application.use-cases.user.update-user uses application.ports.repositories.user.update-user-repository, so a change to application.ports.repositories.user.update-user-repository can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break application.ports.repositories.user.update-user-repository.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
30→26 application.use-cases.user.update-user uses domain.use-cases.user.update-user-use-case✕
- Connections
- 1 pair of types, where a type in application.use-cases.user.update-user uses a type in domain.use-cases.user.update-user-use-case.
- The types involved
src.application.use-cases.user.update-user.UpdateUser→src.domain.use-cases.user.update-user-use-case.UpdateUserUseCase
- Direction
- application.use-cases.user.update-user uses domain.use-cases.user.update-user-use-case, so a change to domain.use-cases.user.update-user-use-case can break application.use-cases.user.update-user, while a change to application.use-cases.user.update-user can't break domain.use-cases.user.update-user-use-case.
- Position
- Below the diagonal: application.use-cases.user.update-user uses a module listed above it, which is the healthy direction.
31→3 infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.find-user-by-email-repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.user.sql.repositories.user-sql-repository uses a type in application.ports.repositories.user.find-user-by-email-repository.
- The types involved
src.infrastructure.repositories.user.sql.repositories.user-sql-repository.UserSqlRepository→src.application.ports.repositories.user.find-user-by-email-repository.FindUserByEmailRepository
- Direction
- infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.find-user-by-email-repository, so a change to application.ports.repositories.user.find-user-by-email-repository can break infrastructure.repositories.user.sql.repositories.user-sql-repository, while a change to infrastructure.repositories.user.sql.repositories.user-sql-repository can't break application.ports.repositories.user.find-user-by-email-repository.
- Position
- Below the diagonal: infrastructure.repositories.user.sql.repositories.user-sql-repository uses a module listed above it, which is the healthy direction.
31→4 infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.find-user-by-id-repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.user.sql.repositories.user-sql-repository uses a type in application.ports.repositories.user.find-user-by-id-repository.
- The types involved
src.infrastructure.repositories.user.sql.repositories.user-sql-repository.UserSqlRepository→src.application.ports.repositories.user.find-user-by-id-repository.FindUserByIdRepository
- Direction
- infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.find-user-by-id-repository, so a change to application.ports.repositories.user.find-user-by-id-repository can break infrastructure.repositories.user.sql.repositories.user-sql-repository, while a change to infrastructure.repositories.user.sql.repositories.user-sql-repository can't break application.ports.repositories.user.find-user-by-id-repository.
- Position
- Below the diagonal: infrastructure.repositories.user.sql.repositories.user-sql-repository uses a module listed above it, which is the healthy direction.
31→13 infrastructure.repositories.user.sql.repositories.user-sql-repository uses domain.models.user.user-request-partial-fields✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.user.sql.repositories.user-sql-repository uses a type in domain.models.user.user-request-partial-fields.
- The types involved
src.infrastructure.repositories.user.sql.repositories.user-sql-repository.UserSqlRepository→src.domain.models.user.user-request-partial-fields.UserRequestPartialFields
- Direction
- infrastructure.repositories.user.sql.repositories.user-sql-repository uses domain.models.user.user-request-partial-fields, so a change to domain.models.user.user-request-partial-fields can break infrastructure.repositories.user.sql.repositories.user-sql-repository, while a change to infrastructure.repositories.user.sql.repositories.user-sql-repository can't break domain.models.user.user-request-partial-fields.
- Position
- Below the diagonal: infrastructure.repositories.user.sql.repositories.user-sql-repository uses a module listed above it, which is the healthy direction.
31→16 infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.update-user-repository✕
- Connections
- 1 pair of types, where a type in infrastructure.repositories.user.sql.repositories.user-sql-repository uses a type in application.ports.repositories.user.update-user-repository.
- The types involved
src.infrastructure.repositories.user.sql.repositories.user-sql-repository.UserSqlRepository→src.application.ports.repositories.user.update-user-repository.UpdateUserRepository
- Direction
- infrastructure.repositories.user.sql.repositories.user-sql-repository uses application.ports.repositories.user.update-user-repository, so a change to application.ports.repositories.user.update-user-repository can break infrastructure.repositories.user.sql.repositories.user-sql-repository, while a change to infrastructure.repositories.user.sql.repositories.user-sql-repository can't break application.ports.repositories.user.update-user-repository.
- Position
- Below the diagonal: infrastructure.repositories.user.sql.repositories.user-sql-repository uses a module listed above it, which is the healthy direction.
32→6 presentation.controllers.sign-in.sign-in-controller uses application.ports.requests.request-model✕
- Connections
- 1 pair of types, where a type in presentation.controllers.sign-in.sign-in-controller uses a type in application.ports.requests.request-model.
- The types involved
src.presentation.controllers.sign-in.sign-in-controller.SignInController→src.application.ports.requests.request-model.RequestModel
- Direction
- presentation.controllers.sign-in.sign-in-controller uses application.ports.requests.request-model, so a change to application.ports.requests.request-model can break presentation.controllers.sign-in.sign-in-controller, while a change to presentation.controllers.sign-in.sign-in-controller can't break application.ports.requests.request-model.
- Position
- Below the diagonal: presentation.controllers.sign-in.sign-in-controller uses a module listed above it, which is the healthy direction.
32→11 presentation.controllers.sign-in.sign-in-controller uses domain.models.sign-in.sign-in-request-model✕
- Connections
- 1 pair of types, where a type in presentation.controllers.sign-in.sign-in-controller uses a type in domain.models.sign-in.sign-in-request-model.
- The types involved
src.presentation.controllers.sign-in.sign-in-controller.SignInController→src.domain.models.sign-in.sign-in-request-model.SignInRequestModel
- Direction
- presentation.controllers.sign-in.sign-in-controller uses domain.models.sign-in.sign-in-request-model, so a change to domain.models.sign-in.sign-in-request-model can break presentation.controllers.sign-in.sign-in-controller, while a change to presentation.controllers.sign-in.sign-in-controller can't break domain.models.sign-in.sign-in-request-model.
- Position
- Below the diagonal: presentation.controllers.sign-in.sign-in-controller uses a module listed above it, which is the healthy direction.
32→14 presentation.controllers.sign-in.sign-in-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.sign-in.sign-in-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.sign-in.sign-in-controller.SignInController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.sign-in.sign-in-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.sign-in.sign-in-controller, while a change to presentation.controllers.sign-in.sign-in-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.sign-in.sign-in-controller uses a module listed above it, which is the healthy direction.
32→17 presentation.controllers.sign-in.sign-in-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.sign-in.sign-in-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.sign-in.sign-in-controller.SignInController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.sign-in.sign-in-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.sign-in.sign-in-controller, while a change to presentation.controllers.sign-in.sign-in-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.sign-in.sign-in-controller uses a module listed above it, which is the healthy direction.
32→24 presentation.controllers.sign-in.sign-in-controller uses domain.use-cases.sign-in.sign-in-use-case✕
- Connections
- 1 pair of types, where a type in presentation.controllers.sign-in.sign-in-controller uses a type in domain.use-cases.sign-in.sign-in-use-case.
- The types involved
src.presentation.controllers.sign-in.sign-in-controller.SignInController→src.domain.use-cases.sign-in.sign-in-use-case.SignInUseCase
- Direction
- presentation.controllers.sign-in.sign-in-controller uses domain.use-cases.sign-in.sign-in-use-case, so a change to domain.use-cases.sign-in.sign-in-use-case can break presentation.controllers.sign-in.sign-in-controller, while a change to presentation.controllers.sign-in.sign-in-controller can't break domain.use-cases.sign-in.sign-in-use-case.
- Position
- Below the diagonal: presentation.controllers.sign-in.sign-in-controller uses a module listed above it, which is the healthy direction.
33→12 presentation.controllers.user.create-user-controller uses domain.models.user.user✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.create-user-controller uses a type in domain.models.user.user.
- The types involved
src.presentation.controllers.user.create-user-controller.CreateUserController→src.domain.models.user.user.User
- Direction
- presentation.controllers.user.create-user-controller uses domain.models.user.user, so a change to domain.models.user.user can break presentation.controllers.user.create-user-controller, while a change to presentation.controllers.user.create-user-controller can't break domain.models.user.user.
- Position
- Below the diagonal: presentation.controllers.user.create-user-controller uses a module listed above it, which is the healthy direction.
33→14 presentation.controllers.user.create-user-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.create-user-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.user.create-user-controller.CreateUserController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.user.create-user-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.user.create-user-controller, while a change to presentation.controllers.user.create-user-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.user.create-user-controller uses a module listed above it, which is the healthy direction.
33→17 presentation.controllers.user.create-user-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.create-user-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.user.create-user-controller.CreateUserController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.user.create-user-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.user.create-user-controller, while a change to presentation.controllers.user.create-user-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.user.create-user-controller uses a module listed above it, which is the healthy direction.
34→6 presentation.controllers.user.delete-user-by-id-controller uses application.ports.requests.request-model✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.delete-user-by-id-controller uses a type in application.ports.requests.request-model.
- The types involved
src.presentation.controllers.user.delete-user-by-id-controller.DeleteUserByIdController→src.application.ports.requests.request-model.RequestModel
- Direction
- presentation.controllers.user.delete-user-by-id-controller uses application.ports.requests.request-model, so a change to application.ports.requests.request-model can break presentation.controllers.user.delete-user-by-id-controller, while a change to presentation.controllers.user.delete-user-by-id-controller can't break application.ports.requests.request-model.
- Position
- Below the diagonal: presentation.controllers.user.delete-user-by-id-controller uses a module listed above it, which is the healthy direction.
34→14 presentation.controllers.user.delete-user-by-id-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.delete-user-by-id-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.user.delete-user-by-id-controller.DeleteUserByIdController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.user.delete-user-by-id-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.user.delete-user-by-id-controller, while a change to presentation.controllers.user.delete-user-by-id-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.user.delete-user-by-id-controller uses a module listed above it, which is the healthy direction.
34→17 presentation.controllers.user.delete-user-by-id-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.delete-user-by-id-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.user.delete-user-by-id-controller.DeleteUserByIdController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.user.delete-user-by-id-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.user.delete-user-by-id-controller, while a change to presentation.controllers.user.delete-user-by-id-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.user.delete-user-by-id-controller uses a module listed above it, which is the healthy direction.
35→14 presentation.controllers.user.find-all-users-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-all-users-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.user.find-all-users-controller.FindAllUsersController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.user.find-all-users-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.user.find-all-users-controller, while a change to presentation.controllers.user.find-all-users-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.user.find-all-users-controller uses a module listed above it, which is the healthy direction.
35→17 presentation.controllers.user.find-all-users-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-all-users-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.user.find-all-users-controller.FindAllUsersController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.user.find-all-users-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.user.find-all-users-controller, while a change to presentation.controllers.user.find-all-users-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.user.find-all-users-controller uses a module listed above it, which is the healthy direction.
36→6 presentation.controllers.user.find-by-id-controller uses application.ports.requests.request-model✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-by-id-controller uses a type in application.ports.requests.request-model.
- The types involved
src.presentation.controllers.user.find-by-id-controller.FindUserByIdController→src.application.ports.requests.request-model.RequestModel
- Direction
- presentation.controllers.user.find-by-id-controller uses application.ports.requests.request-model, so a change to application.ports.requests.request-model can break presentation.controllers.user.find-by-id-controller, while a change to presentation.controllers.user.find-by-id-controller can't break application.ports.requests.request-model.
- Position
- Below the diagonal: presentation.controllers.user.find-by-id-controller uses a module listed above it, which is the healthy direction.
36→12 presentation.controllers.user.find-by-id-controller uses domain.models.user.user✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-by-id-controller uses a type in domain.models.user.user.
- The types involved
src.presentation.controllers.user.find-by-id-controller.FindUserByIdController→src.domain.models.user.user.User
- Direction
- presentation.controllers.user.find-by-id-controller uses domain.models.user.user, so a change to domain.models.user.user can break presentation.controllers.user.find-by-id-controller, while a change to presentation.controllers.user.find-by-id-controller can't break domain.models.user.user.
- Position
- Below the diagonal: presentation.controllers.user.find-by-id-controller uses a module listed above it, which is the healthy direction.
36→14 presentation.controllers.user.find-by-id-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-by-id-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.user.find-by-id-controller.FindUserByIdController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.user.find-by-id-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.user.find-by-id-controller, while a change to presentation.controllers.user.find-by-id-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.user.find-by-id-controller uses a module listed above it, which is the healthy direction.
36→17 presentation.controllers.user.find-by-id-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-by-id-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.user.find-by-id-controller.FindUserByIdController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.user.find-by-id-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.user.find-by-id-controller, while a change to presentation.controllers.user.find-by-id-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.user.find-by-id-controller uses a module listed above it, which is the healthy direction.
36→25 presentation.controllers.user.find-by-id-controller uses domain.use-cases.user.find-user-by-id-use-case✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.find-by-id-controller uses a type in domain.use-cases.user.find-user-by-id-use-case.
- The types involved
src.presentation.controllers.user.find-by-id-controller.FindUserByIdController→src.domain.use-cases.user.find-user-by-id-use-case.FindUserByIdUseCase
- Direction
- presentation.controllers.user.find-by-id-controller uses domain.use-cases.user.find-user-by-id-use-case, so a change to domain.use-cases.user.find-user-by-id-use-case can break presentation.controllers.user.find-by-id-controller, while a change to presentation.controllers.user.find-by-id-controller can't break domain.use-cases.user.find-user-by-id-use-case.
- Position
- Below the diagonal: presentation.controllers.user.find-by-id-controller uses a module listed above it, which is the healthy direction.
37→14 presentation.controllers.user.update-user-controller uses application.ports.controllers.controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.update-user-controller uses a type in application.ports.controllers.controller.
- The types involved
src.presentation.controllers.user.update-user-controller.UpdateUserController→src.application.ports.controllers.controller.Controller
- Direction
- presentation.controllers.user.update-user-controller uses application.ports.controllers.controller, so a change to application.ports.controllers.controller can break presentation.controllers.user.update-user-controller, while a change to presentation.controllers.user.update-user-controller can't break application.ports.controllers.controller.
- Position
- Below the diagonal: presentation.controllers.user.update-user-controller uses a module listed above it, which is the healthy direction.
37→17 presentation.controllers.user.update-user-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.update-user-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.user.update-user-controller.UpdateUserController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.user.update-user-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.user.update-user-controller, while a change to presentation.controllers.user.update-user-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.user.update-user-controller uses a module listed above it, which is the healthy direction.
37→26 presentation.controllers.user.update-user-controller uses domain.use-cases.user.update-user-use-case✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.update-user-controller uses a type in domain.use-cases.user.update-user-use-case.
- The types involved
src.presentation.controllers.user.update-user-controller.UpdateUserController→src.domain.use-cases.user.update-user-use-case.UpdateUserUseCase
- Direction
- presentation.controllers.user.update-user-controller uses domain.use-cases.user.update-user-use-case, so a change to domain.use-cases.user.update-user-use-case can break presentation.controllers.user.update-user-controller, while a change to presentation.controllers.user.update-user-controller can't break domain.use-cases.user.update-user-use-case.
- Position
- Below the diagonal: presentation.controllers.user.update-user-controller uses a module listed above it, which is the healthy direction.
37→40 presentation.controllers.user.update-user-controller uses presentation.controllers.token.refresh-token-controller part of a loop✕
- Connections
- 1 pair of types, where a type in presentation.controllers.user.update-user-controller uses a type in presentation.controllers.token.refresh-token-controller.
- The types involved
src.presentation.controllers.user.update-user-controller.UpdateUserController→src.presentation.controllers.token.refresh-token-controller.ResponseType
- Direction
- presentation.controllers.user.update-user-controller uses presentation.controllers.token.refresh-token-controller, so a change to presentation.controllers.token.refresh-token-controller can break presentation.controllers.user.update-user-controller, while a change to presentation.controllers.user.update-user-controller can't break presentation.controllers.token.refresh-token-controller.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→5 presentation.middlewares.authentication.is-authenticated uses application.ports.requests.middleware-request-model✕
- Connections
- 1 pair of types, where a type in presentation.middlewares.authentication.is-authenticated uses a type in application.ports.requests.middleware-request-model.
- The types involved
src.presentation.middlewares.authentication.is-authenticated.IsAuthenticatedMiddleware→src.application.ports.requests.middleware-request-model.MiddlewareRequestModel
- Direction
- presentation.middlewares.authentication.is-authenticated uses application.ports.requests.middleware-request-model, so a change to application.ports.requests.middleware-request-model can break presentation.middlewares.authentication.is-authenticated, while a change to presentation.middlewares.authentication.is-authenticated can't break application.ports.requests.middleware-request-model.
- Position
- Below the diagonal: presentation.middlewares.authentication.is-authenticated uses a module listed above it, which is the healthy direction.
38→15 presentation.middlewares.authentication.is-authenticated uses application.ports.middlewares.middleware✕
- Connections
- 1 pair of types, where a type in presentation.middlewares.authentication.is-authenticated uses a type in application.ports.middlewares.middleware.
- The types involved
src.presentation.middlewares.authentication.is-authenticated.IsAuthenticatedMiddleware→src.application.ports.middlewares.middleware.Middleware
- Direction
- presentation.middlewares.authentication.is-authenticated uses application.ports.middlewares.middleware, so a change to application.ports.middlewares.middleware can break presentation.middlewares.authentication.is-authenticated, while a change to presentation.middlewares.authentication.is-authenticated can't break application.ports.middlewares.middleware.
- Position
- Below the diagonal: presentation.middlewares.authentication.is-authenticated uses a module listed above it, which is the healthy direction.
39→5 presentation.middlewares.authentication.logged-user-is-target-user uses application.ports.requests.middleware-request-model✕
- Connections
- 1 pair of types, where a type in presentation.middlewares.authentication.logged-user-is-target-user uses a type in application.ports.requests.middleware-request-model.
- The types involved
src.presentation.middlewares.authentication.logged-user-is-target-user.LoggedUserIsTargetUserMiddleware→src.application.ports.requests.middleware-request-model.MiddlewareRequestModel
- Direction
- presentation.middlewares.authentication.logged-user-is-target-user uses application.ports.requests.middleware-request-model, so a change to application.ports.requests.middleware-request-model can break presentation.middlewares.authentication.logged-user-is-target-user, while a change to presentation.middlewares.authentication.logged-user-is-target-user can't break application.ports.requests.middleware-request-model.
- Position
- Below the diagonal: presentation.middlewares.authentication.logged-user-is-target-user uses a module listed above it, which is the healthy direction.
39→15 presentation.middlewares.authentication.logged-user-is-target-user uses application.ports.middlewares.middleware✕
- Connections
- 1 pair of types, where a type in presentation.middlewares.authentication.logged-user-is-target-user uses a type in application.ports.middlewares.middleware.
- The types involved
src.presentation.middlewares.authentication.logged-user-is-target-user.LoggedUserIsTargetUserMiddleware→src.application.ports.middlewares.middleware.Middleware
- Direction
- presentation.middlewares.authentication.logged-user-is-target-user uses application.ports.middlewares.middleware, so a change to application.ports.middlewares.middleware can break presentation.middlewares.authentication.logged-user-is-target-user, while a change to presentation.middlewares.authentication.logged-user-is-target-user can't break application.ports.middlewares.middleware.
- Position
- Below the diagonal: presentation.middlewares.authentication.logged-user-is-target-user uses a module listed above it, which is the healthy direction.
40→17 presentation.controllers.token.refresh-token-controller uses application.ports.responses.response-handler✕
- Connections
- 1 pair of types, where a type in presentation.controllers.token.refresh-token-controller uses a type in application.ports.responses.response-handler.
- The types involved
src.presentation.controllers.token.refresh-token-controller.RefreshTokenController→src.application.ports.responses.response-handler.ResponseHandler
- Direction
- presentation.controllers.token.refresh-token-controller uses application.ports.responses.response-handler, so a change to application.ports.responses.response-handler can break presentation.controllers.token.refresh-token-controller, while a change to presentation.controllers.token.refresh-token-controller can't break application.ports.responses.response-handler.
- Position
- Below the diagonal: presentation.controllers.token.refresh-token-controller uses a module listed above it, which is the healthy direction.
40→37 presentation.controllers.token.refresh-token-controller uses presentation.controllers.user.update-user-controller✕
- Connections
- 1 pair of types, where a type in presentation.controllers.token.refresh-token-controller uses a type in presentation.controllers.user.update-user-controller.
- The types involved
src.presentation.controllers.token.refresh-token-controller.RefreshTokenController→src.presentation.controllers.user.update-user-controller.RequestType
- Direction
- presentation.controllers.token.refresh-token-controller uses presentation.controllers.user.update-user-controller, so a change to presentation.controllers.user.update-user-controller can break presentation.controllers.token.refresh-token-controller, while a change to presentation.controllers.token.refresh-token-controller can't break presentation.controllers.user.update-user-controller.
- Position
- Below the diagonal: presentation.controllers.token.refresh-token-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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 80 | High / Critical |
| A07:2025 — Authentication Failures | 7 | High / Critical |
| A05:2025 — Injection | 2 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED; Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with token-sql-repository.ts, user-sql-repository.ts, sign-in.ts; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. | +21.5 pts | Low | REDACTED Scanning |
| Resolve the 5 Orphaned file finding(s) in Knowledge Freshness — start with token-sql-repository.ts, user-sql-repository.ts, sign-in.ts. | +4.1 pts | Low | Knowledge Freshness |
| Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with sign-in.test.ts, user.test.ts. | +2.3 pts | Low | Test Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +3.9 pts | Medium | CI/CD gates |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +3.9 pts | Medium | Observability |
| Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +3.9 pts | Medium | Security & performance tooling |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps. | +3.1 pts | Medium | Data Protection |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +1.2 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Near-clean | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/infrastructure/express/routes/sign-in.test.ts | 8.0 | Near-clean | Test Quality: No assertions (empty test): should test |
| src/infrastructure/express/routes/user.test.ts | 8.0 | Near-clean | Test Quality: No assertions (empty test): should test |
| src/application/validation/user/composite/create-user-validation.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/application/validation/user/composite/create-user-validation.ts |
| src/application/validation/user/composite/update-user-validation.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/application/validation/user/composite/update-user-validation.ts |
| src/infrastructure/repositories/token/token-default-repository.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/infrastructure/repositories/token/token-default-repository.ts |
| src/infrastructure/repositories/user/user-default-repository.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/infrastructure/repositories/user/user-default-repository.ts |
| src/main/factories/controllers/sign-in/sign-in-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/sign-in/sign-in-controller-factory.ts |
| src/main/factories/controllers/token/refresh-token-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/token/refresh-token-controller-factory.ts |
| src/main/factories/controllers/user/create-user-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/user/create-user-controller-factory.ts |
| src/main/factories/controllers/user/delete-user-by-id-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/user/delete-user-by-id-controller-factory.ts |
| src/main/factories/controllers/user/find-all-users-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/user/find-all-users-controller-factory.ts |
| src/main/factories/controllers/user/find-user-by-id-controller-factory.ts | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/factories/controllers/user/find-user-by-id-controller-factory.ts |
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 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 73 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, 133 of 142 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 — 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. 9 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 15 production file(s) those files import that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 76.1% rather than published as low coverage. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository's 1 committed lockfile(s) are in a format this engine does not resolve. The resolver reads pnpm-lock.yaml, REDACTED / npm-shrinkwrap.json at lockfileVersion 2 or 3, yarn.lock in both the classic and berry dialects, and bun's text bun.lock; what it cannot read is bun.lockb, a binary serialisation of bun's install graph with no published layout, and a lockfileVersion 1 REDACTED, which is a differently-shaped nested tree. So nothing here could be graded and registry.npmjs.org was never asked. This is OUR side and it is a COLLECTOR gap, not an environment fault: the remedy is to write the reader for the format this repository commits, and no change to the scan image or the egress allowlist can close it.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 178 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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 defines its own container in src/main/factories/middlewares/authentication/is-authenticated-middleware-factory.ts, 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.
- 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 129 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- 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.
- 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 this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 76.1% — 13 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `npm ci --ignore-scripts` in the repository root).
What to do
- Resolve the 13 Low coverage finding(s) in Code Coverage — start with create-user-validation.ts, update-user-validation.ts, token-default-repository.ts. — One of this dimension's main actionable groups (13 warning-level).
- Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
181 test methods: 181 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 181 `it`/`test` case(s) across 52 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 181 tests.
What to do
- Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with sign-in.test.ts, user.test.ts. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 Mock-dominated test finding(s) in Test Quality — start with user-composite-validation.spec.ts. — One of this dimension's main actionable groups (1 recommendation-level).
- Stand up a CI pipeline, then gate Test Quality in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (128 tests)): measured (0 flaky).
D13 · REDACTED Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: src/presentation/middlewares/authentication/logged-user-is-target-user.ts (3 of 5 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with logged-user-is-target-user.ts. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 2068 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D24 · Comment Value
0 of 30 judged comments only repeat the code they sit on (0.0 %). 5 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
5 finding(s): 0 critical, 5 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 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 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)
2 finding(s): 0 critical, 1 high, 1 medium, 0 low.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
80 finding(s): 10 critical, 44 high, 17 medium, 9 low.
What to do
- Resolve the 44 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (44). — One of this dimension's main actionable groups (44 issue-level).
- Resolve the 17 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17). — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 10 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
D31 · IaC & Container Security
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
5 of 5 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/infrastructure/repositories/token/sql/token-sql-repository.ts. Counted over 5 of the 131 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 5 Orphaned file finding(s) in Knowledge Freshness — start with token-sql-repository.ts, user-sql-repository.ts, sign-in.ts. — One of this dimension's main actionable groups (5 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 0 platform declaration(s) and 10 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
C1 · Data Protection
- No in-app HTTPS enforcement, but a trusted-proxy setting ('trust proxy' / trustProxy) indicates a reverse-proxy topology — terminating TLS in the app would be wrong in this layout. Verify the reverse proxy enforces TLS. — src/infrastructure/express/setup/setup-app.ts:4
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — src/application/use-cases/sign-in/sign-in.ts:93
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 129 JavaScript/TypeScript production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:37
What to do
- Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
P8 · Schema migrations
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6 · src/application/validation/user/leaf/user-required-fields-validation.ts:9 — the two spans are one implementation copied and then locally edited — 124 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6
- src/application/validation/user/leaf/user-passwords-must-match-validation.ts:6 · src/application/validation/user/leaf/user-required-fields-validation.ts:6 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/application/validation/user/leaf/user-passwords-must-match-validation.ts:6
- src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6 · src/application/validation/user/leaf/user-passwords-must-match-validation.ts:7 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6
- src/infrastructure/knex/migrations/20201202132246_create_token.ts:1 · src/infrastructure/knex/migrations/20201206220633_create_user_roles.ts:1 — the two spans are one implementation copied and then locally edited — 115 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infrastructure/knex/migrations/20201202132246_create_token.ts:1
- src/infrastructure/repositories/token/sql/token-sql-repository.ts:21 · src/infrastructure/repositories/token/sql/token-sql-repository.ts:39 · src/infrastructure/repositories/token/sql/token-sql-repository.ts:57 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/infrastructure/repositories/token/sql/token-sql-repository.ts:21
- src/infrastructure/knex/migrations/20201202132246_create_token.ts:1 · src/infrastructure/knex/migrations/20201206220538_create_roles.ts:1 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/infrastructure/knex/migrations/20201202132246_create_token.ts:1
- src/application/use-cases/user/delete-user-by-id.ts:10 · src/application/use-cases/user/find-user-by-id.ts:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/application/use-cases/user/delete-user-by-id.ts:10
- src/infrastructure/express/adapters/express-middleware-adapter.ts:5 · src/infrastructure/express/adapters/express-route-adapter.ts:5 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/infrastructure/express/adapters/express-middleware-adapter.ts:5
- src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts:26 · src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts:32 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts:26
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- src/application/use-cases/sign-in/sign-in.spec.ts:7 imports src/infrastructure/repositories/token/sql/token-sql-repository.ts against the layered-src rules. — src/application/use-cases/sign-in/sign-in.spec.ts:7
What to do
- Fix the listed violations: respect the layer/slice order — import only through a slice's public index and never upward into a higher layer (1 row).
R2 · Cyclomatic Complexity
- (top-level) has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — src/application/validation/user/leaf/user-passwords-must-match-validation.ts:1, src/application/validation/user/leaf/user-required-fields-validation.ts:1
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — src/infrastructure/knex/seeds/01_users.ts:1, src/infrastructure/knex/seeds/02_roles.ts:1, src/infrastructure/knex/seeds/03_user_roles.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 44 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 2 application, 10 tooling and 52 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (2 application, 10 tooling, 52 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — src/infrastructure/knex/seeds/01_users.ts, src/infrastructure/knex/seeds/02_roles.ts, src/infrastructure/knex/seeds/03_user_roles.ts
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — src/infrastructure/express/routes/user.test.ts:6
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~0.8 `!` null assertions per 1k TypeScript source lines — 2 assertion(s) across the 2521 source line(s) of the 125 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/infrastructure/repositories/user/sql/helpers/map-user-fields.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 94% | Exemplary | Solid. |
| Architecture | 82% | Strong | Solid. |
| Maturity | 61% | Adequate — gated by D34 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 22% | Weak — gated by D13, P1, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Adequate | Acceptable, with room to improve. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 62 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D12 Dependency Hygiene — Dependency currency not established — no reader for this repository's lockfile format
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 — D21 withholds its sibling role token rows: 1 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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 npm 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
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/infrastructure/express/server.ts:8 (express()))
- P9 Domain vs controller coverage — coverage data present for 76 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — Not assessed: 129 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- 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
- 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 — 64 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): should test src/infrastructure/express/routes/sign-in.test.ts:70
- No assertions (empty test): should test src/infrastructure/express/routes/user.test.ts:238
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 53 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low coverage: src/application/validation/user/composite/create-user-validation.ts src/application/validation/user/composite/create-user-validation.ts:1
- Low coverage: src/application/validation/user/composite/update-user-validation.ts src/application/validation/user/composite/update-user-validation.ts:1
- Low coverage: src/infrastructure/repositories/token/token-default-repository.ts src/infrastructure/repositories/token/token-default-repository.ts:1
- Low coverage: src/infrastructure/repositories/user/user-default-repository.ts src/infrastructure/repositories/user/user-default-repository.ts:1
- Low coverage: src/main/factories/controllers/sign-in/sign-in-controller-factory.ts src/main/factories/controllers/sign-in/sign-in-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/token/refresh-token-controller-factory.ts src/main/factories/controllers/token/refresh-token-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/user/create-user-controller-factory.ts src/main/factories/controllers/user/create-user-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/user/delete-user-by-id-controller-factory.ts src/main/factories/controllers/user/delete-user-by-id-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/user/find-all-users-controller-factory.ts src/main/factories/controllers/user/find-all-users-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/user/find-user-by-id-controller-factory.ts src/main/factories/controllers/user/find-user-by-id-controller-factory.ts:1
- Low coverage: src/main/factories/controllers/user/update-user-controller-factory.ts src/main/factories/controllers/user/update-user-controller-factory.ts:1
- Low coverage: src/main/factories/middlewares/authentication/is-authenticated-middleware-factory.ts src/main/factories/middlewares/authentication/is-authenticated-middleware-factory.ts:1
- Low coverage: src/main/factories/middlewares/authentication/logged-user-is-target-user-middleware-factory.ts src/main/factories/middlewares/authentication/logged-user-is-target-user-middleware-factory.ts:1
- No test reaches this file src/infrastructure/knex/seeds/01_users.ts:1
- No test reaches this file src/infrastructure/knex/seeds/02_roles.ts:1
- No test reaches this file src/infrastructure/knex/seeds/03_user_roles.ts:1
- Duplicated block with local edits (15 matched lines × 2 locations) src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6
- Duplicated block with local edits (15 matched lines × 2 locations) src/infrastructure/knex/migrations/20201202132246_create_token.ts:1
- Complex function (top-level) (cyclomatic 12, cognitive 11) src/application/validation/user/leaf/user-passwords-must-match-validation.ts:1
- Complex function (top-level) (cyclomatic 12, cognitive 11) src/application/validation/user/leaf/user-required-fields-validation.ts:1
- Dead file (~19 LoC) src/infrastructure/knex/seeds/02_roles.ts
- Dead file (~19 LoC) src/infrastructure/knex/seeds/03_user_roles.ts
- Repeated repair: src/presentation/middlewares/authentication/logged-user-is-target-user.ts src/presentation/middlewares/authentication/logged-user-is-target-user.ts:9
- REDACTED
- No CI pipeline
- No structured logging
- Duplicated block with local edits (22 matched lines × 2 locations) src/application/validation/user/leaf/user-partial-required-fields-validation.ts:6
- Duplicated block with local edits (18 matched lines × 2 locations) src/application/validation/user/leaf/user-passwords-must-match-validation.ts:6
- Duplicated block (15 lines × 3 locations) src/infrastructure/repositories/token/sql/token-sql-repository.ts:21
- Duplicated block with local edits (11 matched lines × 2 locations) src/infrastructure/knex/migrations/20201202132246_create_token.ts:1
- Duplicated block (9 lines × 2 locations) src/application/use-cases/user/delete-user-by-id.ts:10
- Duplicated block (8 lines × 2 locations) src/infrastructure/express/adapters/express-middleware-adapter.ts:5
- Duplicated block (5 lines × 2 locations) src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts:26
- Boundary violation [layered:upward-import] src/application/use-cases/sign-in/sign-in.spec.ts:7
- Dependency Freshness
- Dead file (~23 LoC) src/infrastructure/knex/seeds/01_users.ts
Minor — 25 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/infrastructure/repositories/token/sql/token-sql-repository.ts:1
- Orphaned file src/infrastructure/repositories/user/sql/repositories/user-sql-repository.ts:1
- Orphaned file src/application/use-cases/sign-in/sign-in.ts:1
- Orphaned file src/application/use-cases/user/update-user.ts:1
- Orphaned file src/infrastructure/express/routes/user.ts:1
- No named authorization policies src/application/use-cases/sign-in/sign-in.ts:93
- Mock-dominated test: should call all validations with correct values src/application/validation/user/composite/user-composite-validation.spec.ts:42
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- No SAST
- No dependency-update automation package.json:37
- No rollback/health safety
- Unused module-local declaration 'testingUsersFactory' src/infrastructure/express/routes/user.test.ts:6
- Duplicated predicate src/presentation/controllers/user/delete-user-by-id-controller.ts:18
- Null assertions (`!`) reduce the strict null checking score
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-dd8c4d5566b042ccb95d1bd71ba56bab/history.json --exit-code 0 --source . | 5 | 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-dd8c4d5566b042ccb95d1bd71ba56bab/tree.json --exit-code 0 --source . | 3 | 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 . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 80 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 1 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |