Public report of DGouron/review-flow, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 17:56 UTC · Survey ID cd_d176723b246847318fc6c58a2cf6ff67

DGouron/review-flow

Measured 22 October 2026, 17:33 UTC, at code version a89a6e6

CAI score 44out of 100 At risk Down 7 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Architecture 78 Adequate Code Health 69 Adequate Performance 60 Adequate Maturity 55 Adequate Accessibility 51 Adequate Production Readiness 49 Weak Security and Compliance 33 Weak

A medium codebase: 43,354 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Security and Compliance, 33

Findings by how serious they are

37 critical 429 serious 172 minor

4 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 17:33 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

83of 88 dimensions measured by tools. The other 5 are advisory notes from an AI model, which explain the code but don't count towards the score.
610of 638 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
88dimensions across 7 lenses, read from 43,354 lines of product code in 1 project.
Chapters

Executive summary

DGouron/review-flow scores 44 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Security and Compliance, which scores 33 and is rated Weak. Its Dependency Vulnerabilities dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 46 REDACTED finding(s) in Static Analysis (SAST) and to protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do, and if Security and Compliance rose to 70, the score would rise from 44 to about 53.

37 findings are critical: 15 in Dependency Vulnerabilities, 11 in Static Analysis (SAST), ten in Forms & labels and one in Secrets (history).

Watchdog couldn't measure Navigability, Captive dependencies and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 43,354 lines, which would take an estimated 0.8 person-years, around €110,000, to rebuild.

Code Health 69 Adequate Architecture 78 Adequate, capped by Project Cohesion Maturity 55 Adequate, capped by Documentation accuracy Production Readiness 49 Weak, capped by Security & performance tooling and Outbound HTTP resilience Security and Compliance 33 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing and Access Controls Accessibility 51 Adequate, capped by Forms & labels and Visual & motion safety Performance 60 Adequate

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 33 · counts for 46%Production Readiness 49 · counts for 25%Accessibility 51 · counts for 14%Maturity 55 · counts for 8%Performance 60 · counts for 4%Code Health 69 · counts for 2%Architecture 78 · counts for 1%

If Security and Compliance rose from 33 to 70, the lowest score rated Strong, the score would rise from 44 to about 53.

Code composition: what the lines of code are
Product code 38%Tests 62%
New since the last survey: 194 findings

These 194 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 117 findings

These 117 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.

  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Supply-chain Provenance & Signing 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
  • Slice cohesion · Cross-slice coupling: handleReviewRequestPush_usecase → triggerReview_usecase src/modules/review-execution/usecases/handleReviewRequestPush.usecase.ts
  • Async & latency hygiene · Sync-over-async blocking src/frameworks/settings/runtimeSettings.ts
  • Async & latency hygiene · Sync-over-async blocking src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts
  • Async & latency hygiene · Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts
  • Async & latency hygiene · Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts
  • Async & latency hygiene · Sync-over-async blocking REDACTED
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€36,000 to €180,000, for 605 to 1,919 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 43,354 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 46 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (3).
Raises the score by about 5 points · Medium effort · Static Analysis (SAST)
2
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
Raises the score by about 9 points · Medium effort · Access Controls
3
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.
Raises the score by about 4 points · Medium effort · Web-Security Posture

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Security and Compliance, at 33 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 46 REDACTED finding(s) in Static Analysis (SAST). Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort, because it clears the 46 Static Analysis (SAST) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 171,122 lines over the last 90 days, which is about 693,995 lines a year. At that pace, the extra work comes to an estimated 34.7 to 231.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

611 modules, with 931 dependencies between them. Every module uses only modules listed above it, so there are no loops.

The table shows the 40 modules with the most connections; 571 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 modules.claude-invocation.entities.billingState.environment_gateway2 modules.claude-invocation.entities.claudeSession.claudeSession_gateway3 modules.cli-configuration.entities.projectConfig.projectConfig_gateway4 modules.ember-chat.entities.emberMemory.emberMemory_gateway5 modules.platform-integration.entities.noteComment.noteCommentPost_gateway6 modules.platform-integration.entities.threadFetch.threadFetch_gateway7 modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway8 modules.review-execution.entities.progress.progress_type9 modules.review-execution.entities.review.reviewFile_gateway10 modules.review-execution.entities.reviewContext.reviewContext11 modules.review-execution.services.contextActionsExecutor12 modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway13 modules.tracking.entities.tracking.mrTrackingData14 modules.tracking.entities.tracking.trackedMr15 modules.worktree-management.entities.gitCommand.gitCommand_gateway16 modules.worktree-management.entities.worktree.worktree_schema17 shared.foundation.usecase_base18 tests.stubs.fastifyRequest_stub19 modules.review-execution.entities.job.reviewJob20 modules.review-execution.entities.progress.progress_gateway21 modules.review-execution.entities.reviewContext.reviewContext_gateway22 modules.setup-wizard.entities.wizardContext.wizardContext23 modules.statistics-insights.entities.stats.stats_gateway24 modules.tracking.entities.tracking.reviewRequestTracking_gateway25 modules.worktree-management.usecases26 frameworks.claude.claudeInvoker27 main.commands28 modules.review-execution.services29 modules.review-execution.usecases.executeReview_usecase30 modules.review-execution.usecases.gateClaudeInvocation_usecase31 modules.review-execution.usecases.mcp32 modules.setup-wizard.entities.setupStep.setupStep33 main.dependencies34 main.executeReviewWiring35 modules.platform-integration.interface-adapters.controllers.webhook.github_controller36 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller37 modules.review-execution.usecases38 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes39 main40 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.cli-configuration.entities.projectConfig.projectConfig_gateway
4 modules.ember-chat.entities.emberMemory.emberMemory_gateway
5 modules.platform-integration.entities.noteComment.noteCommentPost_gateway
6 modules.platform-integration.entities.threadFetch.threadFetch_gateway
7 modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway
8 modules.review-execution.entities.progress.progress_type
9 modules.review-execution.entities.review.reviewFile_gateway
10 modules.review-execution.entities.reviewContext.reviewContext
11 modules.review-execution.services.contextActionsExecutor
12 modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway
13 modules.tracking.entities.tracking.mrTrackingData
14 modules.tracking.entities.tracking.trackedMr
15 modules.worktree-management.entities.gitCommand.gitCommand_gateway
16 modules.worktree-management.entities.worktree.worktree_schema
17 shared.foundation.usecase_base
18 tests.stubs.fastifyRequest_stub
19 modules.review-execution.entities.job.reviewJob1
20 modules.review-execution.entities.progress.progress_gateway2
21 modules.review-execution.entities.reviewContext.reviewContext_gateway4
22 modules.setup-wizard.entities.wizardContext.wizardContext1
23 modules.statistics-insights.entities.stats.stats_gateway1
24 modules.tracking.entities.tracking.reviewRequestTracking_gateway11
25 modules.worktree-management.usecases124
26 frameworks.claude.claudeInvoker111111
27 main.commands1
28 modules.review-execution.services12321
29 modules.review-execution.usecases.executeReview_usecase111313
30 modules.review-execution.usecases.gateClaudeInvocation_usecase11
31 modules.review-execution.usecases.mcp11
32 modules.setup-wizard.entities.setupStep.setupStep1
33 main.dependencies1111111
34 main.executeReviewWiring1111111
35 modules.platform-integration.interface-adapters.controllers.webhook.github_controller111111
36 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller111111
37 modules.review-execution.usecases11114
38 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes11111
39 main2321141
40 modules.platform-integration.interface-adapters.controllers.webhook2211
Uses a module listed above itPart of a loopThe module itself
1 modules.claude-invocation.entities.billingState.environment_gateway2 modules.claude-invocation.entities.claudeSession.claudeSession_gateway3 modules.cli-configuration.entities.projectConfig.projectConfig_gateway4 modules.ember-chat.entities.emberMemory.emberMemory_gateway5 modules.platform-integration.entities.noteComment.noteCommentPost_gateway6 modules.platform-integration.entities.threadFetch.threadFetch_gateway7 modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway8 modules.review-execution.entities.progress.progress_type9 modules.review-execution.entities.review.reviewFile_gateway10 modules.review-execution.entities.reviewContext.reviewContext11 modules.review-execution.services.contextActionsExecutor12 modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway13 modules.tracking.entities.tracking.mrTrackingData14 modules.tracking.entities.tracking.trackedMr15 modules.worktree-management.entities.gitCommand.gitCommand_gateway16 modules.worktree-management.entities.worktree.worktree_schema17 shared.foundation.usecase_base18 tests.stubs.fastifyRequest_stub19 modules.review-execution.entities.job.reviewJob20 modules.review-execution.entities.progress.progress_gateway21 modules.review-execution.entities.reviewContext.reviewContext_gateway22 modules.setup-wizard.entities.wizardContext.wizardContext23 modules.statistics-insights.entities.stats.stats_gateway24 modules.tracking.entities.tracking.reviewRequestTracking_gateway25 modules.worktree-management.usecases26 frameworks.claude.claudeInvoker27 main.commands28 modules.review-execution.services29 modules.review-execution.usecases.executeReview_usecase30 modules.review-execution.usecases.gateClaudeInvocation_usecase31 modules.review-execution.usecases.mcp32 modules.setup-wizard.entities.setupStep.setupStep33 main.dependencies34 main.executeReviewWiring35 modules.platform-integration.interface-adapters.controllers.webhook.github_controller36 modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller37 modules.review-execution.usecases38 modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes39 main40 modules.platform-integration.interface-adapters.controllers.webhookmodules.claude-invocation.entities.billingState.environment_gateway1modules.claude-invocation.entities.claudeSession.claudeSession_gateway2modules.cli-configuration.entities.projectConfig.projectConfig_gateway3modules.ember-chat.entities.emberMemory.emberMemory_gateway4modules.platform-integration.entities.noteComment.noteCommentPost_gateway5modules.platform-integration.entities.threadFetch.threadFetch_gateway6modules.platform-integration.interface-adapters.gateways.changedFilesFetch_github_gateway7modules.review-execution.entities.progress.progress_type8modules.review-execution.entities.review.reviewFile_gateway9modules.review-execution.entities.reviewContext.reviewContext10modules.review-execution.services.contextActionsExecutor11modules.shared-kernel.entities.diffStats.diffStatsFetch_gateway12modules.tracking.entities.tracking.mrTrackingData13modules.tracking.entities.tracking.trackedMr14modules.worktree-management.entities.gitCommand.gitCommand_gateway15modules.worktree-management.entities.worktree.worktree_schema16shared.foundation.usecase_base17tests.stubs.fastifyRequest_stub18modules.review-execution.entities.job.reviewJob19modules.review-execution.entities.progress.progress_gateway20modules.review-execution.entities.reviewContext.reviewContext_gateway21modules.setup-wizard.entities.wizardContext.wizardContext22modules.statistics-insights.entities.stats.stats_gateway23modules.tracking.entities.tracking.reviewRequestTracking_gateway24modules.worktree-management.usecases25frameworks.claude.claudeInvoker26main.commands27modules.review-execution.services28modules.review-execution.usecases.executeReview_usecase29modules.review-execution.usecases.gateClaudeInvocation_usecase30modules.review-execution.usecases.mcp31modules.setup-wizard.entities.setupStep.setupStep32main.dependencies33main.executeReviewWiring34modules.platform-integration.interface-adapters.controllers.webhook.github_controller35modules.platform-integration.interface-adapters.controllers.webhook.gitlab_controller36modules.review-execution.usecases37modules.tracking.interface-adapters.controllers.http.mrTrackingAdvanced_routes38main39modules.platform-integration.interface-adapters.controllers.webhook4012411111241111111123211113131111111111111111111111111111111111141111123211412211+571 more modules (most-connected shown)

At a glance — Code Health · 69% · Adequate ·

The Good
D3 · TypeScript God Classes 8.7 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 9.0 R1 · React / TS Type Safety 9.6 R10 · React / TS Code Duplication 8.5 R2 · React / TS Cyclomatic Complexity 9.2 R3 · React / TS Large Files 9.2 R7 · React / TS Dead Code 8.4 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 10.0
The Bad
D1 · TypeScript Cyclomatic Complexity 6.5 D2 · TypeScript Cognitive Complexity 6.2 X13 · Repo Undrained process stream 5.7 X2 · Repo Cancellation propagation 6.4 X3 · Repo Exception handling 5.2 X4 · Repo Structured logging 6.1

At a glance — Architecture · 78% · Adequate · gated by D26 ·

The Good
D6 · TypeScript Cohesion (LCOM4) 9.8 D7 · TypeScript Architectural Integrity 10.0 D23 · TypeScript Boundary Type-Coupling 10.0 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 7.2 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 R9 · React / TS Circular Imports 10.0
The Bad
AX7 · Repo Slice cohesion 5.9
The Ugly
D22 · TypeScript Internal API Consistency 2.0 D26 · TypeScript Project Cohesion 0.0

At a glance — Maturity · 55% · Adequate · gated by M4 ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 9.6 D19 · TypeScript Documentation Quality 10.0 D20 · TypeScript ADR Quality 8.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M2 · Repo Architecture documentation 7.0 M3 · Repo Folder & project structure 10.0
The Ugly
M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 49% · Weak · gated by P3, P7 ·

The Good
D8 · TypeScript Code Coverage 10.0 D9 · TypeScript Test Distribution 9.0 D10 · TypeScript Test Quality 10.0 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 9.4 D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 8.0 P6 · Repo Release Hygiene 10.0 P9 · Repo Domain vs controller coverage 9.8 R4 · React / TS Test Coverage 9.8 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 7.5
The Bad
P4 · Repo Deployment & Rollback 5.0
The Ugly
P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 33% · Weak · gated by D29, D30, D36, C2 ·

The Good
D28 · TypeScript Secrets (history) 9.0 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Bad
S1 · Repo Web-Security Posture 6.0 X24 · Repo Document value interpolated into markup unescaped 6.7
The Ugly
D29 · TypeScript Static Analysis (SAST) 0.6 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0 C2 · Repo Access Controls 0.0

At a glance — Accessibility · 51% · Adequate · gated by AC2, AC6 ·

The Good
AC1 · Repo Text alternatives 10.0 AC3 · Repo Page structure 10.0 AC4 · Repo Keyboard semantics 10.0 AC5 · Repo ARIA correctness 10.0
The Ugly
AC2 · Repo Forms & labels 3.7 AC6 · Repo Visual & motion safety 1.0 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection63High / Critical
A03:2025 — Software Supply Chain Failures31High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

First, implement a global authentication guard with explicit public opt-outs and named role rules to enforce default-deny access controls. Next, resolve the 46 missing authorization findings in static analysis and the 12 high-severity dependency vulnerabilities, prioritizing the specified route and lock files. Then, secure third-party scripts by pinning versions with integrity hashes or restricting origins via Content Security Policy, while vendoring assets where possible. Finally, integrate a SAST step into the CI pipeline to automatically fail builds on security regressions.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 46 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (4), REDACTED (3).+5.3 ptsMediumStatic Analysis (SAST)
Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.+9.1 ptsMediumAccess Controls
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.+4.4 ptsMediumWeb-Security Posture
Resolve the 12 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12).+3.4 ptsMediumDependency Vulnerabilities
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.3 ptsLowSecrets (history)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.3 ptsLowStatic Analysis (SAST)
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED.+1.3 ptsLowDependency Vulnerabilities
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2).+1.3 ptsLowDependency Vulnerabilities

File quality

Per-file score 0–10 — a quality signature. Of 98 files carrying findings, judged against the Production bar: 4% slop · 42% mixed · 54% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
src/frameworks/claude/claudeInvoker.ts5.9MixedCognitive Complexity: claudeInvoker.invokeViaBackgroundSession (cognitive 22)
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 37

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.

Serious — 429

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.

Minor — 172

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 4

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

Watchdog 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. 83 of 88 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 1.0 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 88 dimensions across the health lenses
D1D2D3D6D7D8D9D10D11D12D13D14D15D17D19D20D21D22D23D26D28D29D30D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX5AX6AX7C2GD1IC1M1M2M3M4P1P10P2P3P4P6P7P9PF3R1R10R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 610 of 638 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a164ac-aac1-7a40-a87e-b4f10c1f2250.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • 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.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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 — Watchdog 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/entities/job/jobContext.gateway.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.
  • AXR1 Runtime accessibility — not measured this run — Watchdog 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 120 further occurrence(s) are not listed individually; the score already reflects all 160.
  • 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 — Watchdog measured this, but not all of it. What it 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 — Watchdog measured this, but not all of it. What it 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. 91 further occurrence(s) are not listed individually; the score already reflects all 131.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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 Watchdog's 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 — Watchdog runs 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • 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.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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.

The LLM boundary

LLM-set scores this run (5): D19, D20, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.5 / 10Adequate✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Prevented

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.

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

+ 21 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.2 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Prevented

43 method(s) exceeded the cognitive complexity threshold of 15; the worst was gitlab.controller.handleGitLabWebhook at 86.

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

+ 33 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.7 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Prevented

18 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: routes.registerRoutes · ×13REDACTED:200
FileTooLong: REDACTED · ×5REDACTED

What to do

  1. 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).
  2. 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).
  3. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

2 of 99 classes have LCOM4 above 3.

Low cohesion: StubClaudeSessionGateway (LCOM4 5) · ×2src/tests/stubs/claudeSession.stub.ts:23

What to do

  1. 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).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

All 1 mechanizable ADR(s) are enforced: 1 by analyzers, 0 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

D8 · Code Coverage10.0 / 10Stronggated by 32 serious findings✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

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).

Low coverage: src/mcpServer.ts · ×32src/mcpServer.ts:1

What to do

  1. 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).
  2. Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D9 · Test Distribution9.0 / 10Strong✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

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

  1. 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.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4407 tests.

Mock-dominated test: rejects a fresh review and broadcasts budget-exceeded when enforceBudget returns accepted=false · ×28src/tests/units/interface-adapters/controllers/webhook/gitlab.controller.test.ts:558

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

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).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Verified

12 outdated direct production npm dependency(ies) of 12 graded, 0 pinning defect(s), across 1 package.json (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.

Deprecated: @ungap/structured-cloneREDACTED:1758
Outdated (npm): pino-prettypackage.json:70
Outdated (npm): @fastify/static · ×11

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 12 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 12 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 14 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 13 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

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)

Hotspot: REDACTED · ×13REDACTED:3140

What to do

  1. 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).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

This repository is exceptionally well documented: the READMEs of each directory are complete for that tier, with installation, usage, contribution guidance, and license; architecture/design docs cover every document in a dedicated architecture/index.md index (including current and target architectures, multi-LLM analysis, worktree lifecycle) plus an internal-outside-facing overview; all documents are well structured with headings and ordered outlines. Reviewflow's documentation is clear and complete for a review automation tool: the READMEs (quick-start, project-config, deployment) cover installation, prerequisites, configuration, skills setup, and a full end-to-end setup wizard; architecture/Docs markdown files provide detailed bounded-context modeling, Vaughn Vernon context maps, event-flow scenarios, and quality-metrics guidance. The document outline is visible in every file — all sections present — so no section is flagged as missing. (10 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR QualityStrong◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

Evaluated 1 ADR(s) individually; mean quality 8.0/10 (consistently complete and clear). 0 flagged with a specific gap.

What to do

  1. Improve ADR Quality — currently 8.0/10. — Evaluated 1 ADR(s) individually; mean quality 8.0/10 (consistently complete and clear). 0 flagged with a specific gap.

Detailed fixes: d20_recommendation.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D22 · Internal API ConsistencyCritical◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Critical / 10 · rule-coverage 100% · ceiling Verified

1 API inconsistencies across 3 exposed types.

Redundant operations with identical signatures and likely overlapping intent. Both methods accept the same `ServerOptions` and return the same `Promise<FastifyInstance>`. It is unclear if one creates the instance and the other starts listening, or if they are duplicate entry points. This creates confusion for consumers regarding which method to use.

What to do

  1. Resolve the 1 Redundant operations with identical signatures and likely overlapping… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

No domain types leak across context boundaries (12 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. 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).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

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.

REDACTED
REDACTED

What to do

  1. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)0.6 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.6 / 10 · rule-coverage 100% · ceiling Documented

63 finding(s): 0 critical, 11 high, 52 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. 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).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

23 finding(s): 2 critical, 13 high, 8 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 12 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 issue-level).
  2. 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).
  3. Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: github.controller.ts↔gitlab.controller.ts 76%; eventFilter.ts↔github.controller.ts 73%; eventFilter.ts↔gitlab.controller.ts 64%

Change coupling clique: eventFilter.ts, github.controller.ts, gitlab.controller.tssrc/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts

What to do

  1. 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).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels3.7 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • 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 structure10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC4 · Keyboard semantics10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.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 enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • 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.

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 composition7.2 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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 cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `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 cohesion5.9 / 10Adequate✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

  • `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 Controls0.0 / 10Critical✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • This repository serves requests — Fastify() (src/main/server.ts:172) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/main/server.ts:172

What to do

  • Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `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)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation7.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • 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 structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • 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 package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/current.md:103
  • docs/architecture/index.md links to `./current`, but `docs/architecture/current` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/index.md:20
  • docs/architecture/index.md links to `./target`, but `docs/architecture/target` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/index.md:21
  • docs/architecture/index.md links to `./mcp/specification`, but `docs/architecture/mcp/specification` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/index.md:27
  • docs/architecture/index.md links to `./mcp/architecture`, but `docs/architecture/mcp/architecture` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/index.md:28
  • docs/architecture/multi-llm-analysis.md names `src/frameworks/claude/claudeInsightsInvoker.ts`, but no file or folder `src/frameworks/claude/claudeInsightsInvoker.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/multi-llm-analysis.md:12
  • docs/architecture/multi-llm-analysis.md names `src/services/threadActionsParser.ts`, but no file or folder `src/services/threadActionsParser.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/multi-llm-analysis.md:28
  • docs/architecture/multi-llm-analysis.md names `src/interface-adapters/controllers/http/settings.routes.ts`, but no file or folder `src/interface-adapters/controllers/http/settings.routes.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/architecture/multi-llm-analysis.md:35
  • docs/guide/index.md links to `./quick-start`, but `docs/guide/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/index.md:13
  • docs/guide/index.md links to `./project-config`, but `docs/guide/project-config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/index.md:14
  • docs/guide/index.md links to `./review-skills`, but `docs/guide/review-skills` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/index.md:15
  • docs/guide/index.md links to `./troubleshooting`, but `docs/guide/troubleshooting` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/index.md:16
  • docs/guide/index.md links to `/reference/config`, but `reference/config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/index.md:24
  • docs/reference/index.md links to `./config`, but `docs/reference/config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:11
  • docs/reference/index.md links to `./markers`, but `docs/reference/markers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:12
  • docs/reference/index.md links to `./ubiquitous-language`, but `docs/reference/ubiquitous-language` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/index.md:14
  • docs/reference/ubiquitous-language.md names `entities/actionExecution/`, but no file or folder `entities/actionExecution` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/ubiquitous-language.md:23
  • docs/reports/163-token-budget-cap.report.md documents the environment variable `BUDGET_FLOOR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/163-token-budget-cap.report.md:13
  • docs/reports/163-token-budget-cap.report.md documents the environment variable `BUDGET_CEILING`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/163-token-budget-cap.report.md:13
  • docs/reports/170-prebuilt-worktree-lifecycle.report.md names `entities/worktree/worktree.guard.ts`, but no file or folder `entities/worktree/worktree.guard.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/170-prebuilt-worktree-lifecycle.report.md:15
  • docs/reports/170-prebuilt-worktree-lifecycle.report.md names `entities/gitCommand/gitCommand.schema.ts`, but no file or folder `entities/gitCommand/gitCommand.schema.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/170-prebuilt-worktree-lifecycle.report.md:17
  • docs/reports/172-claude-agents-supervisor-lifecycle.report.md documents the environment variable `SUPERVISOR_CHECK_INTERVAL_MS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/172-claude-agents-supervisor-lifecycle.report.md:77
  • docs/reports/173-dashboard-worktree-panel.report.md names `dashboard/modules/worktreePanel`, but no file or folder `dashboard/modules/worktreePanel` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/173-dashboard-worktree-panel.report.md:54
  • docs/reports/177-dashboard-add-project-ui.report.md names `.dashboard-tab.is-entering`, but no file or folder `.dashboard-tab.is-entering` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/177-dashboard-add-project-ui.report.md:121
  • docs/reports/179-dashboard-project-settings-modal.report.md names `src/modules/cli-configuration/entities/projectConfig/projectConfig.schema.ts`, but no file or folder `src/modules/cli-configuration/entities/projectConfig/projectConfig.schema.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/179-dashboard-project-settings-modal.report.md:22
  • docs/reports/180-quality-threshold-block-approval-iter-B.report.md names `src/tests/units/modules/tracking/usecases/recordBypass.usecase.test.ts`, but no file or folder `src/tests/units/modules/tracking/usecases/recordBypass.usecase.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/180-quality-threshold-block-approval-iter-B.report.md:23
  • docs/reports/182-mark-pending-fix-as-merged.report.md names `src/tests/acceptance/182-mark-pending-fix-as-merged.acceptance.test.ts`, but no file or folder `src/tests/acceptance/182-mark-pending-fix-as-merged.acceptance.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/182-mark-pending-fix-as-merged.report.md:28
  • docs/reports/184-setup-wizard-dashboard-jarvis.report.md names `setup-state.json`, but no file or folder `setup-state.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/184-setup-wizard-dashboard-jarvis.report.md:65
  • docs/reports/189-ember-readonly-review-chat.report.md names `src/tests/acceptance/189-ember-readonly-review-chat.acceptance.test.ts`, but no file or folder `src/tests/acceptance/189-ember-readonly-review-chat.acceptance.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/189-ember-readonly-review-chat.report.md:9
  • docs/reports/189-ember-readonly-review-chat.report.md names `usecases/emberSession/emberSessionRegistry.ts`, but no file or folder `usecases/emberSession/emberSessionRegistry.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/189-ember-readonly-review-chat.report.md:25
  • docs/reports/189-ember-readonly-review-chat.report.md names `gateways/emberSessionTransport.claude.gateway.ts`, but no file or folder `gateways/emberSessionTransport.claude.gateway.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/189-ember-readonly-review-chat.report.md:30
  • docs/reports/189-ember-readonly-review-chat.report.md names `stubs/emberSessionTransport.stub.ts`, but no file or folder `stubs/emberSessionTransport.stub.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/189-ember-readonly-review-chat.report.md:39
  • docs/reports/189-ember-readonly-review-chat.report.md names `emberSessionTransport.claude.gateway.ts`, but no file or folder `emberSessionTransport.claude.gateway.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/189-ember-readonly-review-chat.report.md:56
  • docs/reports/197-trusted-actor-provenance-gate.report.md names `.acceptance.test.ts`, but no file or folder `.acceptance.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/197-trusted-actor-provenance-gate.report.md:76
  • docs/reports/197-trusted-actor-provenance-gate.report.md names `.test.ts`, but no file or folder `.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/197-trusted-actor-provenance-gate.report.md:76
  • docs/reports/199-review-output-egress-scan.report.md runs `yarn vitest run`, but no package.json declares a `vitest` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/199-review-output-egress-scan.report.md:64
  • docs/reports/203-bugs-found-by-category.report.md names `src/tests/units/services/statsService.category.test.ts`, but no file or folder `src/tests/units/services/statsService.category.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/203-bugs-found-by-category.report.md:28
  • docs/reports/203-bugs-found-by-category.report.md names `statsService.category.test.ts`, but no file or folder `statsService.category.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/203-bugs-found-by-category.report.md:63
  • docs/reports/204-analytics-overview-header.report.md names `statsService.summary.test.ts`, but no file or folder `statsService.summary.test.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/204-analytics-overview-header.report.md:22
  • docs/reports/215-mark-any-review-as-merged.report.md names `.badge.merged`, but no file or folder `.badge.merged` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reports/215-mark-any-review-as-merged.report.md:19

What to do

  • Reconcile the README with reality: docs/architecture/current.md names Fastify 4, but the manifest declares `fastify` ^5.0.0; docs/architecture/index.md links to `./current`, but `docs/architecture/current` does not exist; docs/architecture/index.md links to `./target`, but `docs/architecture/target` does not exist; docs/architecture/index.md links to `./mcp/specification`, but `docs/architecture/mcp/specification` does not exist; docs/architecture/index.md links to `./mcp/architecture`, but `docs/architecture/mcp/architecture` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • `src/dashboard/modules/teamTab.js` reports through `console.*` at line 328 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/dashboard/modules/teamTab.js:328
  • `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
  • `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
  • `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/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/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

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 tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • 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 2495 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.

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 & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

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 Watchdog 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 Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `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 coverage9.8 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.

Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.

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 hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `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 Safety9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.5 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • 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 Complexity9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • 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 Files9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • 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 Coverage9.8 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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. (×10) — src/modules/worktree-management/entities/worktree/worktree.schema.ts:1, src/mcpServer.ts:1, scripts/copyAssets.mjs:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • 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 Code8.4 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 94 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 (94 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 Hygiene7.5 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `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 correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream5.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

  • `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 classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation6.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 2/5 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
  • `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
  • `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
  • `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

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 guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped6.7 / 10Adequate✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `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. — src/dashboard/modules/mrSheet.js:191
  • `encodedMrId` is text this program did not author, and it is written into a script or style context through markup built here 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/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 built here 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 built here 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 knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • 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/dashboard/modules/tabBar.js:101, src/frameworks/claude/claudeInvoker.ts:240, src/frameworks/claude/claudeInvoker.ts:269, …
  • `.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
  • `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — REDACTED:895, REDACTED:47, src/modules/cli-configuration/usecases/cli/discoverRepositories.usecase.ts:85, …

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging6.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • `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
  • `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 39 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/modules/platform-integration/usecases/markReviewInProgress.usecase.ts:39
  • `warn` at line 57 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/modules/platform-integration/usecases/markReviewInProgress.usecase.ts:57
  • `warn` at line 31 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/modules/platform-integration/usecases/markReviewDone.usecase.ts:31
  • `warn` at line 30 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/modules/platform-integration/usecases/clearReviewInProgress.usecase.ts:30
  • `warn` at line 129 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/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:129
  • `warn` at line 134 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/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:134
  • `warn` at line 76 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/modules/review-execution/usecases/jobHistory/persistJobRecord.usecase.ts:76
  • `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

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health69%AdequateStrongest area.
Architecture78%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity55%Adequate — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness49%Weak — gated by P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security33%Weak — gated by D29, D30, D36, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility51%Adequate — gated by AC2, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • 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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • 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

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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 did not expose a crawlable HTTP endpoint in time — no runtime evidence 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.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — none of 1 ADRs are conformance-checkable — unverifiable.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.html,.js,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • 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 package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 37 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <button> with no accessible text · ×5
  • <button> with no accessible text REDACTED:32 — 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).
  • <button> with no accessible text REDACTED:35 — 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).
  • <button> with no accessible text REDACTED:184 — 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).
  • <button> with no accessible text REDACTED:335 — 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).
  • <button> with no accessible text src/dashboard/stats.html:208 — 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).
AC2 · Forms & labels · <select> without a programmatic label · ×2
  • <select> without a programmatic label REDACTED:74 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label REDACTED:81 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×1
  • <input> without a programmatic label REDACTED:88 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×1
  • Custom control with no accessible name on <div> REDACTED:272 — 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.
AC2 · Forms & labels · Link with no accessible name · ×1
  • Link with no accessible name src/dashboard/stats.html:212 — 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.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
Serious — 429 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 21 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking src/frameworks/settings/runtimeSettings.ts:74 — `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.
  • Sync-over-async blocking src/frameworks/settings/runtimeSettings.ts:82 — `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.
  • Sync-over-async blocking src/main/commands/init.command.ts:92 — `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.
  • Sync-over-async blocking REDACTED:844 — `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.
  • Sync-over-async blocking src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:199 — `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.
  • Sync-over-async blocking src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:205 — `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.
  • Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:31 — `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.
  • Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:35 — `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.
  • Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:63 — `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.
  • Sync-over-async blocking src/modules/ember-chat/interface-adapters/gateways/emberMemory.fileSystem.gateway.ts:64 — `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.
  • Sync-over-async blocking REDACTED:126 — `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.
  • Sync-over-async blocking REDACTED:127 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:64 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:84 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:44 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:52 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:56 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:69 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:72 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:77 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:92 — `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.
  • Sync-over-async blocking src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:96 — `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.
  • Sync-over-async blocking src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:94 — `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.
  • Sync-over-async blocking src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:100 — `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.
  • Sync-over-async blocking src/modules/token-accounting/interface-adapters/gateways/budget/budget.filesystem.gateway.ts:18 — `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.
  • + 15 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×33
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:91 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:132 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:385 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:482 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:722 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:823 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:918 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:997 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1193 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1199 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1463 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1478 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1685 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:1690 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2025 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2121 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:2895 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3334 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3484 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3627 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:3848 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:4334 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:4392 — `#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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:5212 — `.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.
  • Animation without a prefers-reduced-motion guard src/dashboard/styles.css:5220 — `#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.
  • + 8 more in this group — see findings.md.
D8 · Code Coverage · Low coverage · ×32
  • Low coverage: src/mcpServer.ts src/mcpServer.ts:1 — 0.0% line coverage (0/5).
  • Low coverage: src/frameworks/claude/claudeInvoker.ts src/frameworks/claude/claudeInvoker.ts:1 — 22.5% line coverage (31/138).
  • Low coverage: src/main/cli.ts src/main/cli.ts:1 — 0.0% line coverage (0/30).
  • Low coverage: src/main/executeReviewWiring.ts src/main/executeReviewWiring.ts:1 — 25.8% line coverage (8/31).
  • Low coverage: src/main/githubInventoryWiring.ts src/main/githubInventoryWiring.ts:1 — 33.3% line coverage (1/3).
  • Low coverage: src/main/server.ts src/main/server.ts:1 — 22.0% line coverage (18/82).
  • Low coverage: REDACTED REDACTED:1 — 24.3% line coverage (17/70).
  • Low coverage: src/main/shared/cliConstants.ts src/main/shared/cliConstants.ts:1 — 20.0% line coverage (2/10).
  • Low coverage: src/mcp/mcpLogger.ts src/mcp/mcpLogger.ts:1 — 0.0% line coverage (0/24).
  • Low coverage: src/mcp/mcpServerStdio.ts src/mcp/mcpServerStdio.ts:1 — 42.1% line coverage (32/76).
  • Low coverage: src/modules/claude-invocation/entities/billingState/billingState.schema.ts src/modules/claude-invocation/entities/billingState/billingState.schema.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts:1 — 0.0% line coverage (0/2).
  • Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts:1 — 7.7% line coverage (1/13).
  • Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:1 — 9.1% line coverage (1/11).
  • Low coverage: src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:1 — 9.1% line coverage (1/11).
  • 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 — 0.0% line coverage (0/6).
  • 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 — 0.0% line coverage (0/4).
  • Low coverage: src/modules/review-execution/services/agentInstructionsBuilder.ts src/modules/review-execution/services/agentInstructionsBuilder.ts:1 — 33.3% line coverage (1/3).
  • Low coverage: src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts:1 — 0.0% line coverage (0/1).
  • Low coverage: src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts:1 — 0.0% line coverage (0/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 — 0.0% line coverage (0/2).
  • 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 — 0.0% line coverage (0/12).
  • + 7 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×28
  • Swallowed exception (empty catch) src/dashboard/modules/tabBar.js:101 — 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.
  • Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts:240 — 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.
  • Swallowed exception (empty catch) src/frameworks/claude/claudeInvoker.ts:269 — 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.
  • Swallowed exception (empty catch) src/frameworks/logging/logBuffer.ts:40 — 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.
  • Swallowed exception (empty catch) src/frameworks/queue/pQueueAdapter.ts:303 — `.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.
  • Swallowed exception (empty catch) REDACTED:216 — 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.
  • Swallowed exception (empty catch) src/mcp/mcpLogger.ts:30 — 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.
  • Swallowed exception (empty catch) src/mcp/mcpLogger.ts:45 — 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.
  • Swallowed exception (empty catch) src/modules/claude-invocation/interface-adapters/gateways/mcpCompletion.fileSystem.gateway.ts:169 — 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.
  • Swallowed exception (empty catch) src/modules/claude-invocation/usecases/awaitSessionCompletion.usecase.ts:74 — 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.
  • Swallowed exception (empty catch) src/modules/cli-configuration/interface-adapters/gateways/selfUpdate.cli.gateway.ts:88 — 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.
  • Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:31 — 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.
  • Swallowed exception (empty catch) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:35 — 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.
  • Swallowed exception (empty catch) src/modules/ember-chat/interface-adapters/controllers/mcp/recordInsight.handler.ts:52 — 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.
  • Swallowed exception (empty catch) src/modules/ember-chat/usecases/askEmber/askEmber.usecase.ts:120 — 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.
  • Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:83 — 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.
  • Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/gateways/cli/reviewLabel.gitlab.cli.gateway.ts:32 — 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.
  • Swallowed exception (empty catch) src/modules/platform-integration/interface-adapters/gateways/cli/reviewLabel.github.cli.gateway.ts:22 — 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.
  • Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/pendingReviewRequest.fileSystem.gateway.ts:83 — 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.
  • Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts:37 — 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.
  • Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/reviewFile.fileSystem.ts:42 — 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.
  • Swallowed exception (empty catch) src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:97 — 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.
  • Swallowed exception (empty catch) src/modules/token-accounting/interface-adapters/gateways/tokenUsage/tokenUsage.filesystem.gateway.ts:39 — 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.
  • Swallowed exception (empty catch) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:577 — 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.
  • Swallowed exception (empty catch) src/modules/worktree-management/interface-adapters/gateways/worktree.fileSystem.gateway.ts:98 — 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.
  • + 3 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×15
  • Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:191 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:192 — `encodedMrId` is text this program did not author, and it is written into a script or style context through markup built here 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.
  • Untrusted text written into markup unescaped src/dashboard/modules/mrSheet.js:193 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/overview.js:131 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/overview.js:161 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/pendingReviews.js:60 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/setupWizardForms.js:140 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/sizeBlockPanel.js:62 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/statsPage.js:165 — `escapeHtml(developer)` is text this program did not author, and it is written into a script or style context through markup built here 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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:37 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:174 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:263 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:286 — `translate('export.pdf')` is text this program did not author, and it is written into the text of an element through markup built here 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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:314 — `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.
  • Untrusted text written into markup unescaped src/dashboard/modules/teamTab.js:329 — `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.
D15 · Churn × Complexity Hotspots · Hotspot · ×13
  • Hotspot: REDACTED REDACTED:3140 — REDACTED changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in REDACTED.renderStaticLabels at line 3140. 6 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266 — src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in gitlab.controller.handleGitLabWebhook at line 266. 1 of those changes was a fix/bug commit, and the other 27 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374 — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in github.controller.handleGitHubWebhook at line 374. 1 of those changes was a fix/bug commit, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:200 — REDACTED changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in routes.registerRoutes at line 200. 4 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84 — src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes at line 84. 3 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/frameworks/config/configLoader.ts src/frameworks/config/configLoader.ts:178 — src/frameworks/config/configLoader.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in configLoader.validateAndEnrichConfig at line 178. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/frameworks/config/configLoader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150 — src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in projectConfig.routes.projectConfigRoutes at line 150. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/config/projectConfig.ts src/config/projectConfig.ts:195 — src/config/projectConfig.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in projectConfig.parseProjectConfig at line 195. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/config/projectConfig.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58 — src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in stats.routes.statsRoutes at line 58. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/dashboard/modules/statsCharts.js src/dashboard/modules/statsCharts.js:108 — src/dashboard/modules/statsCharts.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in statsCharts.drawScoreTrendChart at line 108. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/dashboard/modules/statsCharts.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101 — src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in updateProjectConfig.usecase.mergeConfig at line 101. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52 — src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in runClaudeReviewJob.usecase.runClaudeReviewJob at line 52. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48 — src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in OrchestrateSetupUseCase.execute at line 48. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-16..2026-08-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-16 17:32:09 +02:00' --until='2026-08-14 17:32:09 +02:00' --full-history --no-merges -- src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D3 · God Classes · FunctionTooLong · ×13
  • FunctionTooLong: routes.registerRoutes REDACTED:200 — FunctionTooLong — registerRoutes runs 531 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 431 over it, 5.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: gitlab.controller.handleGitLabWebhook src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266 — FunctionTooLong — handleGitLabWebhook runs 373 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 273 over it, 3.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84 — FunctionTooLong — mrTrackingAdvancedRoutes runs 356 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 256 over it, 3.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: github.controller.handleGitHubWebhook src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374 — FunctionTooLong — handleGitHubWebhook runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: claudeInvoker.invokeViaBackgroundSession src/frameworks/claude/claudeInvoker.ts:590 — FunctionTooLong — invokeViaBackgroundSession runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: insightsReport.getReportStyles src/dashboard/modules/insightsReport.js:257 — FunctionTooLong — getReportStyles runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: mrSheet.renderMrSheetContent src/dashboard/modules/mrSheet.js:25 — FunctionTooLong — renderMrSheetContent runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: cliStatus.routes.cliStatusRoutes REDACTED:8 — FunctionTooLong — cliStatusRoutes runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: statsCharts.drawScoreTrendChart src/dashboard/modules/statsCharts.js:108 — FunctionTooLong — drawScoreTrendChart runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: projectConfig.routes.projectConfigRoutes src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150 — FunctionTooLong — projectConfigRoutes runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: github.controller.handleGitHubPullRequestReviewHook src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:135 — FunctionTooLong — handleGitHubPullRequestReviewHook runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: mrSheet.drawScoreTimeline src/dashboard/modules/mrSheet.js:220 — FunctionTooLong — drawScoreTimeline runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: server.startServer src/main/server.ts:188 — FunctionTooLong — startServer runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×13
  • Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:126 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:140 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/budgetSettings.js:155 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/cleanup.js:32 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/emberChat.js:112 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/sizeBlockPanel.js:104 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/sizeBlockPanel.js:117 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/teamTab.js:317 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/tokenUsage.js:113 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:423 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:435 — `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.
  • Outbound HTTP without resilience src/dashboard/modules/worktreePanel.js:454 — `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.
  • Outbound HTTP without resilience src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:13 — `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.
R4 · Test Coverage · No test reaches this file · ×10
  • No test reaches this file src/modules/worktree-management/entities/worktree/worktree.schema.ts:1 — 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.
  • No test reaches this file src/mcpServer.ts:1 — 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.
  • No test reaches this file scripts/copyAssets.mjs:1 — 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.
  • No test reaches this file src/modules/claude-invocation/entities/claudeSession/sessionUsage.schema.ts:1 — 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.
  • No test reaches this file src/modules/claude-invocation/entities/supervisorHealth/supervisorHealth.schema.ts:1 — 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.
  • No test reaches this file src/modules/setup-wizard/entities/agentPreset/agentPreset.schema.ts:1 — 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.
  • No test reaches this file src/modules/claude-invocation/entities/billingState/billingState.schema.ts:1 — 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.
  • No test reaches this file src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts:1 — 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.
  • No test reaches this file src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts:1 — 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.
  • No test reaches this file src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts:1 — 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×5
  • FileTooLong: REDACTED REDACTED — FileTooLong — 2734 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2234 over it, 5.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), about 73% of them inside a single declaration: registerRoutes (200-899). The bar is 500 significant lines; this is 223 over it, 1.45× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: webhook/gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts — FileTooLong — 614 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: handleGitLabWebhook (266-803). The bar is 500 significant lines; this is 114 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: webhook/github.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts — FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 99 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: claude/claudeInvoker.ts src/frameworks/claude/claudeInvoker.ts — FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
AX7 · Slice cohesion · Cross-slice coupling · ×4
  • Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/addRepositoryFromDashboard.usecase.ts:15 — `AddRepositoryFromDashboardDependencies` (slice 'dashboardRepositories') depends on `AddRepositoriesToConfigUseCase` from slice 'cli'.
  • Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:10 — `RemoveRepositoryFromDashboardDependencies` (slice 'dashboardRepositories') depends on `RemoveRepositoryFromConfigUseCase` from slice 'cli'.
  • Cross-slice coupling: dashboardRepositories → cli src/modules/cli-configuration/usecases/dashboardRepositories/updateRepositoryEnabledFromDashboard.usecase.ts:10 — `UpdateRepositoryEnabledFromDashboardDependencies` (slice 'dashboardRepositories') depends on `ToggleRepositoryEnabledUseCase` from slice 'cli'.
  • Cross-slice coupling: enforceBudget → getBudgetStatus src/modules/token-accounting/usecases/enforceBudget/enforceBudget.usecase.ts:5 — `EnforceBudgetDependencies` (slice 'enforceBudget') depends on `GetBudgetStatusUseCase` from slice 'getBudgetStatus'.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) REDACTED:895 — `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:47 — `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/modules/cli-configuration/usecases/cli/discoverRepositories.usecase.ts:85 — `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:101 — `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, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×3
  • Duplicated block (18 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:186 — 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.
  • Duplicated block (18 lines × 2 locations) 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: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.
  • Duplicated block (18 lines × 2 locations) src/modules/worktree-management/interface-adapters/gateways/gitCommand.cli.gateway.ts:11 — 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×3
  • Async function without AbortSignal: fetchAndRenderTeamTab src/dashboard/modules/teamTab.js:310 — `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 })`.
  • Async function without AbortSignal: handleCleanupClick src/dashboard/modules/cleanup.js:20 — `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 })`.
  • Async function without AbortSignal: fetchLatestVersion src/modules/cli-configuration/interface-adapters/gateways/packageVersion.npm.gateway.ts:11 — `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 })`.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: StubClaudeSessionGateway (LCOM4 5) src/tests/stubs/claudeSession.stub.ts:23 — StubClaudeSessionGateway's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: StubPromptGateway (LCOM4 4) src/tests/stubs/setup-wizard/prompt.stub.ts:6 — StubPromptGateway's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×2
  • Duplicated block (36 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:536 — 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.
  • Duplicated block (36 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:745 — 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.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×2
  • Duplicated block (28 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:17 — 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.
  • Duplicated block (28 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:80 — 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.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×2
  • Duplicated block (27 lines × 2 locations) src/dashboard/modules/statsCharts.js:152 — 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.
  • Duplicated block (27 lines × 2 locations) src/modules/cli-configuration/usecases/cli/removeRepositoryFromConfig.usecase.ts:11 — 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.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (25 matched lines × 2 locations) src/modules/cli-configuration/usecases/dashboardRepositories/removeRepositoryFromDashboard.usecase.ts:4 — 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.
  • Duplicated block with local edits (25 matched lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:13 — 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.
R10 · Code Duplication · Duplicated block (15 lines × 3 locations) · ×2
  • Duplicated block (15 lines × 3 locations) src/frameworks/claude/claudeInvoker.ts:149 — 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.
  • Duplicated block (15 lines × 3 locations) REDACTED:14 — 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.
R7 · Dead Code · Dead file (~4 LoC) · ×2
  • Dead file (~4 LoC) src/modules/setup-wizard/entities/agentPreset/agentPreset.guard.ts — no import path from any entry point (94 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
  • Dead file (~4 LoC) src/modules/setup-wizard/entities/stepOutcome/stepOutcome.guard.ts — no import path from any entry point (94 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
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — 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.
C2 · Access Controls · No authorization · ×1
  • No authorization src/main/server.ts:172 — This repository serves requests — Fastify() (src/main/server.ts:172) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected.
D1 · Cyclomatic Complexity · REDACTED.renderStaticLabels (cyclomatic 60) · ×1
  • REDACTED.renderStaticLabels (cyclomatic 60) REDACTED:3140 — REDACTED.renderStaticLabels has cyclomatic complexity 60 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cyclomatic 49) · ×1
  • mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cyclomatic 49) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84 — mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes has cyclomatic complexity 49 (threshold 15). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 108, 464, 200, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · gitlab.controller.handleGitLabWebhook (cyclomatic 42) · ×1
  • gitlab.controller.handleGitLabWebhook (cyclomatic 42) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266 — gitlab.controller.handleGitLabWebhook has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · configLoader.validateAndEnrichConfig (cyclomatic 39) · ×1
  • configLoader.validateAndEnrichConfig (cyclomatic 39) src/frameworks/config/configLoader.ts:178 — configLoader.validateAndEnrichConfig has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · projectConfig.routes.projectConfigRoutes (cyclomatic 35) · ×1
  • projectConfig.routes.projectConfigRoutes (cyclomatic 35) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150 — projectConfig.routes.projectConfigRoutes has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 1 of the 35 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 154, 251). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · projectConfig.routes.extractPatch (cyclomatic 33) · ×1
  • projectConfig.routes.extractPatch (cyclomatic 33) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61 — projectConfig.routes.extractPatch has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · renderMrSheetContent (cyclomatic 32) · ×1
  • renderMrSheetContent (cyclomatic 32) src/dashboard/modules/mrSheet.js:25 — renderMrSheetContent has cyclomatic complexity 32 (threshold 15). Of this number, 23 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · github.controller.handleGitHubWebhook (cyclomatic 29) · ×1
  • github.controller.handleGitHubWebhook (cyclomatic 29) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374 — github.controller.handleGitHubWebhook has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · REDACTED.renderMrItem (cyclomatic 28) · ×1
  • REDACTED.renderMrItem (cyclomatic 28) REDACTED:1568 — REDACTED.renderMrItem has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · projectConfig.parseProjectConfig (cyclomatic 27) · ×1
  • projectConfig.parseProjectConfig (cyclomatic 27) src/config/projectConfig.ts:195 — projectConfig.parseProjectConfig has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · reviewOutput.parser.parseReviewOutput (cyclomatic 25) · ×1
  • reviewOutput.parser.parseReviewOutput (cyclomatic 25) REDACTED:47 — reviewOutput.parser.parseReviewOutput has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · reviews.routes.reviewRoutes (cyclomatic 22) · ×1
  • reviews.routes.reviewRoutes (cyclomatic 22) REDACTED:25 — reviews.routes.reviewRoutes has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 101, 29, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · REDACTED.renderNowLane (cyclomatic 21) · ×1
  • REDACTED.renderNowLane (cyclomatic 21) REDACTED:1675 — REDACTED.renderNowLane has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: REDACTED.connectWebSocket (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · REDACTED.bindSettingsModalForm (cyclomatic 20) · ×1
  • REDACTED.bindSettingsModalForm (cyclomatic 20) REDACTED:2668 — REDACTED.bindSettingsModalForm has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 2679). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: REDACTED.connectWebSocket (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · init.command.executeInit (cyclomatic 19) · ×1
  • init.command.executeInit (cyclomatic 19) src/main/commands/init.command.ts:68 — init.command.executeInit has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · runClaudeReviewJob.usecase.runClaudeReviewJob (cyclomatic 19) · ×1
  • runClaudeReviewJob.usecase.runClaudeReviewJob (cyclomatic 19) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52 — runClaudeReviewJob.usecase.runClaudeReviewJob has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · updateProjectConfig.usecase.mergeConfig (cyclomatic 19) · ×1
  • updateProjectConfig.usecase.mergeConfig (cyclomatic 19) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101 — updateProjectConfig.usecase.mergeConfig has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · REDACTED.renderReview (cyclomatic 18) · ×1
  • REDACTED.renderReview (cyclomatic 18) REDACTED:815 — REDACTED.renderReview has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: REDACTED.connectWebSocket (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · OrchestrateSetupUseCase.execute (cyclomatic 18) · ×1
  • OrchestrateSetupUseCase.execute (cyclomatic 18) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48 — OrchestrateSetupUseCase.execute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stats.routes.statsRoutes (cyclomatic 18) · ×1
  • stats.routes.statsRoutes (cyclomatic 18) src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58 — stats.routes.statsRoutes has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 108, 66, 120). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · statsCharts.drawScoreTrendChart (cyclomatic 17) · ×1
  • statsCharts.drawScoreTrendChart (cyclomatic 17) src/dashboard/modules/statsCharts.js:108 — statsCharts.drawScoreTrendChart has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · addAction.handler.createAddActionHandler (cyclomatic 17) · ×1
  • addAction.handler.createAddActionHandler (cyclomatic 17) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:20 — addAction.handler.createAddActionHandler has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · routes.registerRoutes (cyclomatic 16) · ×1
  • routes.registerRoutes (cyclomatic 16) REDACTED:200 — routes.registerRoutes has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 344, threadFetchGatewayFactory, noteCommentPostGatewayFactory, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · repositories.routes.repositoriesRoutes (cyclomatic 16) · ×1
  • repositories.routes.repositoriesRoutes (cyclomatic 16) REDACTED:38 — repositories.routes.repositoriesRoutes has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 46, 89, 73). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · egressScan.scanner.createEgressScanner.scan (cyclomatic 16) · ×1
  • egressScan.scanner.createEgressScanner.scan (cyclomatic 16) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33 — egressScan.scanner.createEgressScanner.scan has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · connectEmberStream (cyclomatic 16) · ×1
  • connectEmberStream (cyclomatic 16) src/dashboard/modules/emberChat.js:105 — connectEmberStream has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · gitlab.controller.handleGitLabWebhook (cognitive 86) · ×1
  • gitlab.controller.handleGitLabWebhook (cognitive 86) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266 — gitlab.controller.handleGitLabWebhook has cognitive complexity 86 (threshold 15). Drivers by points: if/else 28 (59 pts), ternaries 4 (12 pts), error handling 2 (8 pts), boolean chains 7 (nesting depth added 45). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cognitive 69) · ×1
  • mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes (cognitive 69) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:84 — mrTrackingAdvanced.routes.mrTrackingAdvancedRoutes has cognitive complexity 69 (threshold 15). Drivers by points: if/else 30 (40 pts), ternaries 6 (11 pts), error handling 6 (9 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 19). None of this is in the body itself: all 69 points belong to 7 function literals inside it that branch (lines 464, 108, 200, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · REDACTED.renderStaticLabels (cognitive 58) · ×1
  • REDACTED.renderStaticLabels (cognitive 58) REDACTED:3140 — REDACTED.renderStaticLabels has cognitive complexity 58 (threshold 15). Drivers by points: if/else 57, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · projectConfig.routes.extractPatch (cognitive 44) · ×1
  • projectConfig.routes.extractPatch (cognitive 44) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61 — projectConfig.routes.extractPatch has cognitive complexity 44 (threshold 15). Drivers by points: if/else 27 (36 pts), boolean chains 8 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · configLoader.validateAndEnrichConfig (cognitive 42) · ×1
  • configLoader.validateAndEnrichConfig (cognitive 42) src/frameworks/config/configLoader.ts:178 — configLoader.validateAndEnrichConfig has cognitive complexity 42 (threshold 15). Drivers by points: if/else 22 (30 pts), boolean chains 11, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · github.controller.handleGitHubWebhook (cognitive 42) · ×1
  • github.controller.handleGitHubWebhook (cognitive 42) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374 — github.controller.handleGitHubWebhook has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 7, ternaries 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · REDACTED.renderNowLane (cognitive 35) · ×1
  • REDACTED.renderNowLane (cognitive 35) REDACTED:1675 — REDACTED.renderNowLane has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 18 (33 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectConfig.routes.projectConfigRoutes (cognitive 35) · ×1
  • projectConfig.routes.projectConfigRoutes (cognitive 35) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:150 — projectConfig.routes.projectConfigRoutes has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 6, error handling 3, ternaries 3, loops 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 35 points belong to 2 function literals inside it that branch (lines 154, 251). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · REDACTED.renderMrItem (cognitive 32) · ×1
  • REDACTED.renderMrItem (cognitive 32) REDACTED:1568 — REDACTED.renderMrItem has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 15 (20 pts), boolean chains 8, if/else 4 (nesting depth added 5). Of this number, 26 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · reviews.routes.reviewRoutes (cognitive 32) · ×1
  • reviews.routes.reviewRoutes (cognitive 32) REDACTED:25 — reviews.routes.reviewRoutes has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 3, error handling 1 (3 pts), loops 3 (nesting depth added 11). None of this is in the body itself: all 32 points belong to 4 function literals inside it that branch (lines 101, 29, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · projectConfig.parseProjectConfig (cognitive 30) · ×1
  • projectConfig.parseProjectConfig (cognitive 30) src/config/projectConfig.ts:195 — projectConfig.parseProjectConfig has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 6 (7 pts), boolean chains 6, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · reviewOutput.parser.parseReviewOutput (cognitive 30) · ×1
  • reviewOutput.parser.parseReviewOutput (cognitive 30) REDACTED:47 — reviewOutput.parser.parseReviewOutput has cognitive complexity 30 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · init.command.executeInit (cognitive 28) · ×1
  • init.command.executeInit (cognitive 28) src/main/commands/init.command.ts:68 — init.command.executeInit has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrchestrateSetupUseCase.execute (cognitive 27) · ×1
  • OrchestrateSetupUseCase.execute (cognitive 27) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48 — OrchestrateSetupUseCase.execute has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · updateProjectConfig.usecase.mergeConfig (cognitive 26) · ×1
  • updateProjectConfig.usecase.mergeConfig (cognitive 26) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101 — updateProjectConfig.usecase.mergeConfig has cognitive complexity 26 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 6 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · renderMrSheetContent (cognitive 26) · ×1
  • renderMrSheetContent (cognitive 26) src/dashboard/modules/mrSheet.js:25 — renderMrSheetContent has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 16, other 6, boolean chains 4. Of this number, 17 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · statsCharts.drawScoreTrendChart (cognitive 23) · ×1
  • statsCharts.drawScoreTrendChart (cognitive 23) src/dashboard/modules/statsCharts.js:108 — statsCharts.drawScoreTrendChart has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (8 pts), if/else 6 (7 pts), ternaries 3 (6 pts), boolean chains 2 (nesting depth added 7). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · REDACTED.bindSettingsModalForm (cognitive 23) · ×1
  • REDACTED.bindSettingsModalForm (cognitive 23) REDACTED:2668 — REDACTED.bindSettingsModalForm has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 1, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 2679). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · egressScan.scanner.createEgressScanner.scan (cognitive 23) · ×1
  • egressScan.scanner.createEgressScanner.scan (cognitive 23) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33 — egressScan.scanner.createEgressScanner.scan has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 3 (6 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · reviewRecovery.service.runReviewRecovery (cognitive 23) · ×1
  • reviewRecovery.service.runReviewRecovery (cognitive 23) src/modules/review-execution/services/reviewRecovery.service.ts:43 — reviewRecovery.service.runReviewRecovery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 1 (4 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · claudeInvoker.invokeViaBackgroundSession (cognitive 22) · ×1
  • claudeInvoker.invokeViaBackgroundSession (cognitive 22) src/frameworks/claude/claudeInvoker.ts:590 — claudeInvoker.invokeViaBackgroundSession has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 3 (7 pts), ternaries 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AiInsightsSessionClaudeGateway.readAnswer (cognitive 22) · ×1
  • AiInsightsSessionClaudeGateway.readAnswer (cognitive 22) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:79 — AiInsightsSessionClaudeGateway.readAnswer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · REDACTED.updateLoadingStateUI (cognitive 21) · ×1
  • REDACTED.updateLoadingStateUI (cognitive 21) REDACTED:593 — REDACTED.updateLoadingStateUI has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runClaudeReviewJob.usecase.runClaudeReviewJob (cognitive 21) · ×1
  • runClaudeReviewJob.usecase.runClaudeReviewJob (cognitive 21) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52 — runClaudeReviewJob.usecase.runClaudeReviewJob has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · stats.routes.statsRoutes (cognitive 21) · ×1
  • stats.routes.statsRoutes (cognitive 21) src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts:58 — stats.routes.statsRoutes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 4, loops 1 (nesting depth added 4). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 66, 108, 120). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · statsCharts.drawScoreDistributionChart (cognitive 19) · ×1
  • statsCharts.drawScoreDistributionChart (cognitive 19) src/dashboard/modules/statsCharts.js:462 — statsCharts.drawScoreDistributionChart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, loops 3 (4 pts), ternaries 2 (4 pts) (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · developerSheet.drawRadarChart (cognitive 19) · ×1
  • developerSheet.drawRadarChart (cognitive 19) src/dashboard/modules/developerSheet.js:286 — developerSheet.drawRadarChart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 6 (7 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateProjectConfigUseCase.execute (cognitive 19) · ×1
  • UpdateProjectConfigUseCase.execute (cognitive 19) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:159 — UpdateProjectConfigUseCase.execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · addAction.usecase.validateAction (cognitive 19) · ×1
  • addAction.usecase.validateAction (cognitive 19) src/modules/review-execution/usecases/mcp/addAction.usecase.ts:25 — addAction.usecase.validateAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · constrainActionSurface.constrainActionSurface (cognitive 18) · ×1
  • constrainActionSurface.constrainActionSurface (cognitive 18) src/modules/review-execution/services/constrainActionSurface.ts:20 — constrainActionSurface.constrainActionSurface has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · connectEmberStream (cognitive 18) · ×1
  • connectEmberStream (cognitive 18) src/dashboard/modules/emberChat.js:105 — connectEmberStream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (11 pts), loops 2 (3 pts), other 2, ternaries 1 (2 pts) (nesting depth added 3). Of this number, 11 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · REDACTED.renderReview (cognitive 17) · ×1
  • REDACTED.renderReview (cognitive 17) REDACTED:815 — REDACTED.renderReview has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 14, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · github.controller.handleGitHubPullRequestReviewHook (cognitive 17) · ×1
  • github.controller.handleGitHubPullRequestReviewHook (cognitive 17) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:135 — github.controller.handleGitHubPullRequestReviewHook has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, ternaries 2 (6 pts), error handling 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sizeBlocks.routes.sizeBlocksRoutes (cognitive 17) · ×1
  • sizeBlocks.routes.sizeBlocksRoutes (cognitive 17) REDACTED:50 — sizeBlocks.routes.sizeBlocksRoutes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 63, 83, 107). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · WorktreePanelPresenter.present (cognitive 17) · ×1
  • WorktreePanelPresenter.present (cognitive 17) src/modules/worktree-management/interface-adapters/presenters/worktreePanel.presenter.ts:155 — WorktreePanelPresenter.present has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (3 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · routes.registerRoutes (cognitive 16) · ×1
  • routes.registerRoutes (cognitive 16) REDACTED:200 — routes.registerRoutes has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5, if/else 4, loops 2 (3 pts), boolean chains 2, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 344, threadFetchGatewayFactory, noteCommentPostGatewayFactory, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AddProjectStep.execute (cognitive 16) · ×1
  • AddProjectStep.execute (cognitive 16) src/modules/setup-wizard/usecases/steps/addProject.step.ts:15 — AddProjectStep.execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · computeInsightsWithPersistence.usecase.reconcileDiffStatsFromWindow (cognitive 16) · ×1
  • computeInsightsWithPersistence.usecase.reconcileDiffStatsFromWindow (cognitive 16) src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:157 — computeInsightsWithPersistence.usecase.reconcileDiffStatsFromWindow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D22 · Internal API Consistency · Redundant operations with identical signatures and likely overlapping intent. Both methods accept the same `ServerOptions` and return the same `Promise<FastifyInstance>`. It is unclear if one creates the instance and the other starts listening, or if they are duplicate entry points. This creates confusion for consumers regarding which method to use. · ×1
  • Redundant operations with identical signatures and likely overlapping intent. Both methods accept the same `ServerOptions` and return the same `Promise<FastifyInstance>`. It is unclear if one creates the instance and the other starts listening, or if they are duplicate entry points. This creates confusion for consumers regarding which method to use. — Unify into a single method, e.g., `startServer(options?: ServerOptions): Promise<FastifyInstance>`, or clearly distinguish responsibilities (e.g., `createServer` returns the instance without listening, `startServer` binds to the port). (signatures: server.createServer(options?: ServerOptions): Promise<FastifyInstance> | server.startServer(options?: ServerOptions): Promise<FastifyInstance>)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: eventFilter.ts, github.controller.ts, gitlab.controller.ts src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts — 3 files — `src/modules/platform-integration/interface-adapters/controllers/webhook/eventFilter.ts`, `src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts`, `src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits REDACTED:187 — `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.
R10 · Code Duplication · Duplication concentrated across 11 sibling directories (21 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (21 clone groups) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11 — 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.
R10 · Code Duplication · Duplicated block (157 lines × 2 locations) · ×1
  • Duplicated block (157 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:110 — 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.
R10 · Code Duplication · Duplicated block with local edits (87 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (87 matched lines × 2 locations) src/dashboard/modules/mrSheet.js:207 — 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.
R10 · Code Duplication · Duplicated block (81 lines × 2 locations) · ×1
  • Duplicated block (81 lines × 2 locations) REDACTED:621 — 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.
R10 · Code Duplication · Duplicated block (68 lines × 2 locations) · ×1
  • Duplicated block (68 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:313 — 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.
R10 · Code Duplication · Duplicated block with local edits (55 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (55 matched lines × 2 locations) src/dashboard/modules/emberAvatarRenderer.js:26 — 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.
R10 · Code Duplication · Duplicated block with local edits (48 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (48 matched lines × 2 locations) src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts:66 — 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.
R10 · Code Duplication · Duplicated block (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:397 — 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.
R10 · Code Duplication · Duplicated block (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) REDACTED:57 — 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.
R10 · Code Duplication · Duplicated block (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:486 — 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.
R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) src/dashboard/modules/developerSheet.js:112 — 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.
R10 · Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:66 — 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.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:695 — 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.
R10 · Code Duplication · Duplicated block with local edits (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) src/modules/data-lifecycle/interface-adapters/gateways/fileSystem/reviewLogFile.fileSystem.gateway.ts:11 — 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.
R10 · Code Duplication · Duplicated block (34 lines × 2 locations) · ×1
  • Duplicated block (34 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:227 — 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.
R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:304 — 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.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/setPhase.handler.ts:18 — 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.
R10 · Code Duplication · Duplicated block with local edits (27 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (27 matched lines × 2 locations) src/modules/statistics-insights/usecases/insights/buildAiInsightsPrompt.ts:21 — 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.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) src/modules/review-execution/interface-adapters/controllers/mcp/getThreads.handler.ts:8 — 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.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) src/modules/review-execution/services/contextActionsExecutor.ts:89 — 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.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:153 — 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.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) src/dashboard/modules/insightsReport.js:82 — 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.
R10 · Code Duplication · Duplicated block (18 lines × 3 locations) · ×1
  • Duplicated block (18 lines × 3 locations) src/dashboard/modules/statsCharts.js:270 — 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.
R10 · Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) src/modules/review-execution/usecases/mcp/addAction.usecase.ts:88 — 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.
R10 · Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (16 matched lines × 2 locations) src/frameworks/settings/runtimeSettings.ts:77 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1
  • Duplicated block (16 lines × 3 locations) src/modules/cli-configuration/usecases/cli/addRepositoriesToConfig.usecase.ts:17 — 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.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) src/dashboard/modules/statsCharts.js:423 — 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.
R2 · Cyclomatic Complexity · Complex function handleGitLabWebhook (cyclomatic 42, cognitive 86) · ×1
  • Complex function handleGitLabWebhook (cyclomatic 42, cognitive 86) src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts:266 — 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.
R2 · Cyclomatic Complexity · Complex function validateAndEnrichConfig (cyclomatic 39, cognitive 42) · ×1
  • Complex function validateAndEnrichConfig (cyclomatic 39, cognitive 42) src/frameworks/config/configLoader.ts:178 — 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.
R2 · Cyclomatic Complexity · Complex function handleGitHubWebhook (cyclomatic 34, cognitive 47) · ×1
  • Complex function handleGitHubWebhook (cyclomatic 34, cognitive 47) src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:374 — 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.
R2 · Cyclomatic Complexity · Complex function extractPatch (cyclomatic 33, cognitive 44) · ×1
  • Complex function extractPatch (cyclomatic 33, cognitive 44) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:61 — 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.
R2 · Cyclomatic Complexity · Complex function parseProjectConfig (cyclomatic 27, cognitive 29) · ×1
  • Complex function parseProjectConfig (cyclomatic 27, cognitive 29) src/config/projectConfig.ts:195 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 26, cognitive 29) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 29) src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:154 — (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.
R2 · Cyclomatic Complexity · Complex function parseReviewOutput (cyclomatic 25, cognitive 30) · ×1
  • Complex function parseReviewOutput (cyclomatic 25, cognitive 30) REDACTED:47 — 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.
R2 · Cyclomatic Complexity · Complex function renderMrSheetContent (cyclomatic 23, cognitive 17) · ×1
  • Complex function renderMrSheetContent (cyclomatic 23, cognitive 17) src/dashboard/modules/mrSheet.js:25 — 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.
R2 · Cyclomatic Complexity · Complex function executeInit (cyclomatic 19, cognitive 28) · ×1
  • Complex function executeInit (cyclomatic 19, cognitive 28) src/main/commands/init.command.ts:68 — 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.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 19, cognitive 28) · ×1
  • Complex function execute (cyclomatic 19, cognitive 28) src/modules/setup-wizard/usecases/orchestrateSetup.usecase.ts:48 — 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.
R2 · Cyclomatic Complexity · Complex function mergeConfig (cyclomatic 19, cognitive 26) · ×1
  • Complex function mergeConfig (cyclomatic 19, cognitive 26) src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:101 — 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.
R2 · Cyclomatic Complexity · Complex function runClaudeReviewJob (cyclomatic 19, cognitive 21) · ×1
  • Complex function runClaudeReviewJob (cyclomatic 19, cognitive 21) src/modules/claude-invocation/usecases/runClaudeReviewJob.usecase.ts:52 — 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.
R2 · Cyclomatic Complexity · Complex function scan (cyclomatic 18, cognitive 24) · ×1
  • Complex function scan (cyclomatic 18, cognitive 24) src/modules/platform-integration/entities/egressScan/egressScan.scanner.ts:33 — 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 17, cognitive 25) · ×1
  • Complex function (anonymous) (cyclomatic 17, cognitive 25) src/modules/review-execution/interface-adapters/controllers/mcp/addAction.handler.ts:23 — (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.
R2 · Cyclomatic Complexity · Complex function invokeViaBackgroundSession (cyclomatic 16, cognitive 24) · ×1
  • Complex function invokeViaBackgroundSession (cyclomatic 16, cognitive 24) src/frameworks/claude/claudeInvoker.ts:590 — 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.
R2 · Cyclomatic Complexity · Complex function buildContext (cyclomatic 16, cognitive 15) · ×1
  • Complex function buildContext (cyclomatic 16, cognitive 15) src/tests/acceptance/183-setup-wizard.acceptance.test.ts:100 — 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.
R2 · Cyclomatic Complexity · Complex function drawScoreTrendChart (cyclomatic 15, cognitive 21) · ×1
  • Complex function drawScoreTrendChart (cyclomatic 15, cognitive 21) src/dashboard/modules/statsCharts.js:108 — 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.
R2 · Cyclomatic Complexity · Complex function buildPayload (cyclomatic 15, cognitive 17) · ×1
  • Complex function buildPayload (cyclomatic 15, cognitive 17) src/tests/factories/projectConfig.factory.ts:18 — 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.
R2 · Cyclomatic Complexity · Complex function updateAggregatesForNewReview (cyclomatic 15, cognitive 14) · ×1
  • Complex function updateAggregatesForNewReview (cyclomatic 15, cognitive 14) src/modules/statistics-insights/usecases/stats/addReviewStats.usecase.ts:90 — 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.
R2 · Cyclomatic Complexity · Complex function readAnswer (cyclomatic 14, cognitive 25) · ×1
  • Complex function readAnswer (cyclomatic 14, cognitive 25) src/modules/statistics-insights/interface-adapters/gateways/aiInsightsSession.claude.gateway.ts:79 — 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.
R3 · Large Files · src/dashboard/modules/i18n.js · ×1
  • src/dashboard/modules/i18n.js: 920 lines of code src/dashboard/modules/i18n.js:1 — 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.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 844 lines of code REDACTED: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.
R3 · Large Files · src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts · ×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/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.
R3 · Large Files · src/frameworks/claude/claudeInvoker.ts · ×1
  • src/frameworks/claude/claudeInvoker.ts: 761 lines of code src/frameworks/claude/claudeInvoker.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.
R3 · Large Files · src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.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/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.
R3 · Large Files · src/dashboard/modules/statsCharts.js · ×1
  • src/dashboard/modules/statsCharts.js: 594 lines of code src/dashboard/modules/statsCharts.js: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.
R3 · Large Files · src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts · ×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/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.
R3 · Large Files · src/dashboard/modules/insightsReport.js · ×1
  • src/dashboard/modules/insightsReport.js: 493 lines of code src/dashboard/modules/insightsReport.js: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.
R3 · Large Files · src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts · ×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/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.
R3 · Large Files · src/frameworks/queue/pQueueAdapter.ts · ×1
  • src/frameworks/queue/pQueueAdapter.ts: 457 lines of code src/frameworks/queue/pQueueAdapter.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.
R3 · Large Files · src/dashboard/modules/worktreePanel.js · ×1
  • src/dashboard/modules/worktreePanel.js: 438 lines of code src/dashboard/modules/worktreePanel.js: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.
R3 · Large Files · src/dashboard/modules/animations.js · ×1
  • src/dashboard/modules/animations.js: 401 lines of code src/dashboard/modules/animations.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.
R4 · Test Coverage · This test file cannot be loaded · ×1
  • This test file cannot be loaded src/tests/units/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.test.ts:16 — 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.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • 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 — 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.
R7 · Dead Code · Dead file (~7 LoC) · ×1
  • Dead file (~7 LoC) src/modules/claude-invocation/entities/claudeSession/claudeSession.guard.ts — no import path from any entry point (94 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
R8 · Dependency Hygiene · Unused dependency '@hono/node-server' · ×1
  • Unused dependency '@hono/node-server' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@stryker-mutator/vitest-runner' · ×1
  • Unused dependency '@stryker-mutator/vitest-runner' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'animejs' · ×1
  • Unused dependency 'animejs' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity REDACTED:11 — `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.
X13 · Undrained process stream · Redirected process stream is never drained (deadlock) · ×1
  • Redirected process stream is never drained (deadlock) src/modules/supervisor-management/interface-adapters/gateways/supervisor.cli.gateway.ts:34 — `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.
Minor — 161 finding(s)
M4 · Documentation accuracy · README/code drift · ×40
  • README/code drift docs/architecture/current.md:103 — 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 package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/index.md:20 — docs/architecture/index.md links to `./current`, but `docs/architecture/current` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/index.md:21 — docs/architecture/index.md links to `./target`, but `docs/architecture/target` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/index.md:27 — docs/architecture/index.md links to `./mcp/specification`, but `docs/architecture/mcp/specification` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/index.md:28 — docs/architecture/index.md links to `./mcp/architecture`, but `docs/architecture/mcp/architecture` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/multi-llm-analysis.md:12 — docs/architecture/multi-llm-analysis.md names `src/frameworks/claude/claudeInsightsInvoker.ts`, but no file or folder `src/frameworks/claude/claudeInsightsInvoker.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/multi-llm-analysis.md:28 — docs/architecture/multi-llm-analysis.md names `src/services/threadActionsParser.ts`, but no file or folder `src/services/threadActionsParser.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/architecture/multi-llm-analysis.md:35 — docs/architecture/multi-llm-analysis.md names `src/interface-adapters/controllers/http/settings.routes.ts`, but no file or folder `src/interface-adapters/controllers/http/settings.routes.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/guide/index.md:13 — docs/guide/index.md links to `./quick-start`, but `docs/guide/quick-start` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/guide/index.md:14 — docs/guide/index.md links to `./project-config`, but `docs/guide/project-config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/guide/index.md:15 — docs/guide/index.md links to `./review-skills`, but `docs/guide/review-skills` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/guide/index.md:16 — docs/guide/index.md links to `./troubleshooting`, but `docs/guide/troubleshooting` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/guide/index.md:24 — docs/guide/index.md links to `/reference/config`, but `reference/config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference/index.md:11 — docs/reference/index.md links to `./config`, but `docs/reference/config` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference/index.md:12 — docs/reference/index.md links to `./markers`, but `docs/reference/markers` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference/index.md:14 — docs/reference/index.md links to `./ubiquitous-language`, but `docs/reference/ubiquitous-language` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference/ubiquitous-language.md:23 — docs/reference/ubiquitous-language.md names `entities/actionExecution/`, but no file or folder `entities/actionExecution` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/163-token-budget-cap.report.md:13 — docs/reports/163-token-budget-cap.report.md documents the environment variable `BUDGET_FLOOR`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/163-token-budget-cap.report.md:13 — docs/reports/163-token-budget-cap.report.md documents the environment variable `BUDGET_CEILING`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/170-prebuilt-worktree-lifecycle.report.md:15 — docs/reports/170-prebuilt-worktree-lifecycle.report.md names `entities/worktree/worktree.guard.ts`, but no file or folder `entities/worktree/worktree.guard.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/170-prebuilt-worktree-lifecycle.report.md:17 — docs/reports/170-prebuilt-worktree-lifecycle.report.md names `entities/gitCommand/gitCommand.schema.ts`, but no file or folder `entities/gitCommand/gitCommand.schema.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/172-claude-agents-supervisor-lifecycle.report.md:77 — docs/reports/172-claude-agents-supervisor-lifecycle.report.md documents the environment variable `SUPERVISOR_CHECK_INTERVAL_MS`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/173-dashboard-worktree-panel.report.md:54 — docs/reports/173-dashboard-worktree-panel.report.md names `dashboard/modules/worktreePanel`, but no file or folder `dashboard/modules/worktreePanel` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/177-dashboard-add-project-ui.report.md:121 — docs/reports/177-dashboard-add-project-ui.report.md names `.dashboard-tab.is-entering`, but no file or folder `.dashboard-tab.is-entering` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reports/179-dashboard-project-settings-modal.report.md:22 — docs/reports/179-dashboard-project-settings-modal.report.md names `src/modules/cli-configuration/entities/projectConfig/projectConfig.schema.ts`, but no file or folder `src/modules/cli-configuration/entities/projectConfig/projectConfig.schema.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • + 15 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×28
  • Mock-dominated test: rejects a fresh review and broadcasts budget-exceeded when enforceBudget returns accepted=false src/tests/units/interface-adapters/controllers/webhook/gitlab.controller.test.ts:558 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: returns 401 when the GitLab signature is invalid src/tests/units/interface-adapters/controllers/webhook/gitlab.controller.test.ts:879 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: rejects a followup and broadcasts when the budget is exceeded src/tests/units/interface-adapters/controllers/webhook/gitlab.controller.test.ts:1206 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • 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 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: responds 401 when signature verification fails src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:761 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: ignores a non-PR event type src/tests/units/interface-adapters/controllers/webhook/github.controller.test.ts:777 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • 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 — This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • 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 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should call exit(1) when stop fails src/tests/units/main/executeStop.test.ts:51 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should output initial lines and set up watcher in follow mode src/tests/units/main/executeLogs.test.ts:49 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should exit with code 1 when Node version is too low src/tests/units/main/executeInit.test.ts:57 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should exit with code 1 when Claude CLI is not installed src/tests/units/main/executeInit.test.ts:76 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should ask to overwrite when config already exists src/tests/units/main/executeInit.test.ts:96 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should skip overwrite prompt in --yes mode src/tests/units/main/executeInit.test.ts:114 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should only ask gitlab username when platform is gitlab src/tests/units/main/executeInit.test.ts:134 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should only ask github username when platform is github src/tests/units/main/executeInit.test.ts:149 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should ask both usernames when platform is both src/tests/units/main/executeInit.test.ts:164 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should use defaults without prompting src/tests/units/main/executeInit.test.ts:181 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should always generate both secrets regardless of platform src/tests/units/main/executeInit.test.ts:209 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should call selectRepositories with discovered repos in interactive mode src/tests/units/main/executeInit.test.ts:293 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: invokes fetch on the running server port when daemon is alive src/tests/units/main/executeFollowupImportants.test.ts:49 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should log message and skip when no repositories found src/tests/units/main/executeDiscover.test.ts:48 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should not write config when user selects nothing src/tests/units/main/executeDiscover.test.ts:63 — This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should load context from file and register it src/tests/units/mcp/mcpServerStdio.test.ts:147 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should skip loading if context is already registered src/tests/units/mcp/mcpServerStdio.test.ts:179 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • + 3 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×19
  • Duplicated predicate src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:144 — `!projectPath.startsWith('/') || projectPath.includes('..')` appears character-identically in 3 files — src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts, REDACTED, src/modules/statistics-insights/interface-adapters/controllers/http/stats.routes.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:36 — `!trimmed.startsWith('/') || trimmed.includes('..')` appears character-identically in 3 files — REDACTED, src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/mcpDependencies.ts:55 — `a.status === 'completed' || a.status === 'failed'` appears character-identically in 2 files — src/main/mcpDependencies.ts, src/modules/review-execution/entities/progress/progress.calculator.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/dashboard/modules/insightsReport.js:471 — `aiInsights?.team !== undefined && aiInsights?.team !== null` appears character-identically in 2 files — src/dashboard/modules/insightsReport.js, src/dashboard/modules/teamTab.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:125 — `categoryLevels[category].level < 7 && categoryLevels[category].trend === 'improving'` appears character-identically in 2 files — src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts, src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:500 — `eligibility.type === 'followup-skipped' && eligibility.reason === 'Auto-followup disabled'` appears character-identically in 2 files — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts, src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:518 — `projectConfig?.reviewFollowupSkill || 'review-followup'` appears character-identically in 3 files — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts, src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts, src/modules/tracking/interface-adapters/controllers/http/mrTrackingAdvanced.routes.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts:94 — `review.diffStats !== null && review.diffStats !== undefined` appears character-identically in 3 files — src/modules/statistics-insights/usecases/insights/computeDeveloperInsights.usecase.ts, src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts, src/modules/statistics-insights/usecases/stats/recalculateProjectStats.usecase.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts:307 — `review.score !== null && review.diffStats !== null && review.diffStats !== undefined` appears character-identically in 2 files — src/modules/statistics-insights/usecases/insights/computeInsightsWithPersistence.usecase.ts, src/modules/statistics-insights/usecases/insights/insightLevelComputation.service.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/dashboard/modules/statsCharts.js:116 — `review.score !== null && review.score !== undefined` appears character-identically in 2 files — src/dashboard/modules/statsCharts.js, src/modules/statistics-insights/interface-adapters/presenters/overview.presenter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/statistics-insights/entities/stats/keyInsights.ts:84 — `right.count - left.count || left.index - right.index` appears character-identically in 2 files — src/modules/statistics-insights/entities/stats/keyInsights.ts, src/modules/statistics-insights/interface-adapters/presenters/bugsByCategory.presenter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts:29 — `typeof agentName !== 'string' || !agentName` appears character-identically in 2 files — src/modules/review-execution/interface-adapters/controllers/mcp/completeAgent.handler.ts, src/modules/review-execution/interface-adapters/controllers/mcp/startAgent.handler.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/frameworks/config/configLoader.ts:190 — `typeof port !== 'number' || port < 1 || port > 65535` appears character-identically in 2 files — src/frameworks/config/configLoader.ts, src/modules/cli-configuration/usecases/cli/validateConfig.usecase.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.github.gateway.ts:8 — `typeof value !== 'object' || value === null || !(field in value)` appears character-identically in 3 files — src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.github.gateway.ts, src/modules/platform-integration/interface-adapters/gateways/changedFilesFetch.gitlab.gateway.ts, src/modules/statistics-insights/interface-adapters/gateways/diffStatsFetch.gitlab.gateway.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/dashboard/modules/desktopNotifications.js:38 — `typeof value === 'number' && Number.isFinite(value)` appears character-identically in 2 files — src/dashboard/modules/desktopNotifications.js, src/dashboard/modules/priority.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/config/projectConfig.ts:45 — `typeof value === 'string' && value.length > 0` appears character-identically in 3 files — src/config/projectConfig.ts, src/modules/claude-invocation/interface-adapters/gateways/environment.process.gateway.ts, src/modules/platform-integration/interface-adapters/controllers/webhook/transportGuard.middleware.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts:485 — `updateResult.shouldProcess && updateResult.isFollowup` appears character-identically in 2 files — src/modules/platform-integration/interface-adapters/controllers/webhook/github.controller.ts, src/modules/platform-integration/interface-adapters/controllers/webhook/gitlab.controller.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts:43 — `value !== null && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 2 files — src/modules/cli-configuration/interface-adapters/controllers/http/projectConfig.routes.ts, src/modules/cli-configuration/interface-adapters/gateways/projectConfig.fileSystem.gateway.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/dashboard/modules/keyInsights.js:50 — `viewModel && typeof viewModel === 'object'` appears character-identically in 2 files — src/dashboard/modules/keyInsights.js, src/dashboard/modules/overview.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X4 · Structured logging · Interpolated log message defeats structured logging · ×15
  • Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:85 — `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.
  • Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:96 — `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.
  • Interpolated log message defeats structured logging src/frameworks/settings/runtimeSettings.ts:103 — `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.
  • Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:279 — `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.
  • Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:288 — `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.
  • Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:299 — `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.
  • Interpolated log message defeats structured logging src/mcp/mcpServerStdio.ts:308 — `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.
  • Interpolated log message defeats structured logging src/modules/platform-integration/usecases/markReviewInProgress.usecase.ts:39 — `warn` at line 39 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.
  • Interpolated log message defeats structured logging src/modules/platform-integration/usecases/markReviewInProgress.usecase.ts:57 — `warn` at line 57 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.
  • Interpolated log message defeats structured logging src/modules/platform-integration/usecases/markReviewDone.usecase.ts:31 — `warn` at line 31 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.
  • Interpolated log message defeats structured logging src/modules/platform-integration/usecases/clearReviewInProgress.usecase.ts:30 — `warn` at line 30 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.
  • Interpolated log message defeats structured logging src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:129 — `warn` at line 129 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.
  • Interpolated log message defeats structured logging src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:134 — `warn` at line 134 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.
  • Interpolated log message defeats structured logging src/modules/review-execution/usecases/jobHistory/persistJobRecord.usecase.ts:76 — `warn` at line 76 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.
  • Interpolated log message defeats structured logging src/modules/supervisor-management/usecases/checkSupervisorAndRespawn.usecase.ts:69 — `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.
P2 · Observability · Console output used as the logging channel · ×8
  • Console output used as the logging channel src/dashboard/modules/teamTab.js:328 — `src/dashboard/modules/teamTab.js` reports through `console.*` at line 328 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel src/frameworks/config/configLoader.ts:135 — `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.
  • Console output used as the logging channel src/frameworks/config/configLoader.ts:140 — `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.
  • Console output used as the logging channel src/frameworks/settings/runtimeSettings.ts:56 — `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.
  • Console output used as the logging channel src/frameworks/settings/runtimeSettings.ts:218 — `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.
  • Console output used as the logging channel REDACTED:64 — `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.
  • Console output used as the logging channel src/main/commands/setup.command.ts:171 — `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.
  • Console output used as the logging channel src/main/shared/cliConstants.ts:16 — `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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch src/config/projectConfig.ts:334 — `getProjectLanguage` swallows every exception into `return 'en'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/dashboard/modules/html.js:29 — `sanitizeHttpUrl` swallows every exception into `return '#'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/main/commands/setup.command.ts:119 — `resolveMcpServerPath` swallows every exception into `return 'mcpServer.js'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/modules/claude-invocation/interface-adapters/gateways/claudeSession.cli.gateway.ts:173 — `listAgents` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch src/modules/review-execution/interface-adapters/gateways/fileSystem/jobHistory.fileSystem.gateway.ts:108 — `readFileRecords` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: InitDependencies (18 required operations) src/main/commands/init.command.ts:42 — `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.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: @ungap/structured-clone REDACTED:1758 — @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): pino-pretty package.json:70 — pino-pretty is pinned at 10.3.1; registry.npmjs.org publishes 13.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (39352 LoC, 1077 module-visible types across 166 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · ADRs not easily discoverable · ×1
  • ADRs not easily discoverable — 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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 2495 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.
R7 · Dead Code · Unused export 'getLogsByLevel' · ×1
  • Unused export 'getLogsByLevel' src/frameworks/logging/logBuffer.ts:56 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'logDebug' · ×1
  • Unused export 'logDebug' src/frameworks/logging/logBuffer.ts:91 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'getJobProgress' · ×1
  • Unused export 'getJobProgress' src/frameworks/queue/pQueueAdapter.ts:522 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'getWsClientsCount' · ×1
  • Unused export 'getWsClientsCount' REDACTED:24 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ClaudeSessionStatus' · ×1
  • Unused export 'ClaudeSessionStatus' src/modules/claude-invocation/entities/claudeSession/claudeSession.schema.ts:36 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'markTimedOut' · ×1
  • Unused export 'markTimedOut' src/modules/claude-invocation/entities/claudeSession/claudeSession.ts:37 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'SessionCompletionSource' · ×1
  • Unused export 'SessionCompletionSource' src/modules/claude-invocation/entities/sessionCompletion/sessionCompletion.schema.ts:12 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'EDITABLE_PROJECT_CONFIG_KEYS' · ×1
  • Unused export 'EDITABLE_PROJECT_CONFIG_KEYS' src/modules/cli-configuration/usecases/projectConfig/updateProjectConfig.usecase.ts:7 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'THREADS_AGENT' · ×1
  • Unused export 'THREADS_AGENT' src/modules/review-execution/entities/progress/agentDefinition.type.ts:6 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'REPORT_AGENT' · ×1
  • Unused export 'REPORT_AGENT' src/modules/review-execution/entities/progress/agentDefinition.type.ts:7 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'safeParseReviewAction' · ×1
  • Unused export 'safeParseReviewAction' src/modules/review-execution/entities/reviewAction/reviewAction.guard.ts:9 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'parseReviewActionCollection' · ×1
  • Unused export 'parseReviewActionCollection' src/modules/review-execution/entities/reviewAction/reviewAction.guard.ts:12 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AddLabelAction' · ×1
  • Unused export 'AddLabelAction' src/modules/review-execution/entities/reviewAction/reviewAction.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'PostInlineCommentAction' · ×1
  • Unused export 'PostInlineCommentAction' src/modules/review-execution/entities/reviewAction/reviewAction.ts:18 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'safeParseReviewContextResult' · ×1
  • Unused export 'safeParseReviewContextResult' src/modules/review-execution/entities/reviewContext/reviewContextResult.guard.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'BackfilledReviewResult' · ×1
  • Unused export 'BackfilledReviewResult' src/modules/review-execution/entities/reviewContext/reviewContextResult.schema.ts:24 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'formatInstructionsForPrompt' · ×1
  • Unused export 'formatInstructionsForPrompt' src/modules/review-execution/services/agentInstructionsBuilder.ts:49 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ConfirmAnswer' · ×1
  • Unused export 'ConfirmAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:7 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ChoiceAnswer' · ×1
  • Unused export 'ChoiceAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:8 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'MultiSelectAnswer' · ×1
  • Unused export 'MultiSelectAnswer' src/modules/setup-wizard/entities/answerLine/answerLine.schema.ts:9 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'StepStartedEvent' · ×1
  • Unused export 'StepStartedEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:68 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'StepCompletedEvent' · ×1
  • Unused export 'StepCompletedEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:69 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AwaitingInputEvent' · ×1
  • Unused export 'AwaitingInputEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:70 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'InstructionsBannerEvent' · ×1
  • Unused export 'InstructionsBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:71 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'WarningBannerEvent' · ×1
  • Unused export 'WarningBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:72 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'ResumeBannerEvent' · ×1
  • Unused export 'ResumeBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:73 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DoneBannerEvent' · ×1
  • Unused export 'DoneBannerEvent' src/modules/setup-wizard/entities/wizardStreamEvent/wizardStreamEvent.schema.ts:74 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AiDeveloperInsight' · ×1
  • Unused export 'AiDeveloperInsight' src/modules/statistics-insights/entities/insight/aiInsight.ts:9 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AiTeamInsight' · ×1
  • Unused export 'AiTeamInsight' src/modules/statistics-insights/entities/insight/aiInsight.ts:11 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'safeParseCategoryBreakdown' · ×1
  • Unused export 'safeParseCategoryBreakdown' src/modules/statistics-insights/entities/stats/categoryBreakdown.guard.ts:14 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'RecalculateBody' · ×1
  • Unused export 'RecalculateBody' src/modules/statistics-insights/entities/stats/recalculateBody.guard.ts:10 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DegradedReasonKind' · ×1
  • Unused export 'DegradedReasonKind' src/modules/worktree-management/entities/worktree/worktreeHealth.schema.ts:22 — Nothing imports this binding — it is safe to review for removal.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1
  • No app-layer HTTPS enforcement detected src/main/server.ts:292 — `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.)
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 2/5 async functions that make a cancellable request (fetch, axios, ky, ofetch) 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.
Minor — 11 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×11
  • Outdated (npm): @fastify/static — @fastify/static is pinned at 10.1.2; registry.npmjs.org publishes 10.1.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @fastify/websocket — @fastify/websocket is pinned at 11.2.0; registry.npmjs.org publishes 11.3.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @hono/node-server — @hono/node-server is pinned at 2.0.10; registry.npmjs.org publishes 2.1.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @inquirer/prompts — @inquirer/prompts is pinned at 8.2.0; registry.npmjs.org publishes 8.7.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.26.0; registry.npmjs.org publishes 1.32.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): animejs — animejs is pinned at 4.4.1; registry.npmjs.org publishes 4.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): dotenv — dotenv is pinned at 16.6.1; registry.npmjs.org publishes 18.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): fastify — fastify is pinned at 5.8.5; registry.npmjs.org publishes 5.12.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): p-queue — p-queue is pinned at 8.1.1; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): pino — pino is pinned at 8.21.0; registry.npmjs.org publishes 10.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): zod — zod is pinned at 4.3.6; registry.npmjs.org publishes 4.6.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-81a875d1005947059c0a478bc8df56a4/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-81a875d1005947059c0a478bc8df56a4/tree.json --exit-code 0 --source .0artifacts/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .63artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update23artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a164ac-aac1-7a40-a87e-b4f10c1f2250 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 37 · Warnings: 429 · Recommendations: 161 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 17:33 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md