Executive summary
DGouron/review-flow is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has buttons or links with no name. It scores 52 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 45, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 5 points. Adding automated security scanning comes next, worth about 3 points. Raising Accessibility to 70 would lift the score to about 57.
Seventeen known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and seven buttons or links have no name a screen reader can say. Updating the vulnerable packages, pinning each tool to an exact version and naming the buttons and links would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed, and the password or key in the code's history needs replacing, with the old one switched off. The three form fields without a label need a label.
The product code is 43,354 lines, about €120,000 to rebuild.
If Accessibility rose from 45 to 70, the lowest score rated Strong, the score would rise from 52 to about 57.
New since the last survey: 21 findings
- Cyclomatic Complexity · addAction.handler.createAddActionHandler.<returned closure> (cyclomatic 17) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Exception handling · Swallowed exception (empty catch) src/shared/services/claudePathResolver.ts
- Exception handling · Swallowed exception (empty catch) src/shared/services/claudePathResolver.ts
- Exception handling · Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts
- Exception handling · Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts
- Exception handling · Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts
- Exception handling · Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts
- Exception handling · Swallowed exception (empty catch) src/mcp/mcpLogger.ts
- Exception handling · Swallowed exception (empty catch) src/mcp/mcpLogger.ts
- Exception handling · Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts
- Exception handling · Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts
- Keyboard semantics · Click handler on a non-interactive <dialog> REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (1.7:1) src/dashboard/styles.css
- Visual & motion safety · Low contrast colour pair in CSS (2.4:1) docs/.vitepress/theme/components/QuickStart.vue
Fixed since the last survey: 112 findings
- Cyclomatic Complexity · addAction.handler.createAddActionHandler (cyclomatic 17) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Code Duplication · Duplicated block (15 lines × 4 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.github.gateway.ts
- Code Duplication · Duplicated block (15 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts
- Code Duplication · Duplicated block (15 lines × 4 locations) REDACTED
- Code Duplication · Duplicated block (14 lines × 2 locations) src/dashboard/modules/emberAvatar.js
- Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) src/frameworks/config/configLoader.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts
- Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (13 lines × 2 locations) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) src/modules/platform-integration/entities/gitlab/gitlabMergeRequestEvent.guard.ts
- Code Duplication · Duplicated block (13 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) src/modules/setup-wizard/services/jsonWizardEventEmitter.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) src/dashboard/modules/emberChat.js
- Code Duplication · Duplicated block (12 lines × 2 locations) src/main/commands/discover.command.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (12 lines × 3 locations) REDACTED
- Code Duplication · Duplicated block (12 lines × 2 locations) src/modules/platform-integration/interface-adapters/gateways/egressScanned.noteCommentPost.gateway.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) src/modules/platform-integration/usecases/processWebhook.usecase.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) src/modules/review-execution/usecases/confirmPendingReview.usecase.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) src/modules/review-execution/usecases/mcp/completeAgent.usecase.ts
- Code Duplication · Duplicated block (12 lines × 2 locations) src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/dashboard/modules/statsCharts.js
- Code Duplication · Duplicated block (11 lines × 3 locations) src/frameworks/settings/runtimeSettings.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/cli-configuration/interface-adapters/gateways/sourceCheckoutUpdate.cli.gateway.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/ember-chat/interface-adapters/gateways/emberAnswerTransport.claude.gateway.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) src/modules/platform-integration/interface-adapters/gateways/cli/noteCommentPost.github.cli.gateway.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/platform-integration/usecases/markReviewDone.usecase.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/statistics-insights/entities/insight/persistedInsightsData.schema.ts
- Code Duplication · Duplicated block (11 lines × 3 locations) REDACTED
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/statistics-insights/interface-adapters/gateways/fileSystem/insights.fileSystem.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts
- Code Duplication · Duplicated block (11 lines × 2 locations) src/modules/tracking/usecases/tracking/recordBypass.usecase.ts
- Code Duplication · Duplicated block (10 lines × 3 locations) src/dashboard/modules/budgetSettings.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/dashboard/modules/developerSheet.js
- Code Duplication · Duplicated block (10 lines × 2 locations) src/dashboard/modules/statsCharts.js
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) src/frameworks/scheduler/cleanupScheduler.ts
- Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (10 lines × 2 locations) src/modules/ember-chat/services/emberSystemPrompt.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts
- Code Duplication · Duplicated block (10 lines × 2 locations) src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts
- Code Duplication · Duplicated block (9 lines × 3 locations) src/config/projectConfig.ts
- Code Duplication · Duplicated block (9 lines × 3 locations) src/dashboard/modules/budgetSettings.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/dashboard/modules/overview.js
- Code Duplication · Duplicated block (9 lines × 2 locations) src/dashboard/modules/settingsModal.js
- Code Duplication · Duplicated block (9 lines × 4 locations) src/dashboard/modules/statsCharts.js
- Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) src/frameworks/claude/progressParser.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/frameworks/config/configLoader.ts
- Code Duplication · Duplicated block (9 lines × 3 locations) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/modules/cli-configuration/usecases/cli/queryStatus.usecase.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts
- Code Duplication · Duplicated block (9 lines × 4 locations) src/modules/platform-integration/usecases/clearReviewInProgress.usecase.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/modules/review-execution/entities/reviewContext/reviewContext.schema.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts
- Code Duplication · Duplicated block (9 lines × 2 locations) src/modules/setup-wizard/interface-adapters/gateways/prompt.stdinJson.gateway.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/dashboard/modules/budgetSettings.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/dashboard/modules/developerSheet.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/dashboard/modules/statsCharts.js
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/claude-invocation/usecases/cleanupClaudeSession.usecase.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/platform-integration/entities/github/githubIssueCommentEvent.guard.ts
- Code Duplication · Duplicated block (8 lines × 3 locations) src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.github.gateway.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) src/modules/setup-wizard/usecases/steps/registerProject.step.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/statistics-insights/interface-adapters/gateways/fileSystem/stats.fileSystem.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/tracking/interface-adapters/gateways/fileSystem/reviewRequestTracking.fileSystem.ts
- Code Duplication · Duplicated block (8 lines × 3 locations) src/modules/tracking/usecases/tracking/handlePlatformApproval.usecase.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/modules/worktree-management/usecases/ensureWorktree.usecase.ts
- Code Duplication · Duplicated block (8 lines × 2 locations) src/shared/foundation/guard.base.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/modules/platform-integration/interface-adapters/gateways/cli/noteCommentPost.gitlab.cli.gateway.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (7 lines × 2 locations) src/modules/setup-wizard/interface-adapters/gateways/prompt.tty.gateway.ts
- Code Duplication · Duplicated block (7 lines × 2 locations) src/modules/statistics-insights/entities/insight/aiInsight.schema.ts
- Code Duplication · Duplicated block (6 lines × 3 locations) src/modules/ember-chat/interface-adapters/controllers/mcp/recordInsight.handler.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (6 lines × 2 locations) src/modules/review-execution/interface-adapters/gateways/reviewContext.fileSystem.gateway.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) src/modules/review-execution/interface-adapters/gateways/reviewProgress.memory.gateway.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) src/modules/review-execution/usecases/executeReview.usecase.ts
- Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) src/modules/setup-wizard/services/humanWizardEventEmitter.ts
- Code Duplication · Duplicated block (6 lines × 2 locations) src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) src/modules/cli-configuration/usecases/cli/validateConfig.usecase.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) src/modules/review-execution/entities/job/jobRecord.schema.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) src/modules/statistics-insights/entities/insight/persistedInsightsData.schema.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) src/modules/statistics-insights/usecases/insights/buildAiInsightsPrompt.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts
- Test Coverage · No test reaches this file scripts/copyAssets.mjs
- Access Controls · No authorization src/main/server.ts
- Exception handling · Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts
- Exception handling · Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts
- Exception handling · Swallowed exception (empty catch) src/mcp/mcpLogger.ts
- Exception handling · Swallowed exception (empty catch) src/mcp/mcpLogger.ts
- Exception handling · Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts
Rebuild cost: about €120,000 · Estimate
| Cost to rebuild | €40,000 to €200,000, for 662 to 2,099 hours of work, about 0.8 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. 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: 43,354 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 modules.claude-invocation.entities.billingState.environment_gateway | 2 modules.claude-invocation.entities.claudeSession.claudeSession_gateway | 3 modules.claude-invocation.usecases | 4 modules.cli-configuration.entities.projectConfig.projectConfig_gateway | 5 modules.cli-configuration.interface-adapters.controllers.http.version_routes | 6 modules.ember-chat.entities.emberMemory.emberMemory_gateway | 7 modules.platform-integration.entities.noteComment.noteCommentPost_gateway | 8 modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway | 9 modules.review-execution.entities.progress.progress_type | 10 modules.review-execution.entities.review.reviewFile_gateway | 11 modules.review-execution.entities.reviewContext.reviewContext | 12 modules.review-execution.services.contextActionsExecutor | 13 modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway | 14 modules.tracking.entities.tracking.mrTrackingData | 15 modules.tracking.entities.tracking.trackedMr | 16 modules.worktree-management.entities.gitCommand.gitCommand_gateway | 17 modules.worktree-management.entities.worktree.worktree_schema | 18 shared.foundation.usecase_base | 19 modules.review-execution.entities.job.reviewJob | 20 modules.review-execution.entities.progress.progress_gateway | 21 modules.review-execution.entities.reviewContext.reviewContext_gateway | 22 modules.setup-wizard.entities.wizardContext.wizardContext | 23 modules.statistics-insights.entities.stats.stats_gateway | 24 modules.tracking.entities.tracking.reviewRequestTracking_gateway | 25 modules.worktree-management.usecases | 26 frameworks.claude.claudeInvoker | 27 main.commands | 28 modules.review-execution.services | 29 modules.review-execution.usecases.executeReview_usecase | 30 modules.review-execution.usecases.gateClaudeInvocation_usecase | 31 modules.review-execution.usecases.mcp | 32 modules.setup-wizard.entities.setupStep.setupStep | 33 main.dependencies | 34 main.executeReviewWiring | 35 modules.platform-integration.interface-adapters.controllers.webhook.github_controller | 36 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller | 37 modules.review-execution.usecases | 38 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes | 39 main | 40 modules.platform-integration.interface-adapters.controllers.webhook |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 modules.claude-invocation.entities.billingState.environment_gateway | ||||||||||||||||||||||||||||||||||||||||
| 2 modules.claude-invocation.entities.claudeSession.claudeSession_gateway | ||||||||||||||||||||||||||||||||||||||||
| 3 modules.claude-invocation.usecases | ||||||||||||||||||||||||||||||||||||||||
| 4 modules.cli-configuration.entities.projectConfig.projectConfig_gateway | ||||||||||||||||||||||||||||||||||||||||
| 5 modules.cli-configuration.interface-adapters.controllers.http.version_routes | ||||||||||||||||||||||||||||||||||||||||
| 6 modules.ember-chat.entities.emberMemory.emberMemory_gateway | ||||||||||||||||||||||||||||||||||||||||
| 7 modules.platform-integration.entities.noteComment.noteCommentPost_gateway | ||||||||||||||||||||||||||||||||||||||||
| 8 modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway | ||||||||||||||||||||||||||||||||||||||||
| 9 modules.review-execution.entities.progress.progress_type | ||||||||||||||||||||||||||||||||||||||||
| 10 modules.review-execution.entities.review.reviewFile_gateway | ||||||||||||||||||||||||||||||||||||||||
| 11 modules.review-execution.entities.reviewContext.reviewContext | ||||||||||||||||||||||||||||||||||||||||
| 12 modules.review-execution.services.contextActionsExecutor | ||||||||||||||||||||||||||||||||||||||||
| 13 modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway | ||||||||||||||||||||||||||||||||||||||||
| 14 modules.tracking.entities.tracking.mrTrackingData | ||||||||||||||||||||||||||||||||||||||||
| 15 modules.tracking.entities.tracking.trackedMr | ||||||||||||||||||||||||||||||||||||||||
| 16 modules.worktree-management.entities.gitCommand.gitCommand_gateway | ||||||||||||||||||||||||||||||||||||||||
| 17 modules.worktree-management.entities.worktree.worktree_schema | ||||||||||||||||||||||||||||||||||||||||
| 18 shared.foundation.usecase_base | ||||||||||||||||||||||||||||||||||||||||
| 19 modules.review-execution.entities.job.reviewJob | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 modules.review-execution.entities.progress.progress_gateway | 2 | |||||||||||||||||||||||||||||||||||||||
| 21 modules.review-execution.entities.reviewContext.reviewContext_gateway | 4 | |||||||||||||||||||||||||||||||||||||||
| 22 modules.setup-wizard.entities.wizardContext.wizardContext | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 modules.statistics-insights.entities.stats.stats_gateway | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 modules.tracking.entities.tracking.reviewRequestTracking_gateway | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 modules.worktree-management.usecases | 1 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 26 frameworks.claude.claudeInvoker | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 27 main.commands | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 modules.review-execution.services | 1 | 2 | 3 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 29 modules.review-execution.usecases.executeReview_usecase | 1 | 1 | 1 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 30 modules.review-execution.usecases.gateClaudeInvocation_usecase | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 modules.review-execution.usecases.mcp | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 modules.setup-wizard.entities.setupStep.setupStep | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 main.dependencies | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 34 main.executeReviewWiring | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 modules.platform-integration.interface-adapters.controllers.webhook.github_controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 37 modules.review-execution.usecases | 1 | 1 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||||
| 38 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 39 main | 3 | 2 | 1 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 40 modules.platform-integration.interface-adapters.controllers.webhook | 2 | 2 | 2 | 1 | 1 |
19→9 modules.review-execution.entities.job.reviewJob uses modules.review-execution.entities.progress.progress_type✕
- Connections
- 1 pair of types, where a type in modules.review-execution.entities.job.reviewJob uses a type in modules.review-execution.entities.progress.progress_type.
- The types involved
src.modules.review-execution.entities.job.reviewJob.JobStatus→src.modules.review-execution.entities.progress.progress_type.ReviewProgress
- Direction
- modules.review-execution.entities.job.reviewJob uses modules.review-execution.entities.progress.progress_type, so a change to modules.review-execution.entities.progress.progress_type can break modules.review-execution.entities.job.reviewJob, while a change to modules.review-execution.entities.job.reviewJob can't break modules.review-execution.entities.progress.progress_type.
- Position
- Below the diagonal: modules.review-execution.entities.job.reviewJob uses a module listed above it, which is the healthy direction.
20→9 modules.review-execution.entities.progress.progress_gateway uses modules.review-execution.entities.progress.progress_type✕
- Connections
- 2 pairs of types, where a type in modules.review-execution.entities.progress.progress_gateway uses a type in modules.review-execution.entities.progress.progress_type.
- The types involved
src.modules.review-execution.entities.progress.progress_gateway.ReviewProgressGateway→src.modules.review-execution.entities.progress.progress_type.ReviewPhasesrc.modules.review-execution.entities.progress.progress_gateway.ReviewProgressGateway→src.modules.review-execution.entities.progress.progress_type.ReviewProgress
- Direction
- modules.review-execution.entities.progress.progress_gateway uses modules.review-execution.entities.progress.progress_type, so a change to modules.review-execution.entities.progress.progress_type can break modules.review-execution.entities.progress.progress_gateway, while a change to modules.review-execution.entities.progress.progress_gateway can't break modules.review-execution.entities.progress.progress_type.
- Position
- Below the diagonal: modules.review-execution.entities.progress.progress_gateway uses a module listed above it, which is the healthy direction.
21→11 modules.review-execution.entities.reviewContext.reviewContext_gateway uses modules.review-execution.entities.reviewContext.reviewContext✕
- Connections
- 4 pairs of types, where a type in modules.review-execution.entities.reviewContext.reviewContext_gateway uses a type in modules.review-execution.entities.reviewContext.reviewContext.
- The types involved
src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway→src.modules.review-execution.entities.reviewContext.reviewContext.CreateReviewContextInputsrc.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway→src.modules.review-execution.entities.reviewContext.reviewContext.CreateReviewContextResultsrc.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway→src.modules.review-execution.entities.reviewContext.reviewContext.DeleteReviewContextResultsrc.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway→src.modules.review-execution.entities.reviewContext.reviewContext.ReviewContextProgress
- Direction
- modules.review-execution.entities.reviewContext.reviewContext_gateway uses modules.review-execution.entities.reviewContext.reviewContext, so a change to modules.review-execution.entities.reviewContext.reviewContext can break modules.review-execution.entities.reviewContext.reviewContext_gateway, while a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can't break modules.review-execution.entities.reviewContext.reviewContext.
- Position
- Below the diagonal: modules.review-execution.entities.reviewContext.reviewContext_gateway uses a module listed above it, which is the healthy direction.
22→4 modules.setup-wizard.entities.wizardContext.wizardContext uses modules.cli-configuration.entities.projectConfig.projectConfig_gateway✕
- Connections
- 1 pair of types, where a type in modules.setup-wizard.entities.wizardContext.wizardContext uses a type in modules.cli-configuration.entities.projectConfig.projectConfig_gateway.
- The types involved
src.modules.setup-wizard.entities.wizardContext.wizardContext.WizardGateways→src.modules.cli-configuration.entities.projectConfig.projectConfig_gateway.ProjectConfigGateway
- Direction
- modules.setup-wizard.entities.wizardContext.wizardContext uses modules.cli-configuration.entities.projectConfig.projectConfig_gateway, so a change to modules.cli-configuration.entities.projectConfig.projectConfig_gateway can break modules.setup-wizard.entities.wizardContext.wizardContext, while a change to modules.setup-wizard.entities.wizardContext.wizardContext can't break modules.cli-configuration.entities.projectConfig.projectConfig_gateway.
- Position
- Below the diagonal: modules.setup-wizard.entities.wizardContext.wizardContext uses a module listed above it, which is the healthy direction.
23→14 modules.statistics-insights.entities.stats.stats_gateway uses modules.tracking.entities.tracking.mrTrackingData✕
- Connections
- 1 pair of types, where a type in modules.statistics-insights.entities.stats.stats_gateway uses a type in modules.tracking.entities.tracking.mrTrackingData.
- The types involved
src.modules.statistics-insights.entities.stats.stats_gateway.StatsGateway→src.modules.tracking.entities.tracking.mrTrackingData.ProjectStats
- Direction
- modules.statistics-insights.entities.stats.stats_gateway uses modules.tracking.entities.tracking.mrTrackingData, so a change to modules.tracking.entities.tracking.mrTrackingData can break modules.statistics-insights.entities.stats.stats_gateway, while a change to modules.statistics-insights.entities.stats.stats_gateway can't break modules.tracking.entities.tracking.mrTrackingData.
- Position
- Below the diagonal: modules.statistics-insights.entities.stats.stats_gateway uses a module listed above it, which is the healthy direction.
24→14 modules.tracking.entities.tracking.reviewRequestTracking_gateway uses modules.tracking.entities.tracking.mrTrackingData✕
- Connections
- 1 pair of types, where a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway uses a type in modules.tracking.entities.tracking.mrTrackingData.
- The types involved
src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.ReviewRequestTrackingGateway→src.modules.tracking.entities.tracking.mrTrackingData.MrTrackingData
- Direction
- modules.tracking.entities.tracking.reviewRequestTracking_gateway uses modules.tracking.entities.tracking.mrTrackingData, so a change to modules.tracking.entities.tracking.mrTrackingData can break modules.tracking.entities.tracking.reviewRequestTracking_gateway, while a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can't break modules.tracking.entities.tracking.mrTrackingData.
- Position
- Below the diagonal: modules.tracking.entities.tracking.reviewRequestTracking_gateway uses a module listed above it, which is the healthy direction.
24→15 modules.tracking.entities.tracking.reviewRequestTracking_gateway uses modules.tracking.entities.tracking.trackedMr✕
- Connections
- 1 pair of types, where a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway uses a type in modules.tracking.entities.tracking.trackedMr.
- The types involved
src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.ReviewRequestTrackingGateway→src.modules.tracking.entities.tracking.trackedMr.TrackedMr
- Direction
- modules.tracking.entities.tracking.reviewRequestTracking_gateway uses modules.tracking.entities.tracking.trackedMr, so a change to modules.tracking.entities.tracking.trackedMr can break modules.tracking.entities.tracking.reviewRequestTracking_gateway, while a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can't break modules.tracking.entities.tracking.trackedMr.
- Position
- Below the diagonal: modules.tracking.entities.tracking.reviewRequestTracking_gateway uses a module listed above it, which is the healthy direction.
25→15 modules.worktree-management.usecases uses modules.tracking.entities.tracking.trackedMr✕
- Connections
- 1 pair of types, where a type in modules.worktree-management.usecases uses a type in modules.tracking.entities.tracking.trackedMr.
- The types involved
src.modules.worktree-management.usecases.sweepStaleWorktrees.usecase→src.modules.tracking.entities.tracking.trackedMr.TrackedMr
- Direction
- modules.worktree-management.usecases uses modules.tracking.entities.tracking.trackedMr, so a change to modules.tracking.entities.tracking.trackedMr can break modules.worktree-management.usecases, while a change to modules.worktree-management.usecases can't break modules.tracking.entities.tracking.trackedMr.
- Position
- Below the diagonal: modules.worktree-management.usecases uses a module listed above it, which is the healthy direction.
25→16 modules.worktree-management.usecases uses modules.worktree-management.entities.gitCommand.gitCommand_gateway✕
- Connections
- 2 pairs of types, where a type in modules.worktree-management.usecases uses a type in modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- The types involved
src.modules.worktree-management.usecases.ensureWorktree.usecase→src.modules.worktree-management.entities.gitCommand.gitCommand_gateway.GitCommandExecutorsrc.modules.worktree-management.usecases.ensureWorktree.usecase→src.modules.worktree-management.entities.gitCommand.gitCommand_gateway.GitCommandResult
- Direction
- modules.worktree-management.usecases uses modules.worktree-management.entities.gitCommand.gitCommand_gateway, so a change to modules.worktree-management.entities.gitCommand.gitCommand_gateway can break modules.worktree-management.usecases, while a change to modules.worktree-management.usecases can't break modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- Position
- Below the diagonal: modules.worktree-management.usecases uses a module listed above it, which is the healthy direction.
25→17 modules.worktree-management.usecases uses modules.worktree-management.entities.worktree.worktree_schema✕
- Connections
- 4 pairs of types, where a type in modules.worktree-management.usecases uses a type in modules.worktree-management.entities.worktree.worktree_schema.
- The types involved
src.modules.worktree-management.usecases.ensureWorktree.usecase→src.modules.worktree-management.entities.worktree.worktree_schema.EnsureResultsrc.modules.worktree-management.usecases.ensureWorktree.usecase→src.modules.worktree-management.entities.worktree.worktree_schema.WorktreePathsrc.modules.worktree-management.usecases.removeWorktree.usecase→src.modules.worktree-management.entities.worktree.worktree_schema.RemoveResultsrc.modules.worktree-management.usecases.sweepStaleWorktrees.usecase→src.modules.worktree-management.entities.worktree.worktree_schema.WorktreeEntry
- Direction
- modules.worktree-management.usecases uses modules.worktree-management.entities.worktree.worktree_schema, so a change to modules.worktree-management.entities.worktree.worktree_schema can break modules.worktree-management.usecases, while a change to modules.worktree-management.usecases can't break modules.worktree-management.entities.worktree.worktree_schema.
- Position
- Below the diagonal: modules.worktree-management.usecases uses a module listed above it, which is the healthy direction.
26→1 frameworks.claude.claudeInvoker uses modules.claude-invocation.entities.billingState.environment_gateway✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.claude-invocation.entities.billingState.environment_gateway.
- The types involved
src.frameworks.claude.claudeInvoker.ClaudeInvocationDeps→src.modules.claude-invocation.entities.billingState.environment_gateway.EnvironmentGateway
- Direction
- frameworks.claude.claudeInvoker uses modules.claude-invocation.entities.billingState.environment_gateway, so a change to modules.claude-invocation.entities.billingState.environment_gateway can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.claude-invocation.entities.billingState.environment_gateway.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
26→2 frameworks.claude.claudeInvoker uses modules.claude-invocation.entities.claudeSession.claudeSession_gateway✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.claude-invocation.entities.claudeSession.claudeSession_gateway.
- The types involved
src.frameworks.claude.claudeInvoker.ClaudeInvocationDeps→src.modules.claude-invocation.entities.claudeSession.claudeSession_gateway.ClaudeSessionGateway
- Direction
- frameworks.claude.claudeInvoker uses modules.claude-invocation.entities.claudeSession.claudeSession_gateway, so a change to modules.claude-invocation.entities.claudeSession.claudeSession_gateway can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.claude-invocation.entities.claudeSession.claudeSession_gateway.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
26→9 frameworks.claude.claudeInvoker uses modules.review-execution.entities.progress.progress_type✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.review-execution.entities.progress.progress_type.
- The types involved
src.frameworks.claude.claudeInvoker.InvocationResult→src.modules.review-execution.entities.progress.progress_type.ReviewProgress
- Direction
- frameworks.claude.claudeInvoker uses modules.review-execution.entities.progress.progress_type, so a change to modules.review-execution.entities.progress.progress_type can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.review-execution.entities.progress.progress_type.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
26→16 frameworks.claude.claudeInvoker uses modules.worktree-management.entities.gitCommand.gitCommand_gateway✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- The types involved
src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies→src.modules.worktree-management.entities.gitCommand.gitCommand_gateway.GitCommandExecutor
- Direction
- frameworks.claude.claudeInvoker uses modules.worktree-management.entities.gitCommand.gitCommand_gateway, so a change to modules.worktree-management.entities.gitCommand.gitCommand_gateway can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
26→19 frameworks.claude.claudeInvoker uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.frameworks.claude.claudeInvoker.BackgroundDispatchContext→src.modules.review-execution.entities.job.reviewJob.ReviewJob
- Direction
- frameworks.claude.claudeInvoker uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
26→23 frameworks.claude.claudeInvoker uses modules.statistics-insights.entities.stats.stats_gateway✕
- Connections
- 1 pair of types, where a type in frameworks.claude.claudeInvoker uses a type in modules.statistics-insights.entities.stats.stats_gateway.
- The types involved
src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies→src.modules.statistics-insights.entities.stats.stats_gateway.StatsGateway
- Direction
- frameworks.claude.claudeInvoker uses modules.statistics-insights.entities.stats.stats_gateway, so a change to modules.statistics-insights.entities.stats.stats_gateway can break frameworks.claude.claudeInvoker, while a change to frameworks.claude.claudeInvoker can't break modules.statistics-insights.entities.stats.stats_gateway.
- Position
- Below the diagonal: frameworks.claude.claudeInvoker uses a module listed above it, which is the healthy direction.
27→22 main.commands uses modules.setup-wizard.entities.wizardContext.wizardContext✕
- Connections
- 1 pair of types, where a type in main.commands uses a type in modules.setup-wizard.entities.wizardContext.wizardContext.
- The types involved
src.main.commands.setup.command→src.modules.setup-wizard.entities.wizardContext.wizardContext.WizardContext
- Direction
- main.commands uses modules.setup-wizard.entities.wizardContext.wizardContext, so a change to modules.setup-wizard.entities.wizardContext.wizardContext can break main.commands, while a change to main.commands can't break modules.setup-wizard.entities.wizardContext.wizardContext.
- Position
- Below the diagonal: main.commands uses a module listed above it, which is the healthy direction.
28→7 modules.review-execution.services uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.services uses a type in modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- The types involved
src.modules.review-execution.services.publicOutputExecutor→src.modules.platform-integration.entities.noteComment.noteCommentPost_gateway.NoteCommentPostGateway
- Direction
- modules.review-execution.services uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway, so a change to modules.platform-integration.entities.noteComment.noteCommentPost_gateway can break modules.review-execution.services, while a change to modules.review-execution.services can't break modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- Position
- Below the diagonal: modules.review-execution.services uses a module listed above it, which is the healthy direction.
28→8 modules.review-execution.services uses modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway✕
- Connections
- 2 pairs of types, where a type in modules.review-execution.services uses a type in modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.
- The types involved
src.modules.review-execution.services.contextActionsExecutor→src.modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.CommandExecutorsrc.modules.review-execution.services.threadActionsExecutor→src.modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.CommandExecutor
- Direction
- modules.review-execution.services uses modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway, so a change to modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway can break modules.review-execution.services, while a change to modules.review-execution.services can't break modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.
- Position
- Below the diagonal: modules.review-execution.services uses a module listed above it, which is the healthy direction.
28→11 modules.review-execution.services uses modules.review-execution.entities.reviewContext.reviewContext✕
- Connections
- 3 pairs of types, where a type in modules.review-execution.services uses a type in modules.review-execution.entities.reviewContext.reviewContext.
- The types involved
src.modules.review-execution.services.agentInstructionsBuilder→src.modules.review-execution.entities.reviewContext.reviewContext.AgentInstructionssrc.modules.review-execution.services.contextActionsExecutor→src.modules.review-execution.entities.reviewContext.reviewContext.ReviewContextsrc.modules.review-execution.services.reviewRecovery.service→src.modules.review-execution.entities.reviewContext.reviewContext.ReviewContext
- Direction
- modules.review-execution.services uses modules.review-execution.entities.reviewContext.reviewContext, so a change to modules.review-execution.entities.reviewContext.reviewContext can break modules.review-execution.services, while a change to modules.review-execution.services can't break modules.review-execution.entities.reviewContext.reviewContext.
- Position
- Below the diagonal: modules.review-execution.services uses a module listed above it, which is the healthy direction.
28→12 modules.review-execution.services uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 2 pairs of types, where a type in modules.review-execution.services uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.review-execution.services.contextActionsExecutor→src.modules.review-execution.services.contextActionsExecutor.Loggersrc.modules.review-execution.services.threadActionsExecutor→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.review-execution.services uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.review-execution.services, while a change to modules.review-execution.services can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.review-execution.services uses a module listed above it, which is the healthy direction.
28→21 modules.review-execution.services uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.services uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.modules.review-execution.services.reviewRecovery.service→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- modules.review-execution.services uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break modules.review-execution.services, while a change to modules.review-execution.services can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: modules.review-execution.services uses a module listed above it, which is the healthy direction.
29→11 modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.reviewContext.reviewContext✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.review-execution.entities.reviewContext.reviewContext.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteContextActionsInput→src.modules.review-execution.entities.reviewContext.reviewContext.ReviewContext
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.reviewContext.reviewContext, so a change to modules.review-execution.entities.reviewContext.reviewContext can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.review-execution.entities.reviewContext.reviewContext.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
29→12 modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewDependencies→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
29→13 modules.review-execution.usecases.executeReview_usecase uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewDependencies→src.modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.DiffStatsFetchGateway
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway, so a change to modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
29→19 modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 3 pairs of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteFallbackActionsInput→src.modules.review-execution.entities.job.reviewJob.ReviewJobsrc.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewInput→src.modules.review-execution.entities.job.reviewJob.ReviewJobsrc.modules.review-execution.usecases.executeReview_usecase.ResolveThreadsInput→src.modules.review-execution.entities.job.reviewJob.ReviewJob
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
29→21 modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewDependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
29→24 modules.review-execution.usecases.executeReview_usecase uses modules.tracking.entities.tracking.reviewRequestTracking_gateway✕
- Connections
- 3 pairs of types, where a type in modules.review-execution.usecases.executeReview_usecase uses a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- The types involved
src.modules.review-execution.usecases.executeReview_usecase.ExecuteFallbackActionsInput→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.Platformsrc.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewInput→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.Platformsrc.modules.review-execution.usecases.executeReview_usecase.ResolveThreadsInput→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.Platform
- Direction
- modules.review-execution.usecases.executeReview_usecase uses modules.tracking.entities.tracking.reviewRequestTracking_gateway, so a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can break modules.review-execution.usecases.executeReview_usecase, while a change to modules.review-execution.usecases.executeReview_usecase can't break modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases.executeReview_usecase uses a module listed above it, which is the healthy direction.
30→12 modules.review-execution.usecases.gateClaudeInvocation_usecase uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.gateClaudeInvocation_usecase uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.review-execution.usecases.gateClaudeInvocation_usecase.GateClaudeInvocationDependencies→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.review-execution.usecases.gateClaudeInvocation_usecase uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.review-execution.usecases.gateClaudeInvocation_usecase, while a change to modules.review-execution.usecases.gateClaudeInvocation_usecase can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.review-execution.usecases.gateClaudeInvocation_usecase uses a module listed above it, which is the healthy direction.
30→19 modules.review-execution.usecases.gateClaudeInvocation_usecase uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.gateClaudeInvocation_usecase uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.modules.review-execution.usecases.gateClaudeInvocation_usecase.GateClaudeInvocationInput→src.modules.review-execution.entities.job.reviewJob.ReviewJob
- Direction
- modules.review-execution.usecases.gateClaudeInvocation_usecase uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break modules.review-execution.usecases.gateClaudeInvocation_usecase, while a change to modules.review-execution.usecases.gateClaudeInvocation_usecase can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: modules.review-execution.usecases.gateClaudeInvocation_usecase uses a module listed above it, which is the healthy direction.
31→9 modules.review-execution.usecases.mcp uses modules.review-execution.entities.progress.progress_type✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.mcp uses a type in modules.review-execution.entities.progress.progress_type.
- The types involved
src.modules.review-execution.usecases.mcp.setPhase.usecase→src.modules.review-execution.entities.progress.progress_type.ReviewPhase
- Direction
- modules.review-execution.usecases.mcp uses modules.review-execution.entities.progress.progress_type, so a change to modules.review-execution.entities.progress.progress_type can break modules.review-execution.usecases.mcp, while a change to modules.review-execution.usecases.mcp can't break modules.review-execution.entities.progress.progress_type.
- Position
- Below the diagonal: modules.review-execution.usecases.mcp uses a module listed above it, which is the healthy direction.
31→20 modules.review-execution.usecases.mcp uses modules.review-execution.entities.progress.progress_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases.mcp uses a type in modules.review-execution.entities.progress.progress_gateway.
- The types involved
src.modules.review-execution.usecases.mcp.completeAgent.usecase→src.modules.review-execution.entities.progress.progress_gateway.AgentCompletionStatus
- Direction
- modules.review-execution.usecases.mcp uses modules.review-execution.entities.progress.progress_gateway, so a change to modules.review-execution.entities.progress.progress_gateway can break modules.review-execution.usecases.mcp, while a change to modules.review-execution.usecases.mcp can't break modules.review-execution.entities.progress.progress_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases.mcp uses a module listed above it, which is the healthy direction.
32→22 modules.setup-wizard.entities.setupStep.setupStep uses modules.setup-wizard.entities.wizardContext.wizardContext✕
- Connections
- 1 pair of types, where a type in modules.setup-wizard.entities.setupStep.setupStep uses a type in modules.setup-wizard.entities.wizardContext.wizardContext.
- The types involved
src.modules.setup-wizard.entities.setupStep.setupStep.SetupStep→src.modules.setup-wizard.entities.wizardContext.wizardContext.WizardContext
- Direction
- modules.setup-wizard.entities.setupStep.setupStep uses modules.setup-wizard.entities.wizardContext.wizardContext, so a change to modules.setup-wizard.entities.wizardContext.wizardContext can break modules.setup-wizard.entities.setupStep.setupStep, while a change to modules.setup-wizard.entities.setupStep.setupStep can't break modules.setup-wizard.entities.wizardContext.wizardContext.
- Position
- Below the diagonal: modules.setup-wizard.entities.setupStep.setupStep uses a module listed above it, which is the healthy direction.
33→10 main.dependencies uses modules.review-execution.entities.review.reviewFile_gateway✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.review-execution.entities.review.reviewFile_gateway.
- The types involved
src.main.dependencies.Dependencies→src.modules.review-execution.entities.review.reviewFile_gateway.ReviewFileGateway
- Direction
- main.dependencies uses modules.review-execution.entities.review.reviewFile_gateway, so a change to modules.review-execution.entities.review.reviewFile_gateway can break main.dependencies, while a change to main.dependencies can't break modules.review-execution.entities.review.reviewFile_gateway.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→12 main.dependencies uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.main.dependencies.Dependencies→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- main.dependencies uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break main.dependencies, while a change to main.dependencies can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→16 main.dependencies uses modules.worktree-management.entities.gitCommand.gitCommand_gateway✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- The types involved
src.main.dependencies.Dependencies→src.modules.worktree-management.entities.gitCommand.gitCommand_gateway.GitCommandExecutor
- Direction
- main.dependencies uses modules.worktree-management.entities.gitCommand.gitCommand_gateway, so a change to modules.worktree-management.entities.gitCommand.gitCommand_gateway can break main.dependencies, while a change to main.dependencies can't break modules.worktree-management.entities.gitCommand.gitCommand_gateway.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→21 main.dependencies uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.main.dependencies.Dependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- main.dependencies uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break main.dependencies, while a change to main.dependencies can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→23 main.dependencies uses modules.statistics-insights.entities.stats.stats_gateway✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.statistics-insights.entities.stats.stats_gateway.
- The types involved
src.main.dependencies.Dependencies→src.modules.statistics-insights.entities.stats.stats_gateway.StatsGateway
- Direction
- main.dependencies uses modules.statistics-insights.entities.stats.stats_gateway, so a change to modules.statistics-insights.entities.stats.stats_gateway can break main.dependencies, while a change to main.dependencies can't break modules.statistics-insights.entities.stats.stats_gateway.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→24 main.dependencies uses modules.tracking.entities.tracking.reviewRequestTracking_gateway✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- The types involved
src.main.dependencies.Dependencies→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.ReviewRequestTrackingGateway
- Direction
- main.dependencies uses modules.tracking.entities.tracking.reviewRequestTracking_gateway, so a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can break main.dependencies, while a change to main.dependencies can't break modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
33→26 main.dependencies uses frameworks.claude.claudeInvoker✕
- Connections
- 1 pair of types, where a type in main.dependencies uses a type in frameworks.claude.claudeInvoker.
- The types involved
src.main.dependencies.Dependencies→src.frameworks.claude.claudeInvoker.ClaudeInvocationDeps
- Direction
- main.dependencies uses frameworks.claude.claudeInvoker, so a change to frameworks.claude.claudeInvoker can break main.dependencies, while a change to main.dependencies can't break frameworks.claude.claudeInvoker.
- Position
- Below the diagonal: main.dependencies uses a module listed above it, which is the healthy direction.
34→7 main.executeReviewWiring uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.modules.platform-integration.entities.noteComment.noteCommentPost_gateway.NoteCommentPostGateway
- Direction
- main.executeReviewWiring uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway, so a change to modules.platform-integration.entities.noteComment.noteCommentPost_gateway can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
34→12 main.executeReviewWiring uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- main.executeReviewWiring uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
34→13 main.executeReviewWiring uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.DiffStatsFetchGateway
- Direction
- main.executeReviewWiring uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway, so a change to modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
34→21 main.executeReviewWiring uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- main.executeReviewWiring uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
34→24 main.executeReviewWiring uses modules.tracking.entities.tracking.reviewRequestTracking_gateway✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.Platform
- Direction
- main.executeReviewWiring uses modules.tracking.entities.tracking.reviewRequestTracking_gateway, so a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
34→26 main.executeReviewWiring uses frameworks.claude.claudeInvoker✕
- Connections
- 1 pair of types, where a type in main.executeReviewWiring uses a type in frameworks.claude.claudeInvoker.
- The types involved
src.main.executeReviewWiring.ExecuteReviewWiringDependencies→src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies
- Direction
- main.executeReviewWiring uses frameworks.claude.claudeInvoker, so a change to frameworks.claude.claudeInvoker can break main.executeReviewWiring, while a change to main.executeReviewWiring can't break frameworks.claude.claudeInvoker.
- Position
- Below the diagonal: main.executeReviewWiring uses a module listed above it, which is the healthy direction.
35→7 modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a type in modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies→src.modules.platform-integration.entities.noteComment.noteCommentPost_gateway.NoteCommentPostGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway, so a change to modules.platform-integration.entities.noteComment.noteCommentPost_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.github_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can't break modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a module listed above it, which is the healthy direction.
35→13 modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a type in modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies→src.modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.DiffStatsFetchGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway, so a change to modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.github_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can't break modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a module listed above it, which is the healthy direction.
35→21 modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.github_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a module listed above it, which is the healthy direction.
35→26 modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses frameworks.claude.claudeInvoker✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a type in frameworks.claude.claudeInvoker.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies→src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses frameworks.claude.claudeInvoker, so a change to frameworks.claude.claudeInvoker can break modules.platform-integration.interface-adapters.controllers.webhook.github_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can't break frameworks.claude.claudeInvoker.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a module listed above it, which is the healthy direction.
35→30 modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.review-execution.usecases.gateClaudeInvocation_usecase✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a type in modules.review-execution.usecases.gateClaudeInvocation_usecase.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies→src.modules.review-execution.usecases.gateClaudeInvocation_usecase.GateClaudeInvocationUseCase
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses modules.review-execution.usecases.gateClaudeInvocation_usecase, so a change to modules.review-execution.usecases.gateClaudeInvocation_usecase can break modules.platform-integration.interface-adapters.controllers.webhook.github_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can't break modules.review-execution.usecases.gateClaudeInvocation_usecase.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.github_controller uses a module listed above it, which is the healthy direction.
36→7 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a type in modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies→src.modules.platform-integration.entities.noteComment.noteCommentPost_gateway.NoteCommentPostGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.platform-integration.entities.noteComment.noteCommentPost_gateway, so a change to modules.platform-integration.entities.noteComment.noteCommentPost_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can't break modules.platform-integration.entities.noteComment.noteCommentPost_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a module listed above it, which is the healthy direction.
36→13 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a type in modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies→src.modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.DiffStatsFetchGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway, so a change to modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can't break modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a module listed above it, which is the healthy direction.
36→21 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a module listed above it, which is the healthy direction.
36→26 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses frameworks.claude.claudeInvoker✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a type in frameworks.claude.claudeInvoker.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies→src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses frameworks.claude.claudeInvoker, so a change to frameworks.claude.claudeInvoker can break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can't break frameworks.claude.claudeInvoker.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a module listed above it, which is the healthy direction.
36→30 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.review-execution.usecases.gateClaudeInvocation_usecase✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a type in modules.review-execution.usecases.gateClaudeInvocation_usecase.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies→src.modules.review-execution.usecases.gateClaudeInvocation_usecase.GateClaudeInvocationUseCase
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses modules.review-execution.usecases.gateClaudeInvocation_usecase, so a change to modules.review-execution.usecases.gateClaudeInvocation_usecase can break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, while a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can't break modules.review-execution.usecases.gateClaudeInvocation_usecase.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller uses a module listed above it, which is the healthy direction.
37→12 modules.review-execution.usecases uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.review-execution.usecases uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.review-execution.usecases, while a change to modules.review-execution.usecases can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.review-execution.usecases uses a module listed above it, which is the healthy direction.
37→13 modules.review-execution.usecases uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases uses a type in modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- The types involved
src.modules.review-execution.usecases.executeReview.usecase→src.modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.DiffStatsFetchGateway
- Direction
- modules.review-execution.usecases uses modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway, so a change to modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway can break modules.review-execution.usecases, while a change to modules.review-execution.usecases can't break modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases uses a module listed above it, which is the healthy direction.
37→19 modules.review-execution.usecases uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.entities.job.reviewJob.ReviewJob
- Direction
- modules.review-execution.usecases uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break modules.review-execution.usecases, while a change to modules.review-execution.usecases can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: modules.review-execution.usecases uses a module listed above it, which is the healthy direction.
37→24 modules.review-execution.usecases uses modules.tracking.entities.tracking.reviewRequestTracking_gateway✕
- Connections
- 1 pair of types, where a type in modules.review-execution.usecases uses a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- The types involved
src.modules.review-execution.usecases.executeReview.usecase→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.Platform
- Direction
- modules.review-execution.usecases uses modules.tracking.entities.tracking.reviewRequestTracking_gateway, so a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can break modules.review-execution.usecases, while a change to modules.review-execution.usecases can't break modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- Position
- Below the diagonal: modules.review-execution.usecases uses a module listed above it, which is the healthy direction.
37→29 modules.review-execution.usecases uses modules.review-execution.usecases.executeReview_usecase✕
- Connections
- 4 pairs of types, where a type in modules.review-execution.usecases uses a type in modules.review-execution.usecases.executeReview_usecase.
- The types involved
src.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewDependenciessrc.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewInputsrc.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewResultsrc.modules.review-execution.usecases.executeReview.usecase→src.modules.review-execution.usecases.executeReview_usecase.ReviewLabelTarget
- Direction
- modules.review-execution.usecases uses modules.review-execution.usecases.executeReview_usecase, so a change to modules.review-execution.usecases.executeReview_usecase can break modules.review-execution.usecases, while a change to modules.review-execution.usecases can't break modules.review-execution.usecases.executeReview_usecase.
- Position
- Below the diagonal: modules.review-execution.usecases uses a module listed above it, which is the healthy direction.
38→8 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway✕
- Connections
- 1 pair of types, where a type in modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a type in modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.
- The types involved
src.modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes.MrTrackingAdvancedRoutesOptions→src.modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.CommandExecutor
- Direction
- modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway, so a change to modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway can break modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes, while a change to modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes can't break modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway.
- Position
- Below the diagonal: modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a module listed above it, which is the healthy direction.
38→12 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 1 pair of types, where a type in modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes.MrTrackingAdvancedRoutesOptions→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes, while a change to modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a module listed above it, which is the healthy direction.
38→24 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.tracking.entities.tracking.reviewRequestTracking_gateway✕
- Connections
- 1 pair of types, where a type in modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a type in modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- The types involved
src.modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes.MrTrackingAdvancedRoutesOptions→src.modules.tracking.entities.tracking.reviewRequestTracking_gateway.ReviewRequestTrackingGateway
- Direction
- modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.tracking.entities.tracking.reviewRequestTracking_gateway, so a change to modules.tracking.entities.tracking.reviewRequestTracking_gateway can break modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes, while a change to modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes can't break modules.tracking.entities.tracking.reviewRequestTracking_gateway.
- Position
- Below the diagonal: modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a module listed above it, which is the healthy direction.
38→26 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses frameworks.claude.claudeInvoker✕
- Connections
- 1 pair of types, where a type in modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a type in frameworks.claude.claudeInvoker.
- The types involved
src.modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes.MrTrackingAdvancedRoutesOptions→src.frameworks.claude.claudeInvoker.ClaudeInvokerDependencies
- Direction
- modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses frameworks.claude.claudeInvoker, so a change to frameworks.claude.claudeInvoker can break modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes, while a change to modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes can't break frameworks.claude.claudeInvoker.
- Position
- Below the diagonal: modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a module listed above it, which is the healthy direction.
38→30 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.review-execution.usecases.gateClaudeInvocation_usecase✕
- Connections
- 1 pair of types, where a type in modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a type in modules.review-execution.usecases.gateClaudeInvocation_usecase.
- The types involved
src.modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes.MrTrackingAdvancedRoutesOptions→src.modules.review-execution.usecases.gateClaudeInvocation_usecase.GateClaudeInvocationUseCase
- Direction
- modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses modules.review-execution.usecases.gateClaudeInvocation_usecase, so a change to modules.review-execution.usecases.gateClaudeInvocation_usecase can break modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes, while a change to modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes can't break modules.review-execution.usecases.gateClaudeInvocation_usecase.
- Position
- Below the diagonal: modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes uses a module listed above it, which is the healthy direction.
39→9 main uses modules.review-execution.entities.progress.progress_type✕
- Connections
- 3 pairs of types, where a type in main uses a type in modules.review-execution.entities.progress.progress_type.
- The types involved
src.main.mcpDependencies→src.modules.review-execution.entities.progress.progress_type.ReviewProgresssrc.main.websocket→src.modules.review-execution.entities.progress.progress_type.ProgressEventsrc.main.websocket→src.modules.review-execution.entities.progress.progress_type.ReviewProgress
- Direction
- main uses modules.review-execution.entities.progress.progress_type, so a change to modules.review-execution.entities.progress.progress_type can break main, while a change to main can't break modules.review-execution.entities.progress.progress_type.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
39→12 main uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 2 pairs of types, where a type in main uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.main.dependencies→src.modules.review-execution.services.contextActionsExecutor.Loggersrc.main.executeReviewWiring→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- main uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break main, while a change to main can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
39→19 main uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 1 pair of types, where a type in main uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.main.server→src.modules.review-execution.entities.job.reviewJob.JobStatus
- Direction
- main uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break main, while a change to main can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
39→21 main uses modules.review-execution.entities.reviewContext.reviewContext_gateway✕
- Connections
- 1 pair of types, where a type in main uses a type in modules.review-execution.entities.reviewContext.reviewContext_gateway.
- The types involved
src.main.mcpDependencies→src.modules.review-execution.entities.reviewContext.reviewContext_gateway.ReviewContextGateway
- Direction
- main uses modules.review-execution.entities.reviewContext.reviewContext_gateway, so a change to modules.review-execution.entities.reviewContext.reviewContext_gateway can break main, while a change to main can't break modules.review-execution.entities.reviewContext.reviewContext_gateway.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
39→33 main uses main.dependencies✕
- Connections
- 4 pairs of types, where a type in main uses a type in main.dependencies.
- The types involved
src.main.dependencies→src.main.dependencies.Dependenciessrc.main.routes→src.main.dependencies.Dependenciessrc.main.server→src.main.dependencies.Dependenciessrc.main.websocket→src.main.dependencies.Dependencies
- Direction
- main uses main.dependencies, so a change to main.dependencies can break main, while a change to main can't break main.dependencies.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
39→34 main uses main.executeReviewWiring✕
- Connections
- 1 pair of types, where a type in main uses a type in main.executeReviewWiring.
- The types involved
src.main.executeReviewWiring→src.main.executeReviewWiring.ExecuteReviewWiringDependencies
- Direction
- main uses main.executeReviewWiring, so a change to main.executeReviewWiring can break main, while a change to main can't break main.executeReviewWiring.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
40→12 modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.services.contextActionsExecutor✕
- Connections
- 2 pairs of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook uses a type in modules.review-execution.services.contextActionsExecutor.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github.controller→src.modules.review-execution.services.contextActionsExecutor.Loggersrc.modules.platform-integration.interface-adapters.controllers.webhook.gitlab.controller→src.modules.review-execution.services.contextActionsExecutor.Logger
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.services.contextActionsExecutor, so a change to modules.review-execution.services.contextActionsExecutor can break modules.platform-integration.interface-adapters.controllers.webhook, while a change to modules.platform-integration.interface-adapters.controllers.webhook can't break modules.review-execution.services.contextActionsExecutor.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook uses a module listed above it, which is the healthy direction.
40→19 modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.entities.job.reviewJob✕
- Connections
- 2 pairs of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook uses a type in modules.review-execution.entities.job.reviewJob.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github.controller→src.modules.review-execution.entities.job.reviewJob.ReviewJobsrc.modules.platform-integration.interface-adapters.controllers.webhook.gitlab.controller→src.modules.review-execution.entities.job.reviewJob.ReviewJob
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.entities.job.reviewJob, so a change to modules.review-execution.entities.job.reviewJob can break modules.platform-integration.interface-adapters.controllers.webhook, while a change to modules.platform-integration.interface-adapters.controllers.webhook can't break modules.review-execution.entities.job.reviewJob.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook uses a module listed above it, which is the healthy direction.
40→29 modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.usecases.executeReview_usecase✕
- Connections
- 2 pairs of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook uses a type in modules.review-execution.usecases.executeReview_usecase.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github.controller→src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewInputsrc.modules.platform-integration.interface-adapters.controllers.webhook.gitlab.controller→src.modules.review-execution.usecases.executeReview_usecase.ExecuteReviewInput
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook uses modules.review-execution.usecases.executeReview_usecase, so a change to modules.review-execution.usecases.executeReview_usecase can break modules.platform-integration.interface-adapters.controllers.webhook, while a change to modules.platform-integration.interface-adapters.controllers.webhook can't break modules.review-execution.usecases.executeReview_usecase.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook uses a module listed above it, which is the healthy direction.
40→35 modules.platform-integration.interface-adapters.controllers.webhook uses modules.platform-integration.interface-adapters.controllers.webhook.github_controller✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook uses a type in modules.platform-integration.interface-adapters.controllers.webhook.github_controller.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.github.controller→src.modules.platform-integration.interface-adapters.controllers.webhook.github_controller.GitHubWebhookDependencies
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook uses modules.platform-integration.interface-adapters.controllers.webhook.github_controller, so a change to modules.platform-integration.interface-adapters.controllers.webhook.github_controller can break modules.platform-integration.interface-adapters.controllers.webhook, while a change to modules.platform-integration.interface-adapters.controllers.webhook can't break modules.platform-integration.interface-adapters.controllers.webhook.github_controller.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook uses a module listed above it, which is the healthy direction.
40→36 modules.platform-integration.interface-adapters.controllers.webhook uses modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller✕
- Connections
- 1 pair of types, where a type in modules.platform-integration.interface-adapters.controllers.webhook uses a type in modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.
- The types involved
src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab.controller→src.modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.GitLabWebhookDependencies
- Direction
- modules.platform-integration.interface-adapters.controllers.webhook uses modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller, so a change to modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller can break modules.platform-integration.interface-adapters.controllers.webhook, while a change to modules.platform-integration.interface-adapters.controllers.webhook can't break modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller.
- Position
- Below the diagonal: modules.platform-integration.interface-adapters.controllers.webhook 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 64 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 36 | High / Critical |
| A07:2025 — Authentication Failures | 2 | 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; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
| 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. | +4.8 pts | Medium | Visual & motion safety |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +3.3 pts | Medium | Security & performance tooling |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +3.0 pts | Medium | Forms & labels |
| Enforce accessibility in the toolchain you already use: add `jsx-a11y` to the `plugins` array in your oxlint config (its a11y rules are off until the plugin is listed), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI. | +2.8 pts | Medium | A11y enforcement |
| Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail. | +2.3 pts | Medium | Outbound HTTP resilience |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.3 pts | Medium | Keyboard semantics |
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. | +0.8 pts | Low | Dependency Hygiene |
| Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED. | +0.8 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/frameworks/claude/claudeInvoker.ts | 5.4 | Mixed | Cognitive Complexity: claudeInvoker.invokeViaBackgroundSession (cognitive 22) |
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: 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 88 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 88 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, 578 of 603 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 641 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 3 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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's deterministic call-shape 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. This says nothing about whether that surface is consistent.
- D32 Data Compliance (PII/GDPR) — 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. `docs/.vitepress/theme/index.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/modules/review-execution/services/processorRegistry.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — 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. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at startServer (<repo>/src/main/server.ts:189:36) / at Object.startServer (<repo>/src/main/commands/start.command.ts:106:28) / at startForeground (<repo>/src/main/commands/start.command.ts:81:18) / at executeStart (<repo>/src/main/commands/start.command.ts:88:3) / at <anonymous> (<repo>/src/main/cli.ts:55:7) / at ModuleJob.run (node:internal/modules/esm/module_job:271:25) / at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:26) / at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at startServer (<repo>/src/main/server.ts:189:36) / at Object.startServer (<repo>/src/main/commands/start.command.ts:106:28) / at startForeground (<repo>/src/main/commands/start.command.ts:81:18) / at executeStart (<repo>/src/main/commands/start.command.ts:88:3) / at <anonymous> (<repo>/src/main/cli.ts:55:7) / at ModuleJob.run (node:internal/modules/esm/module_job:271:25) / at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:26) / at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)" No runtime evidence was gathered.
- 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, 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. The .NET and Node.js version checks are a different kind and still publish.
- 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.
- P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- PF3 Async & latency hygiene — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
- R10 Code Duplication — 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. 89 further occurrence(s) are not listed individually; the score already reflects all 129.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- 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".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was REDACTED.renderStaticLabels at 60. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being REDACTED.connectWebSocket at 26 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with REDACTED.renderStaticLabels (cyclomatic 60), mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cyclomatic 49), gitlab.controller.handleGitLabWebhook (cyclomatic 42). — 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 28 together lifts Cyclomatic Complexity from 6.5 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
43 method(s) exceeded the cognitive complexity threshold of 15; the worst was gitlab.controller.handleGitLabWebhook at 86.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with gitlab.controller.handleGitLabWebhook (cognitive 86), mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cognitive 69). — 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 2 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
18 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 13 FunctionTooLong finding(s) in God Classes — start with github.controller.ts (2), mrSheet.js (2), REDACTED. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 5 FileTooLong finding(s) in God Classes — start with REDACTED, REDACTED, gitlab.controller.ts. — One of this dimension's main actionable groups (5 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.
D6 · Cohesion (LCOM4)
2 of 99 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with claudeSession.stub.ts, prompt.stub.ts. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
- Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D8 · Code Coverage
Line coverage 87.8% — 32 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `yarn install --frozen-lockfile --ignore-scripts` in the repository root).
What to do
- Resolve the 32 Low coverage finding(s) in Code Coverage — start with mcpServer.ts, claudeInvoker.ts, cli.ts. — One of this dimension's main actionable groups (32 warning-level).
- Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
4407 test methods: 3941 unit, 11 integration, 455 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 4407 `it`/`test` case(s) across 523 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
- Improve Test Distribution — currently 9.0/10. — 4407 test methods: 3941 unit, 11 integration, 455 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 4407 `it`/`test` case(s) across 523 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4407 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (4440 tests)): measured (0 flaky).
D12 · Dependency Hygiene
12 outdated direct production npm dependency(ies) of 12 graded, 0 pinning defect(s), across 1 REDACTED (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry 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, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 201 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 201 package(s) this repository's committed lockfile installs for a consumer — its 12 production, optional and peer dependency(ies), across 1 product REDACTED manifest(s), and everything those install in turn. Its 14 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: REDACTED (38×60=2280); src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts (28×42=1176); src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts (26×29=754)
What to do
- Resolve the 13 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, gitlab.controller.ts, github.controller.ts. — One of this dimension's main actionable groups (13 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 31322 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 186 document(s) read across 1 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (12 contexts). Contexts: claude-invocation, cli-configuration, data-lifecycle, ember-chat, platform-integration, review-execution, setup-wizard, statistics-insights, supervisor-management, token-accounting, tracking, worktree-management.
D24 · Comment Value
6 of 218 judged comments only repeat the code they sit on (2.8 %). 4 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with claudeInvoker.ts, eventFilter.ts. — One of this dimension's main actionable groups (2 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (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).
D27 · Navigability
26 % of calls cross a namespace and 0 % go through an interface, but 64 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
64 finding(s): 0 critical, 11 high, 53 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `docs/.vitepress/theme/index.ts` (line 11) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 46 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (46 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
28 finding(s): 2 critical, 15 high, 11 medium, 0 low.
What to do
- Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
- Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 162 of the 593 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: github.controller.ts↔gitlab.controller.ts 76%; eventFilter.ts↔github.controller.ts 73%; eventFilter.ts↔gitlab.controller.ts 64%
What to do
- Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with eventFilter.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 12 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
AC1 · Text alternatives
AC2 · Forms & labels
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×5) — REDACTED:32, REDACTED:35, REDACTED:184, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — REDACTED:74, REDACTED:81, REDACTED:88
- This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — REDACTED:272
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — src/dashboard/stats.html:212
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
AC4 · Keyboard semantics
- A script attaches a click listener to this <dialog>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — REDACTED:368
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.budget-slider-row button` sets color: #fff on background-color: #FFBC54 — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/dashboard/styles.css:4351
- `.step-number` sets color: white on background-color: #06b6d4 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/.vitepress/theme/components/QuickStart.vue:80
- `.toggle-icon [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:91
- `.agent-box.running [data-lucide]` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:132
- `.btn-update` moves (`transition: opacity 0.2s, transform 0.1s`) 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. — src/dashboard/styles.css:385
- `.btn-icon.spinning [data-lucide]` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:482
- `.data-loading [data-lucide]` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:722
- `.section-header .btn-sync .spinning` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:823
- `.review-description-toggle [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:918
- `.progress-bar-fill` moves (`transition: width 0.3s ease`) 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. — src/dashboard/styles.css:997
- `.review-accordion-toggle` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1193
- `.review-accordion-toggle [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1199
- `.toggle-icon` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1463
- `.section-toggle [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1478
- `.mr-toggle` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1685
- `.mr-toggle [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:1690
- `.queue-lane-toggle [data-lucide]` moves (`transition: transform 0.2s`) 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. — src/dashboard/styles.css:2025
- `.quality-progress-fill` moves (`transition: width 180ms ease`) 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. — src/dashboard/styles.css:2121
- `.sheet-panel` moves (`transition: transform 0.35s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/dashboard/styles.css:2895
- `.dev-card` moves (`transition: transform 0.2s, box-shadow 0.2s, border-color 0.2s`) 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. — src/dashboard/styles.css:3334
- `.stat-bar-fill` moves (`transition: width 0.8s 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. — src/dashboard/styles.css:3484
- `.team-loading .spinning` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:3627
- `.ai-generate-btn.loading [data-lucide]` moves (`animation: spin 1s linear infinite`) 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. — src/dashboard/styles.css:3848
- `.budget-gauge-fill` moves (`transition: width 0.25s 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. — src/dashboard/styles.css:4334
- `#claude-economics-section .economics-panel` moves (`animation: economics-reveal 250ms 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. — src/dashboard/styles.css:4392
- `.manage-projects-toggle-icon` moves (`transition: transform 200ms ease`) 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. — src/dashboard/styles.css:5212
- `#manage-panel` moves (`transition: max-height 250ms ease, opacity 250ms ease, margin-bottom 250ms ease`) 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. — src/dashboard/styles.css:5220
- `#manage-panel[data-open="true"]` moves (`transition: max-height 250ms ease, opacity 250ms ease, margin-bottom 250ms ease`) 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. — src/dashboard/styles.css:5227
- `#manage-panel[data-open="false"]` moves (`transition: max-height 200ms ease, opacity 200ms ease, margin-bottom 200ms ease`) 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. — src/dashboard/styles.css:5231
- `.manage-row` moves (`transition: opacity 200ms ease, max-height 250ms ease, box-shadow 1500ms ease`) 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. — src/dashboard/styles.css:5265
- `.manage-row-toggle` moves (`transition: transform 200ms ease, border-color 200ms ease, background-color 200ms ease`) 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. — src/dashboard/styles.css:5299
- `.manage-row-toggle .row-toggle-icon` moves (`transition: transform 200ms ease, background-color 200ms ease`) 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. — src/dashboard/styles.css:5308
- `.manage-row.is-leaving` moves (`transition: max-height 250ms ease, opacity 250ms ease, padding 250ms ease, margin 250ms ease`) 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. — src/dashboard/styles.css:5337
- `.dashboard-tab` moves (`transition: opacity 200ms ease, transform 1500ms ease, max-width 250ms ease, box-shadow 1500ms ease`) 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. — src/dashboard/styles.css:5454
- `.dashboard-tab.is-leaving` moves (`transition: opacity 250ms ease, max-width 250ms ease, padding 250ms ease, margin 250ms ease`) 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. — src/dashboard/styles.css:5491
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 — your oxlint config does not list the `jsx-a11y` plugin (its a11y rules are off until it does) and there's no axe/pa11y/Lighthouse in tests or CI. Start by enabling that plugin to catch issues at author time. What was searched, so you can tell an absence from a miss: the 9 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. — REDACTED:73
What to do
- Enforce accessibility in the toolchain you already use: add `jsx-a11y` to the `plugins` array in your oxlint config (its a11y rules are off until the plugin is listed), then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `InitDependencies` declares 18 required operations: `log`, `exit`, `getConfigDir`, `existsSync`, `checkPrerequisites`, `confirmOverwrite`, `promptPlatform`, `promptPort`, `promptGitlabUsername`, `promptGithubUsername`, `confirmScanRepositories`, `selectRepositories`, `generateWebhookSecret`, `truncateSecret`, `discoverRepositories`, `configureMcp`, `writeConfig`, `formatSummary`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/commands/init.command.ts:42
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX7 · Slice cohesion
- `AddRepositoryFromDashboardDependencies` (slice 'dashboardRepositories') depends on `AddRepositoriesToConfigUseCase` from slice 'cli'. — src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts:15
- `RemoveRepositoryFromDashboardDependencies` (slice 'dashboardRepositories') depends on `RemoveRepositoryFromConfigUseCase` from slice 'cli'. — src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:10
- `UpdateRepositoryEnabledFromDashboardDependencies` (slice 'dashboardRepositories') depends on `ToggleRepositoryEnabledUseCase` from slice 'cli'. — src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:10
- `EnforceBudgetDependencies` (slice 'enforceBudget') depends on `GetBudgetStatusUseCase` from slice 'getBudgetStatus'. — src/modules/token-accounting/usecases/enforceBudget/enforceBudget.usecase.ts:5
What to do
- Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — REDACTED:72
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `registerWebSocketRoutes` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:187
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)
M2 · Architecture documentation
- 1 ADR-shaped document(s) detected by content — `docs/architecture/mcp/architecture.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
- docs/architecture/current.md names Fastify 4, but the manifest declares `fastify` ^5.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, 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. — docs/architecture/current.md:103
What to do
- Reconcile the README with reality: docs/architecture/current.md names Fastify 4, but the manifest declares `fastify` ^5.0.0.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `REDACTED` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:64
- `src/main/shared/cliConstants.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/main/shared/cliConstants.ts:16
- `src/main/commands/setup.command.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/main/commands/setup.command.ts:171
- `src/frameworks/settings/runtimeSettings.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/frameworks/settings/runtimeSettings.ts:56
- `src/frameworks/settings/runtimeSettings.ts` reports through `console.*` at line 218 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/frameworks/settings/runtimeSettings.ts:218
- `src/frameworks/config/configLoader.ts` reports through `console.*` at line 135 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/frameworks/config/configLoader.ts:135
- `src/frameworks/config/configLoader.ts` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/frameworks/config/configLoader.ts:140
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.
- Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:59
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×9) — src/dashboard/modules/budgetSettings.js:126, src/dashboard/modules/budgetSettings.js:140, src/dashboard/modules/budgetSettings.js:155, …
- `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — src/dashboard/modules/cleanup.js:32, src/dashboard/modules/teamTab.js:317, src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:13
- `fetchImplementation(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/dashboard/modules/emberChat.js:112
What to do
- Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
P9 · Domain vs controller coverage
What to do
- Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
PF3 · Async & latency hygiene
- `existsSync` in `loadSettingsFromDisk` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/frameworks/settings/runtimeSettings.ts:74
- `readFileSync` in `loadSettingsFromDisk` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/frameworks/settings/runtimeSettings.ts:82
- `deps.existsSync` in `executeInit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/main/commands/init.command.ts:92
- `statSync` in `isExistingDirectory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:844
- `existsSync` in `getSessionUsage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:199
- `readFileSync` in `getSessionUsage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:205
- `existsSync` in `load` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:31, src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:52, src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:18
- `readFileSync` in `load` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:35, src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:56, src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:24
- `existsSync` in `clear` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:63
- `unlinkSync` in `clear` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:64
- `existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:126
- `unlinkSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:127
- `existsSync` in `loadRecordsWithinWindow` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:64
- `existsSync` in `deleteRecordsOutsideWindow` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:84
- `writeFileSync` in `save` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:44, src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:49
- `existsSync` in `listAll` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:69
- `readdirSync` in `listAll` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:72
- `readFileSync` in `listAll` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:77
- `existsSync` in `delete` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:92
- `unlinkSync` in `delete` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:96
- `existsSync` in `readAnswer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:94
- `readFileSync` in `readAnswer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:100
- `existsSync` in `save` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:45
- `mkdirSync` in `save` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:46
- `existsSync` in `record` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:15
- `mkdirSync` in `record` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:16
- `appendFileSync` in `record` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:19
- `existsSync` in `loadAll` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:24
- `readFileSync` in `loadAll` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:28
- `mkdirSync` in `ensure` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:43
- `existsSync` in `worktreeExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:53, src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:71
- `rmSync` in `removeDirectory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:54
- `existsSync` in `exists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:81
- `existsSync` in `list` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:85
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 21 duplicated blocks under src/modules/ have copies in at least two of the sibling directories claude-invocation, cli-configuration, data-lifecycle, ember-chat, platform-integration, review-execution (+5 more sibling(s) not listed) — 11 of them are reported below, and 10 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 21 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 21 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 21 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11
- src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:110 · src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:352 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:110
- src/dashboard/modules/mrSheet.js:207 · src/dashboard/modules/statsCharts.js:26 — the two spans are one implementation copied and then locally edited — 772 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/dashboard/modules/mrSheet.js:207
- REDACTED:621 · REDACTED:706 — 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. — REDACTED:621
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:313 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:205 — the 2 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:313
- src/dashboard/modules/emberAvatarRenderer.js:26 · src/dashboard/modules/setupWizardAvatarRenderer.js:25 — the two spans are one implementation copied and then locally edited — 390 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/dashboard/modules/emberAvatarRenderer.js:26
- src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:66 · REDACTED:23 — the two spans are one implementation copied and then locally edited — 305 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:66
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:397 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:305 — the 2 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:397
- REDACTED:57 · REDACTED:121 — 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. — REDACTED:57
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:486 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:535 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:486
- src/dashboard/modules/developerSheet.js:112 · src/dashboard/modules/teamTab.js:188 — the two spans are one implementation copied and then locally edited — 192 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/dashboard/modules/developerSheet.js:112
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:66 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:103 — the two spans are one implementation copied and then locally edited — 205 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:66
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:536 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:584 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:536
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:745 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:785 — the 2 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:745
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:695 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:734 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:695
- src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11 · src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts:6 — the two spans are one implementation copied and then locally edited — 192 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:227 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:445 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:227
- src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:304 · src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts:317 — the 2 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. — src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:304
- src/modules/review-execution/interface-adapters/controllers/mcp/setPhase.handler.ts:18 · src/modules/review-execution/interface-adapters/controllers/mcp/startAgent.handler.ts:8 — the two spans are one implementation copied and then locally edited — 166 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/review-execution/interface-adapters/controllers/mcp/setPhase.handler.ts:18
- src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:17 · src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:17
- src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:80 · src/modules/review-execution/interface-adapters/controllers/mcp/setPhase.handler.ts:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:80
- src/dashboard/modules/statsCharts.js:152 · src/dashboard/modules/statsCharts.js:289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/dashboard/modules/statsCharts.js:152
- src/modules/cli-configuration/usecases/cli/removeRepositoryFromConfig.usecase.ts:11 · src/modules/cli-configuration/usecases/cli/toggleRepositoryEnabled.usecase.ts:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/cli-configuration/usecases/cli/removeRepositoryFromConfig.usecase.ts:11
- src/modules/statistics-insights/usecases/insights/buildAiInsightsPrompt.ts:21 · src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:52 — the two spans are one implementation copied and then locally edited — 195 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/statistics-insights/usecases/insights/buildAiInsightsPrompt.ts:21
- src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:4 · src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:4 — the two spans are one implementation copied and then locally edited — 138 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:4
- src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:13 · src/modules/review-execution/interface-adapters/controllers/mcp/startAgent.handler.ts:8 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:13
- src/modules/review-execution/interface-adapters/controllers/mcp/getThreads.handler.ts:8 · src/modules/review-execution/interface-adapters/controllers/mcp/getWorkflow.handler.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. — src/modules/review-execution/interface-adapters/controllers/mcp/getThreads.handler.ts:8
- src/modules/review-execution/services/contextActionsExecutor.ts:89 · src/modules/review-execution/services/threadActionsExecutor.ts:85 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/review-execution/services/contextActionsExecutor.ts:89
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:153 · src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:300 — 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:153
- src/dashboard/modules/insightsReport.js:82 · src/dashboard/modules/insightsReport.js:204 — 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. — src/dashboard/modules/insightsReport.js:82
- src/dashboard/modules/statsCharts.js:270 · src/dashboard/modules/statsCharts.js:396 · src/dashboard/modules/statsCharts.js:558 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/dashboard/modules/statsCharts.js:270
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:186 · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:406 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:186
- src/modules/review-execution/interface-adapters/gateways/cli/reviewAction.github.cli.gateway.ts:22 · src/modules/review-execution/interface-adapters/gateways/cli/reviewAction.github.cli.gateway.ts:50 — 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. — src/modules/review-execution/interface-adapters/gateways/cli/reviewAction.github.cli.gateway.ts:22
- src/modules/review-execution/usecases/mcp/addAction.usecase.ts:88 · src/modules/review-execution/usecases/mcp/getThreads.usecase.ts:14 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/modules/review-execution/usecases/mcp/addAction.usecase.ts:88
- src/modules/worktree-management/interface-adapters/gateways/gitCommand.cli.gateway.ts:11 · src/modules/worktree-management/interface-adapters/gateways/worktreeSizeProbe.cli.gateway.ts:18 — the 2 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. — src/modules/worktree-management/interface-adapters/gateways/gitCommand.cli.gateway.ts:11
- src/frameworks/settings/runtimeSettings.ts:77 · src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:19 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/frameworks/settings/runtimeSettings.ts:77
- src/modules/cli-configuration/usecases/cli/addRepositoriesToConfig.usecase.ts:17 · src/modules/cli-configuration/usecases/cli/removeRepositoryFromConfig.usecase.ts:16 · src/modules/cli-configuration/usecases/cli/toggleRepositoryEnabled.usecase.ts:17 — 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. — src/modules/cli-configuration/usecases/cli/addRepositoriesToConfig.usecase.ts:17
- src/dashboard/modules/statsCharts.js:423 · src/dashboard/modules/statsCharts.js:585 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/dashboard/modules/statsCharts.js:423
- src/frameworks/claude/claudeInvoker.ts:149 · src/modules/worktree-management/interface-adapters/gateways/gitCommand.cli.gateway.ts:14 · src/modules/worktree-management/interface-adapters/gateways/worktreeSizeProbe.cli.gateway.ts:21 — 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. — src/frameworks/claude/claudeInvoker.ts:149
- REDACTED:14 · REDACTED:69 · REDACTED:133 — all 3 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. — REDACTED:14
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
- handleGitLabWebhook has cyclomatic complexity 42 and cognitive complexity 86; 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- validateAndEnrichConfig has cyclomatic complexity 39 and cognitive complexity 42; 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. — src/frameworks/config/configLoader.ts:178
- handleGitHubWebhook has cyclomatic complexity 34 and cognitive complexity 47; 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. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- extractPatch has cyclomatic complexity 33 and cognitive complexity 44; 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. — src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61
- parseProjectConfig has cyclomatic complexity 27 and cognitive complexity 29; 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. — src/config/projectConfig.ts:195
- (anonymous) has cyclomatic complexity 26 and cognitive complexity 29; 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. — src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:154
- parseReviewOutput has cyclomatic complexity 25 and cognitive complexity 30; 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. — REDACTED:47
- renderMrSheetContent has cyclomatic complexity 23 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 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. — src/dashboard/modules/mrSheet.js:25
- executeInit has cyclomatic complexity 19 and cognitive complexity 28; 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. — src/main/commands/init.command.ts:68
- execute has cyclomatic complexity 19 and cognitive complexity 28; 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. — src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48
- mergeConfig has cyclomatic complexity 19 and cognitive complexity 26; 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. — src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101
- runClaudeReviewJob has cyclomatic complexity 19 and cognitive complexity 21; 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. — src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52
- scan has cyclomatic complexity 18 and cognitive complexity 24; 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. — src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33
- (anonymous) has cyclomatic complexity 17 and cognitive complexity 25; 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. — src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:23
- invokeViaBackgroundSession has cyclomatic complexity 16 and cognitive complexity 24; 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. — src/frameworks/claude/claudeInvoker.ts:590
- buildContext has cyclomatic complexity 16 and cognitive complexity 15; 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. — src/tests/acceptance/183-setup-wizard.acceptance.test.ts:100
- drawScoreTrendChart has cyclomatic complexity 15 and cognitive complexity 21; 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. — src/dashboard/modules/statsCharts.js:108
- buildPayload has cyclomatic complexity 15 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. — src/tests/factories/projectConfig.factory.ts:18
- updateAggregatesForNewReview has cyclomatic complexity 15 and cognitive complexity 14; 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. — src/modules/statistics-insights/usecases/stats/addReviewStats.usecase.ts:90
- readAnswer has cyclomatic complexity 14 and cognitive complexity 25; 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. — src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:79
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- src/dashboard/modules/i18n.js has 920 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/dashboard/modules/i18n.js:1
- REDACTED has 844 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts has 786 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:1
- src/frameworks/claude/claudeInvoker.ts has 761 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/frameworks/claude/claudeInvoker.ts:1
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts has 741 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:1
- src/dashboard/modules/statsCharts.js has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/dashboard/modules/statsCharts.js:1
- src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts has 533 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:1
- src/dashboard/modules/insightsReport.js has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/dashboard/modules/insightsReport.js:1
- src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:1
- src/frameworks/queue/pQueueAdapter.ts has 457 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/frameworks/queue/pQueueAdapter.ts:1
- src/dashboard/modules/worktreePanel.js has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/dashboard/modules/worktreePanel.js:1
- src/dashboard/modules/animations.js has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/dashboard/modules/animations.js: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
- src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16 imports '../../../../../fixtures/claudeCli/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16
- 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. (×9) — src/modules/worktree-management/entities/worktree/worktree.schema.ts:1, src/mcpServer.ts:1, src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16
R7 · Dead Code
- Unreachable from the 304 application, 51 tooling and 629 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (304 application, 51 tooling, 629 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts, src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts, src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts
- Nothing imports this binding — it is safe to review for removal. (×32) — src/frameworks/logging/logBuffer.ts:56, src/frameworks/logging/logBuffer.ts:91, src/frameworks/queue/pQueueAdapter.ts:522, …
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 the root REDACTED 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
S1 · Web-Security Posture
- `https://unpkg.com/lucide@latest` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 2 such include(s) across the repository's markup. — REDACTED:11
- `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — src/main/server.ts:292
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
- `spawn` pipes `stderr` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `child.stderr`, while `child.stdout` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stderr (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`child.stderr.on('data', …)`, or `child.stderr.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — src/modules/supervisor-management/interface-adapters/gateways/supervisor.cli.gateway.ts:34
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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
- Only 2/5 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchLatestVersion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:11
- `handleCleanupClick` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/dashboard/modules/cleanup.js:20
- `fetchAndRenderTeamTab` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/dashboard/modules/teamTab.js:310
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `encodedMrId` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. (×2) — src/dashboard/modules/mrSheet.js:191, src/dashboard/modules/mrSheet.js:192
- `sanitizeHttpUrl(mr.url)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/dashboard/modules/mrSheet.js:193
- `escapeHtml(sanitizeHttpUrl(item.mrUrl))` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/dashboard/modules/overview.js:131
- `escapeHtml(safeHref)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/dashboard/modules/overview.js:161
- `mrUrl` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/dashboard/modules/pendingReviews.js:60
- `placeholder` is text this program did not author, and it is written into an unquoted attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — src/dashboard/modules/setupWizardForms.js:140
- `escapeHtml(sanitizeHttpUrl(row.url))` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/dashboard/modules/sizeBlockPanel.js:62
- `escapeHtml(developer)` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — src/dashboard/modules/statsPage.js:165
- `encodedName` is text this program did not author, and it is written into a script or style context through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — src/dashboard/modules/teamTab.js:37
- `translate('ai.lastGenerated',{date:generatedDate})` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/dashboard/modules/teamTab.js:174
- `translate('team.noData')` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/dashboard/modules/teamTab.js:263
- `translate('export.pdf')` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/dashboard/modules/teamTab.js:286
- `translate('team.loading')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/dashboard/modules/teamTab.js:314
- `translate('team.noData')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/dashboard/modules/teamTab.js:329
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
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. (×27) — src/shared/services/browserOpener.ts:24, src/shared/services/claudePathResolver.ts:15, src/shared/services/claudePathResolver.ts:31, …
- `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×4) — src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:101, src/modules/cli-configuration/usecases/cli/discoverRepositories.usecase.ts:85, REDACTED:47, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — src/frameworks/queue/pQueueAdapter.ts:303
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 69 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/modules/supervisor-management/usecases/checkSupervisorAndRespawn.usecase.ts:69
- `info` at line 279 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/mcp/mcpServerStdio.ts:279
- `error` at line 288 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/mcp/mcpServerStdio.ts:288
- `info` at line 299 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.info({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.info('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/mcp/mcpServerStdio.ts:299
- `error` at line 308 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/mcp/mcpServerStdio.ts:308
- `warn` at line 85 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/frameworks/settings/runtimeSettings.ts:85
- `warn` at line 96 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/frameworks/settings/runtimeSettings.ts:96
- `warn` at line 103 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — src/frameworks/settings/runtimeSettings.ts:103
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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 | 70% | Strong | Solid. |
| Architecture | 74% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 81% | Strong | Strongest area. |
| Readiness | 49% | Weak — gated by P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 62% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 45% | Weak — gated by AC2, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 41 check(s) not relevant to this codebase
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "at startServer (<repo>main/server.ts:189:36) / at Object.startServer (<repo>main/commands/start.command.ts:106:28) / at startForeground (<repo>main/commands/start.command.ts:81:18) / at executeStart (<repo>main/commands/start.command.ts:88:3) / at <anonymous> (<repo>main/cli.ts:55:7) / at ModuleJob.run (node:internal/modules/esm/module_job:271:25) / at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:26) / at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)" No runtime evidence was gathered. 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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 yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- SC1 Supply-chain hygiene — 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.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — 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 — 40 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
- <button> with no accessible text REDACTED:32
- <button> with no accessible text REDACTED:35
- <button> with no accessible text REDACTED:184
- <button> with no accessible text REDACTED:335
- <button> with no accessible text src/dashboard/stats.html:208
- <select> without a programmatic label REDACTED:74
- <select> without a programmatic label REDACTED:81
- REDACTED
- REDACTED
- <input> without a programmatic label REDACTED:88
- Custom control with no accessible name on <div> REDACTED:272
- Link with no accessible name src/dashboard/stats.html:212
- Click handler on a non-interactive <dialog> REDACTED:368
- REDACTED
- REDACTED
- REDACTED
Serious — 432 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
- Sync-over-async blocking src/frameworks/settings/runtimeSettings.ts:74
- Sync-over-async blocking src/frameworks/settings/runtimeSettings.ts:82
- Sync-over-async blocking src/main/commands/init.command.ts:92
- Sync-over-async blocking REDACTED:844
- Sync-over-async blocking src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:199
- Sync-over-async blocking src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:205
- Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:31
- Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:35
- Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:63
- Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:64
- Sync-over-async blocking REDACTED:126
- Sync-over-async blocking REDACTED:127
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:64
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:84
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:44
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:52
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:56
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:69
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:72
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:77
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:92
- Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:96
- Sync-over-async blocking src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:94
- Sync-over-async blocking src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:100
- Sync-over-async blocking src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:18
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:91
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:132
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:385
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:482
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:722
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:823
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:918
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:997
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1193
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1199
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1463
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1478
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1685
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1690
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2025
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2121
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2895
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3334
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3484
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3627
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3848
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:4334
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:4392
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:5212
- Animation without a prefers-reduced-motion guard src/dashboard/styles.css:5220
- Low coverage: src/mcpServer.ts src/mcpServer.ts:1
- Low coverage: src/frameworks/claude/claudeInvoker.ts src/frameworks/claude/claudeInvoker.ts:1
- Low coverage: src/main/cli.ts src/main/cli.ts:1
- Low coverage: src/main/executeReviewWiring.ts src/main/executeReviewWiring.ts:1
- Low coverage: src/main/githubInventoryWiring.ts src/main/githubInventoryWiring.ts:1
- Low coverage: src/main/server.ts src/main/server.ts:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: src/main/shared/cliConstants.ts src/main/shared/cliConstants.ts:1
- Low coverage: src/mcp/mcpLogger.ts src/mcp/mcpLogger.ts:1
- Low coverage: src/mcp/mcpServerStdio.ts src/mcp/mcpServerStdio.ts:1
- Low coverage: src/modules/claude-invocation/entities/billingState/billingState.schema.ts src/modules/claude-invocation/entities/billingState/billingState.schema.ts:1
- Low coverage: src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts:1
- Low coverage: src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts:1
- Low coverage: src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts:1
- Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts:1
- Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:1
- Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:1
- Low coverage: src/modules/platform-integration/interface-adapters/gateways/cli/approvalRevocation.github.cli.gateway.ts src/modules/platform-integration/interface-adapters/gateways/cli/approvalRevocation.github.cli.gateway.ts:1
- Low coverage: src/modules/platform-integration/interface-adapters/gateways/cli/approvalRevocation.gitlab.cli.gateway.ts src/modules/platform-integration/interface-adapters/gateways/cli/approvalRevocation.gitlab.cli.gateway.ts:1
- Low coverage: src/modules/review-execution/services/agentInstructionsBuilder.ts src/modules/review-execution/services/agentInstructionsBuilder.ts:1
- Low coverage: src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts:1
- Low coverage: src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts:1
- Low coverage: src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts:1
- Low coverage: src/modules/setup-wizard/interface-adapters/gateways/aiFallback.noop.gateway.ts src/modules/setup-wizard/interface-adapters/gateways/aiFallback.noop.gateway.ts:1
- Low coverage: src/modules/setup-wizard/interface-adapters/gateways/daemonHealthProbe.http.gateway.ts src/modules/setup-wizard/interface-adapters/gateways/daemonHealthProbe.http.gateway.ts:1
- Swallowed exception (empty catch) src/shared/services/browserOpener.ts:24
- Swallowed exception (empty catch) src/shared/services/claudePathResolver.ts:15
- Swallowed exception (empty catch) src/shared/services/claudePathResolver.ts:31
- Swallowed exception (empty catch) src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:98
- Swallowed exception (empty catch) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:577
- Swallowed exception (empty catch) src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:39
- Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:83
- Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:97
- Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts:37
- Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts:42
- Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/gateways/cli/reviewLabel.github.cli.gateway.ts:22
- Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/gateways/cli/reviewLabel.gitlab.cli.gateway.ts:32
- Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:83
- Swallowed exception (empty catch) src/modules/ember-chat/usecases/askEmber/askEmber.usecase.ts:120
- Swallowed exception (empty catch) src/modules/ember-chat/interface-adapters/controllers/mcp/recordInsight.handler.ts:52
- Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:31
- Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:35
- Swallowed exception (empty catch) src/modules/cli-configuration/interface-adapters/gateways/selfUpdate.cli.gateway.ts:88
- Swallowed exception (empty catch) src/modules/claude-invocation/usecases/awaitSessionCompletion.usecase.ts:74
- Swallowed exception (empty catch) src/modules/claude-invocation/interface-adapters/gateways/mcpCompletion.fileSystem.gateway.ts:169
- Swallowed exception (empty catch) src/mcp/mcpLogger.ts:30
- Swallowed exception (empty catch) src/mcp/mcpLogger.ts:45
- Swallowed exception (empty catch) REDACTED:216
- Swallowed exception (empty catch) src/frameworks/queue/pQueueAdapter.ts:303
- Swallowed exception (empty catch) src/frameworks/logging/logBuffer.ts:40
- Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:191
- Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:192
- Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:193
- Untrusted text written into markup unescaped src/dashboard/modules/overview.js:131
- Untrusted text written into markup unescaped src/dashboard/modules/overview.js:161
- Untrusted text written into markup unescaped src/dashboard/modules/pendingReviews.js:60
- Untrusted text written into markup unescaped src/dashboard/modules/setupWizardForms.js:140
- Untrusted text written into markup unescaped src/dashboard/modules/sizeBlockPanel.js:62
- Untrusted text written into markup unescaped src/dashboard/modules/statsPage.js:165
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:37
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:174
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:263
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:286
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:314
- Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:329
- Hotspot: REDACTED REDACTED:3140
- Hotspot: src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- Hotspot: src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- Hotspot: REDACTED REDACTED:200
- Hotspot: src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84
- Hotspot: src/frameworks/config/configLoader.ts src/frameworks/config/configLoader.ts:178
- Hotspot: src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150
- Hotspot: src/config/projectConfig.ts src/config/projectConfig.ts:195
- Hotspot: src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58
- Hotspot: src/dashboard/modules/statsCharts.js src/dashboard/modules/statsCharts.js:108
- Hotspot: src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101
- Hotspot: src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52
- Hotspot: src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48
- FunctionTooLong: routes.registerRoutes REDACTED:200
- FunctionTooLong: gitlab.controller.handleGitLabWebhook src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- FunctionTooLong: mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84
- FunctionTooLong: github.controller.handleGitHubWebhook src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- FunctionTooLong: claudeInvoker.invokeViaBackgroundSession src/frameworks/claude/claudeInvoker.ts:590
- FunctionTooLong: insightsReport.getReportStyles src/dashboard/modules/insightsReport.js:257
- FunctionTooLong: mrSheet.renderMrSheetContent src/dashboard/modules/mrSheet.js:25
- FunctionTooLong: cliStatus.routes.cliStatusRoutes REDACTED:8
- FunctionTooLong: statsCharts.drawScoreTrendChart src/dashboard/modules/statsCharts.js:108
- FunctionTooLong: projectConfig.routes.projectConfigRoutes src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150
- FunctionTooLong: github.controller.handleGitHubPullRequestReviewHook src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:135
- FunctionTooLong: mrSheet.drawScoreTimeline src/dashboard/modules/mrSheet.js:220
- FunctionTooLong: server.startServer src/main/server.ts:188
- Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:126
- Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:140
- Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:155
- Outbound HTTP without resilience src/dashboard/modules/cleanup.js:32
- Outbound HTTP without resilience src/dashboard/modules/emberChat.js:112
- Outbound HTTP without resilience src/dashboard/modules/sizeBlockPanel.js:104
- Outbound HTTP without resilience src/dashboard/modules/sizeBlockPanel.js:117
- Outbound HTTP without resilience src/dashboard/modules/teamTab.js:317
- Outbound HTTP without resilience src/dashboard/modules/tokenUsage.js:113
- Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:423
- Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:435
- Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:454
- Outbound HTTP without resilience src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:13
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file src/modules/worktree-management/entities/worktree/worktree.schema.ts:1
- No test reaches this file src/mcpServer.ts:1
- No test reaches this file src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts:1
- No test reaches this file src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts:1
- No test reaches this file src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts:1
- No test reaches this file src/modules/claude-invocation/entities/billingState/billingState.schema.ts:1
- No test reaches this file src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts:1
- No test reaches this file src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts:1
- No test reaches this file src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts:1
- FileTooLong: REDACTED REDACTED
- FileTooLong: REDACTED REDACTED
- FileTooLong: webhook/gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts
- FileTooLong: webhook/github.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts
- FileTooLong: claude/claudeInvoker.ts src/frameworks/claude/claudeInvoker.ts
- Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts:15
- Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:10
- Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:10
- Cross-slice coupling: enforceBudget → getBudgetStatus src/modules/token-accounting/usecases/enforceBudget/enforceBudget.usecase.ts:5
- Swallowed exception (caught, then discarded) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:101
- Swallowed exception (caught, then discarded) src/modules/cli-configuration/usecases/cli/discoverRepositories.usecase.ts:85
- Swallowed exception (caught, then discarded) REDACTED:47
- Swallowed exception (caught, then discarded) REDACTED:895
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (18 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:186
- Duplicated block (18 lines × 2 locations) src/modules/review-execution/interface-adapters/gateways/cli/reviewAction.github.cli.gateway.ts:22
- Duplicated block (18 lines × 2 locations) src/modules/worktree-management/interface-adapters/gateways/gitCommand.cli.gateway.ts:11
- Async function without AbortSignal: fetchLatestVersion src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:11
- Async function without AbortSignal: handleCleanupClick src/dashboard/modules/cleanup.js:20
- Async function without AbortSignal: fetchAndRenderTeamTab src/dashboard/modules/teamTab.js:310
- REDACTED
- REDACTED
- Low cohesion: StubClaudeSessionGateway (LCOM4 5) src/tests/stubs/claudeSession.stub.ts:23
- Low cohesion: StubPromptGateway (LCOM4 4) src/tests/stubs/setup-wizard/prompt.stub.ts:6
- Duplicated block (36 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:536
- Duplicated block (36 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:745
- Duplicated block (28 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:17
- Duplicated block (28 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:80
- Duplicated block (27 lines × 2 locations) src/dashboard/modules/statsCharts.js:152
- Duplicated block (27 lines × 2 locations) src/modules/cli-configuration/usecases/cli/removeRepositoryFromConfig.usecase.ts:11
- Duplicated block with local edits (25 matched lines × 2 locations) src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:4
- Duplicated block with local edits (25 matched lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:13
- Duplicated block (15 lines × 3 locations) src/frameworks/claude/claudeInvoker.ts:149
- Duplicated block (15 lines × 3 locations) REDACTED:14
- Dead file (~4 LoC) src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts
- Dead file (~4 LoC) src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts
- Low contrast colour pair in CSS (1.7:1) src/dashboard/styles.css:4351
- Low contrast colour pair in CSS (2.4:1) docs/.vitepress/theme/components/QuickStart.vue:80
- Accessibility enforcement below the top rung REDACTED:73
- REDACTED.renderStaticLabels (cyclomatic 60) REDACTED:3140
- mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cyclomatic 49) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84
- gitlab.controller.handleGitLabWebhook (cyclomatic 42) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- configLoader.validateAndEnrichConfig (cyclomatic 39) src/frameworks/config/configLoader.ts:178
- projectConfig.routes.projectConfigRoutes (cyclomatic 35) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150
- projectConfig.routes.extractPatch (cyclomatic 33) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61
- renderMrSheetContent (cyclomatic 32) src/dashboard/modules/mrSheet.js:25
- github.controller.handleGitHubWebhook (cyclomatic 29) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- REDACTED.renderMrItem (cyclomatic 28) REDACTED:1568
- projectConfig.parseProjectConfig (cyclomatic 27) src/config/projectConfig.ts:195
- reviewOutput.parser.parseReviewOutput (cyclomatic 25) REDACTED:47
- reviews.routes.reviewRoutes (cyclomatic 22) REDACTED:25
- REDACTED.renderNowLane (cyclomatic 21) REDACTED:1675
- REDACTED.bindSettingsModalForm (cyclomatic 20) REDACTED:2668
- init.command.executeInit (cyclomatic 19) src/main/commands/init.command.ts:68
- runClaudeReviewJob.usecase.runClaudeReviewJob (cyclomatic 19) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52
- updateProjectConfig.usecase.mergeConfig (cyclomatic 19) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101
- REDACTED.renderReview (cyclomatic 18) REDACTED:815
- OrchestrateSetupUseCase.execute (cyclomatic 18) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48
- stats.routes.statsRoutes (cyclomatic 18) src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58
- statsCharts.drawScoreTrendChart (cyclomatic 17) src/dashboard/modules/statsCharts.js:108
- addAction.handler.createAddActionHandler.<returned closure> (cyclomatic 17) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:23
- routes.registerRoutes (cyclomatic 16) REDACTED:200
- repositories.routes.repositoriesRoutes (cyclomatic 16) REDACTED:38
- egressScan.scanner.createEgressScanner.scan (cyclomatic 16) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33
- connectEmberStream (cyclomatic 16) src/dashboard/modules/emberChat.js:105
- gitlab.controller.handleGitLabWebhook (cognitive 86) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cognitive 69) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84
- REDACTED.renderStaticLabels (cognitive 58) REDACTED:3140
- projectConfig.routes.extractPatch (cognitive 44) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61
- configLoader.validateAndEnrichConfig (cognitive 42) src/frameworks/config/configLoader.ts:178
- github.controller.handleGitHubWebhook (cognitive 42) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- REDACTED.renderNowLane (cognitive 35) REDACTED:1675
- projectConfig.routes.projectConfigRoutes (cognitive 35) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150
- REDACTED.renderMrItem (cognitive 32) REDACTED:1568
- reviews.routes.reviewRoutes (cognitive 32) REDACTED:25
- projectConfig.parseProjectConfig (cognitive 30) src/config/projectConfig.ts:195
- reviewOutput.parser.parseReviewOutput (cognitive 30) REDACTED:47
- init.command.executeInit (cognitive 28) src/main/commands/init.command.ts:68
- OrchestrateSetupUseCase.execute (cognitive 27) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48
- updateProjectConfig.usecase.mergeConfig (cognitive 26) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101
- renderMrSheetContent (cognitive 26) src/dashboard/modules/mrSheet.js:25
- statsCharts.drawScoreTrendChart (cognitive 23) src/dashboard/modules/statsCharts.js:108
- REDACTED.bindSettingsModalForm (cognitive 23) REDACTED:2668
- egressScan.scanner.createEgressScanner.scan (cognitive 23) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33
- reviewRecovery.service.runReviewRecovery (cognitive 23) src/modules/review-execution/services/reviewRecovery.service.ts:43
- claudeInvoker.invokeViaBackgroundSession (cognitive 22) src/frameworks/claude/claudeInvoker.ts:590
- AiInsightsSessionClaudeGateway.readAnswer (cognitive 22) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:79
- REDACTED.updateLoadingStateUI (cognitive 21) REDACTED:593
- runClaudeReviewJob.usecase.runClaudeReviewJob (cognitive 21) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52
- stats.routes.statsRoutes (cognitive 21) src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58
- statsCharts.drawScoreDistributionChart (cognitive 19) src/dashboard/modules/statsCharts.js:462
- developerSheet.drawRadarChart (cognitive 19) src/dashboard/modules/developerSheet.js:286
- UpdateProjectConfigUseCase.execute (cognitive 19) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:159
- addAction.usecase.validateAction (cognitive 19) src/modules/review-execution/usecases/mcp/addAction.usecase.ts:25
- constrainActionSurface.constrainActionSurface (cognitive 18) src/modules/review-execution/services/constrainActionSurface.ts:20
- connectEmberStream (cognitive 18) src/dashboard/modules/emberChat.js:105
- REDACTED.renderReview (cognitive 17) REDACTED:815
- github.controller.handleGitHubPullRequestReviewHook (cognitive 17) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:135
- sizeBlocks.routes.sizeBlocksRoutes (cognitive 17) REDACTED:50
- WorktreePanelPresenter.present (cognitive 17) src/modules/worktree-management/interface-adapters/presenters/worktreePanel.presenter.ts:155
- routes.registerRoutes (cognitive 16) REDACTED:200
- AddProjectStep.execute (cognitive 16) src/modules/setup-wizard/usecases/steps/addProject.step.ts:15
- computeInsightsWithPersistence.usecase.reconcileDiffStatsFromWindow (cognitive 16) src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:157
- REDACTED
- REDACTED
- REDACTED
- Change coupling clique: eventFilter.ts, github.controller.ts, gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits REDACTED:187
- Duplication concentrated across 11 sibling directories (21 clone groups) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11
- Duplicated block (157 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:110
- Duplicated block with local edits (87 matched lines × 2 locations) src/dashboard/modules/mrSheet.js:207
- Duplicated block (81 lines × 2 locations) REDACTED:621
- Duplicated block (68 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:313
- Duplicated block with local edits (55 matched lines × 2 locations) src/dashboard/modules/emberAvatarRenderer.js:26
- Duplicated block with local edits (48 matched lines × 2 locations) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:66
- Duplicated block (47 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:397
- Duplicated block (43 lines × 2 locations) REDACTED:57
- Duplicated block (41 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:486
- Duplicated block with local edits (38 matched lines × 2 locations) src/dashboard/modules/developerSheet.js:112
- Duplicated block with local edits (37 matched lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:66
- Duplicated block (35 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:695
- Duplicated block with local edits (34 matched lines × 2 locations) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11
- Duplicated block (34 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:227
- Duplicated block (33 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:304
- Duplicated block with local edits (30 matched lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/setPhase.handler.ts:18
- Duplicated block with local edits (27 matched lines × 2 locations) src/modules/statistics-insights/usecases/insights/buildAiInsightsPrompt.ts:21
- Duplicated block (23 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/getThreads.handler.ts:8
- Duplicated block (22 lines × 2 locations) src/modules/review-execution/services/contextActionsExecutor.ts:89
- Duplicated block (21 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:153
- Duplicated block (19 lines × 2 locations) src/dashboard/modules/insightsReport.js:82
- Duplicated block (18 lines × 3 locations) src/dashboard/modules/statsCharts.js:270
- Duplicated block with local edits (18 matched lines × 2 locations) src/modules/review-execution/usecases/mcp/addAction.usecase.ts:88
- Duplicated block with local edits (16 matched lines × 2 locations) src/frameworks/settings/runtimeSettings.ts:77
- Duplicated block (16 lines × 3 locations) src/modules/cli-configuration/usecases/cli/addRepositoriesToConfig.usecase.ts:17
- Duplicated block (15 lines × 2 locations) src/dashboard/modules/statsCharts.js:423
- Complex function handleGitLabWebhook (cyclomatic 42, cognitive 86) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266
- Complex function validateAndEnrichConfig (cyclomatic 39, cognitive 42) src/frameworks/config/configLoader.ts:178
- Complex function handleGitHubWebhook (cyclomatic 34, cognitive 47) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374
- Complex function extractPatch (cyclomatic 33, cognitive 44) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61
- Complex function parseProjectConfig (cyclomatic 27, cognitive 29) src/config/projectConfig.ts:195
- Complex function (anonymous) (cyclomatic 26, cognitive 29) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:154
- Complex function parseReviewOutput (cyclomatic 25, cognitive 30) REDACTED:47
- Complex function renderMrSheetContent (cyclomatic 23, cognitive 17) src/dashboard/modules/mrSheet.js:25
- Complex function executeInit (cyclomatic 19, cognitive 28) src/main/commands/init.command.ts:68
- Complex function execute (cyclomatic 19, cognitive 28) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48
- Complex function mergeConfig (cyclomatic 19, cognitive 26) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101
- Complex function runClaudeReviewJob (cyclomatic 19, cognitive 21) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52
- Complex function scan (cyclomatic 18, cognitive 24) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33
- Complex function (anonymous) (cyclomatic 17, cognitive 25) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:23
- Complex function invokeViaBackgroundSession (cyclomatic 16, cognitive 24) src/frameworks/claude/claudeInvoker.ts:590
- Complex function buildContext (cyclomatic 16, cognitive 15) src/tests/acceptance/183-setup-wizard.acceptance.test.ts:100
- Complex function drawScoreTrendChart (cyclomatic 15, cognitive 21) src/dashboard/modules/statsCharts.js:108
- Complex function buildPayload (cyclomatic 15, cognitive 17) src/tests/factories/projectConfig.factory.ts:18
- Complex function updateAggregatesForNewReview (cyclomatic 15, cognitive 14) src/modules/statistics-insights/usecases/stats/addReviewStats.usecase.ts:90
- Complex function readAnswer (cyclomatic 14, cognitive 25) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:79
- src/dashboard/modules/i18n.js: 920 lines of code src/dashboard/modules/i18n.js:1
- REDACTED: 844 lines of code REDACTED:1
- src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts: 786 lines of code src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:1
- src/frameworks/claude/claudeInvoker.ts: 761 lines of code src/frameworks/claude/claudeInvoker.ts:1
- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts: 741 lines of code src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:1
- src/dashboard/modules/statsCharts.js: 594 lines of code src/dashboard/modules/statsCharts.js:1
- src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts: 533 lines of code src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:1
- src/dashboard/modules/insightsReport.js: 493 lines of code src/dashboard/modules/insightsReport.js:1
- src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts: 461 lines of code src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:1
- src/frameworks/queue/pQueueAdapter.ts: 457 lines of code src/frameworks/queue/pQueueAdapter.ts:1
- src/dashboard/modules/worktreePanel.js: 438 lines of code src/dashboard/modules/worktreePanel.js:1
- src/dashboard/modules/animations.js: 401 lines of code src/dashboard/modules/animations.js:1
- This test file cannot be loaded src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16
- The declared test suite includes a file that cannot be loaded src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16
- Dead file (~7 LoC) src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts
- Unused dependency '@hono/node-server'
- Unused dependency '@stryker-mutator/vitest-runner'
- Unused dependency 'animejs'
- Third-party script without Subresource Integrity REDACTED:11
- Redirected process stream is never drained (deadlock) src/modules/supervisor-management/interface-adapters/gateways/supervisor.cli.gateway.ts:34
Minor — 119 finding(s)
- Mock-dominated test: should pass onLine callback to watchFile in follow mode src/tests/units/usecases/cli/readLogs.usecase.test.ts:68
- Mock-dominated test: enqueues the followup with sourceBranch and targetBranch from TrackedMr when MR is tracked src/tests/units/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.test.ts:196
- Mock-dominated test: should load context from file and register it src/tests/units/mcp/mcpServerStdio.test.ts:147
- Mock-dominated test: should skip loading if context is already registered src/tests/units/mcp/mcpServerStdio.test.ts:179
- Mock-dominated test: should use followup agents when jobType is followup src/tests/units/mcp/mcpServerStdio.test.ts:196
- Mock-dominated test: should log message and skip when no repositories found src/tests/units/main/executeDiscover.test.ts:48
- Mock-dominated test: should not write config when user selects nothing src/tests/units/main/executeDiscover.test.ts:63
- Mock-dominated test: invokes fetch on the running server port when daemon is alive src/tests/units/main/executeFollowupImportants.test.ts:49
- Mock-dominated test: should exit with code 1 when Node version is too low src/tests/units/main/executeInit.test.ts:57
- Mock-dominated test: should exit with code 1 when Claude CLI is not installed src/tests/units/main/executeInit.test.ts:76
- Mock-dominated test: should ask to overwrite when config already exists src/tests/units/main/executeInit.test.ts:96
- Mock-dominated test: should skip overwrite prompt in --yes mode src/tests/units/main/executeInit.test.ts:114
- Mock-dominated test: should only ask gitlab username when platform is gitlab src/tests/units/main/executeInit.test.ts:134
- Mock-dominated test: should only ask github username when platform is github src/tests/units/main/executeInit.test.ts:149
- Mock-dominated test: should ask both usernames when platform is both src/tests/units/main/executeInit.test.ts:164
- Mock-dominated test: should use defaults without prompting src/tests/units/main/executeInit.test.ts:181
- Mock-dominated test: should always generate both secrets regardless of platform src/tests/units/main/executeInit.test.ts:209
- Mock-dominated test: should call selectRepositories with discovered repos in interactive mode src/tests/units/main/executeInit.test.ts:293
- Mock-dominated test: should output initial lines and set up watcher in follow mode src/tests/units/main/executeLogs.test.ts:49
- Mock-dominated test: should call exit(1) when stop fails src/tests/units/main/executeStop.test.ts:51
- Mock-dominated test: rejects a fresh review and broadcasts budget-exceeded when enforceBudget returns accepted=false src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:403
- Mock-dominated test: responds 401 when signature verification fails src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:761
- Mock-dominated test: ignores a non-PR event type src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:777
- Mock-dominated test: ignores a review request when the repository is not configured src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:812
- Mock-dominated test: responds 202 pending-confirmation when the gate parks the review src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:1137
- Duplicated predicate src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:144
- Duplicated predicate REDACTED:36
- Duplicated predicate src/main/mcpDependencies.ts:55
- Duplicated predicate src/dashboard/modules/insightsReport.js:471
- Duplicated predicate src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:125
- Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:500
- Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:518
- Duplicated predicate src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:94
- Duplicated predicate src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:307
- Duplicated predicate src/dashboard/modules/statsCharts.js:116
- Duplicated predicate src/modules/statistics-insights/entities/stats/keyInsights.ts:84
- Duplicated predicate src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:29
- Duplicated predicate src/frameworks/config/configLoader.ts:190
- Duplicated predicate src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.github.gateway.ts:8
- Duplicated predicate src/dashboard/modules/desktopNotifications.js:38
- Duplicated predicate src/config/projectConfig.ts:45
- Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:485
- Duplicated predicate src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:43
- Duplicated predicate src/dashboard/modules/keyInsights.js:50
- Interpolated log message defeats structured logging src/modules/supervisor-management/usecases/checkSupervisorAndRespawn.usecase.ts:69
- Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:279
- Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:288
- Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:299
- Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:308
- Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:85
- Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:96
- Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:103
- Console output used as the logging channel REDACTED:64
- Console output used as the logging channel src/main/shared/cliConstants.ts:16
- Console output used as the logging channel src/main/commands/setup.command.ts:171
- Console output used as the logging channel src/frameworks/settings/runtimeSettings.ts:56
- Console output used as the logging channel src/frameworks/settings/runtimeSettings.ts:218
- Console output used as the logging channel src/frameworks/config/configLoader.ts:135
- Console output used as the logging channel src/frameworks/config/configLoader.ts:140
- Silent fallback default in catch src/config/projectConfig.ts:334
- Silent fallback default in catch src/dashboard/modules/html.js:29
- Silent fallback default in catch src/main/commands/setup.command.ts:119
- Silent fallback default in catch src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:173
- Silent fallback default in catch src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:108
- redundant comment src/frameworks/claude/claudeInvoker.ts:485
- redundant comment src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts:103
- Fat interface: InitDependencies (18 required operations) src/main/commands/init.command.ts:42
- No named authorization policies REDACTED:72
- Deprecated: @ungap/structured-clone REDACTED:1758
- Outdated (npm): pino-pretty REDACTED:70
- Projects may be oversized for their cohesion
- Pass-through layer src/modules/review-execution/interface-adapters/gateways/jobContext.memory.gateway.ts:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ADRs not easily discoverable
- README/code drift docs/architecture/current.md:103
- No SAST REDACTED:6
- No dependency-update automation REDACTED:59
- Unused export 'getLogsByLevel' src/frameworks/logging/logBuffer.ts:56
- Unused export 'logDebug' src/frameworks/logging/logBuffer.ts:91
- Unused export 'getJobProgress' src/frameworks/queue/pQueueAdapter.ts:522
- Unused export 'getWsClientsCount' REDACTED:24
- Unused export 'ClaudeSessionStatus' src/modules/claude-invocation/entities/claudeSession/claudeSession.schema.ts:36
- Unused export 'markTimedOut' src/modules/claude-invocation/entities/claudeSession/claudeSession.ts:37
- Unused export 'SessionCompletionSource' src/modules/claude-invocation/entities/sessionCompletion/sessionCompletion.schema.ts:12
- Unused export 'EDITABLE_PROJECT_CONFIG_KEYS' src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:7
- Unused export 'THREADS_AGENT' src/modules/review-execution/entities/progress/agentDefinition.type.ts:6
- Unused export 'REPORT_AGENT' src/modules/review-execution/entities/progress/agentDefinition.type.ts:7
- Unused export 'safeParseReviewAction' src/modules/review-execution/entities/reviewAction/reviewAction.guard.ts:9
- Unused export 'parseReviewActionCollection' src/modules/review-execution/entities/reviewAction/reviewAction.guard.ts:12
- Unused export 'AddLabelAction' src/modules/review-execution/entities/reviewAction/reviewAction.ts:17
- Unused export 'PostInlineCommentAction' src/modules/review-execution/entities/reviewAction/reviewAction.ts:18
- Unused export 'safeParseReviewContextResult' src/modules/review-execution/entities/reviewContext/reviewContextResult.guard.ts:17
- Unused export 'BackfilledReviewResult' src/modules/review-execution/entities/reviewContext/reviewContextResult.schema.ts:24
- Unused export 'formatInstructionsForPrompt' src/modules/review-execution/services/agentInstructionsBuilder.ts:49
- Unused export 'ConfirmAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:7
- Unused export 'ChoiceAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:8
- Unused export 'MultiSelectAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:9
- Unused export 'StepStartedEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:68
- Unused export 'StepCompletedEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:69
- Unused export 'AwaitingInputEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:70
- Unused export 'InstructionsBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:71
- Unused export 'WarningBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:72
- Unused export 'ResumeBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:73
- Unused export 'DoneBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:74
- Unused export 'AiDeveloperInsight' src/modules/statistics-insights/entities/insight/aiInsight.ts:9
- Unused export 'AiTeamInsight' src/modules/statistics-insights/entities/insight/aiInsight.ts:11
- Unused export 'safeParseCategoryBreakdown' src/modules/statistics-insights/entities/stats/categoryBreakdown.guard.ts:14
- Unused export 'RecalculateBody' src/modules/statistics-insights/entities/stats/recalculateBody.guard.ts:10
- Unused export 'DegradedReasonKind' src/modules/worktree-management/entities/worktree/worktreeHealth.schema.ts:22
- No app-layer HTTPS enforcement detected src/main/server.ts:292
- Not all async functions that make a request accept an AbortSignal
Minor — 12 finding(s)
- Outdated (npm): @fastify/static
- Outdated (npm): @fastify/websocket
- Outdated (npm): @hono/node-server
- Outdated (npm): @inquirer/prompts
- Outdated (npm): @modelcontextprotocol/sdk
- Outdated (npm): animejs
- Outdated (npm): dotenv
- Outdated (npm): fastify
- Outdated (npm): p-queue
- Outdated (npm): pino
- Outdated (npm): zod
- doc comments repeat the names src/frameworks/claude/progressParser.ts:171
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-93387680b70b40ed9830f8d0cc51b38a/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-93387680b70b40ed9830f8d0cc51b38a/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/dashboard/vendor . | 64 | 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 | 28 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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. semgrep could not parse 1 file(s) — `docs/.vitepress/theme/index.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |