Executive summary
erweixin/Go-GenAI-Stack is rated At risk because critical security findings are open. Its score is held back in part because it has labels or groups of fields with no name. It scores 44 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 36, is the weakest lens and counts most in the score. The best first steps are fixing focus, motion and contrast and labelling the form fields and buttons, each worth about 5 points. Raising Accessibility to 70 would lift the score to about 50.
Sixty-two known security holes in the packages the code depends on can be used by attackers. Thirty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and fifteen passwords or keys in the code's history and 11 in the code are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Passing outside input through environment variables would fix the three pipeline steps that put outside input straight into a shell command, and the four unsafe settings in infrastructure or container files need changing to safe values. The 16 pieces of business logic tied to the database or web code need separating from the database and web code.
The product code is 20,576 lines, about €35,000 to rebuild.
If Accessibility rose from 36 to 70, the lowest score rated Strong, the score would rise from 44 to about 50.
New since the last survey: 38 findings
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Test isolation · Production project references a test package: go-genai-stack-backend-nodejs → @vitest/ui backend-nodejs/package.json
- Test isolation · Production project references a test package: go-genai-stack-backend-nodejs → supertest backend-nodejs/package.json
Fixed since the last survey: 56 findings
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: 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
- Supply-chain Provenance & Signing · Unpinned build actions
- Import Boundaries · Boundary violation [fsd:cross-slice] frontend/web/src/features/user/__tests__/hooks/useUserProfile.test.ts
- Import Boundaries · Boundary violation [fsd:cross-slice] frontend/web/src/features/user/hooks/useUserProfile.ts
- Test Coverage · No test reaches this file frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/dropdown-menu.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ErrorBoundary.tsx
- Test Coverage · No test reaches this file frontend/web/src/pages/RegisterPage/RegisterPage.tsx
- Test Coverage · No test reaches this file frontend/web/src/pages/TasksPage/TasksPage.tsx
- Test Coverage · No test reaches this file frontend/web/src/pages/HomePage/HomePage.tsx
- Test Coverage · No test reaches this file frontend/web/src/features/task/components/TaskItem.tsx
- Test Coverage · No test reaches this file frontend/web/src/pages/LoginPage/LoginPage.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/breadcrumb.tsx
- Test Coverage · No test reaches this file frontend/web/src/router/index.tsx
- Test Coverage · No test reaches this file frontend/web/src/features/task/components/TaskFilters.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/table.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ErrorPage.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/typography.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/card.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/theme-provider.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/accordion.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/alert.tsx
- Test Coverage · No test reaches this file frontend/web/src/lib/query-client.ts
- Test Coverage · No test reaches this file frontend/web/src/components/ui/slider.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/tooltip.tsx
- Test Coverage · No test reaches this file frontend/web/src/features/task/components/TaskList.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/tabs.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/radio-group.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/theme-toggle.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/popover.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/sonner.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/avatar.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/badge.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/spinner.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/checkbox.tsx
- Test Coverage · No test reaches this file frontend/web/src/main.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/separator.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/switch.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/progress.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/empty.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ProtectedRoute.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/PageLoader.tsx
- Test Coverage · No test reaches this file frontend/web/src/App.tsx
- Test Coverage · No test reaches this file frontend/web/src/components/ui/skeleton.tsx
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €58,000, for 192 to 608 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 44. 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 | Medium: 20,576 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 backend-nodejs.domains.auth.service.jwt_service | 2 backend-nodejs.domains.task.http.dto.task | 3 backend-nodejs.domains.task.model.task | 4 backend-nodejs.domains.user.model.user | 5 backend-nodejs.infrastructure.middleware.tracing | 6 backend-nodejs.infrastructure.persistence.postgres.database | 7 backend-nodejs.shared.types.context | 8 frontend.shared.types.domains.auth | 9 frontend.web.src.components | 10 frontend.web.src.components.ui | 11 github.com/erweixin/go-genai-stack/backend/domains/task/model | 12 github.com/erweixin/go-genai-stack/backend/domains/user/repository | 13 github.com/erweixin/go-genai-stack/backend/infrastructure/config | 14 github.com/erweixin/go-genai-stack/backend/infrastructure/persistence | 15 backend-nodejs.domains.task.repository.interface | 16 backend-nodejs.domains.user.repository.interface | 17 backend-nodejs.infrastructure.bootstrap | 18 backend-nodejs.infrastructure.middleware | 19 backend-nodejs.infrastructure.monitoring.health | 20 frontend.shared.types.domains.task | 21 frontend.shared.types.domains.user | 22 frontend.web.src.features.task.components.TaskItem | 23 github.com/erweixin/go-genai-stack/backend/domains/auth/service | 24 github.com/erweixin/go-genai-stack/backend/domains/task/service | 25 github.com/erweixin/go-genai-stack/backend/domains/user/service | 26 backend-nodejs.domains.auth.service.auth_service | 27 backend-nodejs.domains.task.repository.task_repo | 28 backend-nodejs.domains.task.service.task_service | 29 backend-nodejs.domains.user.repository.user_repo | 30 backend-nodejs.domains.user.service.user_service | 31 frontend.web.src.features.task.components | 32 github.com/erweixin/go-genai-stack/backend/domains/auth/handlers | 33 github.com/erweixin/go-genai-stack/backend/domains/task/handlers | 34 github.com/erweixin/go-genai-stack/backend/domains/user/handlers | 35 github.com/erweixin/go-genai-stack/backend/infrastructure/middleware | 36 backend-nodejs.domains.task.handlers.dependencies | 37 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap | 38 backend-nodejs.domains.auth.handlers | 39 backend-nodejs.domains.task.handlers | 40 backend-nodejs.domains.user.handlers |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 backend-nodejs.domains.auth.service.jwt_service | ||||||||||||||||||||||||||||||||||||||||
| 2 backend-nodejs.domains.task.http.dto.task | ||||||||||||||||||||||||||||||||||||||||
| 3 backend-nodejs.domains.task.model.task | ||||||||||||||||||||||||||||||||||||||||
| 4 backend-nodejs.domains.user.model.user | ||||||||||||||||||||||||||||||||||||||||
| 5 backend-nodejs.infrastructure.middleware.tracing | ||||||||||||||||||||||||||||||||||||||||
| 6 backend-nodejs.infrastructure.persistence.postgres.database | ||||||||||||||||||||||||||||||||||||||||
| 7 backend-nodejs.shared.types.context | ||||||||||||||||||||||||||||||||||||||||
| 8 frontend.shared.types.domains.auth | ||||||||||||||||||||||||||||||||||||||||
| 9 frontend.web.src.components | ||||||||||||||||||||||||||||||||||||||||
| 10 frontend.web.src.components.ui | ||||||||||||||||||||||||||||||||||||||||
| 11 github.com/erweixin/go-genai-stack/backend/domains/task/model | ||||||||||||||||||||||||||||||||||||||||
| 12 github.com/erweixin/go-genai-stack/backend/domains/user/repository | ||||||||||||||||||||||||||||||||||||||||
| 13 github.com/erweixin/go-genai-stack/backend/infrastructure/config | ||||||||||||||||||||||||||||||||||||||||
| 14 github.com/erweixin/go-genai-stack/backend/infrastructure/persistence | ||||||||||||||||||||||||||||||||||||||||
| 15 backend-nodejs.domains.task.repository.interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 backend-nodejs.domains.user.repository.interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 backend-nodejs.infrastructure.bootstrap | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 backend-nodejs.infrastructure.middleware | 1 | 4 | ||||||||||||||||||||||||||||||||||||||
| 19 backend-nodejs.infrastructure.monitoring.health | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 frontend.shared.types.domains.task | 6 | |||||||||||||||||||||||||||||||||||||||
| 21 frontend.shared.types.domains.user | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 frontend.web.src.features.task.components.TaskItem | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 github.com/erweixin/go-genai-stack/backend/domains/auth/service | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 github.com/erweixin/go-genai-stack/backend/domains/task/service | 8 | |||||||||||||||||||||||||||||||||||||||
| 25 github.com/erweixin/go-genai-stack/backend/domains/user/service | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 backend-nodejs.domains.auth.service.auth_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 backend-nodejs.domains.task.repository.task_repo | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 28 backend-nodejs.domains.task.service.task_service | 4 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 29 backend-nodejs.domains.user.repository.user_repo | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 backend-nodejs.domains.user.service.user_service | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 frontend.web.src.features.task.components | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 github.com/erweixin/go-genai-stack/backend/domains/auth/handlers | 8 | |||||||||||||||||||||||||||||||||||||||
| 33 github.com/erweixin/go-genai-stack/backend/domains/task/handlers | 14 | |||||||||||||||||||||||||||||||||||||||
| 34 github.com/erweixin/go-genai-stack/backend/domains/user/handlers | 8 | |||||||||||||||||||||||||||||||||||||||
| 35 github.com/erweixin/go-genai-stack/backend/infrastructure/middleware | 2 | |||||||||||||||||||||||||||||||||||||||
| 36 backend-nodejs.domains.task.handlers.dependencies | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 backend-nodejs.domains.auth.handlers | 3 | 3 | 6 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 backend-nodejs.domains.task.handlers | 6 | 1 | 6 | 2 | 6 | 6 | ||||||||||||||||||||||||||||||||||
| 40 backend-nodejs.domains.user.handlers | 1 | 3 | 2 | 3 | 3 |
15→3 backend-nodejs.domains.task.repository.interface uses backend-nodejs.domains.task.model.task✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.repository.interface uses a type in backend-nodejs.domains.task.model.task.
- The types involved
backend-nodejs.domains.task.repository.interface.TaskRepository→backend-nodejs.domains.task.model.task.Task
- Direction
- backend-nodejs.domains.task.repository.interface uses backend-nodejs.domains.task.model.task, so a change to backend-nodejs.domains.task.model.task can break backend-nodejs.domains.task.repository.interface, while a change to backend-nodejs.domains.task.repository.interface can't break backend-nodejs.domains.task.model.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.interface uses a module listed above it, which is the healthy direction.
15→7 backend-nodejs.domains.task.repository.interface uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.repository.interface uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.task.repository.interface.TaskRepository→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.task.repository.interface uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.task.repository.interface, while a change to backend-nodejs.domains.task.repository.interface can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.interface uses a module listed above it, which is the healthy direction.
16→4 backend-nodejs.domains.user.repository.interface uses backend-nodejs.domains.user.model.user✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.interface uses a type in backend-nodejs.domains.user.model.user.
- The types involved
backend-nodejs.domains.user.repository.interface.UserRepository→backend-nodejs.domains.user.model.user.User
- Direction
- backend-nodejs.domains.user.repository.interface uses backend-nodejs.domains.user.model.user, so a change to backend-nodejs.domains.user.model.user can break backend-nodejs.domains.user.repository.interface, while a change to backend-nodejs.domains.user.repository.interface can't break backend-nodejs.domains.user.model.user.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.interface uses a module listed above it, which is the healthy direction.
16→7 backend-nodejs.domains.user.repository.interface uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.interface uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.user.repository.interface.UserRepository→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.user.repository.interface uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.user.repository.interface, while a change to backend-nodejs.domains.user.repository.interface can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.interface uses a module listed above it, which is the healthy direction.
17→6 backend-nodejs.infrastructure.bootstrap uses backend-nodejs.infrastructure.persistence.postgres.database✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.infrastructure.bootstrap uses a type in backend-nodejs.infrastructure.persistence.postgres.database.
- The types involved
backend-nodejs.infrastructure.bootstrap.dependencies→backend-nodejs.infrastructure.persistence.postgres.database.Databasebackend-nodejs.infrastructure.bootstrap.server→backend-nodejs.infrastructure.persistence.postgres.database.Database
- Direction
- backend-nodejs.infrastructure.bootstrap uses backend-nodejs.infrastructure.persistence.postgres.database, so a change to backend-nodejs.infrastructure.persistence.postgres.database can break backend-nodejs.infrastructure.bootstrap, while a change to backend-nodejs.infrastructure.bootstrap can't break backend-nodejs.infrastructure.persistence.postgres.database.
- Position
- Below the diagonal: backend-nodejs.infrastructure.bootstrap uses a module listed above it, which is the healthy direction.
18→1 backend-nodejs.infrastructure.middleware uses backend-nodejs.domains.auth.service.jwt_service✕
- Connections
- 1 pair of types, where a type in backend-nodejs.infrastructure.middleware uses a type in backend-nodejs.domains.auth.service.jwt_service.
- The types involved
backend-nodejs.infrastructure.middleware.auth→backend-nodejs.domains.auth.service.jwt_service.JWTService
- Direction
- backend-nodejs.infrastructure.middleware uses backend-nodejs.domains.auth.service.jwt_service, so a change to backend-nodejs.domains.auth.service.jwt_service can break backend-nodejs.infrastructure.middleware, while a change to backend-nodejs.infrastructure.middleware can't break backend-nodejs.domains.auth.service.jwt_service.
- Position
- Below the diagonal: backend-nodejs.infrastructure.middleware uses a module listed above it, which is the healthy direction.
18→5 backend-nodejs.infrastructure.middleware uses backend-nodejs.infrastructure.middleware.tracing✕
- Connections
- 4 pairs of types, where a type in backend-nodejs.infrastructure.middleware uses a type in backend-nodejs.infrastructure.middleware.tracing.
- The types involved
backend-nodejs.infrastructure.middleware.auth→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.infrastructure.middleware.metrics→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.infrastructure.middleware.ratelimit→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.infrastructure.middleware.tracing→backend-nodejs.infrastructure.middleware.tracing.FastifyRequest
- Direction
- backend-nodejs.infrastructure.middleware uses backend-nodejs.infrastructure.middleware.tracing, so a change to backend-nodejs.infrastructure.middleware.tracing can break backend-nodejs.infrastructure.middleware, while a change to backend-nodejs.infrastructure.middleware can't break backend-nodejs.infrastructure.middleware.tracing.
- Position
- Below the diagonal: backend-nodejs.infrastructure.middleware uses a module listed above it, which is the healthy direction.
19→6 backend-nodejs.infrastructure.monitoring.health uses backend-nodejs.infrastructure.persistence.postgres.database✕
- Connections
- 1 pair of types, where a type in backend-nodejs.infrastructure.monitoring.health uses a type in backend-nodejs.infrastructure.persistence.postgres.database.
- The types involved
backend-nodejs.infrastructure.monitoring.health.health→backend-nodejs.infrastructure.persistence.postgres.database.Database
- Direction
- backend-nodejs.infrastructure.monitoring.health uses backend-nodejs.infrastructure.persistence.postgres.database, so a change to backend-nodejs.infrastructure.persistence.postgres.database can break backend-nodejs.infrastructure.monitoring.health, while a change to backend-nodejs.infrastructure.monitoring.health can't break backend-nodejs.infrastructure.persistence.postgres.database.
- Position
- Below the diagonal: backend-nodejs.infrastructure.monitoring.health uses a module listed above it, which is the healthy direction.
20→3 frontend.shared.types.domains.task uses backend-nodejs.domains.task.model.task✕
- Connections
- 6 pairs of types, where a type in frontend.shared.types.domains.task uses a type in backend-nodejs.domains.task.model.task.
- The types involved
frontend.shared.types.domains.task.CompleteTaskResponse→backend-nodejs.domains.task.model.task.TaskStatusfrontend.shared.types.domains.task.CreateTaskResponse→backend-nodejs.domains.task.model.task.TaskStatusfrontend.shared.types.domains.task.GetTaskResponse→backend-nodejs.domains.task.model.task.TaskStatusfrontend.shared.types.domains.task.ListTasksRequest→backend-nodejs.domains.task.model.task.TaskStatusfrontend.shared.types.domains.task.TaskItem→backend-nodejs.domains.task.model.task.TaskStatusfrontend.shared.types.domains.task.UpdateTaskResponse→backend-nodejs.domains.task.model.task.TaskStatus
- Direction
- frontend.shared.types.domains.task uses backend-nodejs.domains.task.model.task, so a change to backend-nodejs.domains.task.model.task can break frontend.shared.types.domains.task, while a change to frontend.shared.types.domains.task can't break backend-nodejs.domains.task.model.task.
- Position
- Below the diagonal: frontend.shared.types.domains.task uses a module listed above it, which is the healthy direction.
21→4 frontend.shared.types.domains.user uses backend-nodejs.domains.user.model.user✕
- Connections
- 1 pair of types, where a type in frontend.shared.types.domains.user uses a type in backend-nodejs.domains.user.model.user.
- The types involved
frontend.shared.types.domains.user.GetUserProfileResponse→backend-nodejs.domains.user.model.user.UserStatus
- Direction
- frontend.shared.types.domains.user uses backend-nodejs.domains.user.model.user, so a change to backend-nodejs.domains.user.model.user can break frontend.shared.types.domains.user, while a change to frontend.shared.types.domains.user can't break backend-nodejs.domains.user.model.user.
- Position
- Below the diagonal: frontend.shared.types.domains.user uses a module listed above it, which is the healthy direction.
22→2 frontend.web.src.features.task.components.TaskItem uses backend-nodejs.domains.task.http.dto.task✕
- Connections
- 1 pair of types, where a type in frontend.web.src.features.task.components.TaskItem uses a type in backend-nodejs.domains.task.http.dto.task.
- The types involved
frontend.web.src.features.task.components.TaskItem.TaskItemProps→backend-nodejs.domains.task.http.dto.task.TaskItem
- Direction
- frontend.web.src.features.task.components.TaskItem uses backend-nodejs.domains.task.http.dto.task, so a change to backend-nodejs.domains.task.http.dto.task can break frontend.web.src.features.task.components.TaskItem, while a change to frontend.web.src.features.task.components.TaskItem can't break backend-nodejs.domains.task.http.dto.task.
- Position
- Below the diagonal: frontend.web.src.features.task.components.TaskItem uses a module listed above it, which is the healthy direction.
23→12 github.com/erweixin/go-genai-stack/backend/domains/auth/service uses github.com/erweixin/go-genai-stack/backend/domains/user/repository✕
- Connections
- 2 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/auth/service uses a type in github.com/erweixin/go-genai-stack/backend/domains/user/repository.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/auth/service.AuthService→github.com/erweixin/go-genai-stack/backend/domains/user/repository.UserRepositorygithub.com/erweixin/go-genai-stack/backend/domains/auth/service.service→github.com/erweixin/go-genai-stack/backend/domains/user/repository.UserRepository
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/auth/service uses github.com/erweixin/go-genai-stack/backend/domains/user/repository, so a change to github.com/erweixin/go-genai-stack/backend/domains/user/repository can break github.com/erweixin/go-genai-stack/backend/domains/auth/service, while a change to github.com/erweixin/go-genai-stack/backend/domains/auth/service can't break github.com/erweixin/go-genai-stack/backend/domains/user/repository.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/auth/service uses a module listed above it, which is the healthy direction.
24→11 github.com/erweixin/go-genai-stack/backend/domains/task/service uses github.com/erweixin/go-genai-stack/backend/domains/task/model✕
- Connections
- 8 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/task/service uses a type in github.com/erweixin/go-genai-stack/backend/domains/task/model.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/task/service.CompleteTaskOutput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Taskgithub.com/erweixin/go-genai-stack/backend/domains/task/service.CreateTaskInput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Prioritygithub.com/erweixin/go-genai-stack/backend/domains/task/service.CreateTaskOutput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Taskgithub.com/erweixin/go-genai-stack/backend/domains/task/service.GetTaskOutput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Taskgithub.com/erweixin/go-genai-stack/backend/domains/task/service.ListTasksOutput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Taskgithub.com/erweixin/go-genai-stack/backend/domains/task/service.UpdateTaskInput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Prioritygithub.com/erweixin/go-genai-stack/backend/domains/task/service.UpdateTaskOutput→github.com/erweixin/go-genai-stack/backend/domains/task/model.Taskgithub.com/erweixin/go-genai-stack/backend/domains/task/service.service→github.com/erweixin/go-genai-stack/backend/domains/task/model.Priority
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/task/service uses github.com/erweixin/go-genai-stack/backend/domains/task/model, so a change to github.com/erweixin/go-genai-stack/backend/domains/task/model can break github.com/erweixin/go-genai-stack/backend/domains/task/service, while a change to github.com/erweixin/go-genai-stack/backend/domains/task/service can't break github.com/erweixin/go-genai-stack/backend/domains/task/model.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/task/service uses a module listed above it, which is the healthy direction.
25→12 github.com/erweixin/go-genai-stack/backend/domains/user/service uses github.com/erweixin/go-genai-stack/backend/domains/user/repository✕
- Connections
- 2 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/user/service uses a type in github.com/erweixin/go-genai-stack/backend/domains/user/repository.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/user/service.UserService→github.com/erweixin/go-genai-stack/backend/domains/user/repository.UserRepositorygithub.com/erweixin/go-genai-stack/backend/domains/user/service.service→github.com/erweixin/go-genai-stack/backend/domains/user/repository.UserRepository
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/user/service uses github.com/erweixin/go-genai-stack/backend/domains/user/repository, so a change to github.com/erweixin/go-genai-stack/backend/domains/user/repository can break github.com/erweixin/go-genai-stack/backend/domains/user/service, while a change to github.com/erweixin/go-genai-stack/backend/domains/user/service can't break github.com/erweixin/go-genai-stack/backend/domains/user/repository.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/user/service uses a module listed above it, which is the healthy direction.
26→1 backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.domains.auth.service.jwt_service✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.auth.service.auth_service uses a type in backend-nodejs.domains.auth.service.jwt_service.
- The types involved
backend-nodejs.domains.auth.service.auth_service.AuthService→backend-nodejs.domains.auth.service.jwt_service.JWTService
- Direction
- backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.domains.auth.service.jwt_service, so a change to backend-nodejs.domains.auth.service.jwt_service can break backend-nodejs.domains.auth.service.auth_service, while a change to backend-nodejs.domains.auth.service.auth_service can't break backend-nodejs.domains.auth.service.jwt_service.
- Position
- Below the diagonal: backend-nodejs.domains.auth.service.auth_service uses a module listed above it, which is the healthy direction.
26→7 backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.auth.service.auth_service uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.auth.service.auth_service.AuthService→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.auth.service.auth_service, while a change to backend-nodejs.domains.auth.service.auth_service can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.auth.service.auth_service uses a module listed above it, which is the healthy direction.
26→16 backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.domains.user.repository.interface✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.auth.service.auth_service uses a type in backend-nodejs.domains.user.repository.interface.
- The types involved
backend-nodejs.domains.auth.service.auth_service.AuthService→backend-nodejs.domains.user.repository.interface.UserRepository
- Direction
- backend-nodejs.domains.auth.service.auth_service uses backend-nodejs.domains.user.repository.interface, so a change to backend-nodejs.domains.user.repository.interface can break backend-nodejs.domains.auth.service.auth_service, while a change to backend-nodejs.domains.auth.service.auth_service can't break backend-nodejs.domains.user.repository.interface.
- Position
- Below the diagonal: backend-nodejs.domains.auth.service.auth_service uses a module listed above it, which is the healthy direction.
27→3 backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.domains.task.model.task✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.repository.task_repo uses a type in backend-nodejs.domains.task.model.task.
- The types involved
backend-nodejs.domains.task.repository.task_repo.TaskRepositoryImpl→backend-nodejs.domains.task.model.task.Task
- Direction
- backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.domains.task.model.task, so a change to backend-nodejs.domains.task.model.task can break backend-nodejs.domains.task.repository.task_repo, while a change to backend-nodejs.domains.task.repository.task_repo can't break backend-nodejs.domains.task.model.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.task_repo uses a module listed above it, which is the healthy direction.
27→6 backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.infrastructure.persistence.postgres.database✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.repository.task_repo uses a type in backend-nodejs.infrastructure.persistence.postgres.database.
- The types involved
backend-nodejs.domains.task.repository.task_repo.TaskRepositoryImpl→backend-nodejs.infrastructure.persistence.postgres.database.Database
- Direction
- backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.infrastructure.persistence.postgres.database, so a change to backend-nodejs.infrastructure.persistence.postgres.database can break backend-nodejs.domains.task.repository.task_repo, while a change to backend-nodejs.domains.task.repository.task_repo can't break backend-nodejs.infrastructure.persistence.postgres.database.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.task_repo uses a module listed above it, which is the healthy direction.
27→7 backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.repository.task_repo uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.task.repository.task_repo.TaskRepositoryImpl→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.task.repository.task_repo, while a change to backend-nodejs.domains.task.repository.task_repo can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.task_repo uses a module listed above it, which is the healthy direction.
27→15 backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.domains.task.repository.interface✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.domains.task.repository.task_repo uses a type in backend-nodejs.domains.task.repository.interface.
- The types involved
backend-nodejs.domains.task.repository.task_repo.TaskRepositoryImpl→backend-nodejs.domains.task.repository.interface.TaskFilterbackend-nodejs.domains.task.repository.task_repo.TaskRepositoryImpl→backend-nodejs.domains.task.repository.interface.TaskRepository
- Direction
- backend-nodejs.domains.task.repository.task_repo uses backend-nodejs.domains.task.repository.interface, so a change to backend-nodejs.domains.task.repository.interface can break backend-nodejs.domains.task.repository.task_repo, while a change to backend-nodejs.domains.task.repository.task_repo can't break backend-nodejs.domains.task.repository.interface.
- Position
- Below the diagonal: backend-nodejs.domains.task.repository.task_repo uses a module listed above it, which is the healthy direction.
28→3 backend-nodejs.domains.task.service.task_service uses backend-nodejs.domains.task.model.task✕
- Connections
- 4 pairs of types, where a type in backend-nodejs.domains.task.service.task_service uses a type in backend-nodejs.domains.task.model.task.
- The types involved
backend-nodejs.domains.task.service.task_service.CompleteTaskOutput→backend-nodejs.domains.task.model.task.Taskbackend-nodejs.domains.task.service.task_service.CreateTaskOutput→backend-nodejs.domains.task.model.task.Taskbackend-nodejs.domains.task.service.task_service.GetTaskOutput→backend-nodejs.domains.task.model.task.Taskbackend-nodejs.domains.task.service.task_service.UpdateTaskOutput→backend-nodejs.domains.task.model.task.Task
- Direction
- backend-nodejs.domains.task.service.task_service uses backend-nodejs.domains.task.model.task, so a change to backend-nodejs.domains.task.model.task can break backend-nodejs.domains.task.service.task_service, while a change to backend-nodejs.domains.task.service.task_service can't break backend-nodejs.domains.task.model.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.service.task_service uses a module listed above it, which is the healthy direction.
28→7 backend-nodejs.domains.task.service.task_service uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.service.task_service uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.task.service.task_service.TaskService→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.task.service.task_service uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.task.service.task_service, while a change to backend-nodejs.domains.task.service.task_service can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.task.service.task_service uses a module listed above it, which is the healthy direction.
28→15 backend-nodejs.domains.task.service.task_service uses backend-nodejs.domains.task.repository.interface✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.domains.task.service.task_service uses a type in backend-nodejs.domains.task.repository.interface.
- The types involved
backend-nodejs.domains.task.service.task_service.ListTasksInput→backend-nodejs.domains.task.repository.interface.TaskFilterbackend-nodejs.domains.task.service.task_service.TaskService→backend-nodejs.domains.task.repository.interface.TaskRepository
- Direction
- backend-nodejs.domains.task.service.task_service uses backend-nodejs.domains.task.repository.interface, so a change to backend-nodejs.domains.task.repository.interface can break backend-nodejs.domains.task.service.task_service, while a change to backend-nodejs.domains.task.service.task_service can't break backend-nodejs.domains.task.repository.interface.
- Position
- Below the diagonal: backend-nodejs.domains.task.service.task_service uses a module listed above it, which is the healthy direction.
29→4 backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.domains.user.model.user✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.user_repo uses a type in backend-nodejs.domains.user.model.user.
- The types involved
backend-nodejs.domains.user.repository.user_repo.UserRepositoryImpl→backend-nodejs.domains.user.model.user.User
- Direction
- backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.domains.user.model.user, so a change to backend-nodejs.domains.user.model.user can break backend-nodejs.domains.user.repository.user_repo, while a change to backend-nodejs.domains.user.repository.user_repo can't break backend-nodejs.domains.user.model.user.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.user_repo uses a module listed above it, which is the healthy direction.
29→6 backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.infrastructure.persistence.postgres.database✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.user_repo uses a type in backend-nodejs.infrastructure.persistence.postgres.database.
- The types involved
backend-nodejs.domains.user.repository.user_repo.UserRepositoryImpl→backend-nodejs.infrastructure.persistence.postgres.database.Database
- Direction
- backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.infrastructure.persistence.postgres.database, so a change to backend-nodejs.infrastructure.persistence.postgres.database can break backend-nodejs.domains.user.repository.user_repo, while a change to backend-nodejs.domains.user.repository.user_repo can't break backend-nodejs.infrastructure.persistence.postgres.database.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.user_repo uses a module listed above it, which is the healthy direction.
29→7 backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.user_repo uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.user.repository.user_repo.UserRepositoryImpl→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.user.repository.user_repo, while a change to backend-nodejs.domains.user.repository.user_repo can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.user_repo uses a module listed above it, which is the healthy direction.
29→16 backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.domains.user.repository.interface✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.repository.user_repo uses a type in backend-nodejs.domains.user.repository.interface.
- The types involved
backend-nodejs.domains.user.repository.user_repo.UserRepositoryImpl→backend-nodejs.domains.user.repository.interface.UserRepository
- Direction
- backend-nodejs.domains.user.repository.user_repo uses backend-nodejs.domains.user.repository.interface, so a change to backend-nodejs.domains.user.repository.interface can break backend-nodejs.domains.user.repository.user_repo, while a change to backend-nodejs.domains.user.repository.user_repo can't break backend-nodejs.domains.user.repository.interface.
- Position
- Below the diagonal: backend-nodejs.domains.user.repository.user_repo uses a module listed above it, which is the healthy direction.
30→4 backend-nodejs.domains.user.service.user_service uses backend-nodejs.domains.user.model.user✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.domains.user.service.user_service uses a type in backend-nodejs.domains.user.model.user.
- The types involved
backend-nodejs.domains.user.service.user_service.GetUserProfileOutput→backend-nodejs.domains.user.model.user.Userbackend-nodejs.domains.user.service.user_service.UpdateUserProfileOutput→backend-nodejs.domains.user.model.user.User
- Direction
- backend-nodejs.domains.user.service.user_service uses backend-nodejs.domains.user.model.user, so a change to backend-nodejs.domains.user.model.user can break backend-nodejs.domains.user.service.user_service, while a change to backend-nodejs.domains.user.service.user_service can't break backend-nodejs.domains.user.model.user.
- Position
- Below the diagonal: backend-nodejs.domains.user.service.user_service uses a module listed above it, which is the healthy direction.
30→7 backend-nodejs.domains.user.service.user_service uses backend-nodejs.shared.types.context✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.service.user_service uses a type in backend-nodejs.shared.types.context.
- The types involved
backend-nodejs.domains.user.service.user_service.UserService→backend-nodejs.shared.types.context.RequestContext
- Direction
- backend-nodejs.domains.user.service.user_service uses backend-nodejs.shared.types.context, so a change to backend-nodejs.shared.types.context can break backend-nodejs.domains.user.service.user_service, while a change to backend-nodejs.domains.user.service.user_service can't break backend-nodejs.shared.types.context.
- Position
- Below the diagonal: backend-nodejs.domains.user.service.user_service uses a module listed above it, which is the healthy direction.
30→16 backend-nodejs.domains.user.service.user_service uses backend-nodejs.domains.user.repository.interface✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.service.user_service uses a type in backend-nodejs.domains.user.repository.interface.
- The types involved
backend-nodejs.domains.user.service.user_service.UserService→backend-nodejs.domains.user.repository.interface.UserRepository
- Direction
- backend-nodejs.domains.user.service.user_service uses backend-nodejs.domains.user.repository.interface, so a change to backend-nodejs.domains.user.repository.interface can break backend-nodejs.domains.user.service.user_service, while a change to backend-nodejs.domains.user.service.user_service can't break backend-nodejs.domains.user.repository.interface.
- Position
- Below the diagonal: backend-nodejs.domains.user.service.user_service uses a module listed above it, which is the healthy direction.
31→22 frontend.web.src.features.task.components uses frontend.web.src.features.task.components.TaskItem✕
- Connections
- 1 pair of types, where a type in frontend.web.src.features.task.components uses a type in frontend.web.src.features.task.components.TaskItem.
- The types involved
frontend.web.src.features.task.components.TaskItem→frontend.web.src.features.task.components.TaskItem.TaskItemProps
- Direction
- frontend.web.src.features.task.components uses frontend.web.src.features.task.components.TaskItem, so a change to frontend.web.src.features.task.components.TaskItem can break frontend.web.src.features.task.components, while a change to frontend.web.src.features.task.components can't break frontend.web.src.features.task.components.TaskItem.
- Position
- Below the diagonal: frontend.web.src.features.task.components uses a module listed above it, which is the healthy direction.
32→23 github.com/erweixin/go-genai-stack/backend/domains/auth/handlers uses github.com/erweixin/go-genai-stack/backend/domains/auth/service✕
- Connections
- 8 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/auth/handlers uses a type in github.com/erweixin/go-genai-stack/backend/domains/auth/service.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/auth/handlers.HandlerDependencies→github.com/erweixin/go-genai-stack/backend/domains/auth/service.AuthServicegithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.AuthServicegithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.LoginInputgithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.LoginOutputgithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.RefreshTokenInputgithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.RefreshTokenOutputgithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.RegisterInputgithub.com/erweixin/go-genai-stack/backend/domains/auth/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/auth/service.RegisterOutput
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/auth/handlers uses github.com/erweixin/go-genai-stack/backend/domains/auth/service, so a change to github.com/erweixin/go-genai-stack/backend/domains/auth/service can break github.com/erweixin/go-genai-stack/backend/domains/auth/handlers, while a change to github.com/erweixin/go-genai-stack/backend/domains/auth/handlers can't break github.com/erweixin/go-genai-stack/backend/domains/auth/service.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/auth/handlers uses a module listed above it, which is the healthy direction.
33→24 github.com/erweixin/go-genai-stack/backend/domains/task/handlers uses github.com/erweixin/go-genai-stack/backend/domains/task/service✕
- Connections
- 14 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/task/handlers uses a type in github.com/erweixin/go-genai-stack/backend/domains/task/service.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/task/handlers.HandlerDependencies→github.com/erweixin/go-genai-stack/backend/domains/task/service.TaskServicegithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.CompleteTaskInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.CompleteTaskOutputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.CreateTaskInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.CreateTaskOutputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.DeleteTaskInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.DeleteTaskOutputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.GetTaskInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.GetTaskOutputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.ListTasksInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.ListTasksOutputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.TaskServicegithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.UpdateTaskInputgithub.com/erweixin/go-genai-stack/backend/domains/task/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/task/service.UpdateTaskOutput
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/task/handlers uses github.com/erweixin/go-genai-stack/backend/domains/task/service, so a change to github.com/erweixin/go-genai-stack/backend/domains/task/service can break github.com/erweixin/go-genai-stack/backend/domains/task/handlers, while a change to github.com/erweixin/go-genai-stack/backend/domains/task/handlers can't break github.com/erweixin/go-genai-stack/backend/domains/task/service.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/task/handlers uses a module listed above it, which is the healthy direction.
34→25 github.com/erweixin/go-genai-stack/backend/domains/user/handlers uses github.com/erweixin/go-genai-stack/backend/domains/user/service✕
- Connections
- 8 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/domains/user/handlers uses a type in github.com/erweixin/go-genai-stack/backend/domains/user/service.
- The types involved
github.com/erweixin/go-genai-stack/backend/domains/user/handlers.HandlerDependencies→github.com/erweixin/go-genai-stack/backend/domains/user/service.UserServicegithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.ChangePasswordInputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.ChangePasswordOutputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.GetUserProfileInputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.GetUserProfileOutputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.UpdateUserProfileInputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.UpdateUserProfileOutputgithub.com/erweixin/go-genai-stack/backend/domains/user/handlers.handlers→github.com/erweixin/go-genai-stack/backend/domains/user/service.UserService
- Direction
- github.com/erweixin/go-genai-stack/backend/domains/user/handlers uses github.com/erweixin/go-genai-stack/backend/domains/user/service, so a change to github.com/erweixin/go-genai-stack/backend/domains/user/service can break github.com/erweixin/go-genai-stack/backend/domains/user/handlers, while a change to github.com/erweixin/go-genai-stack/backend/domains/user/handlers can't break github.com/erweixin/go-genai-stack/backend/domains/user/service.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/domains/user/handlers uses a module listed above it, which is the healthy direction.
35→23 github.com/erweixin/go-genai-stack/backend/infrastructure/middleware uses github.com/erweixin/go-genai-stack/backend/domains/auth/service✕
- Connections
- 2 pairs of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/middleware uses a type in github.com/erweixin/go-genai-stack/backend/domains/auth/service.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/middleware.AuthMiddleware→github.com/erweixin/go-genai-stack/backend/domains/auth/service.JWTServicegithub.com/erweixin/go-genai-stack/backend/infrastructure/middleware.middleware→github.com/erweixin/go-genai-stack/backend/domains/auth/service.JWTService
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/middleware uses github.com/erweixin/go-genai-stack/backend/domains/auth/service, so a change to github.com/erweixin/go-genai-stack/backend/domains/auth/service can break github.com/erweixin/go-genai-stack/backend/infrastructure/middleware, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/middleware can't break github.com/erweixin/go-genai-stack/backend/domains/auth/service.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/middleware uses a module listed above it, which is the healthy direction.
36→28 backend-nodejs.domains.task.handlers.dependencies uses backend-nodejs.domains.task.service.task_service✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.handlers.dependencies uses a type in backend-nodejs.domains.task.service.task_service.
- The types involved
backend-nodejs.domains.task.handlers.dependencies.HandlerDependencies→backend-nodejs.domains.task.service.task_service.TaskService
- Direction
- backend-nodejs.domains.task.handlers.dependencies uses backend-nodejs.domains.task.service.task_service, so a change to backend-nodejs.domains.task.service.task_service can break backend-nodejs.domains.task.handlers.dependencies, while a change to backend-nodejs.domains.task.handlers.dependencies can't break backend-nodejs.domains.task.service.task_service.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers.dependencies uses a module listed above it, which is the healthy direction.
37→13 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/config✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/infrastructure/config.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.bootstrap→github.com/erweixin/go-genai-stack/backend/infrastructure/config.Config
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/config, so a change to github.com/erweixin/go-genai-stack/backend/infrastructure/config can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/infrastructure/config.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
37→14 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/persistence✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/infrastructure/persistence.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.bootstrap→github.com/erweixin/go-genai-stack/backend/infrastructure/persistence.DatabaseProvider
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/persistence, so a change to github.com/erweixin/go-genai-stack/backend/infrastructure/persistence can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/infrastructure/persistence.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
37→32 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/auth/handlers✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/domains/auth/handlers.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.AppContainer→github.com/erweixin/go-genai-stack/backend/domains/auth/handlers.HandlerDependencies
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/auth/handlers, so a change to github.com/erweixin/go-genai-stack/backend/domains/auth/handlers can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/domains/auth/handlers.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
37→33 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/task/handlers✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/domains/task/handlers.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.AppContainer→github.com/erweixin/go-genai-stack/backend/domains/task/handlers.HandlerDependencies
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/task/handlers, so a change to github.com/erweixin/go-genai-stack/backend/domains/task/handlers can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/domains/task/handlers.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
37→34 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/user/handlers✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/domains/user/handlers.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.AppContainer→github.com/erweixin/go-genai-stack/backend/domains/user/handlers.HandlerDependencies
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/domains/user/handlers, so a change to github.com/erweixin/go-genai-stack/backend/domains/user/handlers can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/domains/user/handlers.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
37→35 github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/middleware✕
- Connections
- 1 pair of types, where a type in github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a type in github.com/erweixin/go-genai-stack/backend/infrastructure/middleware.
- The types involved
github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap.AppContainer→github.com/erweixin/go-genai-stack/backend/infrastructure/middleware.AuthMiddleware
- Direction
- github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses github.com/erweixin/go-genai-stack/backend/infrastructure/middleware, so a change to github.com/erweixin/go-genai-stack/backend/infrastructure/middleware can break github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap, while a change to github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap can't break github.com/erweixin/go-genai-stack/backend/infrastructure/middleware.
- Position
- Below the diagonal: github.com/erweixin/go-genai-stack/backend/infrastructure/bootstrap uses a module listed above it, which is the healthy direction.
38→5 backend-nodejs.domains.auth.handlers uses backend-nodejs.infrastructure.middleware.tracing✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.auth.handlers uses a type in backend-nodejs.infrastructure.middleware.tracing.
- The types involved
backend-nodejs.domains.auth.handlers.login.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.auth.handlers.refresh_token.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.auth.handlers.register.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequest
- Direction
- backend-nodejs.domains.auth.handlers uses backend-nodejs.infrastructure.middleware.tracing, so a change to backend-nodejs.infrastructure.middleware.tracing can break backend-nodejs.domains.auth.handlers, while a change to backend-nodejs.domains.auth.handlers can't break backend-nodejs.infrastructure.middleware.tracing.
- Position
- Below the diagonal: backend-nodejs.domains.auth.handlers uses a module listed above it, which is the healthy direction.
38→8 backend-nodejs.domains.auth.handlers uses frontend.shared.types.domains.auth✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.auth.handlers uses a type in frontend.shared.types.domains.auth.
- The types involved
backend-nodejs.domains.auth.handlers.converters→frontend.shared.types.domains.auth.LoginRequestbackend-nodejs.domains.auth.handlers.converters→frontend.shared.types.domains.auth.RefreshTokenRequestbackend-nodejs.domains.auth.handlers.converters→frontend.shared.types.domains.auth.RegisterRequest
- Direction
- backend-nodejs.domains.auth.handlers uses frontend.shared.types.domains.auth, so a change to frontend.shared.types.domains.auth can break backend-nodejs.domains.auth.handlers, while a change to backend-nodejs.domains.auth.handlers can't break frontend.shared.types.domains.auth.
- Position
- Below the diagonal: backend-nodejs.domains.auth.handlers uses a module listed above it, which is the healthy direction.
38→26 backend-nodejs.domains.auth.handlers uses backend-nodejs.domains.auth.service.auth_service✕
- Connections
- 6 pairs of types, where a type in backend-nodejs.domains.auth.handlers uses a type in backend-nodejs.domains.auth.service.auth_service.
- The types involved
backend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.LoginInputbackend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.LoginOutputbackend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.RefreshTokenInputbackend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.RefreshTokenOutputbackend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.RegisterInputbackend-nodejs.domains.auth.handlers.converters→backend-nodejs.domains.auth.service.auth_service.RegisterOutput
- Direction
- backend-nodejs.domains.auth.handlers uses backend-nodejs.domains.auth.service.auth_service, so a change to backend-nodejs.domains.auth.service.auth_service can break backend-nodejs.domains.auth.handlers, while a change to backend-nodejs.domains.auth.handlers can't break backend-nodejs.domains.auth.service.auth_service.
- Position
- Below the diagonal: backend-nodejs.domains.auth.handlers uses a module listed above it, which is the healthy direction.
38→36 backend-nodejs.domains.auth.handlers uses backend-nodejs.domains.task.handlers.dependencies✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.auth.handlers uses a type in backend-nodejs.domains.task.handlers.dependencies.
- The types involved
backend-nodejs.domains.auth.handlers.login.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.auth.handlers.refresh_token.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.auth.handlers.register.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependencies
- Direction
- backend-nodejs.domains.auth.handlers uses backend-nodejs.domains.task.handlers.dependencies, so a change to backend-nodejs.domains.task.handlers.dependencies can break backend-nodejs.domains.auth.handlers, while a change to backend-nodejs.domains.auth.handlers can't break backend-nodejs.domains.task.handlers.dependencies.
- Position
- Below the diagonal: backend-nodejs.domains.auth.handlers uses a module listed above it, which is the healthy direction.
39→2 backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.http.dto.task✕
- Connections
- 6 pairs of types, where a type in backend-nodejs.domains.task.handlers uses a type in backend-nodejs.domains.task.http.dto.task.
- The types involved
backend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.CompleteTaskResponsebackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.CreateTaskResponsebackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.DeleteTaskResponsebackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.GetTaskResponsebackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.ListTasksResponsebackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.http.dto.task.UpdateTaskResponse
- Direction
- backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.http.dto.task, so a change to backend-nodejs.domains.task.http.dto.task can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break backend-nodejs.domains.task.http.dto.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
39→3 backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.model.task✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.task.handlers uses a type in backend-nodejs.domains.task.model.task.
- The types involved
backend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.model.task.Task
- Direction
- backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.model.task, so a change to backend-nodejs.domains.task.model.task can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break backend-nodejs.domains.task.model.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
39→5 backend-nodejs.domains.task.handlers uses backend-nodejs.infrastructure.middleware.tracing✕
- Connections
- 6 pairs of types, where a type in backend-nodejs.domains.task.handlers uses a type in backend-nodejs.infrastructure.middleware.tracing.
- The types involved
backend-nodejs.domains.task.handlers.complete_task.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.task.handlers.create_task.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.task.handlers.delete_task.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.task.handlers.get_task.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.task.handlers.list_tasks.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.task.handlers.update_task.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequest
- Direction
- backend-nodejs.domains.task.handlers uses backend-nodejs.infrastructure.middleware.tracing, so a change to backend-nodejs.infrastructure.middleware.tracing can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break backend-nodejs.infrastructure.middleware.tracing.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
39→20 backend-nodejs.domains.task.handlers uses frontend.shared.types.domains.task✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.domains.task.handlers uses a type in frontend.shared.types.domains.task.
- The types involved
backend-nodejs.domains.task.handlers.converters→frontend.shared.types.domains.task.CreateTaskRequestbackend-nodejs.domains.task.handlers.converters→frontend.shared.types.domains.task.UpdateTaskRequest
- Direction
- backend-nodejs.domains.task.handlers uses frontend.shared.types.domains.task, so a change to frontend.shared.types.domains.task can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break frontend.shared.types.domains.task.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
39→28 backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.service.task_service✕
- Connections
- 6 pairs of types, where a type in backend-nodejs.domains.task.handlers uses a type in backend-nodejs.domains.task.service.task_service.
- The types involved
backend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.CompleteTaskInputbackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.CreateTaskInputbackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.DeleteTaskInputbackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.GetTaskInputbackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.ListTasksInputbackend-nodejs.domains.task.handlers.converters→backend-nodejs.domains.task.service.task_service.UpdateTaskInput
- Direction
- backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.service.task_service, so a change to backend-nodejs.domains.task.service.task_service can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break backend-nodejs.domains.task.service.task_service.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
39→36 backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.handlers.dependencies✕
- Connections
- 6 pairs of types, where a type in backend-nodejs.domains.task.handlers uses a type in backend-nodejs.domains.task.handlers.dependencies.
- The types involved
backend-nodejs.domains.task.handlers.complete_task.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.task.handlers.create_task.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.task.handlers.delete_task.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.task.handlers.get_task.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.task.handlers.list_tasks.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.task.handlers.update_task.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependencies
- Direction
- backend-nodejs.domains.task.handlers uses backend-nodejs.domains.task.handlers.dependencies, so a change to backend-nodejs.domains.task.handlers.dependencies can break backend-nodejs.domains.task.handlers, while a change to backend-nodejs.domains.task.handlers can't break backend-nodejs.domains.task.handlers.dependencies.
- Position
- Below the diagonal: backend-nodejs.domains.task.handlers uses a module listed above it, which is the healthy direction.
40→4 backend-nodejs.domains.user.handlers uses backend-nodejs.domains.user.model.user✕
- Connections
- 1 pair of types, where a type in backend-nodejs.domains.user.handlers uses a type in backend-nodejs.domains.user.model.user.
- The types involved
backend-nodejs.domains.user.handlers.converters→backend-nodejs.domains.user.model.user.User
- Direction
- backend-nodejs.domains.user.handlers uses backend-nodejs.domains.user.model.user, so a change to backend-nodejs.domains.user.model.user can break backend-nodejs.domains.user.handlers, while a change to backend-nodejs.domains.user.handlers can't break backend-nodejs.domains.user.model.user.
- Position
- Below the diagonal: backend-nodejs.domains.user.handlers uses a module listed above it, which is the healthy direction.
40→5 backend-nodejs.domains.user.handlers uses backend-nodejs.infrastructure.middleware.tracing✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.user.handlers uses a type in backend-nodejs.infrastructure.middleware.tracing.
- The types involved
backend-nodejs.domains.user.handlers.change_password.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.user.handlers.get_user_profile.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequestbackend-nodejs.domains.user.handlers.update_user_profile.handler→backend-nodejs.infrastructure.middleware.tracing.FastifyRequest
- Direction
- backend-nodejs.domains.user.handlers uses backend-nodejs.infrastructure.middleware.tracing, so a change to backend-nodejs.infrastructure.middleware.tracing can break backend-nodejs.domains.user.handlers, while a change to backend-nodejs.domains.user.handlers can't break backend-nodejs.infrastructure.middleware.tracing.
- Position
- Below the diagonal: backend-nodejs.domains.user.handlers uses a module listed above it, which is the healthy direction.
40→21 backend-nodejs.domains.user.handlers uses frontend.shared.types.domains.user✕
- Connections
- 2 pairs of types, where a type in backend-nodejs.domains.user.handlers uses a type in frontend.shared.types.domains.user.
- The types involved
backend-nodejs.domains.user.handlers.converters→frontend.shared.types.domains.user.ChangePasswordRequestbackend-nodejs.domains.user.handlers.converters→frontend.shared.types.domains.user.UpdateUserProfileRequest
- Direction
- backend-nodejs.domains.user.handlers uses frontend.shared.types.domains.user, so a change to frontend.shared.types.domains.user can break backend-nodejs.domains.user.handlers, while a change to backend-nodejs.domains.user.handlers can't break frontend.shared.types.domains.user.
- Position
- Below the diagonal: backend-nodejs.domains.user.handlers uses a module listed above it, which is the healthy direction.
40→30 backend-nodejs.domains.user.handlers uses backend-nodejs.domains.user.service.user_service✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.user.handlers uses a type in backend-nodejs.domains.user.service.user_service.
- The types involved
backend-nodejs.domains.user.handlers.converters→backend-nodejs.domains.user.service.user_service.ChangePasswordInputbackend-nodejs.domains.user.handlers.converters→backend-nodejs.domains.user.service.user_service.GetUserProfileInputbackend-nodejs.domains.user.handlers.converters→backend-nodejs.domains.user.service.user_service.UpdateUserProfileInput
- Direction
- backend-nodejs.domains.user.handlers uses backend-nodejs.domains.user.service.user_service, so a change to backend-nodejs.domains.user.service.user_service can break backend-nodejs.domains.user.handlers, while a change to backend-nodejs.domains.user.handlers can't break backend-nodejs.domains.user.service.user_service.
- Position
- Below the diagonal: backend-nodejs.domains.user.handlers uses a module listed above it, which is the healthy direction.
40→36 backend-nodejs.domains.user.handlers uses backend-nodejs.domains.task.handlers.dependencies✕
- Connections
- 3 pairs of types, where a type in backend-nodejs.domains.user.handlers uses a type in backend-nodejs.domains.task.handlers.dependencies.
- The types involved
backend-nodejs.domains.user.handlers.change_password.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.user.handlers.get_user_profile.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependenciesbackend-nodejs.domains.user.handlers.update_user_profile.handler→backend-nodejs.domains.task.handlers.dependencies.HandlerDependencies
- Direction
- backend-nodejs.domains.user.handlers uses backend-nodejs.domains.task.handlers.dependencies, so a change to backend-nodejs.domains.task.handlers.dependencies can break backend-nodejs.domains.user.handlers, while a change to backend-nodejs.domains.user.handlers can't break backend-nodejs.domains.task.handlers.dependencies.
- Position
- Below the diagonal: backend-nodejs.domains.user.handlers uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 88 | High / Critical |
| A05:2025 — Injection | 56 | High / Critical |
| A07:2025 — Authentication Failures | 27 | High / Critical |
| A02:2025 — Security Misconfiguration | 19 | High / Critical |
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label; Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. | +5.3 pts | Medium | Visual & motion safety |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +4.7 pts | Medium | Forms & labels |
| Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +4.1 pts | Medium | A11y enforcement |
| Resolve the 89 Orphaned file finding(s) in Knowledge Freshness — start with provider.go (3), tracing.go (2), converters.go (2). | +1.8 pts | Medium | Knowledge Freshness |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.6 pts | Low | ADR Quality |
| Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. | +1.3 pts | Low | Secrets (history) |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +2.5 pts | Medium | Page structure |
| Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (2). | +1.2 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.2 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 1.6 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 89 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 89 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, 527 of 558 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, .tsx, .go, and our analyzer cannot run the .go test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 39.1% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`, or `go test -coverprofile=coverage.out ./...`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 270 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 12 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 113 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (backend-nodejs/package.json), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `backend/domains/auth/ai-metadata.json`, `backend-nodejs/domains/auth/ai-metadata.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in backend/infrastructure/bootstrap/dependencies.go, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.postgres.environment.POSTGRES_PASSWORD: required variable POSTGRES_PASSWORD is missing a value: 请设置 POSTGRES_PASSWORD; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
- M4 Documentation accuracy — 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. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
- M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
Dimensions
D1 · Cyclomatic Complexity
4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TaskEditDialog.TaskEditDialog at 19.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TaskEditDialog.TaskEditDialog (cyclomatic 19), TaskService.UpdateTask (cyclomatic 16), TaskRepositoryImpl.list (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was TaskService.UpdateTask at 20.
What to do
- Bring the 8 bodies over 15 down to 15 or less in Cognitive Complexity — start with TaskService.UpdateTask (cognitive 20), Validator.validateMonitoring (cognitive 20), TaskEditDialog.TaskEditDialog (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 5 FunctionTooLong finding(s) in God Classes — start with ShowcasePage.tsx, TaskEditDialog.tsx, TaskCreateDialog.tsx. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with ShowcasePage.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ShowcasePage.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
22 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .ts, .tsx (54% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 5 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with auth_service.go, user_repo.go, helpers.go. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with task_repo.go (2), user_repo.go, provider.go. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with helpers.go (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 6 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 29 classes have LCOM4 above 3.
D9 · Test Distribution
345 test methods: 324 unit, 0 integration, 0 BDD, 21 e2e. The JavaScript/TypeScript suite contributes 270 `it`/`test` case(s) across 35 test file(s) declaring at least one; its tier split is read from package names and paths only. The Go suite contributes 75 test case(s) across 11 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 270 tests. Measured on the JavaScript/TypeScript suite only — at least 12 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 2 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in backend-nodejs/ (151 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in frontend/shared/utils/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in frontend/web/ (98 tests)): measured (0 flaky); Go (github.com/erweixin/go-genai-stack/backend): measured (0 flaky).
What to do
- Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
17 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · REDACTED Scanning
10 secret(s) detected.
What to do
- Resolve the 11 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (11 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
Top hotspots: frontend/web/src/features/task/components/TaskEditDialog.tsx (5×19=95); frontend/web/src/features/task/components/TaskCreateDialog.tsx (5×16=80); frontend/web/src/lib/monitoring/sentry.ts (3×15=45)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with TaskEditDialog.tsx, TaskCreateDialog.tsx, sentry.ts. — One of this dimension's main actionable groups (3 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 20325 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
2 of 2 documentation facets pass in full. 57 document(s) read across 8 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).
D24 · Comment Value
3 of 57 judged comments only repeat the code they sit on (5.3 %). 722 comment(s) in another language or script were not judged.
What to do
- Resolve the 3 redundant comment finding(s) in Comment Value — start with auth_service.test.ts, REDACTED, auth.store.test.ts. — One of this dimension's main actionable groups (3 recommendation-level).
D26 · Project Cohesion
2 of 7 build units (Go, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
56 finding(s): 0 critical, 47 high, 9 medium, 0 low. 36 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 9 file(s) — `backend-nodejs/domains/auth/ai-metadata.json`, `backend-nodejs/domains/auth/usecases.yaml`, `backend-nodejs/domains/task/usecases.yaml`, `backend-nodejs/domains/user/usecases.yaml`, `backend/domains/auth/ai-metadata.json`, … (+4 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 36 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 (36 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
88 finding(s): 9 critical, 53 high, 24 medium, 2 low.
What to do
- Resolve the 53 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (51), REDACTED (2). — One of this dimension's main actionable groups (53 issue-level).
- Resolve the 20 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED (7). — One of this dimension's main actionable groups (20 warning-level).
- Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7), REDACTED (2). — One of this dimension's main actionable groups (9 issue-level).
D31 · IaC & Container Security
19 finding(s): 0 critical, 4 high, 15 medium, 0 low.
What to do
- Resolve the 15 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (4). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
D34 · Knowledge Freshness
90 of 90 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx. Counted over 90 of the 222 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 89 Orphaned file finding(s) in Knowledge Freshness — start with provider.go (3), tracing.go (2), converters.go (2). — One of this dimension's main actionable groups (89 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with ShowcasePage.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×3) — frontend/web/src/features/task/components/TaskFilters.tsx:52, frontend/web/src/features/task/components/TaskFilters.tsx:67, frontend/web/src/features/task/components/TaskFilters.tsx:83
- This select is named only by the placeholder of its value part. Nothing is typed into a select, so the placeholder does not vanish on input: it is shown as the trigger's text until a value is chosen, and then the chosen value replaces it — so at no point does the control state what the choice is for, and the trigger's role (combobox) takes its name from the author, not from that text. Name it: an aria-label on the trigger, or an id on the trigger with a <label htmlFor> pointing at it. (×3) — frontend/web/src/features/task/components/TaskFilters.tsx:53, frontend/web/src/features/task/components/TaskFilters.tsx:68, frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:187
- This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:214
- This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:229
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — frontend/web/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/web/src/components/ui/input.tsx:7
- <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — frontend/web/src/components/ui/textarea.tsx:7
- <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — frontend/web/src/features/task/components/TaskList.tsx:27
- `.animate-in` moves (`animation-name: enter`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:107
- `.animate-out` moves (`animation-name: exit`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:113
- `.slide-in-from-top` moves (`animation: slideInFromTop 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:127
- `.slide-in-from-bottom` moves (`animation: slideInFromBottom 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:131
- `.slide-in-from-left` moves (`animation: slideInFromLeft 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:135
- `.slide-in-from-right` moves (`animation: slideInFromRight 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:139
- `.scale-in` moves (`animation: scaleIn 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/web/src/index.css:143
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 57 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — frontend/package.json:46
What to do
- Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
AX8 · Test isolation
- `go-genai-stack-backend-nodejs` ships in a production host and references `@vitest/ui`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `go-genai-stack-backend-nodejs` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — backend-nodejs/package.json:37
- `go-genai-stack-backend-nodejs` ships in a production host and references `supertest`, a package that exists only to test. It puts a test framework, double or assertion library into the shipped product. Move the code that uses it into a test project, or replace it with production code. If `go-genai-stack-backend-nodejs` is itself a plugin, matcher or preset of the test framework, declare the framework under `peerDependencies` (and `devDependencies`) instead of `dependencies`. — backend-nodejs/package.json:46
What to do
- Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM2 · Strongly-typed ids
- `Task.ID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/domains/task/model/task.go:55
- `Task.UserID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/domains/task/model/task.go:56
- `User.ID` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/domains/user/model/user.go:34
What to do
- Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
DM4 · Rich vs anemic model
DM5 · Encapsulated state
- `Task` exposes publicly writable state (ID, UserID, Title, Description, Status, Priority, and 5 more). — backend/domains/task/model/task.go:54
- `User` exposes publicly writable state (ID, Email, Username, PasswordHash, FullName, AvatarURL, and 5 more). — backend/domains/user/model/user.go:33
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM6 · Domain ↔ infrastructure boundary
- `backend-nodejs/domains/auth/handlers/login.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/auth/handlers/login.handler.ts:5
- `backend-nodejs/domains/auth/handlers/refresh_token.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/auth/handlers/refresh_token.handler.ts:5
- `backend-nodejs/domains/auth/handlers/register.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/auth/handlers/register.handler.ts:6
- `REDACTED` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — REDACTED:6
- `REDACTED` (domain layer) depends on `redis` (import) — a cache module; the domain should own a port and let an infrastructure adapter implement it. — REDACTED:7
- `backend-nodejs/domains/task/handlers/complete_task.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/complete_task.handler.ts:5
- `backend-nodejs/domains/task/handlers/create_task.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/create_task.handler.ts:6
- `backend-nodejs/domains/task/handlers/delete_task.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/delete_task.handler.ts:5
- `backend-nodejs/domains/task/handlers/get_task.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/get_task.handler.ts:5
- `backend-nodejs/domains/task/handlers/list_tasks.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/list_tasks.handler.ts:5
- `backend-nodejs/domains/task/handlers/update_task.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/handlers/update_task.handler.ts:5
- `backend-nodejs/domains/task/http/router.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/task/http/router.ts:6
- `backend-nodejs/domains/user/handlers/change_password.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/user/handlers/change_password.handler.ts:5
- `backend-nodejs/domains/user/handlers/get_user_profile.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/user/handlers/get_user_profile.handler.ts:6
- `backend-nodejs/domains/user/handlers/update_user_profile.handler.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/user/handlers/update_user_profile.handler.ts:5
- `backend-nodejs/domains/user/http/router.ts` (domain layer) depends on `fastify` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend-nodejs/domains/user/http/router.ts:6
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM7 · Repository granularity
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
- A placeholder string ("这是段落文字。Lorem ipsum dolor sit amet, conse…") is still in shipped code — typical of generated boilerplate that was never filled in. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:137
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `metricsMiddleware` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — backend-nodejs/infrastructure/middleware/metrics.ts:14
- `metricsResponseHook` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — backend-nodejs/infrastructure/middleware/metrics.ts:26
What to do
- Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.
M1 · Documentation (README)
What to do
- Add a README to the 1 of 8 project(s) that lack one — worth up to 0.3 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Tests aren't where this ecosystem separates them — a `_test.go` file beside the code it tests is the convention, and none is present.
What to do
- Add `*_test.go` files beside the packages they cover — `go test` compiles only those, in-package, so the suffix IS the separation (a tests/ folder is anti-idiomatic in Go) — and run `go test ./...` in CI.
M4 · Documentation accuracy
- backend-nodejs/README.md links to `docs/MONITORING_AND_SECURITY.md`, but `backend-nodejs/docs/MONITORING_AND_SECURITY.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend-nodejs/README.md:569
- backend-nodejs/README.md links to `docs/QUICK_START_MONITORING.md`, but `backend-nodejs/docs/QUICK_START_MONITORING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend-nodejs/README.md:570
- backend/README.md links to `../docs/Core/architecture-audit.md`, but `docs/Core/architecture-audit.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/README.md:617
- backend/database/README.md links to `./QUICK_START.md`, but `backend/database/QUICK_START.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/database/README.md:776
- backend/database/README.md links to `./MIGRATION_GUIDE.md`, but `backend/database/MIGRATION_GUIDE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/database/README.md:777
- backend/infrastructure/README.md links to `../../docs/vibe-coding-ddd-structure.md`, but `docs/vibe-coding-ddd-structure.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/README.md:389
- backend/infrastructure/README.md links to `../../docs/optimization-plan.md`, but `docs/optimization-plan.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/README.md:390
- backend/infrastructure/README.md links to `../../docs/configuration.md`, but `docs/configuration.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/README.md:391
- docker/frontend-debug/README.md links to `../docker/e2e/README.md`, but `docker/docker/e2e/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docker/frontend-debug/README.md:362
- docker/frontend-debug/README.md links to `../frontend/web/README.md`, but `docker/frontend/web/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docker/frontend-debug/README.md:363
- docker/frontend-debug/README.md links to `../frontend/web/doc/unit-testing.md`, but `docker/frontend/web/doc/unit-testing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docker/frontend-debug/README.md:364
- docker/frontend-debug/README.md links to `../frontend/web/doc/e2e-testing.md`, but `docker/frontend/web/doc/e2e-testing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docker/frontend-debug/README.md:365
- frontend/shared/README.md links to `../docs/optimal-architecture.md`, but `frontend/docs/optimal-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/shared/README.md:255
- frontend/shared/README.md links to `../docs/type-sync.md`, but `frontend/docs/type-sync.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/shared/README.md:256
- frontend/shared/README.md links to `../docs/vibe-coding-ddd-structure.md`, but `frontend/docs/vibe-coding-ddd-structure.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/shared/README.md:257
- backend-nodejs/domains/user/README.md links to `../../database/schema.sql`, but `backend-nodejs/database/schema.sql` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend-nodejs/domains/user/README.md:177
- backend/infrastructure/bootstrap/README.md links to `../../../docs/vibe-coding-ddd-structure.md`, but `docs/vibe-coding-ddd-structure.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/bootstrap/README.md:341
- backend/infrastructure/bootstrap/README.md links to `../../../docs/dependency-injection.md`, but `docs/dependency-injection.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/bootstrap/README.md:342
- backend/infrastructure/bootstrap/README.md links to `../../../docs/testing-strategy.md`, but `docs/testing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/infrastructure/bootstrap/README.md:343
- frontend/shared/constants/README.md links to `../../docs/optimal-architecture.md`, but `frontend/docs/optimal-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/shared/constants/README.md:85
- frontend/shared/utils/README.md links to `../../docs/optimal-architecture.md`, but `frontend/docs/optimal-architecture.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/shared/utils/README.md:92
- frontend/web/doc/README.md links to `../../../docs/FRONTEND_REFACTORING_PLAN.md`, but `docs/FRONTEND_REFACTORING_PLAN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/doc/README.md:78
- frontend/web/doc/README.md links to `../../../docs/FRONTEND_TESTING_PLAN.md`, but `docs/FRONTEND_TESTING_PLAN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/doc/README.md:82
- frontend/web/doc/README.md links to `../../../docs/FRONTEND_E2E_PLAN.md`, but `docs/FRONTEND_E2E_PLAN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/doc/README.md:83
- frontend/web/e2e/README.md links to `../../docs/FRONTEND_E2E_PLAN.md`, but `frontend/docs/FRONTEND_E2E_PLAN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/e2e/README.md:291
- frontend/web/src/features/task/README.md links to `../../../../backend/domains/task/README.md`, but `frontend/backend/domains/task/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/src/features/task/README.md:633
- frontend/web/src/lib/monitoring/README.md links to `../../../../docker/monitoring/README.md`, but `frontend/docker/monitoring/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/src/lib/monitoring/README.md:373
- frontend/web/src/lib/monitoring/README.md links to `../../../components/ErrorBoundary.tsx`, but `frontend/web/components/ErrorBoundary.tsx` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/src/lib/monitoring/README.md:374
- frontend/web/src/pages/ShowcasePage/README.md links to `../../../MIGRATION_SUMMARY.md`, but `frontend/web/MIGRATION_SUMMARY.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/web/src/pages/ShowcasePage/README.md:225
What to do
- Reconcile the README with reality: backend-nodejs/README.md links to `docs/MONITORING_AND_SECURITY.md`, but `backend-nodejs/docs/MONITORING_AND_SECURITY.md` does not exist; backend-nodejs/README.md links to `docs/QUICK_START_MONITORING.md`, but `backend-nodejs/docs/QUICK_START_MONITORING.md` does not exist; backend/README.md links to `../docs/Core/architecture-audit.md`, but `docs/Core/architecture-audit.md` does not exist; backend/database/README.md links to `./QUICK_START.md`, but `backend/database/QUICK_START.md` does not exist; backend/database/README.md links to `./MIGRATION_GUIDE.md`, but `backend/database/MIGRATION_GUIDE.md` does not exist.
P1 · CI/CD gates
- `echo "❌ Code is not formatted. Please run 'gofmt -s -w .'"` invokes gofmt in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `-l` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — REDACTED:121
What to do
- Add `-l` to the gofmt step in `REDACTED` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning
P2 · Observability
- `backend-nodejs/infrastructure/persistence/redis/connection.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/persistence/redis/connection.ts:37
- `backend-nodejs/infrastructure/persistence/redis/connection.ts` reports through `console.*` at line 79 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/persistence/redis/connection.ts:79
- `backend-nodejs/infrastructure/persistence/redis/connection.ts` reports through `console.*` at line 93 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/persistence/redis/connection.ts:93
- `backend-nodejs/infrastructure/persistence/postgres/connection.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/persistence/postgres/connection.ts:44
- `backend-nodejs/infrastructure/monitoring/health/health.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/monitoring/health/health.ts:35
- `backend-nodejs/infrastructure/monitoring/health/health.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/monitoring/health/health.ts:51
- `backend-nodejs/infrastructure/config/config.ts` reports through `console.*` at line 146 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/config/config.ts:146
- `backend-nodejs/infrastructure/config/config.ts` reports through `console.*` at line 149 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/config/config.ts:149
- `backend-nodejs/infrastructure/config/config.ts` reports through `console.*` at line 151 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend-nodejs/infrastructure/config/config.ts:151
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 8 duplicated blocks under backend-nodejs/domains/ have copies in at least two of the sibling directories task, user — 6 of them are reported below, and 2 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — backend-nodejs/domains/task/model/task.ts:47
- 5 duplicated blocks under frontend/web/src/ have copies in at least two of the sibling directories components, features, hooks, pages — 3 of them are reported below, and 2 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. — frontend/web/src/components/theme-provider.tsx:31
- frontend/web/src/features/task/components/TaskCreateDialog.tsx:75 · frontend/web/src/features/task/components/TaskEditDialog.tsx:94 — the two spans are one implementation copied and then locally edited — 900 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. — frontend/web/src/features/task/components/TaskCreateDialog.tsx:75
- frontend/web/src/components/ui/dropdown-menu.tsx:7 · frontend/web/src/components/ui/select.tsx:7 — the two spans are one implementation copied and then locally edited — 488 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. — frontend/web/src/components/ui/dropdown-menu.tsx:7
- frontend/web/src/pages/LoginPage/LoginPage.tsx:37 · frontend/web/src/pages/RegisterPage/RegisterPage.tsx:39 — the two spans are one implementation copied and then locally edited — 379 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. — frontend/web/src/pages/LoginPage/LoginPage.tsx:37
- frontend/web/src/components/ui/dialog.tsx:68 · frontend/web/src/components/ui/sheet.tsx:73 — 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. — frontend/web/src/components/ui/dialog.tsx:68
- frontend/web/src/components/ui/dialog.tsx:7 · frontend/web/src/components/ui/sheet.tsx:9 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/web/src/components/ui/dialog.tsx:7
- frontend/web/src/pages/HomePage/HomePage.tsx:79 · frontend/web/src/pages/HomePage/HomePage.tsx:102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — frontend/web/src/pages/HomePage/HomePage.tsx:79
- backend-nodejs/domains/task/http/router.ts:55 · backend-nodejs/domains/task/http/router.ts:96 — all 2 copies are in the same file, 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. — backend-nodejs/domains/task/http/router.ts:55
- backend-nodejs/domains/auth/service/jwt_service.ts:40 · backend-nodejs/domains/auth/service/jwt_service.ts:66 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — backend-nodejs/domains/auth/service/jwt_service.ts:40
- frontend/web/src/components/theme-provider.tsx:31 · frontend/web/src/hooks/use-theme.ts:8 — 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. — frontend/web/src/components/theme-provider.tsx:31
- frontend/web/src/components/ui/alert.tsx:31 · frontend/web/src/components/ui/breadcrumb.tsx:16 · frontend/web/src/components/ui/card.tsx:23 · frontend/web/src/components/ui/card.tsx:45 · +6 more site(s) not listed — the 10 copies are spread across 8 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. — frontend/web/src/components/ui/alert.tsx:31
- frontend/web/src/components/ui/select.tsx:129 · frontend/web/src/components/ui/select.tsx:144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — frontend/web/src/components/ui/select.tsx:129
- backend-nodejs/domains/task/service/task_service.ts:125 · backend-nodejs/domains/task/service/task_service.ts:184 · backend-nodejs/domains/task/service/task_service.ts:214 · backend-nodejs/domains/task/service/task_service.ts:244 — all 4 copies are in the same file, 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. — backend-nodejs/domains/task/service/task_service.ts:125
- backend-nodejs/domains/user/repository/user_repo.ts:49 · backend-nodejs/domains/user/repository/user_repo.ts:78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — backend-nodejs/domains/user/repository/user_repo.ts:49
- frontend/web/src/components/ErrorBoundary.tsx:107 · frontend/web/src/components/ErrorBoundary.tsx:177 · frontend/web/src/pages/HomePage/HomePage.tsx:82 · frontend/web/src/pages/HomePage/HomePage.tsx:105 — 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. — frontend/web/src/components/ErrorBoundary.tsx:107
- frontend/web/src/features/task/hooks/useTasks.mutation.ts:41 · frontend/web/src/features/task/hooks/useTasks.mutation.ts:87 — all 2 copies are in the same file, 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. — frontend/web/src/features/task/hooks/useTasks.mutation.ts:41
- frontend/web/src/features/task/schemas/task.schema.ts:18 · frontend/web/src/features/task/schemas/task.schema.ts:42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — frontend/web/src/features/task/schemas/task.schema.ts:18
- backend-nodejs/domains/task/model/task.ts:85 · backend-nodejs/domains/task/model/task.ts:123 — the two spans are one implementation copied and then locally edited — 79 tokens are still identical, in the same order in both spans, 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. — backend-nodejs/domains/task/model/task.ts:85
- frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:110 · frontend/web/src/pages/TasksPage/TasksPage.tsx:79 — the two spans are one implementation copied and then locally edited — 61 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. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:110
- backend-nodejs/domains/task/handlers/complete_task.handler.ts:19 · backend-nodejs/domains/task/handlers/delete_task.handler.ts:19 · backend-nodejs/domains/task/handlers/get_task.handler.ts:19 — 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. — backend-nodejs/domains/task/handlers/complete_task.handler.ts:19
- backend-nodejs/domains/task/repository/task_repo.ts:69 · backend-nodejs/domains/user/repository/user_repo.ts:101 — 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. — backend-nodejs/domains/task/repository/task_repo.ts:69
- backend-nodejs/domains/task/repository/task_repo.ts:88 · backend-nodejs/domains/user/repository/user_repo.ts:130 — 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. — backend-nodejs/domains/task/repository/task_repo.ts:88
- backend-nodejs/domains/user/handlers/converters.ts:34 · backend-nodejs/domains/user/handlers/converters.ts:72 — all 2 copies are in the same file, 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. — backend-nodejs/domains/user/handlers/converters.ts:34
- frontend/web/src/components/ui/avatar.tsx:24 · frontend/web/src/components/ui/dialog.tsx:101 · frontend/web/src/components/ui/sheet.tsx:106 · frontend/web/src/components/ui/tabs.tsx:40 — the 4 copies are spread across 4 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. — frontend/web/src/components/ui/avatar.tsx:24
- frontend/web/src/features/task/hooks/useTasks.mutation.ts:84 · frontend/web/src/features/task/hooks/useTasks.mutation.ts:200 — all 2 copies are in the same file, 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. — frontend/web/src/features/task/hooks/useTasks.mutation.ts:84
- frontend/web/src/pages/HomePage/HomePage.tsx:27 · frontend/web/src/pages/LoginPage/LoginPage.tsx:52 · frontend/web/src/pages/RegisterPage/RegisterPage.tsx:54 — the 3 copies are spread across 3 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. — frontend/web/src/pages/HomePage/HomePage.tsx:27
- backend-nodejs/domains/auth/handlers/login.handler.ts:19 · backend-nodejs/domains/auth/handlers/refresh_token.handler.ts:19 · backend-nodejs/domains/auth/handlers/register.handler.ts:20 — 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. — backend-nodejs/domains/auth/handlers/login.handler.ts:19
- backend-nodejs/domains/task/handlers/create_task.handler.ts:21 · backend-nodejs/domains/task/handlers/list_tasks.handler.ts:20 · backend-nodejs/domains/user/handlers/change_password.handler.ts:20 · backend-nodejs/domains/user/handlers/update_user_profile.handler.ts:20 — 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. — backend-nodejs/domains/task/handlers/create_task.handler.ts:21
- backend-nodejs/domains/task/repository/task_repo.ts:42 · backend-nodejs/domains/user/repository/user_repo.ts:47 · backend-nodejs/domains/user/repository/user_repo.ts:76 — the 3 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. — backend-nodejs/domains/task/repository/task_repo.ts:42
- frontend/web/src/features/auth/stores/auth.store.ts:68 · frontend/web/src/features/auth/stores/auth.store.ts:109 — all 2 copies are in the same file, 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. — frontend/web/src/features/auth/stores/auth.store.ts:68
- backend-nodejs/domains/task/repository/task_repo.ts:191 · backend-nodejs/domains/user/repository/user_repo.ts:154 — 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. — backend-nodejs/domains/task/repository/task_repo.ts:191
- backend-nodejs/infrastructure/config/config.ts:76 · backend-nodejs/infrastructure/config/config.ts:85 — all 2 copies are in the same file, 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. — backend-nodejs/infrastructure/config/config.ts:76
- backend-nodejs/infrastructure/monitoring/health/health.ts:24 · backend-nodejs/infrastructure/persistence/postgres/connection.ts:39 — the two spans are one implementation copied and then locally edited — 60 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. — backend-nodejs/infrastructure/monitoring/health/health.ts:24
- frontend/web/src/features/task/components/TaskCreateDialog.tsx:176 · frontend/web/src/features/task/components/TaskEditDialog.tsx:198 · frontend/web/src/features/task/components/TaskFilters.tsx:55 · frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:189 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — frontend/web/src/features/task/components/TaskCreateDialog.tsx:176
- frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:461 · frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:461
- frontend/web/src/features/auth/stores/auth.store.ts:46 · frontend/web/src/features/auth/stores/auth.store.ts:79 — all 2 copies are in the same file, 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. — frontend/web/src/features/auth/stores/auth.store.ts:46
- backend-nodejs/domains/user/repository/user_repo.ts:147 · backend-nodejs/domains/user/repository/user_repo.ts:157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — backend-nodejs/domains/user/repository/user_repo.ts:147
- backend-nodejs/domains/task/handlers/create_task.handler.ts:30 · backend-nodejs/domains/task/handlers/update_task.handler.ts:31 · backend-nodejs/domains/user/handlers/update_user_profile.handler.ts:27 — the 3 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 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. — backend-nodejs/domains/task/handlers/create_task.handler.ts:30
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.
R2 · Cyclomatic Complexity
- transform has cyclomatic complexity 31 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — frontend/web/plugins/removeTestId.js:18
- list has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/task/repository/task_repo.ts:103
- update has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/user/repository/user_repo.ts:92
- updateTask has cyclomatic complexity 12 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/task/service/task_service.ts:131
- updateProfile has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/user/model/user.ts:117
- createTask has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/task/service/task_service.ts:87
- toListTasksInput has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — backend-nodejs/domains/task/handlers/converters.ts:200
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx has 581 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
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. (×24) — REDACTED:1, frontend/web/src/components/ui/calendar.tsx:1, frontend/web/src/components/ui/command.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- Unreachable from the 14 application, 9 tooling and 42 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (14 application, 9 tooling, 42 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×10) — frontend/web/src/components/ui/calendar.tsx, frontend/web/src/components/ui/command.tsx, REDACTED, …
- Nothing imports this binding — it is safe to review for removal. (×21) — backend-nodejs/domains/task/http/dto/task.ts:58, backend-nodejs/domains/task/http/dto/task.ts:137, REDACTED:72, …
- Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/web/src/features/task/hooks/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/web/src/features/task/hooks/index.ts in the same commit, or the barrel will import a name that no longer exists. — frontend/web/src/features/task/hooks/useTasks.query.ts:54
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
- Declared in backend-nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — frontend/web/src/pages/RegisterPage/RegisterPage.tsx:49, frontend/web/src/pages/LoginPage/LoginPage.tsx:47, REDACTED:87, …
- `if err := json.Unmarshal([]byte(str), &value); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:186
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- ~0.2 `!` null assertions per 1k TypeScript source lines — 2 assertion(s) across the 12375 source line(s) of the 143 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: backend-nodejs/domains/task/repository/task_repo.ts (1), frontend/web/src/main.tsx (1). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 83% | Strong | Solid. |
| Architecture | 70% | Adequate | Acceptable, with room to improve. |
| Maturity | 48% | Weak — gated by D34, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 57% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 45% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 50% | Adequate — gated by DM6, DM5, DM2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 36% | Weak — gated by AC2, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 47 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.postgres.environment.POSTGRES_PASSWORD: required variable POSTGRES_PASSWORD is missing a value: 请设置 POSTGRES_PASSWORD; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — Not scored — this repository's 893 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 48 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (domains), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- 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 — polyglot repository, one half has no runner
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (13 domain event(s))
- 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
- 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 Go, JavaScript/TypeScript source (service entry point: REDACTED:25 (Fastify())
- 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 — coverage data present for 70 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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.
- 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 — 161 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Domain depends on infrastructure: login.handler backend-nodejs/domains/auth/handlers/login.handler.ts:5
- Domain depends on infrastructure: refresh_token.handler backend-nodejs/domains/auth/handlers/refresh_token.handler.ts:5
- Domain depends on infrastructure: register.handler backend-nodejs/domains/auth/handlers/register.handler.ts:6
- Domain depends on infrastructure: router REDACTED:6
- Domain depends on infrastructure: router REDACTED:7
- Domain depends on infrastructure: complete_task.handler backend-nodejs/domains/task/handlers/complete_task.handler.ts:5
- Domain depends on infrastructure: create_task.handler backend-nodejs/domains/task/handlers/create_task.handler.ts:6
- Domain depends on infrastructure: delete_task.handler backend-nodejs/domains/task/handlers/delete_task.handler.ts:5
- Domain depends on infrastructure: get_task.handler backend-nodejs/domains/task/handlers/get_task.handler.ts:5
- Domain depends on infrastructure: list_tasks.handler backend-nodejs/domains/task/handlers/list_tasks.handler.ts:5
- Domain depends on infrastructure: update_task.handler backend-nodejs/domains/task/handlers/update_task.handler.ts:5
- Domain depends on infrastructure: router backend-nodejs/domains/task/http/router.ts:6
- Domain depends on infrastructure: change_password.handler backend-nodejs/domains/user/handlers/change_password.handler.ts:5
- Domain depends on infrastructure: get_user_profile.handler backend-nodejs/domains/user/handlers/get_user_profile.handler.ts:6
- Domain depends on infrastructure: update_user_profile.handler backend-nodejs/domains/user/handlers/update_user_profile.handler.ts:5
- Domain depends on infrastructure: router backend-nodejs/domains/user/http/router.ts:6
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control frontend/web/src/features/task/components/TaskFilters.tsx:52
- <label> that labels no control frontend/web/src/features/task/components/TaskFilters.tsx:67
- <label> that labels no control frontend/web/src/features/task/components/TaskFilters.tsx:83
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Production project references a test package: go-genai-stack-backend-nodejs → @vitest/ui backend-nodejs/package.json:37
- Production project references a test package: go-genai-stack-backend-nodejs → supertest backend-nodejs/package.json:46
- Test suite declares a test script but contains no test files: frontend/shared/utils/
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 209 finding(s)
- No test reaches this file REDACTED:1
- No test reaches this file frontend/web/src/components/ui/calendar.tsx:1
- No test reaches this file frontend/web/src/components/ui/command.tsx:1
- No test reaches this file REDACTED:1
- No test reaches this file frontend/web/scripts/version.js:1
- No test reaches this file REDACTED:1
- No test reaches this file frontend/shared/utils/storage.ts:1
- No test reaches this file frontend/shared/constants/models.ts:1
- No test reaches this file frontend/web/src/components/ui/sheet.tsx:1
- No test reaches this file backend-nodejs/infrastructure/bootstrap/dependencies.ts:1
- No test reaches this file frontend/shared/constants/error-codes.ts:1
- No test reaches this file frontend/shared/utils/format.ts:1
- No test reaches this file frontend/shared/utils/validation.ts:1
- No test reaches this file backend-nodejs/infrastructure/persistence/redis/connection.ts:1
- No test reaches this file backend-nodejs/infrastructure/monitoring/health/health.ts:1
- No test reaches this file frontend/shared/constants/api-endpoints.ts:1
- No test reaches this file backend-nodejs/infrastructure/middleware/metrics.ts:1
- No test reaches this file frontend/web/src/components/ui/scroll-area.tsx:1
- No test reaches this file backend-nodejs/infrastructure/monitoring/metrics/metrics.ts:1
- No test reaches this file backend-nodejs/infrastructure/middleware/tracing.ts:1
- No test reaches this file frontend/web/src/hooks/use-theme.ts:1
- No test reaches this file frontend/web/src/components/ui/collapsible.tsx:1
- No test reaches this file frontend/mobile/App.tsx:1
- No test reaches this file frontend/mobile/index.ts:1
- 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
- Animation without a prefers-reduced-motion guard frontend/web/src/features/task/components/TaskList.tsx:27
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:107
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:113
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:127
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:131
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:135
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:139
- Animation without a prefers-reduced-motion guard frontend/web/src/index.css:143
- FunctionTooLong: ShowcasePage.ShowcasePage frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:86
- FunctionTooLong: TaskEditDialog.TaskEditDialog frontend/web/src/features/task/components/TaskEditDialog.tsx:46
- FunctionTooLong: TaskCreateDialog.TaskCreateDialog frontend/web/src/features/task/components/TaskCreateDialog.tsx:45
- FunctionTooLong: calendar.Calendar frontend/web/src/components/ui/calendar.tsx:8
- FunctionTooLong: HomePage.HomePage frontend/web/src/pages/HomePage/HomePage.tsx:17
- Duplicated block (12 lines × 2) backend/domains/auth/service/auth_service.go:192
- Duplicated block (12 lines × 2) backend/domains/user/repository/user_repo.go:79
- Duplicated block (12 lines × 2) backend/domains/auth/handlers/helpers.go:11
- Duplicated block (12 lines × 2) backend/infrastructure/persistence/mysql/provider.go:91
- Duplicated block (12 lines × 2) backend/domains/task/repository/task_repo.go:117
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) backend/domains/user/repository/user_repo.go:324
- Duplicated block (8 lines × 2) backend/infrastructure/persistence/mysql/provider.go:60
- Duplicated block (8 lines × 2) backend/domains/task/repository/task_repo.go:190
- Duplicated block (8 lines × 2) backend/domains/task/repository/task_repo.go:108
- Duplicated block (11 lines × 2 locations) backend-nodejs/domains/task/repository/task_repo.ts:69
- Duplicated block (11 lines × 2 locations) backend-nodejs/domains/task/repository/task_repo.ts:88
- Duplicated block (11 lines × 2 locations) backend-nodejs/domains/user/handlers/converters.ts:34
- Duplicated block (11 lines × 2 locations) frontend/web/src/features/task/hooks/useTasks.mutation.ts:84
- Swallowed exception (empty catch) frontend/web/src/pages/RegisterPage/RegisterPage.tsx:49
- Swallowed exception (empty catch) frontend/web/src/pages/LoginPage/LoginPage.tsx:47
- Swallowed exception (empty catch) REDACTED:87
- Swallowed exception (empty catch) backend-nodejs/domains/auth/service/auth_service.ts:147
- <Select> field component without a label frontend/web/src/features/task/components/TaskFilters.tsx:53
- <Select> field component without a label frontend/web/src/features/task/components/TaskFilters.tsx:68
- <Select> field component without a label frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:187
- Hotspot: frontend/web/src/features/task/components/TaskEditDialog.tsx frontend/web/src/features/task/components/TaskEditDialog.tsx:46
- Hotspot: frontend/web/src/features/task/components/TaskCreateDialog.tsx frontend/web/src/features/task/components/TaskCreateDialog.tsx:45
- Hotspot: frontend/web/src/lib/monitoring/sentry.ts frontend/web/src/lib/monitoring/sentry.ts:18
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2 locations) backend-nodejs/domains/user/repository/user_repo.ts:49
- Duplicated block (13 lines × 2 locations) frontend/web/src/features/task/hooks/useTasks.mutation.ts:41
- Duplicated block (13 lines × 2 locations) frontend/web/src/features/task/schemas/task.schema.ts:18
- Duplicated block (9 lines × 2 locations) backend-nodejs/domains/task/repository/task_repo.ts:191
- Duplicated block (9 lines × 2 locations) backend-nodejs/infrastructure/config/config.ts:76
- Duplicated block (9 lines × 2 locations) frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:461
- Focus outline removed inline frontend/web/src/components/ui/input.tsx:7
- Focus outline removed inline frontend/web/src/components/ui/textarea.tsx:7
- Duplicated block (13 lines × 2) backend/domains/auth/handlers/helpers.go:35
- Duplicated block (13 lines × 2) backend/domains/task/handlers/helpers.go:46
- Duplicated block (9 lines × 3) backend/domains/auth/service/auth_service.go:118
- Duplicated block (9 lines × 3) backend/infrastructure/persistence/postgres/transaction.go:38
- Off the main sequence: @go-genai-stack/constants
- Off the main sequence: @go-genai-stack/utils
- Fake-async — async method never awaits backend-nodejs/infrastructure/middleware/metrics.ts:14
- Fake-async — async method never awaits backend-nodejs/infrastructure/middleware/metrics.ts:26
- Duplicated block (13 lines × 4 locations) backend-nodejs/domains/task/service/task_service.ts:125
- Duplicated block (13 lines × 4 locations) frontend/web/src/components/ErrorBoundary.tsx:107
- Duplicated block with local edits (12 matched lines × 2 locations) backend-nodejs/domains/task/model/task.ts:85
- Duplicated block with local edits (12 matched lines × 2 locations) frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:110
- Duplicated block (11 lines × 3 locations) backend-nodejs/domains/task/handlers/complete_task.handler.ts:19
- Duplicated block (11 lines × 3 locations) frontend/web/src/pages/HomePage/HomePage.tsx:27
- Duplicated block (10 lines × 3 locations) backend-nodejs/domains/auth/handlers/login.handler.ts:19
- Duplicated block (10 lines × 3 locations) backend-nodejs/domains/task/repository/task_repo.ts:42
- <RadioGroup> field component without a label frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:214
- <Slider> field component without a label frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:229
- Page without a main landmark frontend/web/index.html:2
- Accessibility enforcement below the top rung frontend/package.json:46
- TaskEditDialog.TaskEditDialog (cyclomatic 19) frontend/web/src/features/task/components/TaskEditDialog.tsx:46
- TaskService.UpdateTask (cyclomatic 16) backend/domains/task/service/task_service.go:206
- TaskRepositoryImpl.list (cyclomatic 16) backend-nodejs/domains/task/repository/task_repo.ts:103
- TaskCreateDialog.TaskCreateDialog (cyclomatic 16) frontend/web/src/features/task/components/TaskCreateDialog.tsx:45
- TaskService.UpdateTask (cognitive 20) backend/domains/task/service/task_service.go:206
- Validator.validateMonitoring (cognitive 20) backend/infrastructure/config/validator.go:198
- TaskEditDialog.TaskEditDialog (cognitive 18) frontend/web/src/features/task/components/TaskEditDialog.tsx:46
- userRepository.Update (cognitive 17) backend/domains/user/repository/user_repo.go:242
- TaskRepositoryImpl.list (cognitive 17) backend-nodejs/domains/task/repository/task_repo.ts:103
- UserRepositoryImpl.update (cognitive 17) backend-nodejs/domains/user/repository/user_repo.ts:92
- sentry.initSentry (cognitive 17) frontend/web/src/lib/monitoring/sentry.ts:18
- config.loadRedisConfig (cognitive 16) backend/infrastructure/config/loader.go:153
- REDACTED
- REDACTED
- ClassTooLong: ShowcasePage frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:1
- FileTooLong: ShowcasePage/ShowcasePage.tsx frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx
- Members sharing a duplicated core (6 members, 50+ identical tokens) backend/domains/task/handlers/complete_task.handler.go:25
- Members sharing a duplicated core (4 members, 50+ identical tokens) backend/domains/task/service/task_service.go:206
- Duplicated block (40 lines × 3) backend/domains/user/repository/user_repo.go:104
- Duplicated block (27–29 lines × 2) backend/infrastructure/persistence/postgres/transaction.go:33
- Duplicated block (24 lines × 4) backend/domains/task/handlers/complete_task.handler.go:29
- Duplicated block (18–19 lines × 2) backend/domains/task/repository/task_repo.go:259
- Duplicated block (16 lines × 6) backend/domains/task/handlers/complete_task.handler.go:27
- Duplicated block (14 lines × 4) backend/domains/task/service/task_service.go:208
- Duplicated block (10 lines × 2) backend/domains/auth/service/jwt_service.go:81
- Duplicated block (7 lines × 2) backend/domains/auth/handlers/helpers.go:25
- Duplicated block (9 lines × 2) backend/domains/task/events/events.go:84
- CI formatting step cannot fail REDACTED:121
- Duplication concentrated across 2 sibling directories (8 clone groups) backend-nodejs/domains/task/model/task.ts:47
- Duplication concentrated across 4 sibling directories (5 clone groups) frontend/web/src/components/theme-provider.tsx:31
- Duplicated block with local edits (190 matched lines × 2 locations) frontend/web/src/features/task/components/TaskCreateDialog.tsx:75
- Duplicated block with local edits (114 matched lines × 2 locations) frontend/web/src/components/ui/dropdown-menu.tsx:7
- Duplicated block with local edits (72 matched lines × 2 locations) frontend/web/src/pages/LoginPage/LoginPage.tsx:37
- Duplicated block (43 lines × 2 locations) frontend/web/src/components/ui/dialog.tsx:68
- Duplicated block (31 lines × 2 locations) frontend/web/src/components/ui/dialog.tsx:7
- Duplicated block (21 lines × 2 locations) frontend/web/src/pages/HomePage/HomePage.tsx:79
- Duplicated block (19 lines × 2 locations) backend-nodejs/domains/task/http/router.ts:55
- Duplicated block (18 lines × 2 locations) backend-nodejs/domains/auth/service/jwt_service.ts:40
- Duplicated block (17 lines × 2 locations) frontend/web/src/components/theme-provider.tsx:31
- Duplicated block (14 lines × 10 locations) frontend/web/src/components/ui/alert.tsx:31
- Duplicated block (14 lines × 2 locations) frontend/web/src/components/ui/select.tsx:129
- Duplicated block (11 lines × 4 locations) frontend/web/src/components/ui/avatar.tsx:24
- Duplicated block (10 lines × 4 locations) backend-nodejs/domains/task/handlers/create_task.handler.ts:21
- Duplicated block (10 lines × 2 locations) frontend/web/src/features/auth/stores/auth.store.ts:68
- Duplicated block with local edits (9 matched lines × 2 locations) backend-nodejs/infrastructure/monitoring/health/health.ts:24
- Duplicated block (9 lines × 4 locations) frontend/web/src/features/task/components/TaskCreateDialog.tsx:176
- Duplicated block (8 lines × 2 locations) frontend/web/src/features/auth/stores/auth.store.ts:46
- Duplicated block (6 lines × 2 locations) backend-nodejs/domains/user/repository/user_repo.ts:147
- Duplicated block (5 lines × 3 locations) backend-nodejs/domains/task/handlers/create_task.handler.ts:30
- Complex function transform (cyclomatic 31, cognitive 58) frontend/web/plugins/removeTestId.js:18
- Complex function list (cyclomatic 15, cognitive 16) backend-nodejs/domains/task/repository/task_repo.ts:103
- Complex function update (cyclomatic 12, cognitive 17) backend-nodejs/domains/user/repository/user_repo.ts:92
- Complex function updateTask (cyclomatic 12, cognitive 12) backend-nodejs/domains/task/service/task_service.ts:131
- Complex function updateProfile (cyclomatic 11, cognitive 13) backend-nodejs/domains/user/model/user.ts:117
- Complex function createTask (cyclomatic 11, cognitive 11) backend-nodejs/domains/task/service/task_service.ts:87
- Complex function toListTasksInput (cyclomatic 11, cognitive 10) backend-nodejs/domains/task/handlers/converters.ts:200
- frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx: 581 lines of code frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:1
- Dead file (~178 LoC) frontend/web/src/components/ui/calendar.tsx
- Dead file (~161 LoC) frontend/web/src/components/ui/command.tsx
- Dead file (~156 LoC) REDACTED
- Dead file (~130 LoC) frontend/web/src/components/ui/sheet.tsx
- Dead file (~54 LoC) frontend/web/src/components/ui/scroll-area.tsx
- Dead file (~34 LoC) frontend/web/src/hooks/use-theme.ts
- Dead file (~25 LoC) frontend/web/src/features/task/index.ts
- Dead file (~21 LoC) frontend/web/src/components/ui/collapsible.tsx
- Dead file (~11 LoC) frontend/web/src/features/auth/index.ts
- Dead file (~10 LoC) frontend/web/src/features/user/index.ts
- Unused dependency '@fastify/rate-limit'
- Unused dependency 'pino-pretty'
- Unused dependency 'supertest'
- Swallowed exception (caught, then discarded) REDACTED:186
Minor — 171 finding(s)
- Orphaned file backend/domains/task/repository/task_repo.go:1
- Orphaned file backend/infrastructure/config/loader.go:1
- Orphaned file backend/domains/task/service/task_service.go:1
- Orphaned file backend/domains/user/repository/user_repo.go:1
- Orphaned file frontend/web/src/features/task/components/TaskEditDialog.tsx:1
- Orphaned file frontend/web/src/features/task/components/TaskCreateDialog.tsx:1
- Orphaned file backend/infrastructure/monitoring/metrics/metrics.go:1
- Orphaned file backend/infrastructure/monitoring/tracing/tracing.go:1
- Orphaned file backend-nodejs/domains/task/repository/task_repo.ts:1
- Orphaned file frontend/web/src/components/ui/dropdown-menu.tsx:1
- Orphaned file backend/infrastructure/monitoring/logger/logger.go:1
- Orphaned file backend/domains/auth/service/auth_service.go:1
- Orphaned file frontend/web/src/components/ui/calendar.tsx:1
- Orphaned file backend/domains/task/handlers/converters.go:1
- Orphaned file backend-nodejs/domains/task/service/task_service.ts:1
- Orphaned file backend/infrastructure/middleware/ratelimit.go:1
- Orphaned file backend/domains/user/model/user.go:1
- Orphaned file frontend/web/src/lib/monitoring/sentry.ts:1
- Orphaned file backend/domains/task/events/events.go:1
- Orphaned file backend/infrastructure/bootstrap/dependencies.go:1
- Orphaned file backend/domains/shared/events/types.go:1
- Orphaned file REDACTED:1
- Orphaned file frontend/web/src/components/ui/select.tsx:1
- Orphaned file frontend/web/src/components/ErrorBoundary.tsx:1
- Orphaned file backend/pkg/validator/validator.go:1
- README/code drift backend-nodejs/README.md:569
- README/code drift backend-nodejs/README.md:570
- README/code drift backend/README.md:617
- README/code drift backend/database/README.md:776
- README/code drift backend/database/README.md:777
- README/code drift backend/infrastructure/README.md:389
- README/code drift backend/infrastructure/README.md:390
- README/code drift backend/infrastructure/README.md:391
- README/code drift docker/frontend-debug/README.md:362
- README/code drift docker/frontend-debug/README.md:363
- README/code drift docker/frontend-debug/README.md:364
- README/code drift docker/frontend-debug/README.md:365
- README/code drift frontend/shared/README.md:255
- README/code drift frontend/shared/README.md:256
- README/code drift frontend/shared/README.md:257
- README/code drift backend-nodejs/domains/user/README.md:177
- README/code drift backend/infrastructure/bootstrap/README.md:341
- README/code drift backend/infrastructure/bootstrap/README.md:342
- README/code drift backend/infrastructure/bootstrap/README.md:343
- README/code drift frontend/shared/constants/README.md:85
- README/code drift frontend/shared/utils/README.md:92
- README/code drift frontend/web/doc/README.md:78
- README/code drift frontend/web/doc/README.md:82
- README/code drift frontend/web/doc/README.md:83
- README/code drift frontend/web/e2e/README.md:291
- Console output used as the logging channel backend-nodejs/infrastructure/persistence/redis/connection.ts:37
- Console output used as the logging channel backend-nodejs/infrastructure/persistence/redis/connection.ts:79
- Console output used as the logging channel backend-nodejs/infrastructure/persistence/redis/connection.ts:93
- Console output used as the logging channel backend-nodejs/infrastructure/persistence/postgres/connection.ts:44
- Console output used as the logging channel backend-nodejs/infrastructure/monitoring/health/health.ts:35
- Console output used as the logging channel backend-nodejs/infrastructure/monitoring/health/health.ts:51
- Console output used as the logging channel backend-nodejs/infrastructure/config/config.ts:146
- Console output used as the logging channel backend-nodejs/infrastructure/config/config.ts:149
- Console output used as the logging channel backend-nodejs/infrastructure/config/config.ts:151
- redundant comment backend-nodejs/domains/auth/service/auth_service.test.ts:13
- redundant comment REDACTED:116
- redundant comment frontend/web/src/features/auth/__tests__/stores/auth.store.test.ts:152
- Primitive id on a domain type: Task.ID backend/domains/task/model/task.go:55
- Primitive id on a domain type: Task.UserID backend/domains/task/model/task.go:56
- Primitive id on a domain type: User.ID backend/domains/user/model/user.go:34
- Mock-dominated test: 应该成功创建任务 frontend/web/src/features/task/__tests__/components/TaskCreateDialog.test.tsx:83
- Mock-dominated test: 应该成功更新任务 frontend/web/src/features/task/__tests__/components/TaskEditDialog.test.tsx:85
- REDACTED
- REDACTED
- Mutable entity: Task backend/domains/task/model/task.go:54
- Mutable entity: User backend/domains/user/model/user.go:33
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Dormant codebase
- Most significant orphaned file frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:1
- Placeholder literal left in code frontend/web/src/pages/ShowcasePage/ShowcasePage.tsx:137
- No ADRs
- No tests/ separation
- No release approval gate
- Unused export 'TaskParams' backend-nodejs/domains/task/http/dto/task.ts:58
- Unused export 'ErrorResponse' backend-nodejs/domains/task/http/dto/task.ts:137
- Unused export 'createOptionalAuthMiddleware' REDACTED:72
- Unused export 'getUserId' REDACTED:97
- Unused export 'createApiRateLimitMiddleware' backend-nodejs/infrastructure/middleware/ratelimit.ts:134
- Unused export 'dbQueryDuration' backend-nodejs/infrastructure/monitoring/metrics/metrics.ts:34
- Unused export 'dbQueryCounter' backend-nodejs/infrastructure/monitoring/metrics/metrics.ts:43
- Unused export 'testConnection' backend-nodejs/infrastructure/persistence/postgres/connection.ts:39
- Unused export 'withReadOnlyTransaction' backend-nodejs/infrastructure/persistence/postgres/transaction.ts:60
- Unused export 'fromErrorMessage' backend-nodejs/shared/errors/errors.ts:158
- Unused export 'createEmptyContext' backend-nodejs/shared/types/context.ts:40
- Unused export 'H4' frontend/web/src/components/typography.tsx:38
- Unused export 'Blockquote' frontend/web/src/components/typography.tsx:50
- Unused export 'Large' frontend/web/src/components/typography.tsx:73
- Unused export 'Small' frontend/web/src/components/typography.tsx:77
- Unused export 'useTaskQuery' frontend/web/src/features/task/hooks/useTasks.query.ts:54
- Unused export 'APIResponse' frontend/web/src/lib/api-client.ts:78
- Unused export 'default' frontend/web/src/lib/api-client.ts:106
- Unused export 'setTag' frontend/web/src/lib/monitoring/sentry.ts:205
- Unused export 'setContext' frontend/web/src/lib/monitoring/sentry.ts:214
- Unused export 'captureMessage' frontend/web/src/lib/monitoring/sentry.ts:241
- Unused export 'addBreadcrumb' frontend/web/src/lib/monitoring/sentry.ts:250
- Null assertions (`!`) reduce the strict null checking score
Minor — 17 finding(s)
- Outdated: github.com/cloudwego/hertz
- Outdated: github.com/doug-martin/goqu/v9
- Outdated: github.com/go-playground/validator/v10
- Outdated: github.com/go-sql-driver/mysql
- Outdated: github.com/golang-jwt/jwt/v5
- Outdated: github.com/lib/pq
- Outdated: github.com/prometheus/client_golang
- Outdated: github.com/redis/go-redis/v9
- Outdated: github.com/stretchr/testify
- Outdated: go.opentelemetry.io/otel
- Outdated: go.opentelemetry.io/otel/exporters/otlp/otlptrace
- Outdated: go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
- Outdated: go.opentelemetry.io/otel/exporters/stdout/stdouttrace
- Outdated: go.opentelemetry.io/otel/sdk
- Outdated: go.opentelemetry.io/otel/trace
- Outdated: go.uber.org/zap
- Outdated: golang.org/x/crypto
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-dbec67f5e89d427098ac3b190a55b17e/history.json --exit-code 0 --source . | 7 | 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-dbec67f5e89d427098ac3b190a55b17e/tree.json --exit-code 0 --source . | 3 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude frontend/shared/types/domains . | 56 | 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 | 88 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 19 | 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 |