Executive summary
dyarleniber/simple-blog-application-backend-challenge is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 59 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 44, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4 points. Adopting a logging library would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 69.
Thirty-two known security holes in the packages the code depends on can be used by attackers. Four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one secret can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting the secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code.
The product code is 1,971 lines, about €3,900 to rebuild.
If Production Readiness rose from 44 to 70, the lowest score rated Strong, the score would rise from 59 to about 69.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 5 findings
- 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 · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €3,900 · Estimate
| Cost to rebuild | €1,300 to €6,500, for 22 to 69 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | 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.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Very small: 1,971 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.interfaces.repositories.authentication.LoadUserByEmailRepository | 2 infra.http.interfaces.Validation | 3 application.interfaces.repositories.authentication.CreateUserRepository | 4 application.interfaces.repositories.comments.CreateCommentRepository | 5 application.interfaces.repositories.comments.GetCommentByIdRepository | 6 application.interfaces.repositories.posts.GetPostByIdRepository | 7 application.interfaces.use-cases.authentication.AuthenticateInterface | 8 application.interfaces.use-cases.authentication.SignInInterface | 9 application.interfaces.use-cases.authentication.SignUpInterface | 10 application.interfaces.use-cases.comments.CreateCommentInterface | 11 application.interfaces.use-cases.comments.DeleteCommentInterface | 12 application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface | 13 application.interfaces.use-cases.comments.GetCommentByIdInterface | 14 application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface | 15 application.interfaces.use-cases.comments.UpdateCommentInterface | 16 application.interfaces.use-cases.posts.CreatePostInterface | 17 application.interfaces.use-cases.posts.DeletePostInterface | 18 application.interfaces.use-cases.posts.GetLatestPostsInterface | 19 application.interfaces.use-cases.posts.GetPostByIdInterface | 20 application.interfaces.use-cases.posts.UpdatePostInterface | 21 application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface | 22 infra.http.controllers.BaseController | 23 infra.http.validations.ValidationComposite | 24 application.use-cases.authentication.SignIn | 25 application.use-cases.authentication.SignUp | 26 application.use-cases.comments.UpdateComment | 27 application.use-cases.posts.UpdatePost | 28 application.use-cases.posts.UpdatePostTotalComments | 29 infra.db.mongodb.repositories.CommentRepository | 30 infra.db.mongodb.repositories.PostRepository | 31 infra.http.controllers.authentication.SignInController | 32 infra.http.controllers.authentication.SignUpController | 33 infra.http.controllers.comments.CreateCommentController | 34 infra.http.controllers.comments.DeleteCommentController | 35 infra.http.controllers.comments.UpdateCommentController | 36 infra.http.controllers.posts.CreatePostController | 37 infra.http.controllers.posts.DeletePostController | 38 infra.http.controllers.posts.UpdatePostController | 39 main.factories.use-cases.comments | 40 main.factories.use-cases.posts |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 application.interfaces.repositories.authentication.LoadUserByEmailRepository | ||||||||||||||||||||||||||||||||||||||||
| 2 infra.http.interfaces.Validation | ||||||||||||||||||||||||||||||||||||||||
| 3 application.interfaces.repositories.authentication.CreateUserRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 application.interfaces.repositories.comments.CreateCommentRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 5 application.interfaces.repositories.comments.GetCommentByIdRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 application.interfaces.repositories.posts.GetPostByIdRepository | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 application.interfaces.use-cases.authentication.AuthenticateInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 application.interfaces.use-cases.authentication.SignInInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 application.interfaces.use-cases.authentication.SignUpInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 application.interfaces.use-cases.comments.CreateCommentInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 application.interfaces.use-cases.comments.DeleteCommentInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 application.interfaces.use-cases.comments.GetCommentByIdInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 application.interfaces.use-cases.comments.UpdateCommentInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 application.interfaces.use-cases.posts.CreatePostInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 application.interfaces.use-cases.posts.DeletePostInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 application.interfaces.use-cases.posts.GetLatestPostsInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 application.interfaces.use-cases.posts.GetPostByIdInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 application.interfaces.use-cases.posts.UpdatePostInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 infra.http.controllers.BaseController | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 infra.http.validations.ValidationComposite | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 application.use-cases.authentication.SignIn | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 application.use-cases.authentication.SignUp | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 26 application.use-cases.comments.UpdateComment | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 application.use-cases.posts.UpdatePost | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 application.use-cases.posts.UpdatePostTotalComments | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 infra.db.mongodb.repositories.CommentRepository | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 infra.db.mongodb.repositories.PostRepository | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 infra.http.controllers.authentication.SignInController | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 infra.http.controllers.authentication.SignUpController | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 infra.http.controllers.comments.CreateCommentController | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 infra.http.controllers.comments.DeleteCommentController | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 infra.http.controllers.comments.UpdateCommentController | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 infra.http.controllers.posts.CreatePostController | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 infra.http.controllers.posts.DeletePostController | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 infra.http.controllers.posts.UpdatePostController | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 main.factories.use-cases.comments | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 main.factories.use-cases.posts | 1 | 1 | 1 | 1 | 1 | 1 |
3→1 application.interfaces.repositories.authentication.CreateUserRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.repositories.authentication.CreateUserRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.repositories.authentication.CreateUserRepository.CreateUserRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.repositories.authentication.CreateUserRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.repositories.authentication.CreateUserRepository, while a change to application.interfaces.repositories.authentication.CreateUserRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.repositories.authentication.CreateUserRepository uses a module listed above it, which is the healthy direction.
4→1 application.interfaces.repositories.comments.CreateCommentRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.repositories.comments.CreateCommentRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.repositories.comments.CreateCommentRepository.CreateCommentRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.repositories.comments.CreateCommentRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.repositories.comments.CreateCommentRepository, while a change to application.interfaces.repositories.comments.CreateCommentRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.repositories.comments.CreateCommentRepository uses a module listed above it, which is the healthy direction.
5→1 application.interfaces.repositories.comments.GetCommentByIdRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.repositories.comments.GetCommentByIdRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.repositories.comments.GetCommentByIdRepository.GetCommentByIdRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.repositories.comments.GetCommentByIdRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.repositories.comments.GetCommentByIdRepository, while a change to application.interfaces.repositories.comments.GetCommentByIdRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.repositories.comments.GetCommentByIdRepository uses a module listed above it, which is the healthy direction.
6→1 application.interfaces.repositories.posts.GetPostByIdRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.repositories.posts.GetPostByIdRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.repositories.posts.GetPostByIdRepository.GetPostByIdRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.repositories.posts.GetPostByIdRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.repositories.posts.GetPostByIdRepository, while a change to application.interfaces.repositories.posts.GetPostByIdRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.repositories.posts.GetPostByIdRepository uses a module listed above it, which is the healthy direction.
7→1 application.interfaces.use-cases.authentication.AuthenticateInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.authentication.AuthenticateInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.authentication.AuthenticateInterface.AuthenticateInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.authentication.AuthenticateInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.authentication.AuthenticateInterface, while a change to application.interfaces.use-cases.authentication.AuthenticateInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.authentication.AuthenticateInterface uses a module listed above it, which is the healthy direction.
8→1 application.interfaces.use-cases.authentication.SignInInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.authentication.SignInInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.authentication.SignInInterface.SignInInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.authentication.SignInInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.authentication.SignInInterface, while a change to application.interfaces.use-cases.authentication.SignInInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.authentication.SignInInterface uses a module listed above it, which is the healthy direction.
9→1 application.interfaces.use-cases.authentication.SignUpInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.authentication.SignUpInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.authentication.SignUpInterface.SignUpInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.authentication.SignUpInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.authentication.SignUpInterface, while a change to application.interfaces.use-cases.authentication.SignUpInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.authentication.SignUpInterface uses a module listed above it, which is the healthy direction.
10→1 application.interfaces.use-cases.comments.CreateCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.CreateCommentInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.CreateCommentInterface.CreateCommentInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.CreateCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.CreateCommentInterface, while a change to application.interfaces.use-cases.comments.CreateCommentInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.CreateCommentInterface uses a module listed above it, which is the healthy direction.
11→1 application.interfaces.use-cases.comments.DeleteCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.DeleteCommentInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.DeleteCommentInterface.DeleteCommentInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.DeleteCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.DeleteCommentInterface, while a change to application.interfaces.use-cases.comments.DeleteCommentInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.DeleteCommentInterface uses a module listed above it, which is the healthy direction.
12→1 application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.DeleteCommentsByPostIdInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface, while a change to application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface uses a module listed above it, which is the healthy direction.
13→1 application.interfaces.use-cases.comments.GetCommentByIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.GetCommentByIdInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.GetCommentByIdInterface.GetCommentByIdInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.GetCommentByIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.GetCommentByIdInterface, while a change to application.interfaces.use-cases.comments.GetCommentByIdInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.GetCommentByIdInterface uses a module listed above it, which is the healthy direction.
14→1 application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface.GetLatestCommentsByPostIdInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface, while a change to application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface uses a module listed above it, which is the healthy direction.
15→1 application.interfaces.use-cases.comments.UpdateCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.comments.UpdateCommentInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.comments.UpdateCommentInterface.UpdateCommentInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.comments.UpdateCommentInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.comments.UpdateCommentInterface, while a change to application.interfaces.use-cases.comments.UpdateCommentInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.comments.UpdateCommentInterface uses a module listed above it, which is the healthy direction.
16→1 application.interfaces.use-cases.posts.CreatePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.CreatePostInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.CreatePostInterface.CreatePostInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.CreatePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.CreatePostInterface, while a change to application.interfaces.use-cases.posts.CreatePostInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.CreatePostInterface uses a module listed above it, which is the healthy direction.
17→1 application.interfaces.use-cases.posts.DeletePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.DeletePostInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.DeletePostInterface.DeletePostInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.DeletePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.DeletePostInterface, while a change to application.interfaces.use-cases.posts.DeletePostInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.DeletePostInterface uses a module listed above it, which is the healthy direction.
18→1 application.interfaces.use-cases.posts.GetLatestPostsInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.GetLatestPostsInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.GetLatestPostsInterface.GetLatestPostsInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.GetLatestPostsInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.GetLatestPostsInterface, while a change to application.interfaces.use-cases.posts.GetLatestPostsInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.GetLatestPostsInterface uses a module listed above it, which is the healthy direction.
19→1 application.interfaces.use-cases.posts.GetPostByIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.GetPostByIdInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.GetPostByIdInterface.GetPostByIdInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.GetPostByIdInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.GetPostByIdInterface, while a change to application.interfaces.use-cases.posts.GetPostByIdInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.GetPostByIdInterface uses a module listed above it, which is the healthy direction.
20→1 application.interfaces.use-cases.posts.UpdatePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.UpdatePostInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.UpdatePostInterface.UpdatePostInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.UpdatePostInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.UpdatePostInterface, while a change to application.interfaces.use-cases.posts.UpdatePostInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.UpdatePostInterface uses a module listed above it, which is the healthy direction.
21→1 application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.UpdatePostTotalCommentsInterface→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface, while a change to application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface uses a module listed above it, which is the healthy direction.
22→2 infra.http.controllers.BaseController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.BaseController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.BaseController.BaseController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.BaseController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.BaseController, while a change to infra.http.controllers.BaseController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.BaseController uses a module listed above it, which is the healthy direction.
23→2 infra.http.validations.ValidationComposite uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.validations.ValidationComposite uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.validations.ValidationComposite.ValidationComposite→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.validations.ValidationComposite uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.validations.ValidationComposite, while a change to infra.http.validations.ValidationComposite can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.validations.ValidationComposite uses a module listed above it, which is the healthy direction.
24→1 application.use-cases.authentication.SignIn uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 2 pairs of types, where a type in application.use-cases.authentication.SignIn uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.use-cases.authentication.SignIn.SignIn→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.LoadUserByEmailRepositorysrc.application.use-cases.authentication.SignIn.SignIn→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.use-cases.authentication.SignIn uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.use-cases.authentication.SignIn, while a change to application.use-cases.authentication.SignIn can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.use-cases.authentication.SignIn uses a module listed above it, which is the healthy direction.
24→8 application.use-cases.authentication.SignIn uses application.interfaces.use-cases.authentication.SignInInterface✕
- Connections
- 1 pair of types, where a type in application.use-cases.authentication.SignIn uses a type in application.interfaces.use-cases.authentication.SignInInterface.
- The types involved
src.application.use-cases.authentication.SignIn.SignIn→src.application.interfaces.use-cases.authentication.SignInInterface.SignInInterface
- Direction
- application.use-cases.authentication.SignIn uses application.interfaces.use-cases.authentication.SignInInterface, so a change to application.interfaces.use-cases.authentication.SignInInterface can break application.use-cases.authentication.SignIn, while a change to application.use-cases.authentication.SignIn can't break application.interfaces.use-cases.authentication.SignInInterface.
- Position
- Below the diagonal: application.use-cases.authentication.SignIn uses a module listed above it, which is the healthy direction.
25→1 application.use-cases.authentication.SignUp uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 2 pairs of types, where a type in application.use-cases.authentication.SignUp uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.use-cases.authentication.SignUp.SignUp→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.LoadUserByEmailRepositorysrc.application.use-cases.authentication.SignUp.SignUp→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.use-cases.authentication.SignUp uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.use-cases.authentication.SignUp, while a change to application.use-cases.authentication.SignUp can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.use-cases.authentication.SignUp uses a module listed above it, which is the healthy direction.
25→3 application.use-cases.authentication.SignUp uses application.interfaces.repositories.authentication.CreateUserRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.authentication.SignUp uses a type in application.interfaces.repositories.authentication.CreateUserRepository.
- The types involved
src.application.use-cases.authentication.SignUp.SignUp→src.application.interfaces.repositories.authentication.CreateUserRepository.CreateUserRepository
- Direction
- application.use-cases.authentication.SignUp uses application.interfaces.repositories.authentication.CreateUserRepository, so a change to application.interfaces.repositories.authentication.CreateUserRepository can break application.use-cases.authentication.SignUp, while a change to application.use-cases.authentication.SignUp can't break application.interfaces.repositories.authentication.CreateUserRepository.
- Position
- Below the diagonal: application.use-cases.authentication.SignUp uses a module listed above it, which is the healthy direction.
25→9 application.use-cases.authentication.SignUp uses application.interfaces.use-cases.authentication.SignUpInterface✕
- Connections
- 1 pair of types, where a type in application.use-cases.authentication.SignUp uses a type in application.interfaces.use-cases.authentication.SignUpInterface.
- The types involved
src.application.use-cases.authentication.SignUp.SignUp→src.application.interfaces.use-cases.authentication.SignUpInterface.SignUpInterface
- Direction
- application.use-cases.authentication.SignUp uses application.interfaces.use-cases.authentication.SignUpInterface, so a change to application.interfaces.use-cases.authentication.SignUpInterface can break application.use-cases.authentication.SignUp, while a change to application.use-cases.authentication.SignUp can't break application.interfaces.use-cases.authentication.SignUpInterface.
- Position
- Below the diagonal: application.use-cases.authentication.SignUp uses a module listed above it, which is the healthy direction.
26→1 application.use-cases.comments.UpdateComment uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.comments.UpdateComment uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.use-cases.comments.UpdateComment.UpdateComment→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.use-cases.comments.UpdateComment uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.use-cases.comments.UpdateComment, while a change to application.use-cases.comments.UpdateComment can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.use-cases.comments.UpdateComment uses a module listed above it, which is the healthy direction.
26→5 application.use-cases.comments.UpdateComment uses application.interfaces.repositories.comments.GetCommentByIdRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.comments.UpdateComment uses a type in application.interfaces.repositories.comments.GetCommentByIdRepository.
- The types involved
src.application.use-cases.comments.UpdateComment.UpdateComment→src.application.interfaces.repositories.comments.GetCommentByIdRepository.GetCommentByIdRepository
- Direction
- application.use-cases.comments.UpdateComment uses application.interfaces.repositories.comments.GetCommentByIdRepository, so a change to application.interfaces.repositories.comments.GetCommentByIdRepository can break application.use-cases.comments.UpdateComment, while a change to application.use-cases.comments.UpdateComment can't break application.interfaces.repositories.comments.GetCommentByIdRepository.
- Position
- Below the diagonal: application.use-cases.comments.UpdateComment uses a module listed above it, which is the healthy direction.
26→15 application.use-cases.comments.UpdateComment uses application.interfaces.use-cases.comments.UpdateCommentInterface✕
- Connections
- 1 pair of types, where a type in application.use-cases.comments.UpdateComment uses a type in application.interfaces.use-cases.comments.UpdateCommentInterface.
- The types involved
src.application.use-cases.comments.UpdateComment.UpdateComment→src.application.interfaces.use-cases.comments.UpdateCommentInterface.UpdateCommentInterface
- Direction
- application.use-cases.comments.UpdateComment uses application.interfaces.use-cases.comments.UpdateCommentInterface, so a change to application.interfaces.use-cases.comments.UpdateCommentInterface can break application.use-cases.comments.UpdateComment, while a change to application.use-cases.comments.UpdateComment can't break application.interfaces.use-cases.comments.UpdateCommentInterface.
- Position
- Below the diagonal: application.use-cases.comments.UpdateComment uses a module listed above it, which is the healthy direction.
27→1 application.use-cases.posts.UpdatePost uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.posts.UpdatePost uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.use-cases.posts.UpdatePost.UpdatePost→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.use-cases.posts.UpdatePost uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.use-cases.posts.UpdatePost, while a change to application.use-cases.posts.UpdatePost can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.use-cases.posts.UpdatePost uses a module listed above it, which is the healthy direction.
27→6 application.use-cases.posts.UpdatePost uses application.interfaces.repositories.posts.GetPostByIdRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.posts.UpdatePost uses a type in application.interfaces.repositories.posts.GetPostByIdRepository.
- The types involved
src.application.use-cases.posts.UpdatePost.UpdatePost→src.application.interfaces.repositories.posts.GetPostByIdRepository.GetPostByIdRepository
- Direction
- application.use-cases.posts.UpdatePost uses application.interfaces.repositories.posts.GetPostByIdRepository, so a change to application.interfaces.repositories.posts.GetPostByIdRepository can break application.use-cases.posts.UpdatePost, while a change to application.use-cases.posts.UpdatePost can't break application.interfaces.repositories.posts.GetPostByIdRepository.
- Position
- Below the diagonal: application.use-cases.posts.UpdatePost uses a module listed above it, which is the healthy direction.
27→20 application.use-cases.posts.UpdatePost uses application.interfaces.use-cases.posts.UpdatePostInterface✕
- Connections
- 1 pair of types, where a type in application.use-cases.posts.UpdatePost uses a type in application.interfaces.use-cases.posts.UpdatePostInterface.
- The types involved
src.application.use-cases.posts.UpdatePost.UpdatePost→src.application.interfaces.use-cases.posts.UpdatePostInterface.UpdatePostInterface
- Direction
- application.use-cases.posts.UpdatePost uses application.interfaces.use-cases.posts.UpdatePostInterface, so a change to application.interfaces.use-cases.posts.UpdatePostInterface can break application.use-cases.posts.UpdatePost, while a change to application.use-cases.posts.UpdatePost can't break application.interfaces.use-cases.posts.UpdatePostInterface.
- Position
- Below the diagonal: application.use-cases.posts.UpdatePost uses a module listed above it, which is the healthy direction.
28→1 application.use-cases.posts.UpdatePostTotalComments uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in application.use-cases.posts.UpdatePostTotalComments uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.application.use-cases.posts.UpdatePostTotalComments.UpdatePostTotalComments→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- application.use-cases.posts.UpdatePostTotalComments uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break application.use-cases.posts.UpdatePostTotalComments, while a change to application.use-cases.posts.UpdatePostTotalComments can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: application.use-cases.posts.UpdatePostTotalComments uses a module listed above it, which is the healthy direction.
28→21 application.use-cases.posts.UpdatePostTotalComments uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface✕
- Connections
- 1 pair of types, where a type in application.use-cases.posts.UpdatePostTotalComments uses a type in application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- The types involved
src.application.use-cases.posts.UpdatePostTotalComments.UpdatePostTotalComments→src.application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.UpdatePostTotalCommentsInterface
- Direction
- application.use-cases.posts.UpdatePostTotalComments uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface, so a change to application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface can break application.use-cases.posts.UpdatePostTotalComments, while a change to application.use-cases.posts.UpdatePostTotalComments can't break application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- Position
- Below the diagonal: application.use-cases.posts.UpdatePostTotalComments uses a module listed above it, which is the healthy direction.
29→1 infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.db.mongodb.repositories.CommentRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.db.mongodb.repositories.CommentRepository.CommentRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.db.mongodb.repositories.CommentRepository, while a change to infra.db.mongodb.repositories.CommentRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.db.mongodb.repositories.CommentRepository uses a module listed above it, which is the healthy direction.
29→4 infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.comments.CreateCommentRepository✕
- Connections
- 1 pair of types, where a type in infra.db.mongodb.repositories.CommentRepository uses a type in application.interfaces.repositories.comments.CreateCommentRepository.
- The types involved
src.infra.db.mongodb.repositories.CommentRepository.CommentRepository→src.application.interfaces.repositories.comments.CreateCommentRepository.CreateCommentRepository
- Direction
- infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.comments.CreateCommentRepository, so a change to application.interfaces.repositories.comments.CreateCommentRepository can break infra.db.mongodb.repositories.CommentRepository, while a change to infra.db.mongodb.repositories.CommentRepository can't break application.interfaces.repositories.comments.CreateCommentRepository.
- Position
- Below the diagonal: infra.db.mongodb.repositories.CommentRepository uses a module listed above it, which is the healthy direction.
29→5 infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.comments.GetCommentByIdRepository✕
- Connections
- 1 pair of types, where a type in infra.db.mongodb.repositories.CommentRepository uses a type in application.interfaces.repositories.comments.GetCommentByIdRepository.
- The types involved
src.infra.db.mongodb.repositories.CommentRepository.CommentRepository→src.application.interfaces.repositories.comments.GetCommentByIdRepository.GetCommentByIdRepository
- Direction
- infra.db.mongodb.repositories.CommentRepository uses application.interfaces.repositories.comments.GetCommentByIdRepository, so a change to application.interfaces.repositories.comments.GetCommentByIdRepository can break infra.db.mongodb.repositories.CommentRepository, while a change to infra.db.mongodb.repositories.CommentRepository can't break application.interfaces.repositories.comments.GetCommentByIdRepository.
- Position
- Below the diagonal: infra.db.mongodb.repositories.CommentRepository uses a module listed above it, which is the healthy direction.
30→1 infra.db.mongodb.repositories.PostRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.db.mongodb.repositories.PostRepository uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.db.mongodb.repositories.PostRepository.PostRepository→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.db.mongodb.repositories.PostRepository uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.db.mongodb.repositories.PostRepository, while a change to infra.db.mongodb.repositories.PostRepository can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.db.mongodb.repositories.PostRepository uses a module listed above it, which is the healthy direction.
30→6 infra.db.mongodb.repositories.PostRepository uses application.interfaces.repositories.posts.GetPostByIdRepository✕
- Connections
- 1 pair of types, where a type in infra.db.mongodb.repositories.PostRepository uses a type in application.interfaces.repositories.posts.GetPostByIdRepository.
- The types involved
src.infra.db.mongodb.repositories.PostRepository.PostRepository→src.application.interfaces.repositories.posts.GetPostByIdRepository.GetPostByIdRepository
- Direction
- infra.db.mongodb.repositories.PostRepository uses application.interfaces.repositories.posts.GetPostByIdRepository, so a change to application.interfaces.repositories.posts.GetPostByIdRepository can break infra.db.mongodb.repositories.PostRepository, while a change to infra.db.mongodb.repositories.PostRepository can't break application.interfaces.repositories.posts.GetPostByIdRepository.
- Position
- Below the diagonal: infra.db.mongodb.repositories.PostRepository uses a module listed above it, which is the healthy direction.
31→1 infra.http.controllers.authentication.SignInController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignInController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.authentication.SignInController.SignInController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.authentication.SignInController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.authentication.SignInController, while a change to infra.http.controllers.authentication.SignInController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignInController uses a module listed above it, which is the healthy direction.
31→2 infra.http.controllers.authentication.SignInController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignInController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.authentication.SignInController.SignInController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.authentication.SignInController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.authentication.SignInController, while a change to infra.http.controllers.authentication.SignInController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignInController uses a module listed above it, which is the healthy direction.
31→8 infra.http.controllers.authentication.SignInController uses application.interfaces.use-cases.authentication.SignInInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignInController uses a type in application.interfaces.use-cases.authentication.SignInInterface.
- The types involved
src.infra.http.controllers.authentication.SignInController.SignInController→src.application.interfaces.use-cases.authentication.SignInInterface.SignInInterface
- Direction
- infra.http.controllers.authentication.SignInController uses application.interfaces.use-cases.authentication.SignInInterface, so a change to application.interfaces.use-cases.authentication.SignInInterface can break infra.http.controllers.authentication.SignInController, while a change to infra.http.controllers.authentication.SignInController can't break application.interfaces.use-cases.authentication.SignInInterface.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignInController uses a module listed above it, which is the healthy direction.
31→22 infra.http.controllers.authentication.SignInController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignInController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.authentication.SignInController.SignInController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.authentication.SignInController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.authentication.SignInController, while a change to infra.http.controllers.authentication.SignInController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignInController uses a module listed above it, which is the healthy direction.
32→1 infra.http.controllers.authentication.SignUpController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignUpController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.authentication.SignUpController.SignUpController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.authentication.SignUpController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.authentication.SignUpController, while a change to infra.http.controllers.authentication.SignUpController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignUpController uses a module listed above it, which is the healthy direction.
32→2 infra.http.controllers.authentication.SignUpController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignUpController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.authentication.SignUpController.SignUpController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.authentication.SignUpController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.authentication.SignUpController, while a change to infra.http.controllers.authentication.SignUpController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignUpController uses a module listed above it, which is the healthy direction.
32→8 infra.http.controllers.authentication.SignUpController uses application.interfaces.use-cases.authentication.SignInInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignUpController uses a type in application.interfaces.use-cases.authentication.SignInInterface.
- The types involved
src.infra.http.controllers.authentication.SignUpController.SignUpController→src.application.interfaces.use-cases.authentication.SignInInterface.SignInInterface
- Direction
- infra.http.controllers.authentication.SignUpController uses application.interfaces.use-cases.authentication.SignInInterface, so a change to application.interfaces.use-cases.authentication.SignInInterface can break infra.http.controllers.authentication.SignUpController, while a change to infra.http.controllers.authentication.SignUpController can't break application.interfaces.use-cases.authentication.SignInInterface.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignUpController uses a module listed above it, which is the healthy direction.
32→9 infra.http.controllers.authentication.SignUpController uses application.interfaces.use-cases.authentication.SignUpInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignUpController uses a type in application.interfaces.use-cases.authentication.SignUpInterface.
- The types involved
src.infra.http.controllers.authentication.SignUpController.SignUpController→src.application.interfaces.use-cases.authentication.SignUpInterface.SignUpInterface
- Direction
- infra.http.controllers.authentication.SignUpController uses application.interfaces.use-cases.authentication.SignUpInterface, so a change to application.interfaces.use-cases.authentication.SignUpInterface can break infra.http.controllers.authentication.SignUpController, while a change to infra.http.controllers.authentication.SignUpController can't break application.interfaces.use-cases.authentication.SignUpInterface.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignUpController uses a module listed above it, which is the healthy direction.
32→22 infra.http.controllers.authentication.SignUpController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.authentication.SignUpController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.authentication.SignUpController.SignUpController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.authentication.SignUpController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.authentication.SignUpController, while a change to infra.http.controllers.authentication.SignUpController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.authentication.SignUpController uses a module listed above it, which is the healthy direction.
33→1 infra.http.controllers.comments.CreateCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.comments.CreateCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
33→2 infra.http.controllers.comments.CreateCommentController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.comments.CreateCommentController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
33→10 infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.comments.CreateCommentInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in application.interfaces.use-cases.comments.CreateCommentInterface.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.application.interfaces.use-cases.comments.CreateCommentInterface.CreateCommentInterface
- Direction
- infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.comments.CreateCommentInterface, so a change to application.interfaces.use-cases.comments.CreateCommentInterface can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break application.interfaces.use-cases.comments.CreateCommentInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
33→19 infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.posts.GetPostByIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in application.interfaces.use-cases.posts.GetPostByIdInterface.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.application.interfaces.use-cases.posts.GetPostByIdInterface.GetPostByIdInterface
- Direction
- infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.posts.GetPostByIdInterface, so a change to application.interfaces.use-cases.posts.GetPostByIdInterface can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break application.interfaces.use-cases.posts.GetPostByIdInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
33→21 infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.UpdatePostTotalCommentsInterface
- Direction
- infra.http.controllers.comments.CreateCommentController uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface, so a change to application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
33→22 infra.http.controllers.comments.CreateCommentController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.CreateCommentController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.comments.CreateCommentController.CreateCommentController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.comments.CreateCommentController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.comments.CreateCommentController, while a change to infra.http.controllers.comments.CreateCommentController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.comments.CreateCommentController uses a module listed above it, which is the healthy direction.
34→1 infra.http.controllers.comments.DeleteCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.DeleteCommentController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.comments.DeleteCommentController.DeleteCommentController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.comments.DeleteCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.comments.DeleteCommentController, while a change to infra.http.controllers.comments.DeleteCommentController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.comments.DeleteCommentController uses a module listed above it, which is the healthy direction.
34→11 infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.comments.DeleteCommentInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.DeleteCommentController uses a type in application.interfaces.use-cases.comments.DeleteCommentInterface.
- The types involved
src.infra.http.controllers.comments.DeleteCommentController.DeleteCommentController→src.application.interfaces.use-cases.comments.DeleteCommentInterface.DeleteCommentInterface
- Direction
- infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.comments.DeleteCommentInterface, so a change to application.interfaces.use-cases.comments.DeleteCommentInterface can break infra.http.controllers.comments.DeleteCommentController, while a change to infra.http.controllers.comments.DeleteCommentController can't break application.interfaces.use-cases.comments.DeleteCommentInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.DeleteCommentController uses a module listed above it, which is the healthy direction.
34→13 infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.comments.GetCommentByIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.DeleteCommentController uses a type in application.interfaces.use-cases.comments.GetCommentByIdInterface.
- The types involved
src.infra.http.controllers.comments.DeleteCommentController.DeleteCommentController→src.application.interfaces.use-cases.comments.GetCommentByIdInterface.GetCommentByIdInterface
- Direction
- infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.comments.GetCommentByIdInterface, so a change to application.interfaces.use-cases.comments.GetCommentByIdInterface can break infra.http.controllers.comments.DeleteCommentController, while a change to infra.http.controllers.comments.DeleteCommentController can't break application.interfaces.use-cases.comments.GetCommentByIdInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.DeleteCommentController uses a module listed above it, which is the healthy direction.
34→21 infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.DeleteCommentController uses a type in application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- The types involved
src.infra.http.controllers.comments.DeleteCommentController.DeleteCommentController→src.application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.UpdatePostTotalCommentsInterface
- Direction
- infra.http.controllers.comments.DeleteCommentController uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface, so a change to application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface can break infra.http.controllers.comments.DeleteCommentController, while a change to infra.http.controllers.comments.DeleteCommentController can't break application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.DeleteCommentController uses a module listed above it, which is the healthy direction.
34→22 infra.http.controllers.comments.DeleteCommentController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.DeleteCommentController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.comments.DeleteCommentController.DeleteCommentController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.comments.DeleteCommentController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.comments.DeleteCommentController, while a change to infra.http.controllers.comments.DeleteCommentController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.comments.DeleteCommentController uses a module listed above it, which is the healthy direction.
35→1 infra.http.controllers.comments.UpdateCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.UpdateCommentController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.comments.UpdateCommentController.UpdateCommentController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.comments.UpdateCommentController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.comments.UpdateCommentController, while a change to infra.http.controllers.comments.UpdateCommentController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.comments.UpdateCommentController uses a module listed above it, which is the healthy direction.
35→2 infra.http.controllers.comments.UpdateCommentController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.UpdateCommentController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.comments.UpdateCommentController.UpdateCommentController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.comments.UpdateCommentController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.comments.UpdateCommentController, while a change to infra.http.controllers.comments.UpdateCommentController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.comments.UpdateCommentController uses a module listed above it, which is the healthy direction.
35→13 infra.http.controllers.comments.UpdateCommentController uses application.interfaces.use-cases.comments.GetCommentByIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.UpdateCommentController uses a type in application.interfaces.use-cases.comments.GetCommentByIdInterface.
- The types involved
src.infra.http.controllers.comments.UpdateCommentController.UpdateCommentController→src.application.interfaces.use-cases.comments.GetCommentByIdInterface.GetCommentByIdInterface
- Direction
- infra.http.controllers.comments.UpdateCommentController uses application.interfaces.use-cases.comments.GetCommentByIdInterface, so a change to application.interfaces.use-cases.comments.GetCommentByIdInterface can break infra.http.controllers.comments.UpdateCommentController, while a change to infra.http.controllers.comments.UpdateCommentController can't break application.interfaces.use-cases.comments.GetCommentByIdInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.UpdateCommentController uses a module listed above it, which is the healthy direction.
35→15 infra.http.controllers.comments.UpdateCommentController uses application.interfaces.use-cases.comments.UpdateCommentInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.UpdateCommentController uses a type in application.interfaces.use-cases.comments.UpdateCommentInterface.
- The types involved
src.infra.http.controllers.comments.UpdateCommentController.UpdateCommentController→src.application.interfaces.use-cases.comments.UpdateCommentInterface.UpdateCommentInterface
- Direction
- infra.http.controllers.comments.UpdateCommentController uses application.interfaces.use-cases.comments.UpdateCommentInterface, so a change to application.interfaces.use-cases.comments.UpdateCommentInterface can break infra.http.controllers.comments.UpdateCommentController, while a change to infra.http.controllers.comments.UpdateCommentController can't break application.interfaces.use-cases.comments.UpdateCommentInterface.
- Position
- Below the diagonal: infra.http.controllers.comments.UpdateCommentController uses a module listed above it, which is the healthy direction.
35→22 infra.http.controllers.comments.UpdateCommentController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.comments.UpdateCommentController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.comments.UpdateCommentController.UpdateCommentController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.comments.UpdateCommentController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.comments.UpdateCommentController, while a change to infra.http.controllers.comments.UpdateCommentController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.comments.UpdateCommentController uses a module listed above it, which is the healthy direction.
36→1 infra.http.controllers.posts.CreatePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.CreatePostController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.posts.CreatePostController.CreatePostController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.posts.CreatePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.posts.CreatePostController, while a change to infra.http.controllers.posts.CreatePostController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.posts.CreatePostController uses a module listed above it, which is the healthy direction.
36→2 infra.http.controllers.posts.CreatePostController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.CreatePostController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.posts.CreatePostController.CreatePostController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.posts.CreatePostController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.posts.CreatePostController, while a change to infra.http.controllers.posts.CreatePostController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.posts.CreatePostController uses a module listed above it, which is the healthy direction.
36→16 infra.http.controllers.posts.CreatePostController uses application.interfaces.use-cases.posts.CreatePostInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.CreatePostController uses a type in application.interfaces.use-cases.posts.CreatePostInterface.
- The types involved
src.infra.http.controllers.posts.CreatePostController.CreatePostController→src.application.interfaces.use-cases.posts.CreatePostInterface.CreatePostInterface
- Direction
- infra.http.controllers.posts.CreatePostController uses application.interfaces.use-cases.posts.CreatePostInterface, so a change to application.interfaces.use-cases.posts.CreatePostInterface can break infra.http.controllers.posts.CreatePostController, while a change to infra.http.controllers.posts.CreatePostController can't break application.interfaces.use-cases.posts.CreatePostInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.CreatePostController uses a module listed above it, which is the healthy direction.
36→22 infra.http.controllers.posts.CreatePostController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.CreatePostController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.posts.CreatePostController.CreatePostController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.posts.CreatePostController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.posts.CreatePostController, while a change to infra.http.controllers.posts.CreatePostController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.posts.CreatePostController uses a module listed above it, which is the healthy direction.
37→1 infra.http.controllers.posts.DeletePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.DeletePostController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.posts.DeletePostController.DeletePostController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.posts.DeletePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.posts.DeletePostController, while a change to infra.http.controllers.posts.DeletePostController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.posts.DeletePostController uses a module listed above it, which is the healthy direction.
37→12 infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.DeletePostController uses a type in application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.
- The types involved
src.infra.http.controllers.posts.DeletePostController.DeletePostController→src.application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.DeleteCommentsByPostIdInterface
- Direction
- infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface, so a change to application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface can break infra.http.controllers.posts.DeletePostController, while a change to infra.http.controllers.posts.DeletePostController can't break application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.DeletePostController uses a module listed above it, which is the healthy direction.
37→17 infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.posts.DeletePostInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.DeletePostController uses a type in application.interfaces.use-cases.posts.DeletePostInterface.
- The types involved
src.infra.http.controllers.posts.DeletePostController.DeletePostController→src.application.interfaces.use-cases.posts.DeletePostInterface.DeletePostInterface
- Direction
- infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.posts.DeletePostInterface, so a change to application.interfaces.use-cases.posts.DeletePostInterface can break infra.http.controllers.posts.DeletePostController, while a change to infra.http.controllers.posts.DeletePostController can't break application.interfaces.use-cases.posts.DeletePostInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.DeletePostController uses a module listed above it, which is the healthy direction.
37→19 infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.posts.GetPostByIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.DeletePostController uses a type in application.interfaces.use-cases.posts.GetPostByIdInterface.
- The types involved
src.infra.http.controllers.posts.DeletePostController.DeletePostController→src.application.interfaces.use-cases.posts.GetPostByIdInterface.GetPostByIdInterface
- Direction
- infra.http.controllers.posts.DeletePostController uses application.interfaces.use-cases.posts.GetPostByIdInterface, so a change to application.interfaces.use-cases.posts.GetPostByIdInterface can break infra.http.controllers.posts.DeletePostController, while a change to infra.http.controllers.posts.DeletePostController can't break application.interfaces.use-cases.posts.GetPostByIdInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.DeletePostController uses a module listed above it, which is the healthy direction.
37→22 infra.http.controllers.posts.DeletePostController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.DeletePostController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.posts.DeletePostController.DeletePostController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.posts.DeletePostController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.posts.DeletePostController, while a change to infra.http.controllers.posts.DeletePostController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.posts.DeletePostController uses a module listed above it, which is the healthy direction.
38→1 infra.http.controllers.posts.UpdatePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.UpdatePostController uses a type in application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- The types involved
src.infra.http.controllers.posts.UpdatePostController.UpdatePostController→src.application.interfaces.repositories.authentication.LoadUserByEmailRepository.Response
- Direction
- infra.http.controllers.posts.UpdatePostController uses application.interfaces.repositories.authentication.LoadUserByEmailRepository, so a change to application.interfaces.repositories.authentication.LoadUserByEmailRepository can break infra.http.controllers.posts.UpdatePostController, while a change to infra.http.controllers.posts.UpdatePostController can't break application.interfaces.repositories.authentication.LoadUserByEmailRepository.
- Position
- Below the diagonal: infra.http.controllers.posts.UpdatePostController uses a module listed above it, which is the healthy direction.
38→2 infra.http.controllers.posts.UpdatePostController uses infra.http.interfaces.Validation✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.UpdatePostController uses a type in infra.http.interfaces.Validation.
- The types involved
src.infra.http.controllers.posts.UpdatePostController.UpdatePostController→src.infra.http.interfaces.Validation.Validation
- Direction
- infra.http.controllers.posts.UpdatePostController uses infra.http.interfaces.Validation, so a change to infra.http.interfaces.Validation can break infra.http.controllers.posts.UpdatePostController, while a change to infra.http.controllers.posts.UpdatePostController can't break infra.http.interfaces.Validation.
- Position
- Below the diagonal: infra.http.controllers.posts.UpdatePostController uses a module listed above it, which is the healthy direction.
38→19 infra.http.controllers.posts.UpdatePostController uses application.interfaces.use-cases.posts.GetPostByIdInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.UpdatePostController uses a type in application.interfaces.use-cases.posts.GetPostByIdInterface.
- The types involved
src.infra.http.controllers.posts.UpdatePostController.UpdatePostController→src.application.interfaces.use-cases.posts.GetPostByIdInterface.GetPostByIdInterface
- Direction
- infra.http.controllers.posts.UpdatePostController uses application.interfaces.use-cases.posts.GetPostByIdInterface, so a change to application.interfaces.use-cases.posts.GetPostByIdInterface can break infra.http.controllers.posts.UpdatePostController, while a change to infra.http.controllers.posts.UpdatePostController can't break application.interfaces.use-cases.posts.GetPostByIdInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.UpdatePostController uses a module listed above it, which is the healthy direction.
38→20 infra.http.controllers.posts.UpdatePostController uses application.interfaces.use-cases.posts.UpdatePostInterface✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.UpdatePostController uses a type in application.interfaces.use-cases.posts.UpdatePostInterface.
- The types involved
src.infra.http.controllers.posts.UpdatePostController.UpdatePostController→src.application.interfaces.use-cases.posts.UpdatePostInterface.UpdatePostInterface
- Direction
- infra.http.controllers.posts.UpdatePostController uses application.interfaces.use-cases.posts.UpdatePostInterface, so a change to application.interfaces.use-cases.posts.UpdatePostInterface can break infra.http.controllers.posts.UpdatePostController, while a change to infra.http.controllers.posts.UpdatePostController can't break application.interfaces.use-cases.posts.UpdatePostInterface.
- Position
- Below the diagonal: infra.http.controllers.posts.UpdatePostController uses a module listed above it, which is the healthy direction.
38→22 infra.http.controllers.posts.UpdatePostController uses infra.http.controllers.BaseController✕
- Connections
- 1 pair of types, where a type in infra.http.controllers.posts.UpdatePostController uses a type in infra.http.controllers.BaseController.
- The types involved
src.infra.http.controllers.posts.UpdatePostController.UpdatePostController→src.infra.http.controllers.BaseController.BaseController
- Direction
- infra.http.controllers.posts.UpdatePostController uses infra.http.controllers.BaseController, so a change to infra.http.controllers.BaseController can break infra.http.controllers.posts.UpdatePostController, while a change to infra.http.controllers.posts.UpdatePostController can't break infra.http.controllers.BaseController.
- Position
- Below the diagonal: infra.http.controllers.posts.UpdatePostController uses a module listed above it, which is the healthy direction.
39→10 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.CreateCommentInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.CreateCommentInterface.
- The types involved
src.main.factories.use-cases.comments.create-comment-factory→src.application.interfaces.use-cases.comments.CreateCommentInterface.CreateCommentInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.CreateCommentInterface, so a change to application.interfaces.use-cases.comments.CreateCommentInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.CreateCommentInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
39→11 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.DeleteCommentInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.DeleteCommentInterface.
- The types involved
src.main.factories.use-cases.comments.delete-comment-factory→src.application.interfaces.use-cases.comments.DeleteCommentInterface.DeleteCommentInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.DeleteCommentInterface, so a change to application.interfaces.use-cases.comments.DeleteCommentInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.DeleteCommentInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
39→12 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.
- The types involved
src.main.factories.use-cases.comments.delete-comments-by-post-id-factory→src.application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.DeleteCommentsByPostIdInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface, so a change to application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.DeleteCommentsByPostIdInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
39→13 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.GetCommentByIdInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.GetCommentByIdInterface.
- The types involved
src.main.factories.use-cases.comments.get-comment-by-id-factory→src.application.interfaces.use-cases.comments.GetCommentByIdInterface.GetCommentByIdInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.GetCommentByIdInterface, so a change to application.interfaces.use-cases.comments.GetCommentByIdInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.GetCommentByIdInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
39→14 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface.
- The types involved
src.main.factories.use-cases.comments.get-latest-comments-by-post-id-factory→src.application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface.GetLatestCommentsByPostIdInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface, so a change to application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.GetLatestCommentsByPostIdInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
39→15 main.factories.use-cases.comments uses application.interfaces.use-cases.comments.UpdateCommentInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.comments uses a type in application.interfaces.use-cases.comments.UpdateCommentInterface.
- The types involved
src.main.factories.use-cases.comments.update-comment-factory→src.application.interfaces.use-cases.comments.UpdateCommentInterface.UpdateCommentInterface
- Direction
- main.factories.use-cases.comments uses application.interfaces.use-cases.comments.UpdateCommentInterface, so a change to application.interfaces.use-cases.comments.UpdateCommentInterface can break main.factories.use-cases.comments, while a change to main.factories.use-cases.comments can't break application.interfaces.use-cases.comments.UpdateCommentInterface.
- Position
- Below the diagonal: main.factories.use-cases.comments uses a module listed above it, which is the healthy direction.
40→16 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.CreatePostInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.CreatePostInterface.
- The types involved
src.main.factories.use-cases.posts.create-post-factory→src.application.interfaces.use-cases.posts.CreatePostInterface.CreatePostInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.CreatePostInterface, so a change to application.interfaces.use-cases.posts.CreatePostInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.CreatePostInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts uses a module listed above it, which is the healthy direction.
40→17 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.DeletePostInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.DeletePostInterface.
- The types involved
src.main.factories.use-cases.posts.delete-post-factory→src.application.interfaces.use-cases.posts.DeletePostInterface.DeletePostInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.DeletePostInterface, so a change to application.interfaces.use-cases.posts.DeletePostInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.DeletePostInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts uses a module listed above it, which is the healthy direction.
40→18 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.GetLatestPostsInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.GetLatestPostsInterface.
- The types involved
src.main.factories.use-cases.posts.get-latest-posts-factory→src.application.interfaces.use-cases.posts.GetLatestPostsInterface.GetLatestPostsInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.GetLatestPostsInterface, so a change to application.interfaces.use-cases.posts.GetLatestPostsInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.GetLatestPostsInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts uses a module listed above it, which is the healthy direction.
40→19 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.GetPostByIdInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.GetPostByIdInterface.
- The types involved
src.main.factories.use-cases.posts.get-post-by-id-factory→src.application.interfaces.use-cases.posts.GetPostByIdInterface.GetPostByIdInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.GetPostByIdInterface, so a change to application.interfaces.use-cases.posts.GetPostByIdInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.GetPostByIdInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts uses a module listed above it, which is the healthy direction.
40→20 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.UpdatePostInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.UpdatePostInterface.
- The types involved
src.main.factories.use-cases.posts.update-post-factory→src.application.interfaces.use-cases.posts.UpdatePostInterface.UpdatePostInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.UpdatePostInterface, so a change to application.interfaces.use-cases.posts.UpdatePostInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.UpdatePostInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts uses a module listed above it, which is the healthy direction.
40→21 main.factories.use-cases.posts uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface✕
- Connections
- 1 pair of types, where a type in main.factories.use-cases.posts uses a type in application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- The types involved
src.main.factories.use-cases.posts.update-post-total-comments-factory→src.application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.UpdatePostTotalCommentsInterface
- Direction
- main.factories.use-cases.posts uses application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface, so a change to application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface can break main.factories.use-cases.posts, while a change to main.factories.use-cases.posts can't break application.interfaces.use-cases.posts.UpdatePostTotalCommentsInterface.
- Position
- Below the diagonal: main.factories.use-cases.posts 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 | 51 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +3.9 pts | Low | ADR Quality |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +7.3 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +7.3 pts | Medium | Security & performance tooling |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.5 pts | Medium | Architecture documentation |
| 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. | +2.9 pts | Medium | Deployment & Rollback |
| Put every endpoint behind the guard its siblings carry — mount the router after (or with) the authentication middleware, or declare the guard and the rule it needs on the route — so the open surface is only what is public on purpose. | +2.4 pts | Medium | Access Controls |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. | +0.9 pts | Low | Platform End-of-Life |
| Bump outdated dependencies to current versions to limit upgrade debt. | +1.4 pts | Medium | Dependency Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| package.json | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 14 |
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 69 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 69 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, 90 of 112 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
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the jest run in the repository root produced no per-test report (Error: Jest: Got error running globalSetup - node_modules/@shelf/jest-mongodb/setup.js, reason: Status Code is 403 (MongoDB's 404)). This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the jest run in the repository root produced no per-test report (Error: Jest: Got error running globalSetup - node_modules/@shelf/jest-mongodb/setup.js, reason: Status Code is 403 (MongoDB's 404)). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against 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 40 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.
- D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (40 commit(s) sampled).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (src/infra/db/mongodb/repositories/CommentRepository.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (src/infra/db/mongodb/repositories/CommentRepository.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (src/infra/db/mongodb/repositories/CommentRepository.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'mongodb' is imported (src/infra/db/mongodb/repositories/CommentRepository.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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.
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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 3 classes have LCOM4 above 3.
D9 · Test Distribution
69 test methods: 69 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 69 `it`/`test` case(s) across 21 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 69 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 1950 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).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 6 high, 8 medium, 0 low. 4 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `docs/bundle.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 4 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
51 finding(s): 6 critical, 26 high, 12 medium, 7 low.
What to do
- Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26). — One of this dimension's main actionable groups (26 issue-level).
- Resolve the 12 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
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
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 6 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.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
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
C2 · Access Controls
- Access here is not default-deny: this route in router declares no guard, while its 3 sibling routes each declare one and nothing application-wide (an authentication mount or hook, a global guard) covers it. Where the endpoint returns stored data or changes state, D29 reports it as missing authorization. — REDACTED:10
- 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/infra/http/helpers/http.ts:19
What to do
- Put every endpoint behind the guard its siblings carry — mount the router after (or with) the authentication middleware, or declare the guard and the rule it needs on the route — so the open surface is only what is public on purpose.
- 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
- 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
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 144 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 as a CI step. What was searched, so you can tell an absence from a miss: the 910 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `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:30
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — 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.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 5 duplicated blocks under src/application/interfaces/use-cases/ have copies in at least two of the sibling directories authentication, comments, posts — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/application/interfaces/use-cases/authentication/AuthenticateInterface.ts:4
- 5 duplicated blocks under src/infra/http/controllers/ have copies in at least two of the sibling directories authentication, comments, posts — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/infra/http/controllers/comments/UpdateCommentController.ts:11
- src/infra/http/controllers/comments/UpdateCommentController.ts:11 · src/infra/http/controllers/posts/UpdatePostController.ts:11 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/infra/http/controllers/comments/UpdateCommentController.ts:11
- src/infra/db/mongodb/repositories/CommentRepository.ts:65 · src/infra/db/mongodb/repositories/PostRepository.ts:37 — the two spans are one implementation copied and then locally edited — 96 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/infra/db/mongodb/repositories/CommentRepository.ts:65
- src/domain/entities/Comment.ts:18 · src/domain/entities/Post.ts:18 · src/domain/entities/User.ts:18 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/domain/entities/Comment.ts:18
- src/infra/db/mongodb/repositories/CommentRepository.ts:92 · src/infra/db/mongodb/repositories/PostRepository.ts:66 — 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/infra/db/mongodb/repositories/CommentRepository.ts:92
- src/infra/http/controllers/comments/DeleteCommentController.ts:24 · src/infra/http/controllers/comments/UpdateCommentController.ts:25 · src/infra/http/controllers/posts/DeletePostController.ts:22 · src/infra/http/controllers/posts/UpdatePostController.ts:25 — the 4 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/infra/http/controllers/comments/DeleteCommentController.ts:24
- src/application/interfaces/use-cases/authentication/SignUpInterface.ts:5 · src/application/interfaces/use-cases/comments/CreateCommentInterface.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/interfaces/use-cases/authentication/SignUpInterface.ts:5
- src/application/interfaces/use-cases/comments/UpdateCommentInterface.ts:5 · src/application/interfaces/use-cases/posts/UpdatePostInterface.ts:5 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — src/application/interfaces/use-cases/comments/UpdateCommentInterface.ts:5
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
R2 · Cyclomatic Complexity
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. — src/main/server.ts:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. (×6) — src/infra/http/controllers/authentication/SignInController.ts:11, src/infra/http/controllers/authentication/SignUpController.ts:12, src/infra/http/controllers/comments/CreateCommentController.ts:13, …
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
S1 · Web-Security Posture
- `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — src/main/server.ts:9
What to do
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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
- ~8.1 `!` null assertions per 1k TypeScript source lines — 19 assertion(s) across the 2338 source line(s) of the 142 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/infra/http/controllers/comments/UpdateCommentController.ts (3), src/infra/http/controllers/posts/UpdatePostController.ts (3), src/infra/http/controllers/comments/CreateCommentController.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 | 88% | Strong | Solid. |
| Architecture | 83% | Strong | Solid. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 44% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate | Acceptable, with room to improve. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXI1 Runtime container hardening — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'mongodb' (src/infra/db/mongodb/repositories/CommentRepository.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'mongodb' (src/infra/db/mongodb/repositories/CommentRepository.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'mongodb' (src/infra/db/mongodb/repositories/CommentRepository.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- 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 — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'mongodb' (src/infra/db/mongodb/repositories/CommentRepository.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- 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.
- 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"]`.
- D24 Comment Value — Too few judgeable comments (0 of at least 30); comment value is not applicable here.
- 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.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (Error: Jest: Got error running globalSetup - node_modules/@shelf/jest-mongodb/setup.js, reason: Status Code is 403 (MongoDB's 404)), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- 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. 5 claim(s) of kinds M4 does not check were not checked (command argument 5); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/main/config/app.ts:6 (express()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 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 — 38 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
Serious — 51 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Runtime security header not set: content-security-policy
- Runtime security header not set: cross-origin-embedder-policy
- Runtime security header not set: cross-origin-opener-policy
- Runtime security header not set: cross-origin-resource-policy
- Runtime security header not set: permissions-policy
- Runtime security header not set: referrer-policy
- Runtime security header not set: strict-transport-security
- Runtime security header not set: x-content-type-options
- Runtime security header not set: x-dns-prefetch-control
- Runtime security header not set: x-frame-options
- Runtime security header not set: x-permitted-cross-domain-policies
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Container process runs as root: simple-blog-api
- Container process runs as root: simple-blog-mongodb
- REDACTED
- REDACTED
- Duplication concentrated across 3 sibling directories (5 clone groups) src/application/interfaces/use-cases/authentication/AuthenticateInterface.ts:4
- Duplication concentrated across 3 sibling directories (5 clone groups) src/infra/http/controllers/comments/UpdateCommentController.ts:11
- Duplicated block (7 lines × 2 locations) src/application/interfaces/use-cases/authentication/SignUpInterface.ts:5
- Duplicated block (7 lines × 2 locations) src/application/interfaces/use-cases/comments/UpdateCommentInterface.ts:5
- WCAG 2.4.2 reproducibly failed in a rendered surface
- WCAG 3.1.1 reproducibly failed in a rendered surface
- REDACTED
- End-of-life runtime: Node.js 14 package.json:71
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplicated block (36 lines × 2 locations) src/infra/http/controllers/comments/UpdateCommentController.ts:11
- Duplicated block with local edits (18 matched lines × 2 locations) src/infra/db/mongodb/repositories/CommentRepository.ts:65
- Duplicated block (14 lines × 3 locations) src/domain/entities/Comment.ts:18
- Duplicated block (10 lines × 2 locations) src/infra/db/mongodb/repositories/CommentRepository.ts:92
- Duplicated block (8 lines × 4 locations) src/infra/http/controllers/comments/DeleteCommentController.ts:24
- No test reaches this file src/main/server.ts:1
Minor — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Endpoints outside the guard REDACTED:10
- No named authorization policies src/infra/http/helpers/http.ts:19
- No ADRs found
- REDACTED
- No ADRs
- No SAST REDACTED:6
- No dependency-update automation package.json:30
- No rollback/health safety
- Unused private field 'signInValidation' src/infra/http/controllers/authentication/SignInController.ts:11
- Unused private field 'signUpValidation' src/infra/http/controllers/authentication/SignUpController.ts:12
- Unused private field 'createCommentValidation' src/infra/http/controllers/comments/CreateCommentController.ts:13
- Unused private field 'updateCommentValidation' src/infra/http/controllers/comments/UpdateCommentController.ts:13
- Unused private field 'createPostValidation' src/infra/http/controllers/posts/CreatePostController.ts:10
- Unused private field 'updatePostValidation' src/infra/http/controllers/posts/UpdatePostController.ts:13
- No app-layer HTTPS enforcement detected src/main/server.ts:9
- 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-2e145c5bc83d4bb7b6cf0d2d5baa5ddb/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2e145c5bc83d4bb7b6cf0d2d5baa5ddb/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 14 | 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 | 51 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | 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 |