Public report of feder-cr/AIHawk, published 20 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, 20 October 2026, 16:44 UTC · Survey ID cd_31a178bc715646cf835788fc63b06abf

feder-cr/AIHawk

Measured 20 October 2026, 15:58 UTC, at code version ef69f5e

Code coverage: not measured

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).

CAI score 55out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 4 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 87 Strong Security and Compliance 77 Adequate Accessibility 75 Strong Code Health 70 Adequate Performance 60 Adequate Production Readiness 54 Adequate Maturity 48 Weak

A medium codebase: 54,078 lines of product code in 15 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Maturity, 48

Findings by how serious they are

35 critical 433 serious 76 minor

11 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
20 October 2026, 15:58 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.

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.
519of 544 findings point to an exact file and line, so you can open each one in the code. The other 25 concern the repository as a whole, such as missing documentation.
88dimensions across 7 lenses, read from 54,078 lines of product code in 15 projects.
Chapters

Executive summary

feder-cr/AIHawk scores 55 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Architecture at 87 and Accessibility at 75, both rated Strong, and Security and Compliance at 77, Code Health at 70 and Performance at 60, all rated Adequate.

The score is lower than those five because the weakest lens counts most, and here that is Maturity, which scores 48 and is rated Weak. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to reconcile the README with reality: docs/architecture.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists; docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.json` exists; docs/architecture.md names `tools/list`, but no file or folder `tools/list` exists; docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` exists; docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists, and if Maturity rose to 70, the score would rise from 55 to about 61.

35 findings are critical: 33 in Static Analysis (SAST), one in Change Coupling and one in Dependency Hygiene.

Watchdog couldn't measure 9 dimensions in this code, among them Dependency Hygiene, Navigability and Data Protection, so they are left out of the score. The product code is 54,078 lines, which would take an estimated 0.8 person-years, around €120,000, to rebuild.

Code Health 70 Adequate, capped by Cognitive Complexity Architecture 87 Strong Maturity 48 Weak, capped by Documentation accuracy Production Readiness 54 Adequate, capped by Security & performance tooling Security and Compliance 77 Adequate, capped by Static Analysis (SAST) and Supply-chain Provenance & Signing Accessibility 75 Strong 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.
Maturity 48 · counts for 46%Production Readiness 54 · counts for 25%Performance 60 · counts for 14%Code Health 70 · counts for 8%Accessibility 75 · counts for 4%Security and Compliance 77 · counts for 2%Architecture 87 · counts for 1%

If Maturity rose from 48 to 70, the lowest score rated Strong, the score would rise from 55 to about 61.

Code composition: what the lines of code are
Product code 45%Tests 55%
New since the last survey: 456 findings

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

  • Cyclomatic Complexity · cli.run (cyclomatic 131) apps/cli/src/cli.ts
  • Cyclomatic Complexity · Schema.validate_json_schema_value (cyclomatic 54) invisible_engine_dots/nanobot/agent/tools/base.py
  • Cyclomatic Complexity · server.buildServer (cyclomatic 52) REDACTED
  • Cyclomatic Complexity · EditFileTool.execute (cyclomatic 50) invisible_engine_dots/nanobot/agent/tools/filesystem.py
  • Cyclomatic Complexity · GrepTool.execute (cyclomatic 44) invisible_engine_dots/nanobot/agent/tools/search.py
  • Cyclomatic Complexity · ApplyPatchTool.execute (cyclomatic 42) invisible_engine_dots/nanobot/agent/tools/apply_patch.py
  • Cyclomatic Complexity · AgentServer._handle (cyclomatic 41) REDACTED
  • Cyclomatic Complexity · qr-connect.QrConnect (cyclomatic 37) apps/web/src/components/channels/qr-connect.tsx
  • Cyclomatic Complexity · OpenAICompatProvider._parse_chunks (cyclomatic 37) REDACTED
  • Cyclomatic Complexity · AgentRunner._run_core (cyclomatic 34) invisible_engine_dots/nanobot/agent/runner.py
  • Cyclomatic Complexity · FakeBotApi.#handle (cyclomatic 33) packages/channels/src/telegram/fake-bot-api.ts
  • Cyclomatic Complexity · Scheduler.resolveApproval (cyclomatic 30) apps/scheduler/src/scheduler.ts
  • Cyclomatic Complexity · agentd.RunRelay (cyclomatic 30) guest/dot-agentd/internal/agentd/relay.go
  • Cyclomatic Complexity · NeedsYou.NeedsYou (cyclomatic 28) apps/web/src/components/inbox/NeedsYou.tsx
  • Cyclomatic Complexity · Tool._cast_value (cyclomatic 28) invisible_engine_dots/nanobot/agent/tools/base.py
  • Cyclomatic Complexity · task-drawer.TaskDrawer (cyclomatic 27) apps/web/src/components/tasks/task-drawer.tsx
  • Cyclomatic Complexity · agentd.runProcStream (cyclomatic 26) guest/dot-agentd/internal/agentd/proc.go
  • Cyclomatic Complexity · dot-live.applyLiveEvent (cyclomatic 24) apps/web/src/lib/dot-live.ts
  • Cyclomatic Complexity · DotSettings.Editor (cyclomatic 24) apps/web/src/components/dot-settings/DotSettings.tsx
  • Cyclomatic Complexity · Session.get_history (cyclomatic 24) invisible_engine_dots/nanobot/session/manager.py
  • Cyclomatic Complexity · approval-view.approvalBody (cyclomatic 22) apps/web/src/lib/approval-view.ts
  • Cyclomatic Complexity · FindFilesTool.execute (cyclomatic 22) invisible_engine_dots/nanobot/agent/tools/search.py
  • Cyclomatic Complexity · helpers._estimate_prompt_tokens_with_source (cyclomatic 22) invisible_engine_dots/nanobot/utils/helpers.py
  • Cyclomatic Complexity · Server.handleProc (cyclomatic 22) guest/dot-agentd/internal/agentd/proc.go
  • Cyclomatic Complexity · files-tab.FilesTab (cyclomatic 21) apps/web/src/components/computer/files-tab.tsx
  • Cyclomatic Complexity · ReadFileTool.execute (cyclomatic 21) invisible_engine_dots/nanobot/agent/tools/filesystem.py
  • Cyclomatic Complexity · ListDirTool.execute (cyclomatic 21) invisible_engine_dots/nanobot/agent/tools/filesystem.py
  • Cyclomatic Complexity · LLMProvider._sanitize_empty_content (cyclomatic 21) invisible_engine_dots/nanobot/providers/base.py
  • Cyclomatic Complexity · LLMProvider._enforce_role_alternation (cyclomatic 21) invisible_engine_dots/nanobot/providers/base.py
  • Cyclomatic Complexity · ActivityView.ActivityView (cyclomatic 20) apps/web/src/components/activity/ActivityView.tsx
  • Cyclomatic Complexity · wide.html.scenes (cyclomatic 20) docs/hero/html/wide.html
  • Cyclomatic Complexity · CronTool._add_job (cyclomatic 20) invisible_engine_dots/nanobot/agent/tools/cron.py
  • Cyclomatic Complexity · DotHeader.DotHeader (cyclomatic 19) apps/web/src/components/dot/DotHeader.tsx
  • Cyclomatic Complexity · file-preview.FilePreview (cyclomatic 19) apps/web/src/components/computer/file-preview.tsx
  • Cyclomatic Complexity · usage-tab.UsageTab (cyclomatic 19) apps/web/src/components/computer/usage-tab.tsx
  • Cyclomatic Complexity · mobile.html.scenes (cyclomatic 19) docs/hero/html/mobile.html
  • Cyclomatic Complexity · small.html.scenes (cyclomatic 19) docs/hero/html/small.html
  • Cyclomatic Complexity · process.acquirePidLock (cyclomatic 19) packages/shared/src/process.ts
  • Cyclomatic Complexity · exec_session._escape_end (cyclomatic 19) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cyclomatic Complexity · exec_session.terminal_text (cyclomatic 19) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cyclomatic Complexity · transcript_outbox._record_tool_result (cyclomatic 19) invisible_engine_dots/nanobot/dots/transcript_outbox.py
  • Cyclomatic Complexity · helpers.estimate_message_tokens (cyclomatic 19) invisible_engine_dots/nanobot/utils/helpers.py
  • Cyclomatic Complexity · guest-events.applyGuestEvent (cyclomatic 18) apps/scheduler/src/guest-events.ts
  • Cyclomatic Complexity · mcp-servers-panel.McpServersPanel (cyclomatic 18) apps/web/src/components/dot-settings/mcp-servers-panel.tsx
  • Cyclomatic Complexity · story.Body (cyclomatic 18) apps/web/src/components/tasks/story.tsx
  • Cyclomatic Complexity · transcript_outbox.record_transcript_append (cyclomatic 18) invisible_engine_dots/nanobot/dots/transcript_outbox.py
  • Cyclomatic Complexity · approval-card.ApprovalCard (cyclomatic 17) apps/web/src/components/elements/approval-card.tsx
  • Cyclomatic Complexity · yaml.emit (cyclomatic 17) apps/web/src/lib/yaml.ts
  • Cyclomatic Complexity · use-inbox-keys.useInboxKeys::onKeyDown (cyclomatic 17) apps/web/src/components/inbox/use-inbox-keys.ts
  • Cyclomatic Complexity · NewDotPage.NewDotPage (cyclomatic 17) apps/web/src/components/new-dot/NewDotPage.tsx
  • Cyclomatic Complexity · main.serve (cyclomatic 17) guest/dot-agentd/cmd/dot-agentd/main.go
  • Cyclomatic Complexity · web.startWebServer (cyclomatic 16) REDACTED
  • Cyclomatic Complexity · Lifecycle.#readyProcedure (cyclomatic 16) apps/scheduler/src/lifecycle.ts
  • Cyclomatic Complexity · GuestClient.sendRaw (cyclomatic 16) apps/vm-manager/src/guest-client.ts
  • Cyclomatic Complexity · VmManager.startLocked (cyclomatic 16) apps/vm-manager/src/vm-manager.ts
  • Cyclomatic Complexity · ChannelHub.#inbound (cyclomatic 16) packages/channels/src/hub.ts
  • Cyclomatic Complexity · InvisibleDotsClient.stream (cyclomatic 16) packages/sdk/src/client.ts
  • Cyclomatic Complexity · ContextGovernor.backfill_missing_tool_results (cyclomatic 16) invisible_engine_dots/nanobot/agent/context_governance.py
  • Cyclomatic Complexity · Consolidator.summarize (cyclomatic 16) invisible_engine_dots/nanobot/agent/memory.py
  • Cyclomatic Complexity · ExecSessionTool._wait (cyclomatic 16) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cyclomatic Complexity · service._validate_schedule_for_add (cyclomatic 16) invisible_engine_dots/nanobot/cron/service.py
  • Cognitive Complexity · cli.run (cognitive 222) apps/cli/src/cli.ts
  • Cognitive Complexity · ApplyPatchTool.execute (cognitive 100) invisible_engine_dots/nanobot/agent/tools/apply_patch.py
  • Cognitive Complexity · Schema.validate_json_schema_value (cognitive 74) invisible_engine_dots/nanobot/agent/tools/base.py
  • Cognitive Complexity · OpenAICompatProvider._parse_chunks (cognitive 74) REDACTED
  • Cognitive Complexity · AgentServer._handle (cognitive 65) REDACTED
  • Cognitive Complexity · AgentRunner._run_core (cognitive 64) invisible_engine_dots/nanobot/agent/runner.py
  • Cognitive Complexity · GrepTool.execute (cognitive 64) invisible_engine_dots/nanobot/agent/tools/search.py
  • Cognitive Complexity · EditFileTool.execute (cognitive 62) invisible_engine_dots/nanobot/agent/tools/filesystem.py
  • Cognitive Complexity · server.buildServer (cognitive 56) REDACTED
  • Cognitive Complexity · file-preview.FilePreview (cognitive 51) apps/web/src/components/computer/file-preview.tsx
  • Cognitive Complexity · agentd.RunRelay (cognitive 49) guest/dot-agentd/internal/agentd/relay.go
  • Cognitive Complexity · LLMProvider._sanitize_empty_content (cognitive 47) invisible_engine_dots/nanobot/providers/base.py
  • Cognitive Complexity · Session.get_history (cognitive 44) invisible_engine_dots/nanobot/session/manager.py
  • Cognitive Complexity · qr-connect.QrConnect (cognitive 43) apps/web/src/components/channels/qr-connect.tsx
  • Cognitive Complexity · ContextGovernor.backfill_missing_tool_results (cognitive 43) invisible_engine_dots/nanobot/agent/context_governance.py
  • Cognitive Complexity · agentd.runProcStream (cognitive 41) guest/dot-agentd/internal/agentd/proc.go
  • Cognitive Complexity · helpers._estimate_prompt_tokens_with_source (cognitive 40) invisible_engine_dots/nanobot/utils/helpers.py
  • Cognitive Complexity · Lifecycle.#readyProcedure (cognitive 38) apps/scheduler/src/lifecycle.ts
  • Cognitive Complexity · FakeBotApi.#handle (cognitive 38) packages/channels/src/telegram/fake-bot-api.ts
  • Cognitive Complexity · Tool._cast_value (cognitive 38) invisible_engine_dots/nanobot/agent/tools/base.py
  • Cognitive Complexity · ListDirTool.execute (cognitive 37) invisible_engine_dots/nanobot/agent/tools/filesystem.py
  • Cognitive Complexity · task-drawer.TaskDrawer (cognitive 36) apps/web/src/components/tasks/task-drawer.tsx
  • Cognitive Complexity · exec_session._escape_end (cognitive 36) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cognitive Complexity · LLMProvider._enforce_role_alternation (cognitive 35) invisible_engine_dots/nanobot/providers/base.py
  • Cognitive Complexity · ContextGovernor.drop_orphan_tool_results (cognitive 32) invisible_engine_dots/nanobot/agent/context_governance.py
  • Cognitive Complexity · GuestClient.events (cognitive 31) apps/vm-manager/src/guest-client.ts
  • Cognitive Complexity · Lifecycle.recover (cognitive 30) apps/scheduler/src/lifecycle.ts
  • Cognitive Complexity · InvisibleDotsClient.stream (cognitive 30) packages/sdk/src/client.ts
  • Cognitive Complexity · process.acquirePidLock (cognitive 30) packages/shared/src/process.ts
  • Cognitive Complexity · exec_session.terminal_text (cognitive 30) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cognitive Complexity · Scheduler.resolveApproval (cognitive 29) apps/scheduler/src/scheduler.ts
  • Cognitive Complexity · yaml.emit (cognitive 29) apps/web/src/lib/yaml.ts
  • Cognitive Complexity · DotSettings.Editor (cognitive 29) apps/web/src/components/dot-settings/DotSettings.tsx
  • Cognitive Complexity · CronTool._add_job (cognitive 28) invisible_engine_dots/nanobot/agent/tools/cron.py
  • Cognitive Complexity · ExecSessionTool._wait (cognitive 28) invisible_engine_dots/nanobot/agent/tools/exec_session.py
  • Cognitive Complexity · FindFilesTool.execute (cognitive 28) invisible_engine_dots/nanobot/agent/tools/search.py
  • Cognitive Complexity · OpenAICompatProvider._sanitize_messages (cognitive 28) REDACTED
  • Cognitive Complexity · DotHeader.DotHeader (cognitive 27) apps/web/src/components/dot/DotHeader.tsx
  • Cognitive Complexity · ContextGovernor.strip_malformed_tool_calls (cognitive 27) invisible_engine_dots/nanobot/agent/context_governance.py

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: 99 findings

These 99 critical or serious findings were in the previous survey, on 3 October 2026, and are gone from this one.

  • Cyclomatic Complexity · check_content.check_tree (cyclomatic 32) scripts/check_content.py
  • Cyclomatic Complexity · 01-markdown.blocks (cyclomatic 24) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cyclomatic Complexity · 06-sessions.drawChats (cyclomatic 23) src/invisible_playwright_mcp/ui/js/06-sessions.js
  • Cyclomatic Complexity · 03-which-session.onEvent (cyclomatic 21) src/invisible_playwright_mcp/ui/js/03-which-session.js
  • Cyclomatic Complexity · actions_help.summarise (cyclomatic 20) src/invisible_playwright_mcp/actions_help.py
  • Cyclomatic Complexity · check_content.check_way_in (cyclomatic 19) scripts/check_content.py
  • Cyclomatic Complexity · sync_article_pixels.selftest (cyclomatic 16) scripts/sync_article_pixels.py
  • Cyclomatic Complexity · actions.uploadable (cyclomatic 16) src/invisible_playwright_mcp/mcp/actions.py
  • Cyclomatic Complexity · 01-markdown.inline (cyclomatic 16) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cyclomatic Complexity · 05-browser.onePass (cyclomatic 16) src/invisible_playwright_mcp/ui/js/05-browser.js
  • Cognitive Complexity · check_content.check_tree (cognitive 67) scripts/check_content.py
  • Cognitive Complexity · check_content.check_way_in (cognitive 50) scripts/check_content.py
  • Cognitive Complexity · 05-browser.onePass (cognitive 42) src/invisible_playwright_mcp/ui/js/05-browser.js
  • Cognitive Complexity · drawChats (cognitive 28) src/invisible_playwright_mcp/ui/js/06-sessions.js
  • Cognitive Complexity · Conversation.run (cognitive 25) src/invisible_playwright_mcp/agent.py
  • Cognitive Complexity · clean._slim_attributes (cognitive 25) src/invisible_playwright_mcp/mcp/clean.py
  • Cognitive Complexity · 01-markdown.blocks (cognitive 25) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cognitive Complexity · sync_article_pixels.selftest (cognitive 23) scripts/sync_article_pixels.py
  • Cognitive Complexity · actions.uploadable (cognitive 23) src/invisible_playwright_mcp/mcp/actions.py
  • Cognitive Complexity · 03-which-session.onEvent (cognitive 23) src/invisible_playwright_mcp/ui/js/03-which-session.js
  • Cognitive Complexity · actions_help.summarise (cognitive 21) src/invisible_playwright_mcp/actions_help.py
  • Cognitive Complexity · check_content.way_in (cognitive 19) scripts/check_content.py
  • Cognitive Complexity · 01-markdown.listAt (cognitive 19) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cognitive Complexity · ageAll (cognitive 19) src/invisible_playwright_mcp/ui/js/05-browser.js
  • Cognitive Complexity · Work.open (cognitive 18) src/invisible_playwright_mcp/mcp/work.py
  • Cognitive Complexity · 01-markdown.inline (cognitive 18) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cognitive Complexity · actions.snapshot_files (cognitive 17) src/invisible_playwright_mcp/mcp/actions.py
  • Cognitive Complexity · check_content.check_client_lines (cognitive 16) scripts/check_content.py
  • God Classes · FileTooLong: mcp/actions.py src/invisible_playwright_mcp/mcp/actions.py
  • Code Duplication · Edited copy of a member (21 corresponding lines) scripts/pack_bundle.py
  • Code Duplication · Duplicated block (17 lines × 2) scripts/pack_bundle.py
  • Churn × Complexity Hotspots · Hotspot: scripts/check_content.py scripts/check_content.py
  • Churn × Complexity Hotspots · Hotspot: src/invisible_playwright_mcp/mcp/work.py src/invisible_playwright_mcp/mcp/work.py
  • Churn × Complexity Hotspots · Hotspot: src/invisible_playwright_mcp/ui/js/03-which-session.js src/invisible_playwright_mcp/ui/js/03-which-session.js
  • Churn × Complexity Hotspots · Hotspot: src/invisible_playwright_mcp/ui/js/06-sessions.js src/invisible_playwright_mcp/ui/js/06-sessions.js
  • Churn × Complexity Hotspots · Hotspot: src/invisible_playwright_mcp/actions_help.py src/invisible_playwright_mcp/actions_help.py
  • Secrets (history) · Secret: generic-api-key data_folder/secrets.yaml
  • Secrets (history) · Secret: generic-api-key data_folder_example/secrets.yaml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: gha-curl-pipe-shell .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/ci.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/content-gates.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/content-gates.yml
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/publish.yml
  • Static Analysis (SAST) · High: REDACTED .github/workflows/stale.yml
  • Supply-chain Provenance & Signing · PR-triggered workflow without a permissions block
  • Supply-chain Provenance & Signing · Secret handed to the step that runs a pull request's code
  • Type Safety · Type Safety
  • Cyclomatic Complexity · Complex function blocks (cyclomatic 24, cognitive 25) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cyclomatic Complexity · Complex function onEvent (cyclomatic 21, cognitive 23) src/invisible_playwright_mcp/ui/js/03-which-session.js
  • Cyclomatic Complexity · Complex function onePass (cyclomatic 16, cognitive 40) src/invisible_playwright_mcp/ui/js/05-browser.js
  • Cyclomatic Complexity · Complex function inline (cyclomatic 16, cognitive 18) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cyclomatic Complexity · Complex function listAt (cyclomatic 15, cognitive 19) src/invisible_playwright_mcp/ui/js/01-markdown.js
  • Cyclomatic Complexity · Complex function drawChats (cyclomatic 15, cognitive 17) src/invisible_playwright_mcp/ui/js/06-sessions.js
  • Cyclomatic Complexity · Complex function ageAll (cyclomatic 13, cognitive 19) src/invisible_playwright_mcp/ui/js/05-browser.js
  • Test Coverage · Test Coverage
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/storage.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/link.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/chats.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/chats.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/mcp/session.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/mcp/clean.py
  • Exception handling · Swallowed exception (caught, then discarded) src/invisible_playwright_mcp/mcp/actions.py
Rebuild cost: about €120,000 · Estimate
Cost to rebuild€40,000 to €200,000, for 660 to 2,093 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.8 at a score of 55. 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: 54,078 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 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 6 points · Low effort · ADR Quality
2
Reconcile the README with reality: docs/architecture.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists; docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.json` exists; docs/architecture.md names `tools/list`, but no file or folder `tools/list` exists; docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` exists; docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists.
Raises the score by about 6 points · Medium effort · Documentation accuracy
3
Resolve the 1 Documentation finding(s) in Documentation Quality — start with architecture.md.
Raises the score by about 2 points · Low effort · Documentation Quality

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 €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Maturity, at 48 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 ADR Quality 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.4 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 229,616 lines over the last 90 days, which is about 931,220 lines a year. At that pace, the extra work comes to an estimated 46.6 to 310.4 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 · Code Duplication · 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 — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch @invisible-dots/api api @invisible-dots/channels channels @invisible-dots/api->@invisible-dots/channels @invisible-dots/database database @invisible-dots/api->@invisible-dots/database @invisible-dots/events events @invisible-dots/api->@invisible-dots/events @invisible-dots/image-builder image-builder @invisible-dots/api->@invisible-dots/image-builder @invisible-dots/scheduler scheduler @invisible-dots/api->@invisible-dots/scheduler @invisible-dots/sdk sdk @invisible-dots/api->@invisible-dots/sdk @invisible-dots/shared shared @invisible-dots/api->@invisible-dots/shared @invisible-dots/vm-manager vm-manager @invisible-dots/api->@invisible-dots/vm-manager @invisible-dots/channels->@invisible-dots/database @invisible-dots/channels->@invisible-dots/events @invisible-dots/channels->@invisible-dots/shared @invisible-dots/cli cli @invisible-dots/cli->@invisible-dots/api @invisible-dots/cli->@invisible-dots/image-builder @invisible-dots/cli->@invisible-dots/sdk @invisible-dots/cli->@invisible-dots/shared @invisible-dots/cli->@invisible-dots/vm-manager @invisible-dots/database->@invisible-dots/shared @invisible-dots/events->@invisible-dots/database @invisible-dots/events->@invisible-dots/shared @invisible-dots/iso iso @invisible-dots/image-builder->@invisible-dots/iso @invisible-dots/image-builder->@invisible-dots/shared @invisible-dots/image-builder->@invisible-dots/vm-manager @invisible-dots/iso->@invisible-dots/shared @invisible-dots/scheduler->@invisible-dots/database @invisible-dots/scheduler->@invisible-dots/events @invisible-dots/scheduler->@invisible-dots/shared @invisible-dots/sdk->@invisible-dots/shared @invisible-dots/vm-manager->@invisible-dots/iso @invisible-dots/vm-manager->@invisible-dots/shared @invisible-dots/web web @invisible-dots/web->@invisible-dots/sdk @invisible-dots/web->@invisible-dots/shared github.com/feder-cr/dots/guest/dot-agentd dot-agentd invisible-dots-engine invisible-dots-engine invisible-dots-whatsapp-client invisible-dots-whatsapp-client

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.

333 modules, with 515 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; 293 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 invisible_engine_dots.nanobot.agent.tools.base2 invisible_engine_dots.nanobot.dots.computer3 invisible_engine_dots.nanobot.dots.store4 invisible_engine_dots.nanobot.providers.base5 packages.database.src.db6 packages.shared.src.events7 packages.shared.src.paths8 packages.shared.src.protocol9 packages.shared.src.support10 apps.scheduler.src.driver11 apps.vm-manager.src.vm-manager12 guest.image-builder.src.golden13 invisible_engine_dots.nanobot.agent.tools.registry14 invisible_engine_dots.nanobot.dots.browser15 packages.events.src.event-log16 packages.shared.src17 packages.shared.src.api18 apps.cli.src.setup19 apps.vm-manager.src.doctor20 apps.web.src.lib21 guest.image-builder.src22 invisible_engine_dots.nanobot.agent.runner23 invisible_engine_dots.nanobot.agent.tools24 invisible_engine_dots.nanobot.dots.mcp_servers25 packages.database.src.channels26 apps.cli.src27 apps.vm-manager.src28 invisible_engine_dots.nanobot.dots.turns29 packages.channels.src.channel30 packages.database.src.database31 apps.scheduler.src.lifecycle32 invisible_engine_dots.nanobot.dots.engine33 packages.channels.src.runner34 packages.database.src35 apps.scheduler.src.scheduler36 invisible_engine_dots.nanobot.dots37 packages.channels.src.hub38 apps.api.src.start39 apps.api.src40 apps.web.e2e.harness
1 invisible_engine_dots.nanobot.agent.tools.base
2 invisible_engine_dots.nanobot.dots.computer
3 invisible_engine_dots.nanobot.dots.store
4 invisible_engine_dots.nanobot.providers.base
5 packages.database.src.db
6 packages.shared.src.events
7 packages.shared.src.paths
8 packages.shared.src.protocol
9 packages.shared.src.support
10 apps.scheduler.src.driver11
11 apps.vm-manager.src.vm-manager22
12 guest.image-builder.src.golden2
13 invisible_engine_dots.nanobot.agent.tools.registry1
14 invisible_engine_dots.nanobot.dots.browser12
15 packages.events.src.event-log2
16 packages.shared.src341
17 packages.shared.src.api1
18 apps.cli.src.setup2
19 apps.vm-manager.src.doctor1
20 apps.web.src.lib414
21 guest.image-builder.src13
22 invisible_engine_dots.nanobot.agent.runner21
23 invisible_engine_dots.nanobot.agent.tools12
24 invisible_engine_dots.nanobot.dots.mcp_servers2113
25 packages.database.src.channels14
26 apps.cli.src1122
27 apps.vm-manager.src11155
28 invisible_engine_dots.nanobot.dots.turns121111
29 packages.channels.src.channel1
30 packages.database.src.database31
31 apps.scheduler.src.lifecycle15323
32 invisible_engine_dots.nanobot.dots.engine131113
33 packages.channels.src.runner11121
34 packages.database.src61662
35 apps.scheduler.src.scheduler144121022
36 invisible_engine_dots.nanobot.dots245124131
37 packages.channels.src.hub2415161
38 apps.api.src.start1111121
39 apps.api.src4212
40 apps.web.e2e.harness11
Uses a module listed above itPart of a loopThe module itself
1 invisible_engine_dots.nanobot.agent.tools.base2 invisible_engine_dots.nanobot.dots.computer3 invisible_engine_dots.nanobot.dots.store4 invisible_engine_dots.nanobot.providers.base5 packages.database.src.db6 packages.shared.src.events7 packages.shared.src.paths8 packages.shared.src.protocol9 packages.shared.src.support10 apps.scheduler.src.driver11 apps.vm-manager.src.vm-manager12 guest.image-builder.src.golden13 invisible_engine_dots.nanobot.agent.tools.registry14 invisible_engine_dots.nanobot.dots.browser15 packages.events.src.event-log16 packages.shared.src17 packages.shared.src.api18 apps.cli.src.setup19 apps.vm-manager.src.doctor20 apps.web.src.lib21 guest.image-builder.src22 invisible_engine_dots.nanobot.agent.runner23 invisible_engine_dots.nanobot.agent.tools24 invisible_engine_dots.nanobot.dots.mcp_servers25 packages.database.src.channels26 apps.cli.src27 apps.vm-manager.src28 invisible_engine_dots.nanobot.dots.turns29 packages.channels.src.channel30 packages.database.src.database31 apps.scheduler.src.lifecycle32 invisible_engine_dots.nanobot.dots.engine33 packages.channels.src.runner34 packages.database.src35 apps.scheduler.src.scheduler36 invisible_engine_dots.nanobot.dots37 packages.channels.src.hub38 apps.api.src.start39 apps.api.src40 apps.web.e2e.harnessinvisible_engine_dots.nanobot.agent.tools.base1invisible_engine_dots.nanobot.dots.computer2invisible_engine_dots.nanobot.dots.store3invisible_engine_dots.nanobot.providers.base4packages.database.src.db5packages.shared.src.events6packages.shared.src.paths7packages.shared.src.protocol8packages.shared.src.support9apps.scheduler.src.driver10apps.vm-manager.src.vm-manager11guest.image-builder.src.golden12invisible_engine_dots.nanobot.agent.tools.registry13invisible_engine_dots.nanobot.dots.browser14packages.events.src.event-log15packages.shared.src16packages.shared.src.api17apps.cli.src.setup18apps.vm-manager.src.doctor19apps.web.src.lib20guest.image-builder.src21invisible_engine_dots.nanobot.agent.runner22invisible_engine_dots.nanobot.agent.tools23invisible_engine_dots.nanobot.dots.mcp_servers24packages.database.src.channels25apps.cli.src26apps.vm-manager.src27invisible_engine_dots.nanobot.dots.turns28packages.channels.src.channel29packages.database.src.database30apps.scheduler.src.lifecycle31invisible_engine_dots.nanobot.dots.engine32packages.channels.src.runner33packages.database.src34apps.scheduler.src.scheduler35invisible_engine_dots.nanobot.dots36packages.channels.src.hub37apps.api.src.start38apps.api.src39apps.web.e2e.harness4011222112234112141413211221131411221115512111113115323131113111216166214412102224512413124151611111121421211+293 more modules (most-connected shown)

At a glance — Code Health · 70% · Adequate · gated by D2 ·

The Good
D3 · TypeScript God Classes 7.9 D4 · TypeScript Code Duplication 9.9 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 9.2 R2 · React / TS Cyclomatic Complexity 8.8 R3 · React / TS Large Files 8.4 R7 · React / TS Dead Code 9.9 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 9.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 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 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 9.0
The Bad
D1 · TypeScript Cyclomatic Complexity 5.7 X3 · Repo Exception handling 5.9
The Ugly
D2 · TypeScript Cognitive Complexity 4.0 X4 · Repo Structured logging 4.8

At a glance — Architecture · 87% · Strong ·

The Good
D5 · TypeScript Coupling 9.3 D6 · TypeScript Cohesion (LCOM4) 10.0 D26 · TypeScript Project Cohesion 7.3 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 7.3 AX2 · Repo Stateful singletons 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.9 R11 · React / TS Import Boundaries 8.0 R9 · React / TS Circular Imports 10.0
The Bad
D22 · TypeScript Internal API Consistency 6.0

At a glance — Maturity · 48% · Weak · gated by M4 ·

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

At a glance — Readiness · 54% · Adequate · gated by P3 ·

The Good
D9 · TypeScript Test Distribution 9.6 D10 · TypeScript Test Quality 10.0 D11 · TypeScript Test Reliability 10.0 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 7.3 P7 · Repo Outbound HTTP resilience 10.0 P8 · Repo Schema migrations 10.0 R4 · React / TS Test Coverage 9.3 R5 · React / TS Dependency Freshness 8.6 R6 · React / TS Tooling 10.0
The Bad
P4 · Repo Deployment & Rollback 5.0 R8 · React / TS Dependency Hygiene 6.0
The Ugly
P3 · Repo Security & performance tooling 0.0

At a glance — Security · 77% · Adequate · gated by D29, D36 ·

The Good
D28 · TypeScript Secrets (history) 10.0 D30 · TypeScript Dependency Vulnerabilities 9.8 D31 · TypeScript IaC & Container Security 10.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
The Ugly
D29 · TypeScript Static Analysis (SAST) 2.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 2.0 X24 · Repo Document value interpolated into markup unescaped 4.8

At a glance — Domain Modelling · — · — ·

The Good
DM9 · Repo Scattered domain decisions 8.8

At a glance — Accessibility · 75% · Strong ·

The Good
AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0
The Bad
AC3 · Repo Page structure 6.8
The Ugly
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 — Injection56High / Critical
A03:2025 — Software Supply Chain Failures7Medium

Roadmap

First, resolve the missing Architectural Decision Records and reconcile documentation drift by updating references to non-existent files in the architecture and guide docs. Next, establish a dedicated folder for decision records to capture significant design choices with their context and consequences, and add a quick-start build section to the root README to help newcomers. Finally, integrate a static analysis security tool into the CI pipeline to ensure security regressions fail the build automatically.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.+6.4 ptsLowADR Quality
Reconcile the README with reality: docs/architecture.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists; docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.json` exists; docs/architecture.md names `tools/list`, but no file or folder `tools/list` exists; docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` exists; docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists.+6.2 ptsMediumDocumentation accuracy
Resolve the 1 Documentation finding(s) in Documentation Quality — start with architecture.md.+2.1 ptsLowDocumentation Quality
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+3.9 ptsMediumArchitecture documentation
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+3.1 ptsMediumDocumentation (README)
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+3.1 ptsMediumSecurity & performance tooling
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.+2.2 ptsMediumAsync & latency hygiene
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.+1.5 ptsMediumDeployment & Rollback

File quality

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

FileScoreBandWorst signal
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
apps/scheduler/src/scheduler.ts3.6SlopChange Coupling: Boundary-crossing change coupling: scheduler.ts ↔ client.ts
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
invisible_engine_dots/nanobot/agent/tools/filesystem.py7.0MixedCyclomatic Complexity: EditFileTool.execute (cyclomatic 50)
invisible_engine_dots/nanobot/agent/tools/exec_session.py7.0MixedCyclomatic Complexity: exec_session._escape_end (cyclomatic 19)
invisible_engine_dots/nanobot/utils/helpers.py7.0MixedCyclomatic Complexity: helpers._estimate_prompt_tokens_with_source (cyclomatic 22)
invisible_engine_dots/nanobot/providers/base.py7.0MixedCyclomatic Complexity: LLMProvider._sanitize_empty_content (cyclomatic 21)
apps/scheduler/src/lifecycle.ts7.0MixedCyclomatic Complexity: Lifecycle.#readyProcedure (cyclomatic 16)
invisible_engine_dots/nanobot/agent/context_governance.py7.0MixedCyclomatic Complexity: ContextGovernor.backfill_missing_tool_results (cyclomatic 16)
invisible_engine_dots/nanobot/agent/tools/search.py7.1MixedCyclomatic Complexity: GrepTool.execute (cyclomatic 44)
invisible_engine_dots/nanobot/agent/runner.py7.1MixedCyclomatic Complexity: AgentRunner._run_core (cyclomatic 34)
apps/cli/src/cli.ts7.2MixedCyclomatic Complexity: cli.run (cyclomatic 131)
invisible_engine_dots/nanobot/agent/tools/base.py7.2MixedCyclomatic Complexity: Schema.validate_json_schema_value (cyclomatic 54)
guest/dot-agentd/internal/agentd/proc.go7.2MixedCyclomatic Complexity: agentd.runProcStream (cyclomatic 26)
invisible_engine_dots/nanobot/dots/transcript_outbox.py7.2MixedCyclomatic Complexity: transcript_outbox._record_tool_result (cyclomatic 19)

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 — 35

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 — 433

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 — 76

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

Could not be resolved — 11

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
D1D2D3D4D5D6D9D10D11D13D14D15D17D19D20D21D22D26D28D29D30D31D34D35D36D37D43D44AC1AC2AC3AC5AC6AC7AX10AX2AX3AX4AX6DM9GD1IC1M1M2M3M4P1P10P2P3P4P7P8PF3R1R10R11R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X26X27X28X29X3X30X4X5

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, 519 of 544 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ 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 01a15a09-7ac6-7146-8ff9-64cb03b5c8ac.

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.

  • D10 Test Quality — 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. The 1,984 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 160 test source file(s) (.go, .py) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D12 Dependency Hygiene — 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. Not scored — 3 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its Python distribution dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 418 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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. `REDACTED`, `apps/cli/src/cli.ts`, `apps/cli/src/host.ts`, `apps/web/src/components/channels/channel-card.tsx`, `apps/web/src/components/setup/CheckList.tsx`, … (+7 more) 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.
  • 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.
  • C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
  • S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X3 Exception handling — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.

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.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — 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.
  • 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.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • 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".

The LLM boundary

LLM-set scores this run (5): D19, D21, D22, D26, 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 Complexity5.7 / 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 5.7 / 10 · rule-coverage 100% · ceiling Prevented

61 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was cli.run at 131.

cli.run (cyclomatic 131)apps/cli/src/cli.ts:350
Schema.validate_json_schema_value (cyclomatic 54)invisible_engine_dots/nanobot/agent/tools/base.py:56
server.buildServer (cyclomatic 52)REDACTED:101
EditFileTool.execute (cyclomatic 50)invisible_engine_dots/nanobot/agent/tools/filesystem.py:594
GrepTool.execute (cyclomatic 44)invisible_engine_dots/nanobot/agent/tools/search.py:524

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with cli.run (cyclomatic 131). — Refactoring it lifts Cyclomatic Complexity from 5.7 to about 6.5/10.
  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 Complexity4.0 / 10Weak✓ 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 4.0 / 10 · rule-coverage 100% · ceiling Prevented

100 method(s) exceeded the cognitive complexity threshold of 15; the worst was cli.run at 222.

cli.run (cognitive 222)apps/cli/src/cli.ts:350
ApplyPatchTool.execute (cognitive 100)invisible_engine_dots/nanobot/agent/tools/apply_patch.py:96
Schema.validate_json_schema_value (cognitive 74)invisible_engine_dots/nanobot/agent/tools/base.py:56
OpenAICompatProvider._parse_chunks (cognitive 74)REDACTED:613
AgentServer._handle (cognitive 65)REDACTED:250

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with cli.run (cognitive 222). — Refactoring it lifts Cognitive Complexity from 4.0 to about 4.9/10.
  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 Classes7.9 / 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 7.9 / 10 · rule-coverage 100% · ceiling Prevented

33 god class(es) detected.

FileTooLong: tools/mcp.py · ×16invisible_engine_dots/nanobot/agent/tools/mcp.py
TooManyMethods: InvisibleDotsClient · ×9packages/sdk/src/client.ts:97
FunctionTooLong: cli.run · ×6apps/cli/src/cli.ts:350
ClassTooLong: Scheduler · ×2apps/scheduler/src/scheduler.ts:95

What to do

  1. Resolve the 16 FileTooLong finding(s) in God Classes — start with mcp.py, base.py, runner.py. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 9 TooManyMethods finding(s) in God Classes — start with client.ts, scheduler.ts, lifecycle.ts. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 6 FunctionTooLong finding(s) in God Classes — start with cli.ts, REDACTED, DotSettings.tsx. — One of this dimension's main actionable groups (6 warning-level).
  4. 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.

D4 · Code Duplication9.9 / 10Stronggated by 8 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

8 duplicated block group(s) detected. Measured on part of this repository only: .ts, .tsx (62% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (13 lines × 2) · ×2invisible_engine_dots/nanobot/agent/context.py:101
Duplicated block (16 lines × 2)invisible_engine_dots/nanobot/agent/tools/filesystem.py:382
Duplicated block (13–14 lines × 2)invisible_engine_dots/nanobot/agent/runner.py:563
Duplicated block (10 lines × 2)invisible_engine_dots/nanobot/agent/tools/mcp.py:687
Duplicated block (6 lines × 2)invisible_engine_dots/nanobot/dots/browser.py:542

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

What to do

  1. Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with context.py, exec.go. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with filesystem.py. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Duplicated block (13–14 lines × 2) finding(s) in Code Duplication — start with runner.py. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling9.3 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

15 production modules (npm+Go+Python), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 14 of the 15 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Unstable project @invisible-dots/api
Off the main sequence: @invisible-dots/shared

What to do

  1. Resolve the 1 Unstable project @invisible-dots/api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 43 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution9.6 / 10Exemplary✓ 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.6 / 10 · rule-coverage 100% · ceiling Documented

3741 test methods: 3617 unit, 0 integration, 0 BDD, 124 e2e. The JavaScript/TypeScript suite contributes 1984 `it`/`test` case(s) across 172 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 1654 test function(s) across 99 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only. The Go suite contributes 103 test case(s) across 20 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 0 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 8 serious findings✓ 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

2 skipped (2 with a documented reason), 3 zero-assertion, 5 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1984 tests. Measured on the JavaScript/TypeScript suite only — at least 160 test source file(s) (.go, .py) went unread, so its test quality is unmeasured and is not in these counts.

Fixed-sleep synchronisation: claims a task whose Dot's row another transaction held for a moment, without waiting for the timer · ×5apps/scheduler/test/scheduler.test.ts:73
No assertions: starts a VM that stopped by itself at once when a run is due, by the same rule as the idle sleep · ×3apps/scheduler/test/scheduler.test.ts:712
Skipped (documented): (unnamed test) · ×2guest/image-builder/test/guest-files.test.ts:50

What to do

  1. Resolve the 5 Fixed-sleep synchronisation finding(s) in Test Quality — start with scheduler.test.ts (2), units.test.ts, repositories.test.ts. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 No assertions finding(s) in Test Quality — start with scheduler.test.ts, delivery.test.ts, events.test.ts. — One of this dimension's main actionable groups (3 warning-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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 2 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in the repository root (2206 tests); vitest via `npm ci --ignore-scripts` in apps/web/ (487 tests)): measured (0 flaky); Python (invisible_engine_dots, 99 test files): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.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 21 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 3 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (18 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.5 / 10Stronggated by 34 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.5 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: apps/web/test/support/control-plane.ts (26×188=4888); apps/cli/src/cli.ts (21×131=2751); REDACTED (26×52=1352)

Hotspot: apps/web/test/support/control-plane.ts · ×34apps/web/test/support/control-plane.ts:279

What to do

  1. Resolve the 34 Hotspot finding(s) in Churn × Complexity Hotspots — start with control-plane.ts, cli.ts, REDACTED. — One of this dimension's main actionable groups (34 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 53564 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 QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

This repository is well documented: the root README gives a clear overview and a runnable Quickstart for Node 24+, Go 1.25+, Git, hardware virtualization, and an OpenRouter key; each guest/dot-agentd/README.md documents its own directory (the dot-agentd daemon, image-builder, benchmarks) with installation commands and the architecture document docs/architecture.md is a complete reference contract for every part of the repository. The invisible_dots project's documentation is excellent: the README and its sibling guide.md are one-page usage documents that explain what a Dot is (an autonomous AI agent with its own computer) and how to run it; the architecture/Docs hierarchy contains sixteen markdown files covering every study, each named in the outline and present. The guide is an internal-facing single page but the visible_dots README is the project's overview, installation, usage, contribution, and license — all there. The visible documentation is mostly a well-structured set of studies (token-counts across models) and an HTML hero page with a short overview plus the invisible-dots project description, but it is heavily fragmented into unconnected web pages rather than a cohesive repository-level README. The main content is a single study document plus a thin hero page; no root README covers what the project does, installation, usage, or contribution guidance.

Documentation: contradicts the codedocs/architecture.md

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with architecture.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.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 ConsistencyAdequate◐ 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 Adequate / 10 · rule-coverage 100% · ceiling Verified

4 API inconsistencies across a 400-member sample of 232 exposed types.

Duplicate method names with identical signatures and likely identical intent. 'prepare_messages_for_model' and 'prepare_for_model' are semantically redundant.
Inconsistent parameter naming for directory paths. ExecTool uses both 'working_dir' and 'workdir' as potential parameters (or accepts either), while ExecSessionTool does not expose directory parameters in its execute signature (likely inheriting from session context). However, within ExecTool, having both 'working_dir' and 'workdir' suggests an aliasing inconsistency or redundant parameter support.
While 'get' and 'has' are distinct operations (one returns the object, one returns a boolean), the presence of 'has' often indicates a lack of Pythonic 'in' operator support or redundancy if 'get' is used for existence checks. However, this is a minor style issue. A more significant inconsistency is found in the Tool base class vs specific tools.
Inconsistent error representation in hook contexts. AgentHookContext only stores the error as a string, while AgentRunHookContext stores both the error string and the original exception object. This creates an inconsistency in the information available to hooks depending on which context they receive.

What to do

  1. Resolve the 1 Duplicate method names with identical signatures and likely identical… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Inconsistent parameter naming for directory paths. ExecTool uses both… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 While 'get' and 'has' are distinct operations (one returns the object,… 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.

D26 · Project Cohesion7.3 / 10Strong✓ 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 7.3 / 10 · rule-coverage 100% · ceiling Documented

2 of 15 build units (Go, Python, npm) flagged as possibly oversized/incoherent.

Split apps/web

What to do

  1. Resolve the 1 Split apps/web 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)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)2.0 / 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 2.0 / 10 · rule-coverage 100% · ceiling Documented

56 finding(s): 0 critical, 33 high, 15 medium, 8 low. 29 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 15 file(s) — `REDACTED` (line 32), `apps/cli/src/cli.ts` (line 33), `apps/cli/src/host.ts` (line 41), `apps/web/src/components/channels/channel-card.tsx` (line 7), `apps/web/src/components/setup/CheckList.tsx` (line 14), … (+10 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities9.8 / 10Stronggated by 1 serious finding✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.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 251 of the 443 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 / 10Adequategated by 1 critical 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: scheduler.ts↔client.ts 86%; scheduler.ts↔testing.ts 50%

Boundary-crossing change coupling: scheduler.ts ↔ client.tsapps/scheduler/src/scheduler.ts:1
Change coupling: scheduler.ts ↔ testing.tsapps/scheduler/src/scheduler.ts:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with scheduler.ts. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Change coupling finding(s) in Change Coupling — start with scheduler.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

+ 1 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. — One of this dimension's main actionable groups (1 recommendation-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 1 platform declaration(s) and 3 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 & labels10.0 / 10Exemplary○ Nothing flagged

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.

AC3 · Page structure6.8 / 10Adequate✓ Tool-verified

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.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/web/src/app/layout.tsx:24

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA 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 safety10.0 / 10Exemplary○ Nothing flagged

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.

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 — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 124 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: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition7.3 / 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.
AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX6 · Interface segregation9.9 / 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.

  • `GuestApi` declares 19 required operations: `health`, `system`, `pushSecrets`, `putConfig`, `postEvent`, `state`, `listBrowserIdentities`, `createBrowserIdentity`, `getBrowserIdentity`, `deleteBrowserIdentity`, `getBrowserIdentityFrame`, `closeBrowserIdentity`, `listTools`, `listSkills`, `prepareSleep`, `screenshot`, `readFile`, `listFiles`, `events`. 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. — apps/scheduler/src/driver.ts:32

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
DM9 · Scattered domain decisions8.8 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

  • apps.web.src.components.ui.Resource's [data, error] are judged in apps.web.src.components.settings.HostSettings, apps.web.src.components.shell.Rail, apps.web.src.components.shell.attention — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • packages.shared.src.events.StoredEvent's [data, id, type] are judged in tests.e2e.lib, tests.e2e.run — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
  • packages.shared.src.events.StoredEvent's [data, type] are judged in tests.e2e.lib, tests.e2e.run, tests.e2e.scale — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.

What to do

  • Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
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 & stubs10.0 / 10Exemplary○ Nothing flagged

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.

  • `trace` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/channels/src/whatsapp-baileys/baileys.ts:51
  • `debug` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/channels/src/whatsapp-baileys/baileys.ts:52, packages/shared/src/support.ts:21
  • `info` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/channels/src/whatsapp-baileys/baileys.ts:53, packages/shared/src/support.ts:21
  • `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/channels/src/whatsapp-baileys/baileys.ts:54, packages/shared/src/support.ts:21
  • `error` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — packages/channels/src/whatsapp-baileys/baileys.ts:55, packages/shared/src/support.ts:21

What to do

  • Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)6.3 / 10Adequate✓ 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 13 of 15 project(s) that lack one — worth up to 1.7 pts.
M2 · Architecture documentation5.0 / 10Adequate✓ 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.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project 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.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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.md:893
  • docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.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/architecture.md:1194
  • docs/architecture.md names `tools/list`, but no file or folder `tools/list` 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.md:1352
  • docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` 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/guide.md:175
  • docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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/wiki/agent-memory-systems-compared.md:10
  • docs/wiki/how-a-dot-remembers.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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/wiki/how-a-dot-remembers.md:17
  • docs/wiki/mcp-servers-a-person-declares.md names `.mcp.json`, but no file or folder `.mcp.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/wiki/mcp-servers-a-person-declares.md:18
  • docs/wiki/mcp-servers-a-person-declares.md names `config.toml`, but no file or folder `config.toml` 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/wiki/mcp-servers-a-person-declares.md:19
  • docs/wiki/mcp-servers-a-person-declares.md names `config.yaml`, but no file or folder `config.yaml` 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/wiki/mcp-servers-a-person-declares.md:38
  • docs/wiki/the-browser-servers-own-words.md documents the environment variable `PAGE_RULES`, 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/wiki/the-browser-servers-own-words.md:98
  • docs/wiki/the-browser-servers-own-words.md names `packages/core/src/mcp/instructions.ts`, but no file or folder `packages/core/src/mcp/instructions.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/wiki/the-browser-servers-own-words.md:99
  • tests/bench/README.md names `tests/grade.py`, but no file or folder `tests/grade.py` 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. — tests/bench/README.md:35
  • tests/bench/README.md names `tests/test.sh`, but no file or folder `tests/test.sh` 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. — tests/bench/README.md:35
  • tests/e2e/README.md names `.stealth-identity.json`, but no file or folder `.stealth-identity.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. — tests/e2e/README.md:49
  • tests/e2e/README.md runs `docker rm -f idots-e2e`, but `idots-e2e` 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. — tests/e2e/README.md:187
  • guest/image-builder/test/smoke/README.md names `.stealth-identity.json`, but no file or folder `.stealth-identity.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. — guest/image-builder/test/smoke/README.md:110

What to do

  • Reconcile the README with reality: docs/architecture.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists; docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.json` exists; docs/architecture.md names `tools/list`, but no file or folder `tools/list` exists; docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` exists; docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` exists.
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 · Observability7.3 / 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.

  • Only 7/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/web`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • 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 19977 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.

  • The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

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.

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

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.

  • `openSync` in `spawnDetached` 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. — apps/vm-manager/src/runner.ts:172
  • `closeSync` in `spawnDetached` 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. — apps/vm-manager/src/runner.ts:195
  • `appendFileSync` in `spawnDetached` 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) — apps/vm-manager/test/fakes.ts:152, apps/vm-manager/test/fakes.ts:170
  • `writeFileSync` in `spawnDetached` 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. — apps/vm-manager/test/fakes.ts:171
  • `appendFileSync` in `callback to setTimeout` 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. — apps/vm-manager/test/fakes.ts:175

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.9 / 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 Duplication9.2 / 10Exemplary✓ 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.

  • 11 duplicated blocks under apps/web/src/components/ have copies in at least two of the sibling directories approvals, chat, computer, dot-settings, elements, inbox (+4 more sibling(s) not listed) — 9 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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. — apps/web/src/components/dot-settings/panels.tsx:43
  • 6 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, guest, packages — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — guest/image-builder/src/manifest.ts:81
  • apps/web/src/components/ui/dialog.tsx:11 · apps/web/src/components/ui/sheet.tsx:9 — the two spans are one implementation copied and then locally edited — 475 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. — apps/web/src/components/ui/dialog.tsx:11
  • apps/web/src/components/dot-settings/panels.tsx:43 · apps/web/src/components/new-dot/FormSections.tsx:88 — the two spans are one implementation copied and then locally edited — 422 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. — apps/web/src/components/dot-settings/panels.tsx:43
  • apps/web/src/components/new-dot/Field.tsx:92 · apps/web/src/components/new-dot/Field.tsx:140 — the two spans are one implementation copied and then locally edited — 153 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/web/src/components/new-dot/Field.tsx:92
  • packages/channels/src/hub.ts:176 · packages/channels/src/hub.ts:265 — the two spans are one implementation copied and then locally edited — 160 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/channels/src/hub.ts:176
  • apps/web/src/components/inbox/History.tsx:67 · apps/web/src/components/tasks/history-table.tsx:62 — 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. — apps/web/src/components/inbox/History.tsx:67
  • apps/web/src/components/inbox/NeedsYou.tsx:180 · apps/web/src/components/inbox/NeedsYou.tsx: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. — apps/web/src/components/inbox/NeedsYou.tsx:180
  • apps/web/src/lib/computer-view.ts:9 · apps/web/src/lib/inbox.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/web/src/lib/computer-view.ts:9
  • apps/web/src/components/chat/chat-data.tsx:81 · apps/web/src/components/tasks/tasks-data.tsx:173 — the two spans are one implementation copied and then locally edited — 92 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. — apps/web/src/components/chat/chat-data.tsx:81
  • apps/web/src/components/computer/files-tab.tsx:112 · apps/web/src/components/inbox/History.tsx:72 · apps/web/src/components/tasks/history-table.tsx:70 — 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. — apps/web/src/components/computer/files-tab.tsx:112
  • apps/web/src/components/computer/usage-tab.tsx:45 · apps/web/src/components/inbox/NeedsYou.tsx:29 — the two spans are one implementation copied and then locally edited — 55 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. — apps/web/src/components/computer/usage-tab.tsx:45
  • apps/web/src/components/dot-settings/mcp-servers-panel.tsx:83 · apps/web/src/components/dot-settings/mcp-servers-panel.tsx:94 — 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. — apps/web/src/components/dot-settings/mcp-servers-panel.tsx:83
  • packages/database/src/pglite.ts:50 · packages/database/src/postgres.ts:78 — the two spans are one implementation copied and then locally edited — 97 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. — packages/database/src/pglite.ts:50
  • apps/scheduler/src/inbound.ts:156 · apps/scheduler/src/support.ts:50 — the two spans are one implementation copied and then locally edited — 58 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. — apps/scheduler/src/inbound.ts:156
  • apps/web/src/components/approvals/approval-body.tsx:26 · apps/web/src/components/approvals/approval-body.tsx:35 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/web/src/components/approvals/approval-body.tsx:26
  • guest/image-builder/src/manifest.ts:81 · packages/shared/src/files.ts:94 — the two spans are one implementation copied and then locally edited — 75 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. — guest/image-builder/src/manifest.ts:81
  • packages/shared/src/files.ts:93 · packages/shared/src/process.ts:195 — the two spans are one implementation copied and then locally edited — 63 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. — packages/shared/src/files.ts:93
  • apps/scheduler/src/lifecycle.ts:337 · apps/scheduler/src/lifecycle.ts:597 — 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. — apps/scheduler/src/lifecycle.ts:337
  • packages/database/src/computers.ts:58 · packages/database/src/inbound.ts:77 · packages/database/src/tasks.ts:120 — 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. — packages/database/src/computers.ts:58
  • packages/sdk/src/client.ts:190 · packages/sdk/src/client.ts:311 — 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. — packages/sdk/src/client.ts:190
  • apps/scheduler/src/scheduler.ts:534 · apps/scheduler/src/scheduler.ts:543 — 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. — apps/scheduler/src/scheduler.ts:534
  • apps/vm-manager/src/guest-client.ts:227 · packages/shared/src/sockets.ts:94 — the two spans are one implementation copied and then locally edited — 78 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. — apps/vm-manager/src/guest-client.ts:227
  • apps/web/src/components/approvals/TaskApprovals.tsx:15 · apps/web/src/components/inbox/NeedsYou.tsx:128 — the two spans are one implementation copied and then locally edited — 137 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. — apps/web/src/components/approvals/TaskApprovals.tsx:15
  • apps/web/src/components/approvals/approval-body.tsx:62 · apps/web/src/components/elements/approval-card.tsx:104 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/web/src/components/approvals/approval-body.tsx:62
  • apps/web/src/components/inbox/use-history.ts:46 · apps/web/src/components/inbox/use-history.ts:66 — 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. — apps/web/src/components/inbox/use-history.ts:46
  • packages/channels/src/telegram/telegram.ts:127 · packages/channels/src/whatsapp-baileys/whatsapp.ts:120 — the two spans are one implementation copied and then locally edited — 56 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. — packages/channels/src/telegram/telegram.ts:127
  • packages/channels/src/testing.ts:47 · packages/channels/src/whatsapp-baileys/whatsapp.ts:121 — the two spans are one implementation copied and then locally edited — 56 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. — packages/channels/src/testing.ts:47
  • apps/api/src/vm-driver.ts:26 · packages/database/src/migrate.ts:39 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/api/src/vm-driver.ts:26
  • apps/cli/src/cli.ts:463 · apps/cli/src/cli.ts:476 — 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. — apps/cli/src/cli.ts:463
  • apps/web/src/components/chat/chat-data.tsx:42 · apps/web/src/components/chat/chat-data.tsx:66 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — apps/web/src/components/chat/chat-data.tsx:42
  • packages/channels/src/telegram/telegram.ts:128 · packages/channels/src/testing.ts:47 — the two spans are one implementation copied and then locally edited — 52 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. — packages/channels/src/telegram/telegram.ts:128
  • packages/database/src/approvals.ts:63 · packages/database/src/channels.ts:121 · packages/database/src/computers.ts:60 · packages/database/src/inbound.ts:79 · +1 more site(s) not listed — the 5 copies are spread across 5 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. — packages/database/src/approvals.ts:63
  • packages/database/src/channels.ts:116 · packages/database/src/channels.ts:158 · packages/database/src/channels.ts:198 — 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. — packages/database/src/channels.ts:116
  • packages/database/src/channels.ts:157 · packages/database/src/channels.ts:201 — 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. — packages/database/src/channels.ts:157
  • packages/sdk/src/client.ts:335 · packages/sdk/src/client.ts:484 — 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. — packages/sdk/src/client.ts:335
  • apps/cli/src/cli.ts:232 · apps/web/src/lib/events/view.ts:108 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/cli/src/cli.ts:232
  • apps/scheduler/src/testing.ts:741 · apps/scheduler/src/testing.ts:761 — 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. — apps/scheduler/src/testing.ts:741
  • apps/web/src/app/(app)/dots/[id]/activity/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/channels/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/chat/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/settings/page.tsx:5 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/web/src/app/(app)/dots/[id]/activity/page.tsx:5
  • apps/web/src/app/(app)/dots/[id]/activity/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/channels/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/chat/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/computer/page.tsx:3 · +4 more site(s) not listed — the 8 copies are spread across 8 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/web/src/app/(app)/dots/[id]/activity/page.tsx:2

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries8.0 / 10Strong✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • apps/cli/scripts/build.mjs:10 reaches into another package with a relative path (../../../packages/database/scripts/runtime-files.mjs) — import the package by name instead. — apps/cli/scripts/build.mjs:10
  • apps/cli/src/host.ts:41 reaches into another package with a relative path (../../../virtualization/qemu/windows.json) — import the package by name instead. — apps/cli/src/host.ts:41
  • apps/web/e2e/harness.ts:22 reaches past another workspace package's public entry into its internals with a relative path (../../cli/src/web.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — apps/web/e2e/harness.ts:22
  • guest/image-builder/src/pins.ts:7 reaches into another package with a relative path (../../../virtualization/images/base.json) — import the package by name instead. — guest/image-builder/src/pins.ts:7
  • tests/repo/cli-bundle.test.ts:16 reaches past another workspace package's public entry into its internals with a relative path (../../apps/cli/scripts/bundle-options.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/repo/cli-bundle.test.ts:16
  • tests/repo/readme.test.ts:12 reaches past another workspace package's public entry into its internals with a relative path (../../apps/scheduler/src/lifecycle.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/repo/readme.test.ts:12
  • tests/repo/readme.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../apps/cli/src/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/repo/readme.test.ts:13
  • tests/repo/readme.test.ts:15 reaches past another workspace package's public entry into its internals with a relative path (../../apps/web/src/lib/permission-presets.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/repo/readme.test.ts:15
  • tests/repo/whatsapp-optin.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../packages/channels/src/whatsapp-baileys/client.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/repo/whatsapp-optin.test.ts:13

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.8 / 10Strong✓ 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.

  • #answer has cyclomatic complexity 188 and cognitive complexity 388; 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. — apps/web/test/support/control-plane.ts:279
  • run has cyclomatic complexity 132 and cognitive complexity 225; 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. — apps/cli/src/cli.ts:350
  • handle has cyclomatic complexity 62 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 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. — apps/cli/test/cli.test.ts:106
  • (anonymous) has cyclomatic complexity 34 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 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. — apps/api/test/guest-http.ts:48
  • #handle has cyclomatic complexity 32 and cognitive complexity 38; 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. — packages/channels/src/telegram/fake-bot-api.ts:317
  • TaskDrawer has cyclomatic complexity 27 and cognitive complexity 23; 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. — apps/web/src/components/tasks/task-drawer.tsx:41
  • UsageTab has cyclomatic complexity 25 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 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. — apps/web/src/components/computer/usage-tab.tsx:84
  • NeedsYou has cyclomatic complexity 25 and cognitive complexity 19; 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. — apps/web/src/components/inbox/NeedsYou.tsx:127
  • applyLiveEvent has cyclomatic complexity 24 and cognitive complexity 23; 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. — apps/web/src/lib/dot-live.ts:65
  • acquirePidLock has cyclomatic complexity 23 and cognitive complexity 36; 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. — packages/shared/src/process.ts:118
  • QrConnect has cyclomatic complexity 23 and cognitive complexity 20; 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. — apps/web/src/components/channels/qr-connect.tsx:62
  • readDirectory has cyclomatic complexity 22 and cognitive complexity 22; 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. — packages/iso/test/iso-reader.ts:110
  • stream has cyclomatic complexity 19 and cognitive complexity 37; 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. — packages/sdk/src/client.ts:475
  • startLocked has cyclomatic complexity 19 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. — apps/vm-manager/src/vm-manager.ts:525
  • startServer has cyclomatic complexity 19 and cognitive complexity 18; 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. — REDACTED:92
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; 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. — apps/scheduler/src/scheduler.ts:728
  • DotHeader has cyclomatic complexity 19 and cognitive complexity 18; 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. — apps/web/src/components/dot/DotHeader.tsx:27
  • FilesTab has cyclomatic complexity 19 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. — apps/web/src/components/computer/files-tab.tsx:41
  • ApprovalCard has cyclomatic complexity 19 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. — apps/web/src/components/elements/approval-card.tsx:48
  • events has cyclomatic complexity 18 and cognitive complexity 34; 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. — apps/vm-manager/src/guest-client.ts:382

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files8.4 / 10Strong✓ 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.

  • apps/scheduler/src/scheduler.ts has 860 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/scheduler/src/scheduler.ts:1
  • apps/scheduler/src/lifecycle.ts has 822 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/scheduler/src/lifecycle.ts:1
  • apps/scheduler/src/testing.ts has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/scheduler/src/testing.ts:1
  • apps/vm-manager/src/vm-manager.ts has 798 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/vm-manager/src/vm-manager.ts:1
  • apps/cli/src/cli.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/cli/src/cli.ts:1
  • packages/channels/src/hub.ts has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/channels/src/hub.ts:1
  • packages/shared/src/protocol.ts has 499 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/shared/src/protocol.ts:1
  • packages/iso/src/writer.ts has 495 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/iso/src/writer.ts:1
  • packages/sdk/src/client.ts has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/sdk/src/client.ts:1
  • packages/shared/src/config.ts has 464 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/shared/src/config.ts:1
  • apps/vm-manager/src/guest-client.ts has 446 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/vm-manager/src/guest-client.ts:1
  • REDACTED has 441 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
  • packages/shared/src/events.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/shared/src/events.ts:1
  • packages/channels/src/telegram/fake-bot-api.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/channels/src/telegram/fake-bot-api.ts: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.3 / 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.

  • apps/scheduler/test/upgrade.test.ts:18 imports './fixtures/upgrade/', 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. — apps/scheduler/test/upgrade.test.ts:18
  • apps/vm-manager/test/seed.test.ts:86 imports '../../../virtualization/cloud-init/', 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. — apps/vm-manager/test/seed.test.ts:86
  • 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. (×23) — packages/iso/scripts/kernel-check.ts:1, apps/cli/src/main.ts:1, apps/web/src/app/layout.tsx:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.6 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
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 apps/scheduler/test/upgrade.test.ts and 1 other test file(s) in this workspace 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. — apps/scheduler/test/upgrade.test.ts:18
R7 · Dead Code9.9 / 10Exemplary✓ 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.

  • Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect. — apps/vm-manager/src/guest-client.ts:423
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — apps/web/test/computer-page.test.tsx:56

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 Hygiene6.0 / 10Adequate✓ 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.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. — apps/scheduler/test/upgrade.test.ts:13
  • Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — packages/channels/test-optin/auth-state.test.ts:9

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.

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

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.

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

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.

  • `toYaml` is exported, takes a document from its caller (line 107) and hands it to `emit`, which calls itself at line 77 (`emit`) with a piece of `value` (and at line 90) — and nowhere in `emit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `emit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/web/src/lib/yaml.ts:77
  • `validate_json_schema_value` is public and takes `val: Any` from its caller, and it calls itself at line 118 (`self.validate_json_schema_value`) with a piece of `val` (and at line 123, line 139) — and nowhere in `validate_json_schema_value` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `validate_json_schema_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — invisible_engine_dots/nanobot/agent/tools/base.py:118
  • `canonical_arguments` is public, takes a document from its caller (line 970) and hands it to `_whole_numbers_as_integers`, which calls itself at line 986 (`_whole_numbers_as_integers`) with a piece of `value` (and at line 988) — and nowhere in `_whole_numbers_as_integers` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_whole_numbers_as_integers` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — invisible_engine_dots/nanobot/dots/store.py:986
  • `sanitize_surrogates_deep` is public and takes `value: Any` from its caller, and it calls itself at line 72 (`sanitize_surrogates_deep`) with a piece of `value` (and at line 81, line 88) — and nowhere in `sanitize_surrogates_deep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `sanitize_surrogates_deep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — invisible_engine_dots/nanobot/utils/helpers.py:72

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 propagation9.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context or 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 5/6 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) 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.
  • `dotPageTitle` 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 })`. — apps/web/src/lib/dot-title.ts:14

What to do

  • Thread a context.Context or an AbortSignal through 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 unescaped4.8 / 10Weak✓ 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.

  • `THEME_BOOTSTRAP` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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. — apps/web/src/app/layout.tsx:26

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. 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.9 / 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.

  • `.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. (×14) — apps/api/src/database.ts:30, apps/api/src/database.ts:41, apps/scheduler/src/support.ts:15, …
  • 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. (×13) — apps/cli/src/setup/qemu-pin.ts:59, apps/vm-manager/src/vm-manager.ts:214, apps/vm-manager/src/process-file.ts:28, …
  • `.then(…, () => {})` 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. — apps/web/src/components/shell/attention.tsx:79
  • `if err := fs.Parse(args); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — guest/dot-agentd/cmd/dot-agentd/relay.go:69
  • `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — guest/dot-agentd/internal/agentd/proc.go:174
  • `if waitErr != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — guest/dot-agentd/internal/agentd/proc.go:232
  • `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. — guest/image-builder/src/serial.ts:84
  • `except Exception` 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. (×8) — invisible_engine_dots/nanobot/agent/tools/registry.py:148, invisible_engine_dots/nanobot/agent/tools/mcp.py:307, invisible_engine_dots/nanobot/cron/service.py:66, …

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 logging4.8 / 10Weak✓ 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 133 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. — REDACTED:133
  • `warn` at line 204 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. — REDACTED:204
  • `info` at line 208 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. — REDACTED:208

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types9.0 / 10Strong✓ Tool-verified

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.

  • ~2.6 `!` null assertions per 1k TypeScript source lines — 96 assertion(s) across the 36899 source line(s) of the 340 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: apps/scheduler/src/testing.ts (11), apps/vm-manager/src/guest-client.ts (7), apps/vm-manager/src/process-file.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

  • The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

WCAG coverage — what static analysis assessed

Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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
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 42 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.1, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.3, 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 Health70%Adequate — gated by D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture87%StrongStrongest area.
Maturity48%Weak — gated by M4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness54%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security77%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility75%StrongSolid.
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 — 12 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

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.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 45 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.

  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — Not scored — 3 shipped Python distribution(s) were read, but the outdated signal needs pypi.org, and no declaration here carries an exact pin to ask about — a floor or a range installs the newest release it admits and cannot be behind one, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .go, .py, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 12 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.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
  • DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • 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'.
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Go code has 2,962 production line(s), 3 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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.
  • 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 — 35 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
  • + 4 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: scheduler.ts ↔ client.ts apps/scheduler/src/scheduler.ts:1 — `apps/scheduler/src/scheduler.ts` (context scheduler) and `packages/sdk/src/client.ts` (context sdk) sit in DIFFERENT parts of the tree yet change together 86% of the time (12 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `5a65ada6` api, web: the shell reads the failed tasks and the channels of every …; `a60ee568` host: MCP secrets are set write-only, pushed with the key, and none o…; `b75e5e7b` vm proxy: a Dot's whole VM can go out through a SOCKS5 proxy — run `git show` on any of them.
R8 · Dependency Hygiene · Unlisted import 'pg' · ×1
  • Unlisted import 'pg' apps/scheduler/test/upgrade.test.ts:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 433 finding(s)
D15 · Churn × Complexity Hotspots · Hotspot · ×34
  • Hotspot: apps/web/test/support/control-plane.ts apps/web/test/support/control-plane.ts:279 — apps/web/test/support/control-plane.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 188 in #answer at line 279. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/test/support/control-plane.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: apps/cli/src/cli.ts apps/cli/src/cli.ts:350 — apps/cli/src/cli.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 131 in cli.run at line 350. 1 of those changes was a fix/bug commit, and the other 20 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/cli/src/cli.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:101 — REDACTED changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in server.buildServer at line 101. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07: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: apps/scheduler/src/scheduler.ts apps/scheduler/src/scheduler.ts:696 — apps/scheduler/src/scheduler.ts changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Scheduler.resolveApproval at line 696. 1 of those changes was a fix/bug commit, and the other 30 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/scheduler/src/scheduler.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:250 — REDACTED changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in AgentServer._handle at line 250. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07: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: packages/sdk/src/client.ts packages/sdk/src/client.ts:475 — packages/sdk/src/client.ts changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in InvisibleDotsClient.stream at line 475. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- packages/sdk/src/client.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: invisible_engine_dots/nanobot/agent/runner.py invisible_engine_dots/nanobot/agent/runner.py:298 — invisible_engine_dots/nanobot/agent/runner.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in AgentRunner._run_core at line 298. 1 of those changes was a fix/bug commit, and the other 6 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- invisible_engine_dots/nanobot/agent/runner.py`: 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: packages/channels/src/hub.ts packages/channels/src/hub.ts:501 — packages/channels/src/hub.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ChannelHub.#inbound at line 501. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- packages/channels/src/hub.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: apps/scheduler/src/lifecycle.ts apps/scheduler/src/lifecycle.ts:807 — apps/scheduler/src/lifecycle.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Lifecycle.recover at line 807. 1 of those changes was a fix/bug commit, and the other 13 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/scheduler/src/lifecycle.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: apps/vm-manager/src/guest-client.ts apps/vm-manager/src/guest-client.ts:189 — apps/vm-manager/src/guest-client.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in GuestClient.sendRaw at line 189. 1 of those changes was a fix/bug commit, and the other 12 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/vm-manager/src/guest-client.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: invisible_engine_dots/nanobot/dots/engine.py invisible_engine_dots/nanobot/dots/engine.py:487 — invisible_engine_dots/nanobot/dots/engine.py changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Engine._suspend_now at line 487. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- invisible_engine_dots/nanobot/dots/engine.py`: 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: apps/web/src/components/dot/DotHeader.tsx apps/web/src/components/dot/DotHeader.tsx:27 — apps/web/src/components/dot/DotHeader.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in DotHeader.DotHeader at line 27. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/dot/DotHeader.tsx`: 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: invisible_engine_dots/nanobot/dots/transcript_outbox.py invisible_engine_dots/nanobot/dots/transcript_outbox.py:154 — invisible_engine_dots/nanobot/dots/transcript_outbox.py changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in transcript_outbox._record_tool_result at line 154. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- invisible_engine_dots/nanobot/dots/transcript_outbox.py`: 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: invisible_engine_dots/nanobot/agent/tools/search.py invisible_engine_dots/nanobot/agent/tools/search.py:524 — invisible_engine_dots/nanobot/agent/tools/search.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in GrepTool.execute at line 524. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- invisible_engine_dots/nanobot/agent/tools/search.py`: 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:847 — REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in OpenAICompatProvider.model_limits at line 847. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07: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: apps/web/src/components/computer/usage-tab.tsx apps/web/src/components/computer/usage-tab.tsx:84 — apps/web/src/components/computer/usage-tab.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in usage-tab.UsageTab at line 84. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/computer/usage-tab.tsx`: 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: apps/vm-manager/src/vm-manager.ts apps/vm-manager/src/vm-manager.ts:525 — apps/vm-manager/src/vm-manager.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in VmManager.startLocked at line 525. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/vm-manager/src/vm-manager.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: apps/web/src/components/inbox/NeedsYou.tsx apps/web/src/components/inbox/NeedsYou.tsx:127 — apps/web/src/components/inbox/NeedsYou.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in NeedsYou.NeedsYou at line 127. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/inbox/NeedsYou.tsx`: 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: apps/web/src/components/tasks/task-drawer.tsx apps/web/src/components/tasks/task-drawer.tsx:41 — apps/web/src/components/tasks/task-drawer.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in task-drawer.TaskDrawer at line 41. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/tasks/task-drawer.tsx`: 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: packages/channels/src/telegram/fake-bot-api.ts packages/channels/src/telegram/fake-bot-api.ts:317 — packages/channels/src/telegram/fake-bot-api.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in FakeBotApi.#handle at line 317. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- packages/channels/src/telegram/fake-bot-api.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: apps/web/src/components/dot-settings/DotSettings.tsx apps/web/src/components/dot-settings/DotSettings.tsx:43 — apps/web/src/components/dot-settings/DotSettings.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in DotSettings.Editor at line 43. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/dot-settings/DotSettings.tsx`: 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: apps/scheduler/src/guest-events.ts apps/scheduler/src/guest-events.ts:92 — apps/scheduler/src/guest-events.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in guest-events.applyGuestEvent at line 92. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/scheduler/src/guest-events.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: invisible_engine_dots/nanobot/agent/memory.py invisible_engine_dots/nanobot/agent/memory.py:164 — invisible_engine_dots/nanobot/agent/memory.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Consolidator.summarize at line 164. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- invisible_engine_dots/nanobot/agent/memory.py`: 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: apps/web/src/components/tasks/story.tsx apps/web/src/components/tasks/story.tsx:28 — apps/web/src/components/tasks/story.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in story.Body at line 28. 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/web/src/components/tasks/story.tsx`: 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: apps/api/test/guest-http.ts apps/api/test/guest-http.ts:48 — apps/api/test/guest-http.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in (anonymous) 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-07-16..2026-10-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-16 18:38:56 -07:00' --until='2026-10-14 18:38:56 -07:00' --full-history --no-merges -- apps/api/test/guest-http.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.
  • + 9 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×28
  • Swallowed exception (empty catch) apps/api/src/database.ts:30 — `.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) apps/api/src/database.ts:41 — `.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) apps/cli/src/setup/qemu-pin.ts:59 — 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) apps/scheduler/src/support.ts:15 — `.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) apps/scheduler/src/support.ts:48 — `.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) apps/scheduler/src/scheduler.ts:137 — `.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) apps/scheduler/src/scheduler.ts:189 — `.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) apps/scheduler/src/lifecycle.ts:257 — `.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) apps/scheduler/src/lifecycle.ts:342 — `.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) apps/scheduler/src/lifecycle.ts:602 — `.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) apps/vm-manager/src/vm-manager.ts:214 — 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) apps/vm-manager/src/process-file.ts:28 — 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) apps/vm-manager/src/guest-client.ts:116 — 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) apps/vm-manager/src/guest-client.ts:476 — 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) apps/web/src/components/copy-button.tsx:25 — 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) apps/web/src/components/home/last-activity.tsx:33 — `.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) apps/web/src/components/shell/attention.tsx:79 — `.then(…, () => {})` 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) apps/web/src/lib/use-visible-interval.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) apps/web/src/lib/theme.ts:20 — 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) apps/web/src/lib/draft.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) apps/web/src/lib/dismissed.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) invisible_engine_dots/nanobot/utils/helpers.py:332 — 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) invisible_engine_dots/nanobot/utils/helpers.py:479 — 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) invisible_engine_dots/nanobot/utils/helpers.py:536 — 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) packages/channels/src/runner.ts:85 — `.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.
  • + 3 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×23
  • No test reaches this file packages/iso/scripts/kernel-check.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 apps/cli/src/main.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 apps/web/src/app/layout.tsx: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 apps/web/scripts/standalone.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 apps/web/src/app/not-found.tsx: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 apps/web/src/app/(app)/dots/[id]/layout.tsx: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 apps/web/scripts/build.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 apps/web/src/app/(app)/dots/[id]/computer/page.tsx: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 apps/web/src/app/(app)/dots/[id]/skills/page.tsx: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 apps/web/src/app/(app)/dots/[id]/tasks/[taskId]/page.tsx: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 apps/web/src/instrumentation.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 apps/web/src/app/(app)/dots/[id]/activity/page.tsx: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 apps/web/src/app/(app)/dots/[id]/channels/page.tsx: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 apps/web/src/app/(app)/dots/[id]/chat/page.tsx: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 apps/web/src/app/(app)/dots/[id]/settings/page.tsx: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 apps/web/src/app/(app)/dots/[id]/tasks/page.tsx: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 apps/web/src/app/(app)/new/page.tsx: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 apps/web/src/app/(app)/page.tsx: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 apps/web/src/app/(app)/settings/page.tsx: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 apps/web/src/app/(app)/dots/[id]/timeline/page.tsx: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 apps/web/src/app/(app)/dots/[id]/page.tsx: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 apps/web/src/app/(app)/dots/[id]/tasks/layout.tsx: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 apps/web/src/index.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.
D3 · God Classes · FileTooLong · ×16
  • FileTooLong: tools/mcp.py invisible_engine_dots/nanobot/agent/tools/mcp.py — FileTooLong — 884 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 384 over it, 1.77× 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: providers/base.py invisible_engine_dots/nanobot/providers/base.py — FileTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 340 over it, 1.68× 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: agent/runner.py invisible_engine_dots/nanobot/agent/runner.py — FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 258 over it, 1.52× 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 — 694 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 194 over it, 1.39× 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: tools/filesystem.py invisible_engine_dots/nanobot/agent/tools/filesystem.py — FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 over it, 1.35× 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: agent/context_governance.py invisible_engine_dots/nanobot/agent/context_governance.py — FileTooLong — 634 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 134 over it, 1.27× 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: tools/exec_session.py invisible_engine_dots/nanobot/agent/tools/exec_session.py — FileTooLong — 620 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 120 over it, 1.24× 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: dots/store.py invisible_engine_dots/nanobot/dots/store.py — FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 90 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.
  • FileTooLong: dots/engine.py invisible_engine_dots/nanobot/dots/engine.py — FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× 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: src/scheduler.ts apps/scheduler/src/scheduler.ts — FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: Scheduler (95-922). The bar is 500 significant lines; this is 81 over it, 1.16× 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: src/testing.ts apps/scheduler/src/testing.ts — FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 76 over it, 1.15× 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: src/cli.ts apps/cli/src/cli.ts — FileTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 73 over it, 1.15× 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: dots/browser.py invisible_engine_dots/nanobot/dots/browser.py — FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× 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: tools/search.py invisible_engine_dots/nanobot/agent/tools/search.py — FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 24 over it, 1.05× 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: src/vm-manager.ts apps/vm-manager/src/vm-manager.ts — FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: VmManager (236-863). The bar is 500 significant lines; this is 17 over it, 1.03× 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: src/lifecycle.ts apps/scheduler/src/lifecycle.ts — FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Lifecycle (109-878). The bar is 500 significant lines; this is 9 over it, 1.02× 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×12
  • Swallowed exception (caught, then discarded) guest/dot-agentd/cmd/dot-agentd/relay.go:69 — `if err := fs.Parse(args); err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) guest/dot-agentd/internal/agentd/proc.go:174 — `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) guest/dot-agentd/internal/agentd/proc.go:232 — `if waitErr != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) guest/image-builder/src/serial.ts:84 — `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) invisible_engine_dots/nanobot/agent/tools/registry.py:148 — `except Exception` 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) invisible_engine_dots/nanobot/agent/tools/mcp.py:307 — `except Exception` 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) invisible_engine_dots/nanobot/cron/service.py:66 — `except Exception` 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:794 — `except Exception` 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) invisible_engine_dots/nanobot/providers/base.py:91 — `except Exception` 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) invisible_engine_dots/nanobot/providers/base.py:119 — `except Exception` 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) invisible_engine_dots/nanobot/providers/base.py:726 — `except Exception` 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) invisible_engine_dots/nanobot/providers/base.py:1021 — `except Exception` 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.
D3 · God Classes · TooManyMethods · ×9
  • TooManyMethods: InvisibleDotsClient packages/sdk/src/client.ts:97 — TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Scheduler apps/scheduler/src/scheduler.ts:95 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Lifecycle apps/scheduler/src/lifecycle.ts:109 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BrowserManager invisible_engine_dots/nanobot/dots/browser.py:186 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FakeGuest apps/scheduler/src/testing.ts:155 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: VmManager apps/vm-manager/src/vm-manager.ts:236 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Engine invisible_engine_dots/nanobot/dots/engine.py:176 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GuestClient apps/vm-manager/src/guest-client.ts:123 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ChannelHub packages/channels/src/hub.ts:104 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
R11 · Import Boundaries · Boundary violation [package · ×9
  • Boundary violation [package:relative-cross-package] apps/cli/scripts/build.mjs:10 — apps/cli/scripts/build.mjs:10 reaches into another package with a relative path (../../../packages/database/scripts/runtime-files.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] apps/cli/src/host.ts:41 — apps/cli/src/host.ts:41 reaches into another package with a relative path (../../../virtualization/qemu/windows.json) — import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] apps/web/e2e/harness.ts:22 — apps/web/e2e/harness.ts:22 reaches past another workspace package's public entry into its internals with a relative path (../../cli/src/web.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:relative-cross-package] guest/image-builder/src/pins.ts:7 — guest/image-builder/src/pins.ts:7 reaches into another package with a relative path (../../../virtualization/images/base.json) — import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/repo/cli-bundle.test.ts:16 — tests/repo/cli-bundle.test.ts:16 reaches past another workspace package's public entry into its internals with a relative path (../../apps/cli/scripts/bundle-options.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/repo/readme.test.ts:12 — tests/repo/readme.test.ts:12 reaches past another workspace package's public entry into its internals with a relative path (../../apps/scheduler/src/lifecycle.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/repo/readme.test.ts:13 — tests/repo/readme.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../apps/cli/src/cli.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/repo/readme.test.ts:15 — tests/repo/readme.test.ts:15 reaches past another workspace package's public entry into its internals with a relative path (../../apps/web/src/lib/permission-presets.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] tests/repo/whatsapp-optin.test.ts:13 — tests/repo/whatsapp-optin.test.ts:13 reaches past another workspace package's public entry into its internals with a relative path (../../packages/channels/src/whatsapp-baileys/client.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
D3 · God Classes · FunctionTooLong · ×6
  • FunctionTooLong: cli.run apps/cli/src/cli.ts:350 — FunctionTooLong — run runs 331 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 231 over it, 3.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: server.buildServer REDACTED:101 — FunctionTooLong — buildServer runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.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: DotSettings.Editor apps/web/src/components/dot-settings/DotSettings.tsx:43 — FunctionTooLong — Editor runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: chat-data.useChat apps/web/src/components/chat/chat-data.tsx:40 — FunctionTooLong — useChat runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: NeedsYou.NeedsYou apps/web/src/components/inbox/NeedsYou.tsx:127 — FunctionTooLong — NeedsYou 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: qr-connect.QrConnect apps/web/src/components/channels/qr-connect.tsx:62 — FunctionTooLong — QrConnect 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×6
  • Sync-over-async blocking apps/vm-manager/src/runner.ts:172 — `openSync` in `spawnDetached` 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 apps/vm-manager/src/runner.ts:195 — `closeSync` in `spawnDetached` 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 apps/vm-manager/test/fakes.ts:152 — `appendFileSync` in `spawnDetached` 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 apps/vm-manager/test/fakes.ts:170 — `appendFileSync` in `spawnDetached` 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 apps/vm-manager/test/fakes.ts:171 — `writeFileSync` in `spawnDetached` 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 apps/vm-manager/test/fakes.ts:175 — `appendFileSync` in `callback to setTimeout` 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.
D10 · Test Quality · Fixed-sleep synchronisation · ×5
  • Fixed-sleep synchronisation: claims a task whose Dot's row another transaction held for a moment, without waiting for the timer apps/scheduler/test/scheduler.test.ts:73 — This test starts work it did not wait for (`holder`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 100))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: approve with always: a flush that runs between the commit and the push does not send the answer ahead of the config apps/scheduler/test/scheduler.test.ts:356 — This test starts work it did not wait for (`answered`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 150))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: ends when its signal aborts, even while it waits for a frame, and keeps the other watchers going packages/channels/test/units.test.ts:128 — This test starts work it did not wait for (`first`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: event ids become visible in id order: an insert waits for a transaction that drew a lower id packages/database/test/repositories.test.ts:602 — This test starts work it did not wait for (`slow`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 5))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: pglite: transactions run one at a time, so a claim never meets a competitor packages/database/test/adapters.test.ts:227 — This test starts work it did not wait for (`first`, still running when the sleep starts) and then orders itself against it with `new Promise((r) => setTimeout(r, 100))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×4
  • Duplicated block with local edits (10 matched lines × 2 locations) apps/scheduler/src/inbound.ts:156 — apps/scheduler/src/inbound.ts:156 · apps/scheduler/src/support.ts:50 — the two spans are one implementation copied and then locally edited — 58 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 (10 matched lines × 2 locations) apps/web/src/components/approvals/approval-body.tsx:26 — apps/web/src/components/approvals/approval-body.tsx:26 · apps/web/src/components/approvals/approval-body.tsx:35 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (10 matched lines × 2 locations) guest/image-builder/src/manifest.ts:81 — guest/image-builder/src/manifest.ts:81 · packages/shared/src/files.ts:94 — the two spans are one implementation copied and then locally edited — 75 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 (10 matched lines × 2 locations) packages/shared/src/files.ts:93 — packages/shared/src/files.ts:93 · packages/shared/src/process.ts:195 — the two spans are one implementation copied and then locally edited — 63 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 (8 matched lines × 2 locations) · ×4
  • Duplicated block with local edits (8 matched lines × 2 locations) apps/vm-manager/src/guest-client.ts:227 — apps/vm-manager/src/guest-client.ts:227 · packages/shared/src/sockets.ts:94 — the two spans are one implementation copied and then locally edited — 78 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 (8 matched lines × 2 locations) apps/web/src/components/approvals/TaskApprovals.tsx:15 — apps/web/src/components/approvals/TaskApprovals.tsx:15 · apps/web/src/components/inbox/NeedsYou.tsx:128 — the two spans are one implementation copied and then locally edited — 137 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 (8 matched lines × 2 locations) packages/channels/src/telegram/telegram.ts:127 — packages/channels/src/telegram/telegram.ts:127 · packages/channels/src/whatsapp-baileys/whatsapp.ts:120 — the two spans are one implementation copied and then locally edited — 56 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 (8 matched lines × 2 locations) packages/channels/src/testing.ts:47 — packages/channels/src/testing.ts:47 · packages/channels/src/whatsapp-baileys/whatsapp.ts:121 — the two spans are one implementation copied and then locally edited — 56 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 (7 lines × 2 locations) · ×4
  • Duplicated block (7 lines × 2 locations) apps/api/src/vm-driver.ts:26 — apps/api/src/vm-driver.ts:26 · packages/database/src/migrate.ts:39 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (7 lines × 2 locations) apps/cli/src/cli.ts:463 — apps/cli/src/cli.ts:463 · apps/cli/src/cli.ts:476 — 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 (7 lines × 2 locations) packages/database/src/channels.ts:157 — packages/database/src/channels.ts:157 · packages/database/src/channels.ts:201 — 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 (7 lines × 2 locations) packages/sdk/src/client.ts:335 — packages/sdk/src/client.ts:335 · packages/sdk/src/client.ts:484 — 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.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×4
  • Recursive walk over a caller-supplied document has no depth cap apps/web/src/lib/yaml.ts:77 — `toYaml` is exported, takes a document from its caller (line 107) and hands it to `emit`, which calls itself at line 77 (`emit`) with a piece of `value` (and at line 90) — and nowhere in `emit` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `emit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap invisible_engine_dots/nanobot/agent/tools/base.py:118 — `validate_json_schema_value` is public and takes `val: Any` from its caller, and it calls itself at line 118 (`self.validate_json_schema_value`) with a piece of `val` (and at line 123, line 139) — and nowhere in `validate_json_schema_value` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `validate_json_schema_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap invisible_engine_dots/nanobot/dots/store.py:986 — `canonical_arguments` is public, takes a document from its caller (line 970) and hands it to `_whole_numbers_as_integers`, which calls itself at line 986 (`_whole_numbers_as_integers`) with a piece of `value` (and at line 988) — and nowhere in `_whole_numbers_as_integers` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `_whole_numbers_as_integers` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap invisible_engine_dots/nanobot/utils/helpers.py:72 — `sanitize_surrogates_deep` is public and takes `value: Any` from its caller, and it calls itself at line 72 (`sanitize_surrogates_deep`) with a piece of `value` (and at line 81, line 88) — and nowhere in `sanitize_surrogates_deep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. Python's parsers accept far more nesting than its stack allows: `json.loads` turns 3,000 bytes of brackets into 1,500 levels and `xml.etree.ElementTree` parses tens of thousands, while a walk like this one raises `RecursionError` once it passes the interpreter's default limit of 1,000 frames. Wherever that exception lands, the work fails: a request errors, and outside any `try` the worker or the program exits with it. Raising `sys.setrecursionlimit` only moves the number the document has to beat. Thread a depth argument through `sanitize_surrogates_deep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D10 · Test Quality · No assertions · ×3
  • No assertions: starts a VM that stopped by itself at once when a run is due, by the same rule as the idle sleep apps/scheduler/test/scheduler.test.ts:712 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: a VM that powers itself off with a task in progress is started again apps/scheduler/test/delivery.test.ts:365 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: are what the schemas take: a parsed event is the type the code reads packages/shared/test/events.test.ts:38 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
R10 · Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (11 matched lines × 2 locations) apps/web/src/components/chat/chat-data.tsx:81 — apps/web/src/components/chat/chat-data.tsx:81 · apps/web/src/components/tasks/tasks-data.tsx:173 — the two spans are one implementation copied and then locally edited — 92 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 (11 matched lines × 2 locations) apps/web/src/components/computer/usage-tab.tsx:45 — apps/web/src/components/computer/usage-tab.tsx:45 · apps/web/src/components/inbox/NeedsYou.tsx:29 — the two spans are one implementation copied and then locally edited — 55 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 (11 matched lines × 2 locations) packages/database/src/pglite.ts:50 — packages/database/src/pglite.ts:50 · packages/database/src/postgres.ts:78 — the two spans are one implementation copied and then locally edited — 97 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 (8 lines × 2 locations) · ×3
  • Duplicated block (8 lines × 2 locations) apps/scheduler/src/scheduler.ts:534 — apps/scheduler/src/scheduler.ts:534 · apps/scheduler/src/scheduler.ts:543 — 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 (8 lines × 2 locations) apps/web/src/components/approvals/approval-body.tsx:62 — apps/web/src/components/approvals/approval-body.tsx:62 · apps/web/src/components/elements/approval-card.tsx:104 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (8 lines × 2 locations) apps/web/src/components/inbox/use-history.ts:46 — apps/web/src/components/inbox/use-history.ts:46 · apps/web/src/components/inbox/use-history.ts:66 — 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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: Scheduler apps/scheduler/src/scheduler.ts:95 — ClassTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 102 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Lifecycle apps/scheduler/src/lifecycle.ts:109 — ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 51 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) invisible_engine_dots/nanobot/agent/context.py:101 — invisible_engine_dots/nanobot/agent/context.py:101-113 | invisible_engine_dots/nanobot/agent/context_governance.py:225-237 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (13 lines × 2) guest/dot-agentd/internal/agentd/exec.go:89 — guest/dot-agentd/internal/agentd/exec.go:89-101 | guest/dot-agentd/internal/agentd/proc.go:102-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) apps/web/src/components/inbox/NeedsYou.tsx:180 — apps/web/src/components/inbox/NeedsYou.tsx:180 · apps/web/src/components/inbox/NeedsYou.tsx: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.
  • Duplicated block (12 lines × 2 locations) apps/web/src/lib/computer-view.ts:9 — apps/web/src/lib/computer-view.ts:9 · apps/web/src/lib/inbox.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×2
  • Duplicated block (9 lines × 2 locations) apps/scheduler/src/lifecycle.ts:337 — apps/scheduler/src/lifecycle.ts:337 · apps/scheduler/src/lifecycle.ts:597 — 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 (9 lines × 2 locations) packages/sdk/src/client.ts:190 — packages/sdk/src/client.ts:190 · packages/sdk/src/client.ts:311 — 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 with local edits (7 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (7 matched lines × 2 locations) apps/web/src/components/chat/chat-data.tsx:42 — apps/web/src/components/chat/chat-data.tsx:42 · apps/web/src/components/chat/chat-data.tsx:66 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (7 matched lines × 2 locations) packages/channels/src/telegram/telegram.ts:128 — packages/channels/src/telegram/telegram.ts:128 · packages/channels/src/testing.ts:47 — the two spans are one implementation copied and then locally edited — 52 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 (6 lines × 2 locations) · ×2
  • Duplicated block (6 lines × 2 locations) apps/cli/src/cli.ts:232 — apps/cli/src/cli.ts:232 · apps/web/src/lib/events/view.ts:108 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (6 lines × 2 locations) apps/scheduler/src/testing.ts:741 — apps/scheduler/src/testing.ts:741 · apps/scheduler/src/testing.ts:761 — 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.
R4 · Test Coverage · This test file cannot be loaded · ×2
  • This test file cannot be loaded apps/scheduler/test/upgrade.test.ts:18 — apps/scheduler/test/upgrade.test.ts:18 imports './fixtures/upgrade/', 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.
  • This test file cannot be loaded apps/vm-manager/test/seed.test.ts:86 — apps/vm-manager/test/seed.test.ts:86 imports '../../../virtualization/cloud-init/', 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.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark apps/web/src/app/layout.tsx:24 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 124 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.
D1 · Cyclomatic Complexity · cli.run (cyclomatic 131) · ×1
  • cli.run (cyclomatic 131) apps/cli/src/cli.ts:350 — cli.run has cyclomatic complexity 131 (threshold 15). Of this number, 124 points are the body's own statements and 7 belong to 4 function items 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 · Schema.validate_json_schema_value (cyclomatic 54) · ×1
  • Schema.validate_json_schema_value (cyclomatic 54) invisible_engine_dots/nanobot/agent/tools/base.py:56 — Schema.validate_json_schema_value has cyclomatic complexity 54 (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 · server.buildServer (cyclomatic 52) · ×1
  • server.buildServer (cyclomatic 52) REDACTED:101 — server.buildServer has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 2 of the 52 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 391, 126, 364, …). 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 · EditFileTool.execute (cyclomatic 50) · ×1
  • EditFileTool.execute (cyclomatic 50) invisible_engine_dots/nanobot/agent/tools/filesystem.py:594 — EditFileTool.execute has cyclomatic complexity 50 (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 · GrepTool.execute (cyclomatic 44) · ×1
  • GrepTool.execute (cyclomatic 44) invisible_engine_dots/nanobot/agent/tools/search.py:524 — GrepTool.execute has cyclomatic complexity 44 (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 · ApplyPatchTool.execute (cyclomatic 42) · ×1
  • ApplyPatchTool.execute (cyclomatic 42) invisible_engine_dots/nanobot/agent/tools/apply_patch.py:96 — ApplyPatchTool.execute 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 · AgentServer._handle (cyclomatic 41) · ×1
  • AgentServer._handle (cyclomatic 41) REDACTED:250 — AgentServer._handle has cyclomatic complexity 41 (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 · qr-connect.QrConnect (cyclomatic 37) · ×1
  • qr-connect.QrConnect (cyclomatic 37) apps/web/src/components/channels/qr-connect.tsx:62 — qr-connect.QrConnect has cyclomatic complexity 37 (threshold 15). Of this number, 22 points are the body's own statements and 15 belong to 5 function items 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 · OpenAICompatProvider._parse_chunks (cyclomatic 37) · ×1
  • OpenAICompatProvider._parse_chunks (cyclomatic 37) REDACTED:613 — OpenAICompatProvider._parse_chunks has cyclomatic complexity 37 (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 · AgentRunner._run_core (cyclomatic 34) · ×1
  • AgentRunner._run_core (cyclomatic 34) invisible_engine_dots/nanobot/agent/runner.py:298 — AgentRunner._run_core has cyclomatic complexity 34 (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 · FakeBotApi.#handle (cyclomatic 33) · ×1
  • FakeBotApi.#handle (cyclomatic 33) packages/channels/src/telegram/fake-bot-api.ts:317 — FakeBotApi.#handle has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · Scheduler.resolveApproval (cyclomatic 30) · ×1
  • Scheduler.resolveApproval (cyclomatic 30) apps/scheduler/src/scheduler.ts:696 — Scheduler.resolveApproval has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 728). 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 · agentd.RunRelay (cyclomatic 30) · ×1
  • agentd.RunRelay (cyclomatic 30) guest/dot-agentd/internal/agentd/relay.go:42 — agentd.RunRelay has cyclomatic complexity 30 (threshold 15). Of this number, 20 points are the body's own statements and 10 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 · NeedsYou.NeedsYou (cyclomatic 28) · ×1
  • NeedsYou.NeedsYou (cyclomatic 28) apps/web/src/components/inbox/NeedsYou.tsx:127 — NeedsYou.NeedsYou has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · Tool._cast_value (cyclomatic 28) · ×1
  • Tool._cast_value (cyclomatic 28) invisible_engine_dots/nanobot/agent/tools/base.py:241 — Tool._cast_value has cyclomatic complexity 28 (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 · task-drawer.TaskDrawer (cyclomatic 27) · ×1
  • task-drawer.TaskDrawer (cyclomatic 27) apps/web/src/components/tasks/task-drawer.tsx:41 — task-drawer.TaskDrawer has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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 · agentd.runProcStream (cyclomatic 26) · ×1
  • agentd.runProcStream (cyclomatic 26) guest/dot-agentd/internal/agentd/proc.go:138 — agentd.runProcStream has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 183, 164, 141). 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 · dot-live.applyLiveEvent (cyclomatic 24) · ×1
  • dot-live.applyLiveEvent (cyclomatic 24) apps/web/src/lib/dot-live.ts:65 — dot-live.applyLiveEvent has cyclomatic complexity 24 (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 · DotSettings.Editor (cyclomatic 24) · ×1
  • DotSettings.Editor (cyclomatic 24) apps/web/src/components/dot-settings/DotSettings.tsx:43 — DotSettings.Editor has cyclomatic complexity 24 (threshold 15). Of this number, 14 points are the body's own statements and 10 belong to 8 function items 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 · Session.get_history (cyclomatic 24) · ×1
  • Session.get_history (cyclomatic 24) invisible_engine_dots/nanobot/session/manager.py:80 — Session.get_history has cyclomatic complexity 24 (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 · approval-view.approvalBody (cyclomatic 22) · ×1
  • approval-view.approvalBody (cyclomatic 22) apps/web/src/lib/approval-view.ts:212 — approval-view.approvalBody has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to one function literal inside it that branches. 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 · FindFilesTool.execute (cyclomatic 22) · ×1
  • FindFilesTool.execute (cyclomatic 22) invisible_engine_dots/nanobot/agent/tools/search.py:299 — FindFilesTool.execute has cyclomatic complexity 22 (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 · helpers._estimate_prompt_tokens_with_source (cyclomatic 22) · ×1
  • helpers._estimate_prompt_tokens_with_source (cyclomatic 22) invisible_engine_dots/nanobot/utils/helpers.py:434 — helpers._estimate_prompt_tokens_with_source has cyclomatic complexity 22 (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 · Server.handleProc (cyclomatic 22) · ×1
  • Server.handleProc (cyclomatic 22) guest/dot-agentd/internal/agentd/proc.go:63 — Server.handleProc has cyclomatic complexity 22 (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 · files-tab.FilesTab (cyclomatic 21) · ×1
  • files-tab.FilesTab (cyclomatic 21) apps/web/src/components/computer/files-tab.tsx:41 — files-tab.FilesTab has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function items 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 · ReadFileTool.execute (cyclomatic 21) · ×1
  • ReadFileTool.execute (cyclomatic 21) invisible_engine_dots/nanobot/agent/tools/filesystem.py:129 — ReadFileTool.execute has cyclomatic complexity 21 (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 · ListDirTool.execute (cyclomatic 21) · ×1
  • ListDirTool.execute (cyclomatic 21) invisible_engine_dots/nanobot/agent/tools/filesystem.py:847 — ListDirTool.execute 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.
D1 · Cyclomatic Complexity · LLMProvider._sanitize_empty_content (cyclomatic 21) · ×1
  • LLMProvider._sanitize_empty_content (cyclomatic 21) invisible_engine_dots/nanobot/providers/base.py:472 — LLMProvider._sanitize_empty_content 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.
D1 · Cyclomatic Complexity · LLMProvider._enforce_role_alternation (cyclomatic 21) · ×1
  • LLMProvider._enforce_role_alternation (cyclomatic 21) invisible_engine_dots/nanobot/providers/base.py:780 — LLMProvider._enforce_role_alternation 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.
D1 · Cyclomatic Complexity · ActivityView.ActivityView (cyclomatic 20) · ×1
  • ActivityView.ActivityView (cyclomatic 20) apps/web/src/components/activity/ActivityView.tsx:24 — ActivityView.ActivityView has cyclomatic complexity 20 (threshold 15). Of this number, 18 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 · wide.html.scenes (cyclomatic 20) · ×1
  • wide.html.scenes (cyclomatic 20) docs/hero/html/wide.html:192 — wide.html.scenes has cyclomatic complexity 20 (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 · CronTool._add_job (cyclomatic 20) · ×1
  • CronTool._add_job (cyclomatic 20) invisible_engine_dots/nanobot/agent/tools/cron.py:123 — CronTool._add_job has cyclomatic complexity 20 (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 · DotHeader.DotHeader (cyclomatic 19) · ×1
  • DotHeader.DotHeader (cyclomatic 19) apps/web/src/components/dot/DotHeader.tsx:27 — DotHeader.DotHeader has cyclomatic complexity 19 (threshold 15). 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, 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 · file-preview.FilePreview (cyclomatic 19) · ×1
  • file-preview.FilePreview (cyclomatic 19) apps/web/src/components/computer/file-preview.tsx:33 — file-preview.FilePreview has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 5 function items 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 · usage-tab.UsageTab (cyclomatic 19) · ×1
  • usage-tab.UsageTab (cyclomatic 19) apps/web/src/components/computer/usage-tab.tsx:84 — usage-tab.UsageTab 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 · mobile.html.scenes (cyclomatic 19) · ×1
  • mobile.html.scenes (cyclomatic 19) docs/hero/html/mobile.html:140 — mobile.html.scenes 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 · small.html.scenes (cyclomatic 19) · ×1
  • small.html.scenes (cyclomatic 19) docs/hero/html/small.html:140 — small.html.scenes 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 · process.acquirePidLock (cyclomatic 19) · ×1
  • process.acquirePidLock (cyclomatic 19) packages/shared/src/process.ts:118 — process.acquirePidLock 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 · exec_session._escape_end (cyclomatic 19) · ×1
  • exec_session._escape_end (cyclomatic 19) invisible_engine_dots/nanobot/agent/tools/exec_session.py:47 — exec_session._escape_end 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 · exec_session.terminal_text (cyclomatic 19) · ×1
  • exec_session.terminal_text (cyclomatic 19) invisible_engine_dots/nanobot/agent/tools/exec_session.py:88 — exec_session.terminal_text 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 · transcript_outbox._record_tool_result (cyclomatic 19) · ×1
  • transcript_outbox._record_tool_result (cyclomatic 19) invisible_engine_dots/nanobot/dots/transcript_outbox.py:154 — transcript_outbox._record_tool_result 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 · helpers.estimate_message_tokens (cyclomatic 19) · ×1
  • helpers.estimate_message_tokens (cyclomatic 19) invisible_engine_dots/nanobot/utils/helpers.py:500 — helpers.estimate_message_tokens 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 · guest-events.applyGuestEvent (cyclomatic 18) · ×1
  • guest-events.applyGuestEvent (cyclomatic 18) apps/scheduler/src/guest-events.ts:92 — guest-events.applyGuestEvent 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 · mcp-servers-panel.McpServersPanel (cyclomatic 18) · ×1
  • mcp-servers-panel.McpServersPanel (cyclomatic 18) apps/web/src/components/dot-settings/mcp-servers-panel.tsx:155 — mcp-servers-panel.McpServersPanel has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to 3 function items 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 · story.Body (cyclomatic 18) · ×1
  • story.Body (cyclomatic 18) apps/web/src/components/tasks/story.tsx:28 — story.Body 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 · transcript_outbox.record_transcript_append (cyclomatic 18) · ×1
  • transcript_outbox.record_transcript_append (cyclomatic 18) invisible_engine_dots/nanobot/dots/transcript_outbox.py:101 — transcript_outbox.record_transcript_append 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 · approval-card.ApprovalCard (cyclomatic 17) · ×1
  • approval-card.ApprovalCard (cyclomatic 17) apps/web/src/components/elements/approval-card.tsx:48 — approval-card.ApprovalCard has cyclomatic complexity 17 (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 · yaml.emit (cyclomatic 17) · ×1
  • yaml.emit (cyclomatic 17) apps/web/src/lib/yaml.ts:67 — yaml.emit has cyclomatic complexity 17 (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 · use-inbox-keys.useInboxKeys · ×1
  • use-inbox-keys.useInboxKeys::onKeyDown (cyclomatic 17) apps/web/src/components/inbox/use-inbox-keys.ts:48 — use-inbox-keys.useInboxKeys::onKeyDown has cyclomatic complexity 17 (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 · NewDotPage.NewDotPage (cyclomatic 17) · ×1
  • NewDotPage.NewDotPage (cyclomatic 17) apps/web/src/components/new-dot/NewDotPage.tsx:24 — NewDotPage.NewDotPage has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 5 function items 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 · main.serve (cyclomatic 17) · ×1
  • main.serve (cyclomatic 17) guest/dot-agentd/cmd/dot-agentd/main.go:120 — main.serve has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · web.startWebServer (cyclomatic 16) · ×1
  • web.startWebServer (cyclomatic 16) REDACTED:106 — web.startWebServer has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function items 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 · Lifecycle.#readyProcedure (cyclomatic 16) · ×1
  • Lifecycle.#readyProcedure (cyclomatic 16) apps/scheduler/src/lifecycle.ts:399 — Lifecycle.#readyProcedure 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 · GuestClient.sendRaw (cyclomatic 16) · ×1
  • GuestClient.sendRaw (cyclomatic 16) apps/vm-manager/src/guest-client.ts:189 — GuestClient.sendRaw 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 4 function literals inside it that branch (lines 206, 221, 228, …). 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 · VmManager.startLocked (cyclomatic 16) · ×1
  • VmManager.startLocked (cyclomatic 16) apps/vm-manager/src/vm-manager.ts:525 — VmManager.startLocked 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 · ChannelHub.#inbound (cyclomatic 16) · ×1
  • ChannelHub.#inbound (cyclomatic 16) packages/channels/src/hub.ts:501 — ChannelHub.#inbound has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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 · InvisibleDotsClient.stream (cyclomatic 16) · ×1
  • InvisibleDotsClient.stream (cyclomatic 16) packages/sdk/src/client.ts:475 — InvisibleDotsClient.stream 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 · ContextGovernor.backfill_missing_tool_results (cyclomatic 16) · ×1
  • ContextGovernor.backfill_missing_tool_results (cyclomatic 16) invisible_engine_dots/nanobot/agent/context_governance.py:807 — ContextGovernor.backfill_missing_tool_results 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 · Consolidator.summarize (cyclomatic 16) · ×1
  • Consolidator.summarize (cyclomatic 16) invisible_engine_dots/nanobot/agent/memory.py:164 — Consolidator.summarize 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 · ExecSessionTool._wait (cyclomatic 16) · ×1
  • ExecSessionTool._wait (cyclomatic 16) invisible_engine_dots/nanobot/agent/tools/exec_session.py:671 — ExecSessionTool._wait 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 · service._validate_schedule_for_add (cyclomatic 16) · ×1
  • service._validate_schedule_for_add (cyclomatic 16) invisible_engine_dots/nanobot/cron/service.py:72 — service._validate_schedule_for_add has cyclomatic complexity 16 (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.
D2 · Cognitive Complexity · cli.run (cognitive 222) · ×1
  • cli.run (cognitive 222) apps/cli/src/cli.ts:350 — cli.run has cognitive complexity 222 (threshold 15). Drivers by points: if/else 48 (112 pts), ternaries 30 (78 pts), boolean chains 12, loops 4 (11 pts), error handling 4 (6 pts), match/switch 2 (3 pts) (nesting depth added 122). Of this number, 212 points are the body's own statements and 10 belong to 4 function items 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 · ApplyPatchTool.execute (cognitive 100) · ×1
  • ApplyPatchTool.execute (cognitive 100) invisible_engine_dots/nanobot/agent/tools/apply_patch.py:96 — ApplyPatchTool.execute has cognitive complexity 100 (threshold 15). Drivers by points: if/else 28 (70 pts), error handling 7 (17 pts), loops 6 (7 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 54). 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 · Schema.validate_json_schema_value (cognitive 74) · ×1
  • Schema.validate_json_schema_value (cognitive 74) invisible_engine_dots/nanobot/agent/tools/base.py:56 — Schema.validate_json_schema_value has cognitive complexity 74 (threshold 15). Drivers by points: if/else 26 (42 pts), boolean chains 20, loops 3 (7 pts), ternaries 2 (5 pts) (nesting depth added 23). 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 · OpenAICompatProvider._parse_chunks (cognitive 74) · ×1
  • OpenAICompatProvider._parse_chunks (cognitive 74) REDACTED:613 — OpenAICompatProvider._parse_chunks has cognitive complexity 74 (threshold 15). Drivers by points: if/else 20 (54 pts), boolean chains 11, loops 4 (7 pts), ternaries 1 (2 pts) (nesting depth added 38). 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 · AgentServer._handle (cognitive 65) · ×1
  • AgentServer._handle (cognitive 65) REDACTED:250 — AgentServer._handle has cognitive complexity 65 (threshold 15). Drivers by points: if/else 21 (32 pts), error handling 9 (20 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 25). 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 · AgentRunner._run_core (cognitive 64) · ×1
  • AgentRunner._run_core (cognitive 64) invisible_engine_dots/nanobot/agent/runner.py:298 — AgentRunner._run_core has cognitive complexity 64 (threshold 15). Drivers by points: if/else 21 (46 pts), boolean chains 13, ternaries 1 (4 pts), loops 1 (nesting depth added 28). 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 · GrepTool.execute (cognitive 64) · ×1
  • GrepTool.execute (cognitive 64) invisible_engine_dots/nanobot/agent/tools/search.py:524 — GrepTool.execute has cognitive complexity 64 (threshold 15). Drivers by points: if/else 24 (39 pts), ternaries 7 (11 pts), boolean chains 6, error handling 4, loops 2 (4 pts) (nesting depth added 21). 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 · EditFileTool.execute (cognitive 62) · ×1
  • EditFileTool.execute (cognitive 62) invisible_engine_dots/nanobot/agent/tools/filesystem.py:594 — EditFileTool.execute has cognitive complexity 62 (threshold 15). Drivers by points: if/else 30 (43 pts), boolean chains 12, error handling 4, ternaries 1 (2 pts), loops 1 (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 · server.buildServer (cognitive 56) · ×1
  • server.buildServer (cognitive 56) REDACTED:101 — server.buildServer has cognitive complexity 56 (threshold 15). Drivers by points: if/else 22 (24 pts), boolean chains 16, ternaries 7 (11 pts), loops 4, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 56 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 126, 391, 364, …). 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 · file-preview.FilePreview (cognitive 51) · ×1
  • file-preview.FilePreview (cognitive 51) apps/web/src/components/computer/file-preview.tsx:33 — file-preview.FilePreview has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 12 (44 pts), if/else 6, error handling 1 (nesting depth added 32). Of this number, 42 points are the body's own statements and 9 belong to 5 function items inside it that branch. 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 · agentd.RunRelay (cognitive 49) · ×1
  • agentd.RunRelay (cognitive 49) guest/dot-agentd/internal/agentd/relay.go:42 — agentd.RunRelay has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (38 pts), loops 3 (4 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 23). Of this number, 31 points are the body's own statements and 18 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 · LLMProvider._sanitize_empty_content (cognitive 47) · ×1
  • LLMProvider._sanitize_empty_content (cognitive 47) invisible_engine_dots/nanobot/providers/base.py:472 — LLMProvider._sanitize_empty_content has cognitive complexity 47 (threshold 15). Drivers by points: if/else 11 (30 pts), ternaries 3 (8 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 26). 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 · Session.get_history (cognitive 44) · ×1
  • Session.get_history (cognitive 44) invisible_engine_dots/nanobot/session/manager.py:80 — Session.get_history has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (34 pts), loops 4 (6 pts), boolean chains 4 (nesting depth added 19). 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 · qr-connect.QrConnect (cognitive 43) · ×1
  • qr-connect.QrConnect (cognitive 43) apps/web/src/components/channels/qr-connect.tsx:62 — qr-connect.QrConnect has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 13 (19 pts), boolean chains 11, if/else 8 (11 pts), error handling 1, loops 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 22 belong to 5 function items 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 · ContextGovernor.backfill_missing_tool_results (cognitive 43) · ×1
  • ContextGovernor.backfill_missing_tool_results (cognitive 43) invisible_engine_dots/nanobot/agent/context_governance.py:807 — ContextGovernor.backfill_missing_tool_results has cognitive complexity 43 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 4 (7 pts), ternaries 1 (7 pts), boolean chains 2 (nesting depth added 29). 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 · agentd.runProcStream (cognitive 41) · ×1
  • agentd.runProcStream (cognitive 41) guest/dot-agentd/internal/agentd/proc.go:138 — agentd.runProcStream has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 3 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 19). Most of this is not in the body itself: 10 of the 41 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 183, 164, 141). 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 · helpers._estimate_prompt_tokens_with_source (cognitive 40) · ×1
  • helpers._estimate_prompt_tokens_with_source (cognitive 40) invisible_engine_dots/nanobot/utils/helpers.py:434 — helpers._estimate_prompt_tokens_with_source has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (19 pts), ternaries 5 (10 pts), loops 3 (6 pts), boolean chains 4, error handling 1 (nesting depth added 20). 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 · Lifecycle.#readyProcedure (cognitive 38) · ×1
  • Lifecycle.#readyProcedure (cognitive 38) apps/scheduler/src/lifecycle.ts:399 — Lifecycle.#readyProcedure has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (29 pts), error handling 3 (5 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 21). 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 · FakeBotApi.#handle (cognitive 38) · ×1
  • FakeBotApi.#handle (cognitive 38) packages/channels/src/telegram/fake-bot-api.ts:317 — FakeBotApi.#handle has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 6, ternaries 1 (2 pts), error handling 1, loops 1, match/switch 1 (nesting depth added 12). Of this number, 37 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 · Tool._cast_value (cognitive 38) · ×1
  • Tool._cast_value (cognitive 38) invisible_engine_dots/nanobot/agent/tools/base.py:241 — Tool._cast_value has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 7, ternaries 3 (6 pts), error handling 1 (2 pts) (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 · ListDirTool.execute (cognitive 37) · ×1
  • ListDirTool.execute (cognitive 37) invisible_engine_dots/nanobot/agent/tools/filesystem.py:847 — ListDirTool.execute has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 2 (8 pts), loops 2 (4 pts), error handling 3, boolean chains 2 (nesting depth added 17). 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 · task-drawer.TaskDrawer (cognitive 36) · ×1
  • task-drawer.TaskDrawer (cognitive 36) apps/web/src/components/tasks/task-drawer.tsx:41 — task-drawer.TaskDrawer has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 17 (30 pts), boolean chains 6 (nesting depth added 13). Of this number, 35 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 · exec_session._escape_end (cognitive 36) · ×1
  • exec_session._escape_end (cognitive 36) invisible_engine_dots/nanobot/agent/tools/exec_session.py:47 — exec_session._escape_end has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 3 (8 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 18). 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 · LLMProvider._enforce_role_alternation (cognitive 35) · ×1
  • LLMProvider._enforce_role_alternation (cognitive 35) invisible_engine_dots/nanobot/providers/base.py:780 — LLMProvider._enforce_role_alternation has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 7, loops 3 (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 · ContextGovernor.drop_orphan_tool_results (cognitive 32) · ×1
  • ContextGovernor.drop_orphan_tool_results (cognitive 32) invisible_engine_dots/nanobot/agent/context_governance.py:769 — ContextGovernor.drop_orphan_tool_results has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 19). 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 · GuestClient.events (cognitive 31) · ×1
  • GuestClient.events (cognitive 31) apps/vm-manager/src/guest-client.ts:382 — GuestClient.events has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (22 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 17). 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 · Lifecycle.recover (cognitive 30) · ×1
  • Lifecycle.recover (cognitive 30) apps/scheduler/src/lifecycle.ts:807 — Lifecycle.recover has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 2 (7 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (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 · InvisibleDotsClient.stream (cognitive 30) · ×1
  • InvisibleDotsClient.stream (cognitive 30) packages/sdk/src/client.ts:475 — InvisibleDotsClient.stream has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 3 (6 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 17). 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 · process.acquirePidLock (cognitive 30) · ×1
  • process.acquirePidLock (cognitive 30) packages/shared/src/process.ts:118 — process.acquirePidLock has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 2 (4 pts), boolean chains 3, loops 1 (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 · exec_session.terminal_text (cognitive 30) · ×1
  • exec_session.terminal_text (cognitive 30) invisible_engine_dots/nanobot/agent/tools/exec_session.py:88 — exec_session.terminal_text has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 4, loops 1 (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 · Scheduler.resolveApproval (cognitive 29) · ×1
  • Scheduler.resolveApproval (cognitive 29) apps/scheduler/src/scheduler.ts:696 — Scheduler.resolveApproval has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11, ternaries 10, boolean chains 7, loops 1. Most of this is not in the body itself: 13 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 728). 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 · yaml.emit (cognitive 29) · ×1
  • yaml.emit (cognitive 29) apps/web/src/lib/yaml.ts:67 — yaml.emit has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 4 (7 pts), loops 2 (4 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 · DotSettings.Editor (cognitive 29) · ×1
  • DotSettings.Editor (cognitive 29) apps/web/src/components/dot-settings/DotSettings.tsx:43 — DotSettings.Editor has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 8 (9 pts), boolean chains 4, error handling 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 12 belong to 8 function items inside it that branch. 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 · CronTool._add_job (cognitive 28) · ×1
  • CronTool._add_job (cognitive 28) invisible_engine_dots/nanobot/agent/tools/cron.py:123 — CronTool._add_job has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 10). 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 · ExecSessionTool._wait (cognitive 28) · ×1
  • ExecSessionTool._wait (cognitive 28) invisible_engine_dots/nanobot/agent/tools/exec_session.py:671 — ExecSessionTool._wait has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 4 (10 pts), boolean chains 4, loops 1 (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 · FindFilesTool.execute (cognitive 28) · ×1
  • FindFilesTool.execute (cognitive 28) invisible_engine_dots/nanobot/agent/tools/search.py:299 — FindFilesTool.execute has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (17 pts), ternaries 4 (6 pts), error handling 3, boolean chains 1, loops 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 · OpenAICompatProvider._sanitize_messages (cognitive 28) · ×1
  • OpenAICompatProvider._sanitize_messages (cognitive 28) REDACTED:307 — OpenAICompatProvider._sanitize_messages has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 17). 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 · DotHeader.DotHeader (cognitive 27) · ×1
  • DotHeader.DotHeader (cognitive 27) apps/web/src/components/dot/DotHeader.tsx:27 — DotHeader.DotHeader has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 13 (22 pts), boolean chains 4, if/else 1 (nesting depth added 9). Of this number, 26 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 · ContextGovernor.strip_malformed_tool_calls (cognitive 27) · ×1
  • ContextGovernor.strip_malformed_tool_calls (cognitive 27) invisible_engine_dots/nanobot/agent/context_governance.py:714 — ContextGovernor.strip_malformed_tool_calls has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 1, loops 1 (nesting depth added 13). 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 · usage-tab.UsageTab (cognitive 26) · ×1
  • usage-tab.UsageTab (cognitive 26) apps/web/src/components/computer/usage-tab.tsx:84 — usage-tab.UsageTab has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (18 pts), boolean chains 8 (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 · helpers.estimate_message_tokens (cognitive 26) · ×1
  • helpers.estimate_message_tokens (cognitive 26) invisible_engine_dots/nanobot/utils/helpers.py:500 — helpers.estimate_message_tokens has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts), error handling 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 · Consolidator.summarize (cognitive 25) · ×1
  • Consolidator.summarize (cognitive 25) invisible_engine_dots/nanobot/agent/memory.py:164 — Consolidator.summarize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (6 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 10). 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 · ReadFileTool.execute (cognitive 25) · ×1
  • ReadFileTool.execute (cognitive 25) invisible_engine_dots/nanobot/agent/tools/filesystem.py:129 — ReadFileTool.execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (17 pts), error handling 5 (6 pts), boolean chains 2 (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 · Server.handleProc (cognitive 25) · ×1
  • Server.handleProc (cognitive 25) guest/dot-agentd/internal/agentd/proc.go:63 — Server.handleProc has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 5, loops 2 (nesting depth added 5). 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 · ActivityView.ActivityView (cognitive 24) · ×1
  • ActivityView.ActivityView (cognitive 24) apps/web/src/components/activity/ActivityView.tsx:24 — ActivityView.ActivityView has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 16 (22 pts), boolean chains 2 (nesting depth added 6). Of this number, 22 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 · EventLog.stream (cognitive 24) · ×1
  • EventLog.stream (cognitive 24) packages/events/src/event-log.ts:169 — EventLog.stream has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (6 pts) (nesting depth added 12). Of this number, 22 points are the body's own statements and 2 belong 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 · writer.buildTree (cognitive 24) · ×1
  • writer.buildTree (cognitive 24) packages/iso/src/writer.ts:236 — writer.buildTree has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (6 pts), loops 2 (3 pts) (nesting depth added 13). 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 · VmManager.startLocked (cognitive 23) · ×1
  • VmManager.startLocked (cognitive 23) apps/vm-manager/src/vm-manager.ts:525 — VmManager.startLocked has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), boolean chains 3, ternaries 1 (2 pts), loops 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 · dot-live.applyLiveEvent (cognitive 23) · ×1
  • dot-live.applyLiveEvent (cognitive 23) apps/web/src/lib/dot-live.ts:65 — dot-live.applyLiveEvent has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5 (9 pts), boolean chains 3, match/switch 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 · approval-view.approvalBody (cognitive 23) · ×1
  • approval-view.approvalBody (cognitive 23) apps/web/src/lib/approval-view.ts:212 — approval-view.approvalBody has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, ternaries 3 (6 pts), match/switch 1 (nesting depth added 8). Of this number, 15 points are the body's own statements and 8 belong to one function literal inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MCPPromptWrapper.execute (cognitive 23) · ×1
  • MCPPromptWrapper.execute (cognitive 23) invisible_engine_dots/nanobot/agent/tools/mcp.py:757 — MCPPromptWrapper.execute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 4, loops 2 (4 pts), ternaries 2 (4 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 · conversations.render (cognitive 23) · ×1
  • conversations.render (cognitive 23) invisible_engine_dots/nanobot/dots/conversations.py:114 — conversations.render has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (nesting depth added 13). 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 · images.image_size (cognitive 23) · ×1
  • images.image_size (cognitive 23) invisible_engine_dots/nanobot/dots/images.py:51 — images.image_size has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 2, loops 1 (2 pts), error handling 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 · OpenAICompatProvider._extract_text_content (cognitive 23) · ×1
  • OpenAICompatProvider._extract_text_content (cognitive 23) REDACTED:446 — OpenAICompatProvider._extract_text_content has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 13). 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 · files-tab.FilesTab (cognitive 22) · ×1
  • files-tab.FilesTab (cognitive 22) apps/web/src/components/computer/files-tab.tsx:41 — files-tab.FilesTab has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 12 (15 pts), boolean chains 6, if/else 1 (nesting depth added 3). Of this number, 18 points are the body's own statements and 4 belong to 2 function items inside it that branch. 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 · mcp-servers-panel.McpServersPanel (cognitive 22) · ×1
  • mcp-servers-panel.McpServersPanel (cognitive 22) apps/web/src/components/dot-settings/mcp-servers-panel.tsx:155 — mcp-servers-panel.McpServersPanel has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 12 (17 pts), if/else 4, boolean chains 1 (nesting depth added 5). Of this number, 12 points are the body's own statements and 10 belong to 3 function items inside it that branch. 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 · NeedsYou.NeedsYou (cognitive 22) · ×1
  • NeedsYou.NeedsYou (cognitive 22) apps/web/src/components/inbox/NeedsYou.tsx:127 — NeedsYou.NeedsYou has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, ternaries 11. Of this number, 18 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · config.dotConfigSchema (cognitive 22) · ×1
  • config.dotConfigSchema (cognitive 22) packages/shared/src/config.ts:340 — config.dotConfigSchema has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 2 (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 · SseParser.feed (cognitive 22) · ×1
  • SseParser.feed (cognitive 22) packages/shared/src/sse.ts:29 — SseParser.feed has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 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 · ContextGovernor.normalize_tool_result (cognitive 22) · ×1
  • ContextGovernor.normalize_tool_result (cognitive 22) invisible_engine_dots/nanobot/agent/context_governance.py:574 — ContextGovernor.normalize_tool_result has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (4 pts), boolean chains 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 · transcript_outbox.record_transcript_append (cognitive 22) · ×1
  • transcript_outbox.record_transcript_append (cognitive 22) invisible_engine_dots/nanobot/dots/transcript_outbox.py:101 — transcript_outbox.record_transcript_append has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 5). 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 · approval-card.ApprovalCard (cognitive 21) · ×1
  • approval-card.ApprovalCard (cognitive 21) apps/web/src/components/elements/approval-card.tsx:48 — approval-card.ApprovalCard has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13 (19 pts), boolean chains 2 (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 · MemoryUpdater._changed (cognitive 21) · ×1
  • MemoryUpdater._changed (cognitive 21) invisible_engine_dots/nanobot/dots/memory_update.py:250 — MemoryUpdater._changed has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (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 · setup.prepareHost (cognitive 20) · ×1
  • setup.prepareHost (cognitive 20) apps/cli/src/setup/setup.ts:61 — setup.prepareHost has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (2 pts), error handling 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 · pairing-panel.PairingPanel (cognitive 20) · ×1
  • pairing-panel.PairingPanel (cognitive 20) apps/web/src/components/channels/pairing-panel.tsx:22 — pairing-panel.PairingPanel has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 3, if/else 2 (nesting depth added 6). Of this number, 18 points are the body's own statements and 2 belong to 2 function items 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 · AgentRunner._drain_injections (cognitive 20) · ×1
  • AgentRunner._drain_injections (cognitive 20) invisible_engine_dots/nanobot/agent/runner.py:202 — AgentRunner._drain_injections has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1, loops 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 · mcp._normalize_nullable_schema (cognitive 20) · ×1
  • mcp._normalize_nullable_schema (cognitive 20) invisible_engine_dots/nanobot/agent/tools/mcp.py:411 — mcp._normalize_nullable_schema has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 2 (4 pts), boolean chains 1, loops 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 · service._validate_schedule_for_add (cognitive 20) · ×1
  • service._validate_schedule_for_add (cognitive 20) invisible_engine_dots/nanobot/cron/service.py:72 — service._validate_schedule_for_add has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, error handling 2 (5 pts) (nesting depth added 5). 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 · helpers.sanitize_surrogates_deep (cognitive 20) · ×1
  • helpers.sanitize_surrogates_deep (cognitive 20) invisible_engine_dots/nanobot/utils/helpers.py:58 — helpers.sanitize_surrogates_deep has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (6 pts), loops 2 (4 pts) (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 · helpers.find_legal_message_start (cognitive 20) · ×1
  • helpers.find_legal_message_start (cognitive 20) invisible_engine_dots/nanobot/utils/helpers.py:379 — helpers.find_legal_message_start has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 3 (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 · CronService._execute_job (cognitive 19) · ×1
  • CronService._execute_job (cognitive 19) invisible_engine_dots/nanobot/cron/service.py:494 — CronService._execute_job has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 3, ternaries 1 (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 · Engine._suspend_now (cognitive 19) · ×1
  • Engine._suspend_now (cognitive 19) invisible_engine_dots/nanobot/dots/engine.py:487 — Engine._suspend_now has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 2 (3 pts), error handling 1, ternaries 1 (nesting depth added 5). 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 · gate.close_open_calls (cognitive 19) · ×1
  • gate.close_open_calls (cognitive 19) invisible_engine_dots/nanobot/dots/gate.py:180 — gate.close_open_calls has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (7 pts), boolean chains 2, 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 · LLMProvider._run_with_retry (cognitive 19) · ×1
  • LLMProvider._run_with_retry (cognitive 19) invisible_engine_dots/nanobot/providers/base.py:1050 — LLMProvider._run_with_retry has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 2 (3 pts), boolean chains 2, loops 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 · main.serve (cognitive 19) · ×1
  • main.serve (cognitive 19) guest/dot-agentd/cmd/dot-agentd/main.go:120 — main.serve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, loops 2, match/switch 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 3 belong 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 · agentd.resolveLinks (cognitive 19) · ×1
  • agentd.resolveLinks (cognitive 19) guest/dot-agentd/internal/agentd/files.go:102 — agentd.resolveLinks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (18 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 · FakeGuest.events (cognitive 18) · ×1
  • FakeGuest.events (cognitive 18) apps/scheduler/src/testing.ts:634 — FakeGuest.events has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, loops 1 (nesting depth added 8). Of this number, 16 points are the body's own statements and 2 belong 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 · SkillsView.Skills (cognitive 18) · ×1
  • SkillsView.Skills (cognitive 18) apps/web/src/components/skills/SkillsView.tsx:37 — SkillsView.Skills has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 2, if/else 1 (nesting depth added 7). Of this number, 11 points are the body's own statements and 7 belong 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 · History.History (cognitive 18) · ×1
  • History.History (cognitive 18) apps/web/src/components/inbox/History.tsx:36 — History.History has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 3 (nesting depth added 6). Of this number, 14 points are the body's own statements and 4 belong 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 · NewDotPage.NewDotPage (cognitive 18) · ×1
  • NewDotPage.NewDotPage (cognitive 18) apps/web/src/components/new-dot/NewDotPage.tsx:24 — NewDotPage.NewDotPage has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 12 (13 pts), if/else 3, boolean chains 2 (nesting depth added 1). Of this number, 11 points are the body's own statements and 7 belong to 5 function items 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 · BindingRunner.#supervise (cognitive 18) · ×1
  • BindingRunner.#supervise (cognitive 18) packages/channels/src/runner.ts:140 — BindingRunner.#supervise has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). Of this number, 16 points are the body's own statements and 2 belong 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 · BrowserManager.launch (cognitive 18) · ×1
  • BrowserManager.launch (cognitive 18) invisible_engine_dots/nanobot/dots/browser.py:338 — BrowserManager.launch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (2 pts), 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 · transcript_outbox._record_tool_result (cognitive 18) · ×1
  • transcript_outbox._record_tool_result (cognitive 18) invisible_engine_dots/nanobot/dots/transcript_outbox.py:154 — transcript_outbox._record_tool_result has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, ternaries 6, if/else 5. 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 · LLMProvider._strip_image_content (cognitive 18) · ×1
  • LLMProvider._strip_image_content (cognitive 18) invisible_engine_dots/nanobot/providers/base.py:855 — LLMProvider._strip_image_content has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (5 pts), loops 2 (4 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 · OpenAICompatProvider._extract_error_metadata (cognitive 18) · ×1
  • OpenAICompatProvider._extract_error_metadata (cognitive 18) REDACTED:781 — OpenAICompatProvider._extract_error_metadata has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, error handling 1 (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 · openai_compat_provider._extract_tc_extras (cognitive 18) · ×1
  • openai_compat_provider._extract_tc_extras (cognitive 18) REDACTED:97 — openai_compat_provider._extract_tc_extras has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2 (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 · web.startWebServer (cognitive 17) · ×1
  • web.startWebServer (cognitive 17) REDACTED:106 — web.startWebServer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 3 belong to 2 function items 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 · Lifecycle.#pump (cognitive 17) · ×1
  • Lifecycle.#pump (cognitive 17) apps/scheduler/src/lifecycle.ts:697 — Lifecycle.#pump has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), error handling 1 (2 pts) (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 · story.Body (cognitive 17) · ×1
  • story.Body (cognitive 17) apps/web/src/components/tasks/story.tsx:28 — story.Body has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · TasksView.Sections (cognitive 17) · ×1
  • TasksView.Sections (cognitive 17) apps/web/src/components/tasks/TasksView.tsx:43 — TasksView.Sections has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9 (14 pts), boolean chains 3 (nesting depth added 5). 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 · ContextGovernor.strip_placeholder_assistant_messages (cognitive 17) · ×1
  • ContextGovernor.strip_placeholder_assistant_messages (cognitive 17) invisible_engine_dots/nanobot/agent/context_governance.py:676 — ContextGovernor.strip_placeholder_assistant_messages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (2 pts), boolean chains 1, 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 · _ExecSession.poll (cognitive 17) · ×1
  • _ExecSession.poll (cognitive 17) invisible_engine_dots/nanobot/agent/tools/exec_session.py:277 — _ExecSession.poll has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 1 (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, 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 · FindFilesTool._walk (cognitive 17) · ×1
  • FindFilesTool._walk (cognitive 17) invisible_engine_dots/nanobot/agent/tools/search.py:368 — FindFilesTool._walk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (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 · memory_update._pieces (cognitive 17) · ×1
  • memory_update._pieces (cognitive 17) invisible_engine_dots/nanobot/dots/memory_update.py:86 — memory_update._pieces has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 3 (6 pts), ternaries 2 (4 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 · McpSecrets.set (cognitive 17) · ×1
  • McpSecrets.set (cognitive 17) invisible_engine_dots/nanobot/dots/secrets.py:92 — McpSecrets.set has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, loops 2 (3 pts) (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 · Scheduler.setOpenRouterKey (cognitive 16) · ×1
  • Scheduler.setOpenRouterKey (cognitive 16) apps/scheduler/src/scheduler.ts:855 — Scheduler.setOpenRouterKey has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 3, error handling 1 (2 pts), loops 2, ternaries 1 (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 · approval-view.schedulePhrase (cognitive 16) · ×1
  • approval-view.schedulePhrase (cognitive 16) apps/web/src/lib/approval-view.ts:135 — approval-view.schedulePhrase has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (7 pts), boolean chains 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to one function item 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 · HomePage.HomePage (cognitive 16) · ×1
  • HomePage.HomePage (cognitive 16) apps/web/src/components/home/HomePage.tsx:20 — HomePage.HomePage has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 5 (nesting depth added 2). Of this number, 15 points are the body's own statements and 1 belongs 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 · ChannelHub.#inbound (cognitive 16) · ×1
  • ChannelHub.#inbound (cognitive 16) packages/channels/src/hub.ts:501 — ChannelHub.#inbound has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 2). Of this number, 12 points are the body's own statements and 4 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 · MemoryUpdater._run (cognitive 16) · ×1
  • MemoryUpdater._run (cognitive 16) invisible_engine_dots/nanobot/dots/memory_update.py:174 — MemoryUpdater._run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 5). 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 · Duplicate method names with identical signatures and likely identical intent. 'prepare_messages_for_model' and 'prepare_for_model' are semantically redundant. · ×1
  • Duplicate method names with identical signatures and likely identical intent. 'prepare_messages_for_model' and 'prepare_for_model' are semantically redundant. — Remove one of the methods (likely 'prepare_for_model' if it's the older/shorter alias, or 'prepare_messages_for_model' if it's the explicit one) and keep the other. (signatures: ContextGovernor.prepare_messages_for_model(self, config: ContextGovernanceConfig, messages: list[dict[str, Any]]): list[dict[str, Any]] | ContextGovernor.prepare_for_model(self, config: ContextGovernanceConfig, messages: list[dict[str, Any]]): list[dict[str, Any]])
D22 · Internal API Consistency · Inconsistent parameter naming for directory paths. ExecTool uses both 'working_dir' and 'workdir' as potential parameters (or accepts either), while ExecSessionTool does not expose directory parameters in its execute signature (likely inheriting from session context). However, within ExecTool, having both 'working_dir' and 'workdir' suggests an aliasing inconsistency or redundant parameter support. · ×1
  • Inconsistent parameter naming for directory paths. ExecTool uses both 'working_dir' and 'workdir' as potential parameters (or accepts either), while ExecSessionTool does not expose directory parameters in its execute signature (likely inheriting from session context). However, within ExecTool, having both 'working_dir' and 'workdir' suggests an aliasing inconsistency or redundant parameter support. — Standardize on 'working_dir' and remove 'workdir' from the signature, or explicitly document that 'workdir' is a deprecated alias. (signatures: ExecTool.execute(self, command: str | list[str] | None, cmd: str | None, working_dir: str | None, workdir: str | None, ...) | ExecSessionTool.execute(self, session_id: str, input: str | None, close_stdin: bool, terminate: bool, ...))
D22 · Internal API Consistency · While 'get' and 'has' are distinct operations (one returns the object, one returns a boolean), the presence of 'has' often indicates a lack of Pythonic 'in' operator support or redundancy if 'get' is used for existence checks. However, this is a minor style issue. A more significant inconsistency is found in the Tool base class vs specific tools. · ×1
  • While 'get' and 'has' are distinct operations (one returns the object, one returns a boolean), the presence of 'has' often indicates a lack of Pythonic 'in' operator support or redundancy if 'get' is used for existence checks. However, this is a minor style issue. A more significant inconsistency is found in the Tool base class vs specific tools. — Ensure ToolRegistry supports 'in' operator (e.g., `if tool in registry`) to make 'has' redundant, or remove 'has' if 'get' is sufficient for existence checks. (signatures: ToolRegistry.get(self, name: str): Tool | None | ToolRegistry.has(self, name: str): bool)
D22 · Internal API Consistency · Inconsistent error representation in hook contexts. AgentHookContext only stores the error as a string, while AgentRunHookContext stores both the error string and the original exception object. This creates an inconsistency in the information available to hooks depending on which context they receive. · ×1
  • Inconsistent error representation in hook contexts. AgentHookContext only stores the error as a string, while AgentRunHookContext stores both the error string and the original exception object. This creates an inconsistency in the information available to hooks depending on which context they receive. — Standardize AgentHookContext to also include the original exception object (or a unified error wrapper) to provide consistent debugging information across all hook stages. (signatures: AgentHookContext.error: str | None | AgentRunHookContext.error: str | None | AgentRunHookContext.exception: BaseException | None)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: scheduler.ts ↔ testing.ts apps/scheduler/src/scheduler.ts:1 — `apps/scheduler/src/scheduler.ts` and `apps/scheduler/src/testing.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `a60ee568` host: MCP secrets are set write-only, pushed with the key, and none o…; `39ac3052` shared, engine, scheduler: the identity error statuses have one owner; `a4f83f49` shared, engine, host: automations and tools routes — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) invisible_engine_dots/nanobot/agent/tools/filesystem.py:382 — invisible_engine_dots/nanobot/agent/tools/filesystem.py:382-397 | invisible_engine_dots/nanobot/agent/tools/filesystem.py:455-470 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) invisible_engine_dots/nanobot/agent/runner.py:563 — invisible_engine_dots/nanobot/agent/runner.py:563-575 | invisible_engine_dots/nanobot/agent/runner.py:584-597 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `invisible_engine_dots/nanobot/agent/runner.py:584` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) invisible_engine_dots/nanobot/agent/tools/mcp.py:687 — invisible_engine_dots/nanobot/agent/tools/mcp.py:687-696 | invisible_engine_dots/nanobot/agent/tools/mcp.py:785-794 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) invisible_engine_dots/nanobot/dots/browser.py:542 — invisible_engine_dots/nanobot/dots/browser.py:542-547 | invisible_engine_dots/nanobot/dots/browser.py:551-556 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) invisible_engine_dots/nanobot/utils/helpers.py:446 — invisible_engine_dots/nanobot/utils/helpers.py:446-450 | invisible_engine_dots/nanobot/utils/helpers.py:504-508 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) guest/dot-agentd/internal/agentd/files.go:297 — guest/dot-agentd/internal/agentd/files.go:297-307 | guest/dot-agentd/internal/agentd/files.go:334-344 — 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. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D5 · Coupling · Unstable project @invisible-dots/api · ×1
  • Unstable project @invisible-dots/api — @invisible-dots/api has instability 0.89 with 1 dependents.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
R10 · Code Duplication · Duplication concentrated across 10 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 10 sibling directories (11 clone groups) apps/web/src/components/dot-settings/panels.tsx:43 — 11 duplicated blocks under apps/web/src/components/ have copies in at least two of the sibling directories approvals, chat, computer, dot-settings, elements, inbox (+4 more sibling(s) not listed) — 9 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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 · Duplication concentrated across 3 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (6 clone groups) guest/image-builder/src/manifest.ts:81 — 6 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, guest, packages — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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 with local edits (107 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (107 matched lines × 2 locations) apps/web/src/components/ui/dialog.tsx:11 — apps/web/src/components/ui/dialog.tsx:11 · apps/web/src/components/ui/sheet.tsx:9 — the two spans are one implementation copied and then locally edited — 475 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 (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) apps/web/src/components/dot-settings/panels.tsx:43 — apps/web/src/components/dot-settings/panels.tsx:43 · apps/web/src/components/new-dot/FormSections.tsx:88 — the two spans are one implementation copied and then locally edited — 422 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 (23 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (23 matched lines × 2 locations) apps/web/src/components/new-dot/Field.tsx:92 — apps/web/src/components/new-dot/Field.tsx:92 · apps/web/src/components/new-dot/Field.tsx:140 — the two spans are one implementation copied and then locally edited — 153 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (17 matched lines × 2 locations) packages/channels/src/hub.ts:176 — packages/channels/src/hub.ts:176 · packages/channels/src/hub.ts:265 — the two spans are one implementation copied and then locally edited — 160 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) apps/web/src/components/inbox/History.tsx:67 — apps/web/src/components/inbox/History.tsx:67 · apps/web/src/components/tasks/history-table.tsx:62 — 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 (11 lines × 3 locations) · ×1
  • Duplicated block (11 lines × 3 locations) apps/web/src/components/computer/files-tab.tsx:112 — apps/web/src/components/computer/files-tab.tsx:112 · apps/web/src/components/inbox/History.tsx:72 · apps/web/src/components/tasks/history-table.tsx:70 — 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 (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) apps/web/src/components/dot-settings/mcp-servers-panel.tsx:83 — apps/web/src/components/dot-settings/mcp-servers-panel.tsx:83 · apps/web/src/components/dot-settings/mcp-servers-panel.tsx:94 — 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 (9 lines × 3 locations) · ×1
  • Duplicated block (9 lines × 3 locations) packages/database/src/computers.ts:58 — packages/database/src/computers.ts:58 · packages/database/src/inbound.ts:77 · packages/database/src/tasks.ts:120 — 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 (7 lines × 5 locations) · ×1
  • Duplicated block (7 lines × 5 locations) packages/database/src/approvals.ts:63 — packages/database/src/approvals.ts:63 · packages/database/src/channels.ts:121 · packages/database/src/computers.ts:60 · packages/database/src/inbound.ts:79 · +1 more site(s) not listed — the 5 copies are spread across 5 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 (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) packages/database/src/channels.ts:116 — packages/database/src/channels.ts:116 · packages/database/src/channels.ts:158 · packages/database/src/channels.ts:198 — 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.
R10 · Code Duplication · Duplicated block (6 lines × 4 locations) · ×1
  • Duplicated block (6 lines × 4 locations) apps/web/src/app/(app)/dots/[id]/activity/page.tsx:5 — apps/web/src/app/(app)/dots/[id]/activity/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/channels/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/chat/page.tsx:5 · apps/web/src/app/(app)/dots/[id]/settings/page.tsx:5 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (6 lines × 8 locations) · ×1
  • Duplicated block (6 lines × 8 locations) apps/web/src/app/(app)/dots/[id]/activity/page.tsx:2 — apps/web/src/app/(app)/dots/[id]/activity/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/channels/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/chat/page.tsx:2 · apps/web/src/app/(app)/dots/[id]/computer/page.tsx:3 · +4 more site(s) not listed — the 8 copies are spread across 8 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R2 · Cyclomatic Complexity · Complex function #answer (cyclomatic 188, cognitive 388) · ×1
  • Complex function #answer (cyclomatic 188, cognitive 388) apps/web/test/support/control-plane.ts:279 — #answer has cyclomatic complexity 188 and cognitive complexity 388; 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 run (cyclomatic 132, cognitive 225) · ×1
  • Complex function run (cyclomatic 132, cognitive 225) apps/cli/src/cli.ts:350 — run has cyclomatic complexity 132 and cognitive complexity 225; 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 handle (cyclomatic 62, cognitive 42) · ×1
  • Complex function handle (cyclomatic 62, cognitive 42) apps/cli/test/cli.test.ts:106 — handle has cyclomatic complexity 62 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 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 (anonymous) (cyclomatic 34, cognitive 29) · ×1
  • Complex function (anonymous) (cyclomatic 34, cognitive 29) apps/api/test/guest-http.ts:48 — (anonymous) has cyclomatic complexity 34 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 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 #handle (cyclomatic 32, cognitive 38) · ×1
  • Complex function #handle (cyclomatic 32, cognitive 38) packages/channels/src/telegram/fake-bot-api.ts:317 — #handle has cyclomatic complexity 32 and cognitive complexity 38; 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 TaskDrawer (cyclomatic 27, cognitive 23) · ×1
  • Complex function TaskDrawer (cyclomatic 27, cognitive 23) apps/web/src/components/tasks/task-drawer.tsx:41 — TaskDrawer has cyclomatic complexity 27 and cognitive complexity 23; 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 UsageTab (cyclomatic 25, cognitive 24) · ×1
  • Complex function UsageTab (cyclomatic 25, cognitive 24) apps/web/src/components/computer/usage-tab.tsx:84 — UsageTab has cyclomatic complexity 25 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 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 NeedsYou (cyclomatic 25, cognitive 19) · ×1
  • Complex function NeedsYou (cyclomatic 25, cognitive 19) apps/web/src/components/inbox/NeedsYou.tsx:127 — NeedsYou has cyclomatic complexity 25 and cognitive complexity 19; 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 applyLiveEvent (cyclomatic 24, cognitive 23) · ×1
  • Complex function applyLiveEvent (cyclomatic 24, cognitive 23) apps/web/src/lib/dot-live.ts:65 — applyLiveEvent has cyclomatic complexity 24 and cognitive complexity 23; 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 acquirePidLock (cyclomatic 23, cognitive 36) · ×1
  • Complex function acquirePidLock (cyclomatic 23, cognitive 36) packages/shared/src/process.ts:118 — acquirePidLock has cyclomatic complexity 23 and cognitive complexity 36; 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 QrConnect (cyclomatic 23, cognitive 20) · ×1
  • Complex function QrConnect (cyclomatic 23, cognitive 20) apps/web/src/components/channels/qr-connect.tsx:62 — QrConnect has cyclomatic complexity 23 and cognitive complexity 20; 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 readDirectory (cyclomatic 22, cognitive 22) · ×1
  • Complex function readDirectory (cyclomatic 22, cognitive 22) packages/iso/test/iso-reader.ts:110 — readDirectory has cyclomatic complexity 22 and cognitive complexity 22; 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 stream (cyclomatic 19, cognitive 37) · ×1
  • Complex function stream (cyclomatic 19, cognitive 37) packages/sdk/src/client.ts:475 — stream has cyclomatic complexity 19 and cognitive complexity 37; 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 startLocked (cyclomatic 19, cognitive 30) · ×1
  • Complex function startLocked (cyclomatic 19, cognitive 30) apps/vm-manager/src/vm-manager.ts:525 — startLocked has cyclomatic complexity 19 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 startServer (cyclomatic 19, cognitive 18) · ×1
  • Complex function startServer (cyclomatic 19, cognitive 18) REDACTED:92 — startServer has cyclomatic complexity 19 and cognitive complexity 18; 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 (anonymous) (cyclomatic 19, cognitive 18) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 18) apps/scheduler/src/scheduler.ts:728 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 18; 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 DotHeader (cyclomatic 19, cognitive 18) · ×1
  • Complex function DotHeader (cyclomatic 19, cognitive 18) apps/web/src/components/dot/DotHeader.tsx:27 — DotHeader has cyclomatic complexity 19 and cognitive complexity 18; 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 FilesTab (cyclomatic 19, cognitive 17) · ×1
  • Complex function FilesTab (cyclomatic 19, cognitive 17) apps/web/src/components/computer/files-tab.tsx:41 — FilesTab has cyclomatic complexity 19 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 ApprovalCard (cyclomatic 19, cognitive 17) · ×1
  • Complex function ApprovalCard (cyclomatic 19, cognitive 17) apps/web/src/components/elements/approval-card.tsx:48 — ApprovalCard has cyclomatic complexity 19 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 events (cyclomatic 18, cognitive 34) · ×1
  • Complex function events (cyclomatic 18, cognitive 34) apps/vm-manager/src/guest-client.ts:382 — events has cyclomatic complexity 18 and cognitive complexity 34; 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 · apps/scheduler/src/scheduler.ts · ×1
  • apps/scheduler/src/scheduler.ts: 860 lines of code apps/scheduler/src/scheduler.ts:1 — apps/scheduler/src/scheduler.ts has 860 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 · apps/scheduler/src/lifecycle.ts · ×1
  • apps/scheduler/src/lifecycle.ts: 822 lines of code apps/scheduler/src/lifecycle.ts:1 — apps/scheduler/src/lifecycle.ts has 822 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 · apps/scheduler/src/testing.ts · ×1
  • apps/scheduler/src/testing.ts: 804 lines of code apps/scheduler/src/testing.ts:1 — apps/scheduler/src/testing.ts has 804 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 · apps/vm-manager/src/vm-manager.ts · ×1
  • apps/vm-manager/src/vm-manager.ts: 798 lines of code apps/vm-manager/src/vm-manager.ts:1 — apps/vm-manager/src/vm-manager.ts has 798 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 · apps/cli/src/cli.ts · ×1
  • apps/cli/src/cli.ts: 719 lines of code apps/cli/src/cli.ts:1 — apps/cli/src/cli.ts has 719 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 · packages/channels/src/hub.ts · ×1
  • packages/channels/src/hub.ts: 575 lines of code packages/channels/src/hub.ts:1 — packages/channels/src/hub.ts has 575 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 · packages/shared/src/protocol.ts · ×1
  • packages/shared/src/protocol.ts: 499 lines of code packages/shared/src/protocol.ts:1 — packages/shared/src/protocol.ts has 499 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 · packages/iso/src/writer.ts · ×1
  • packages/iso/src/writer.ts: 495 lines of code packages/iso/src/writer.ts:1 — packages/iso/src/writer.ts has 495 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 · packages/sdk/src/client.ts · ×1
  • packages/sdk/src/client.ts: 476 lines of code packages/sdk/src/client.ts:1 — packages/sdk/src/client.ts has 476 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 · packages/shared/src/config.ts · ×1
  • packages/shared/src/config.ts: 464 lines of code packages/shared/src/config.ts:1 — packages/shared/src/config.ts has 464 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 · apps/vm-manager/src/guest-client.ts · ×1
  • apps/vm-manager/src/guest-client.ts: 446 lines of code apps/vm-manager/src/guest-client.ts:1 — apps/vm-manager/src/guest-client.ts has 446 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: 441 lines of code REDACTED:1 — REDACTED has 441 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 · packages/shared/src/events.ts · ×1
  • packages/shared/src/events.ts: 412 lines of code packages/shared/src/events.ts:1 — packages/shared/src/events.ts has 412 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 · packages/channels/src/telegram/fake-bot-api.ts · ×1
  • packages/channels/src/telegram/fake-bot-api.ts: 404 lines of code packages/channels/src/telegram/fake-bot-api.ts:1 — packages/channels/src/telegram/fake-bot-api.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
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 apps/scheduler/test/upgrade.test.ts:18 — This repository declares test tooling, and the ✓ above records that declaration — but apps/scheduler/test/upgrade.test.ts and 1 other test file(s) in this workspace 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.
R8 · Dependency Hygiene · Unlisted import 'baileys' · ×1
  • Unlisted import 'baileys' packages/channels/test-optin/auth-state.test.ts:9 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: dotPageTitle apps/web/src/lib/dot-title.ts:14 — `dotPageTitle` 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 })`.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1
  • Untrusted text written into markup unescaped apps/web/src/app/layout.tsx:26 — `THEME_BOOTSTRAP` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` 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.
Minor — 73 finding(s)
M4 · Documentation accuracy · README/code drift · ×16
  • README/code drift docs/architecture.md:893 — docs/architecture.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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.md:1194 — docs/architecture.md names `.mcp.json`, but no file or folder `.mcp.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.
  • README/code drift docs/architecture.md:1352 — docs/architecture.md names `tools/list`, but no file or folder `tools/list` 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.md:175 — docs/guide.md names `dot.yaml`, but no file or folder `dot.yaml` 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/wiki/agent-memory-systems-compared.md:10 — docs/wiki/agent-memory-systems-compared.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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/wiki/how-a-dot-remembers.md:17 — docs/wiki/how-a-dot-remembers.md names `MEMORY.md`, but no file or folder `MEMORY.md` 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/wiki/mcp-servers-a-person-declares.md:18 — docs/wiki/mcp-servers-a-person-declares.md names `.mcp.json`, but no file or folder `.mcp.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.
  • README/code drift docs/wiki/mcp-servers-a-person-declares.md:19 — docs/wiki/mcp-servers-a-person-declares.md names `config.toml`, but no file or folder `config.toml` 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/wiki/mcp-servers-a-person-declares.md:38 — docs/wiki/mcp-servers-a-person-declares.md names `config.yaml`, but no file or folder `config.yaml` 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/wiki/the-browser-servers-own-words.md:98 — docs/wiki/the-browser-servers-own-words.md documents the environment variable `PAGE_RULES`, 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/wiki/the-browser-servers-own-words.md:99 — docs/wiki/the-browser-servers-own-words.md names `packages/core/src/mcp/instructions.ts`, but no file or folder `packages/core/src/mcp/instructions.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 tests/bench/README.md:35 — tests/bench/README.md names `tests/grade.py`, but no file or folder `tests/grade.py` 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 tests/bench/README.md:35 — tests/bench/README.md names `tests/test.sh`, but no file or folder `tests/test.sh` 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 tests/e2e/README.md:49 — tests/e2e/README.md names `.stealth-identity.json`, but no file or folder `.stealth-identity.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.
  • README/code drift tests/e2e/README.md:187 — tests/e2e/README.md runs `docker rm -f idots-e2e`, but `idots-e2e` 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 guest/image-builder/test/smoke/README.md:110 — guest/image-builder/test/smoke/README.md names `.stealth-identity.json`, but no file or folder `.stealth-identity.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.
X10 · Duplicated predicate · Duplicated predicate · ×12
  • Duplicated predicate apps/cli/src/setup/install.ts:171 — `!request.installQemu && !request.enableAccelerator` appears character-identically in 2 files — apps/cli/src/setup/install.ts, apps/cli/src/setup/setup.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 apps/cli/src/cli.ts:239 — `computer.stop_reason === "user" && computer.next_automation_at !== null` appears character-identically in 2 files — apps/cli/src/cli.ts, apps/web/src/lib/computer.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 apps/cli/src/cli.ts:572 — `error instanceof ApiError && error.code === COMPUTER_STOPPED` appears character-identically in 2 files — apps/cli/src/cli.ts, apps/web/src/lib/computer.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 apps/web/src/components/channels/qr-connect.tsx:76 — `frame.state === "linked" || frame.state === "failed"` appears character-identically in 2 files — apps/web/src/components/channels/qr-connect.tsx, packages/channels/src/link.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 apps/web/src/lib/computer.ts:145 — `status === "RUNNING" || status === "WAITING_APPROVAL"` appears character-identically in 2 files — apps/web/src/lib/computer.ts, apps/web/src/lib/task-view.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 apps/web/src/components/tasks/task-card.tsx:96 — `task.scheduled_at !== null && new Date(task.scheduled_at).getTime() > now` appears character-identically in 2 files — apps/web/src/components/tasks/task-card.tsx, apps/web/src/lib/task-view.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 guest/image-builder/src/pins.ts:63 — `typeof value !== "string" || value === ""` appears character-identically in 2 files — guest/image-builder/src/pins.ts, packages/channels/src/hub.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 apps/web/src/lib/approval-view.ts:187 — `typeof value === "number" || typeof value === "boolean"` appears character-identically in 2 files — apps/web/src/lib/approval-view.ts, apps/web/src/lib/events/view.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 invisible_engine_dots/nanobot/agent/context.py:94 — `isinstance(left, str) and isinstance(right, str)` appears character-identically in 2 files — invisible_engine_dots/nanobot/agent/context.py, invisible_engine_dots/nanobot/agent/context_governance.py. 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 invisible_engine_dots/nanobot/agent/tools/registry.py:13 — `isinstance(result, ToolResult) and result.is_error` appears character-identically in 2 files — invisible_engine_dots/nanobot/agent/tools/registry.py, invisible_engine_dots/nanobot/dots/browser.py. 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 invisible_engine_dots/nanobot/dots/mcp_servers.py:196 — `not isinstance(name, str) or re.fullmatch(MCP_SERVER_NAME_PATTERN, name) is None` appears character-identically in 2 files — invisible_engine_dots/nanobot/dots/mcp_servers.py, invisible_engine_dots/nanobot/dots/protocol.py. 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 invisible_engine_dots/nanobot/dots/engine.py:795 — `task is not None and task.status == "running"` appears character-identically in 2 files — invisible_engine_dots/nanobot/dots/engine.py, invisible_engine_dots/nanobot/dots/transcript_outbox.py. 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.
IC1 · Incompleteness & stubs · Empty method body · ×9
  • Empty method body packages/channels/src/whatsapp-baileys/baileys.ts:51 — `trace` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/channels/src/whatsapp-baileys/baileys.ts:52 — `debug` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/channels/src/whatsapp-baileys/baileys.ts:53 — `info` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/channels/src/whatsapp-baileys/baileys.ts:54 — `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/channels/src/whatsapp-baileys/baileys.ts:55 — `error` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/shared/src/support.ts:21 — `debug` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/shared/src/support.ts:21 — `info` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/shared/src/support.ts:21 — `warn` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/shared/src/support.ts:21 — `error` has an empty body — confirm it's an intentional no-op and not an unfinished method.
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch invisible_engine_dots/nanobot/agent/tools/mcp.py:307 — `_redact_url` swallows every exception into `return '<redacted-url>'` — 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 invisible_engine_dots/nanobot/providers/base.py:119 — `tool_arguments_object_for_replay` 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 apps/vm-manager/src/vm-manager.ts:677 — `readRange` 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 apps/web/src/lib/draft.ts:20 — `readDraft` 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 apps/web/src/lib/theme.ts:34 — `storedPreference` swallows every exception into `return "system"` — 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.
X4 · Structured logging · Interpolated log message defeats structured logging · ×3
  • Interpolated log message defeats structured logging REDACTED:133 — `warn` at line 133 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 REDACTED:204 — `warn` at line 204 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 REDACTED:208 — `info` at line 208 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.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: GuestApi (19 required operations) apps/scheduler/src/driver.ts:32 — `GuestApi` declares 19 required operations: `health`, `system`, `pushSecrets`, `putConfig`, `postEvent`, `state`, `listBrowserIdentities`, `createBrowserIdentity`, `getBrowserIdentity`, `deleteBrowserIdentity`, `getBrowserIdentityFrame`, `closeBrowserIdentity`, `listTools`, `listSkills`, `prepareSleep`, `screenshot`, `readFile`, `listFiles`, `events`. 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.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: contradicts the code docs/architecture.md — The architecture document describes QEMU 8.2 (Ubuntu 24.04's qemu-system-x86, 8.2.2) running the argv of section 3.4 as it is with KVM but the host uses Node 24 and Go 1.25+. Verify that QEMU 8.2 still runs the same command line on both hosts.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Split apps/web · ×1
  • Split apps/web — A 12k-LoC web project with 39 namespaces is large and sprawls across unrelated components like chat/computer/tasks/ui. Suggested:
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
DM9 · Scattered domain decisions · Rule about [data, error] decided in 3 places · ×1
  • Rule about [data, error] decided in 3 places — apps.web.src.components.ui.Resource's [data, error] are judged in apps.web.src.components.settings.HostSettings, apps.web.src.components.shell.Rail, apps.web.src.components.shell.attention — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [data, id, type] decided in 2 places · ×1
  • Rule about [data, id, type] decided in 2 places — packages.shared.src.events.StoredEvent's [data, id, type] are judged in tests.e2e.lib, tests.e2e.run — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions · Rule about [data, type] decided in 3 places · ×1
  • Rule about [data, type] decided in 3 places — packages.shared.src.events.StoredEvent's [data, type] are judged in tests.e2e.lib, tests.e2e.run, tests.e2e.scale — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 7/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/web`.
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 19977 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.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code · Unused private field 'async' · ×1
  • Unused private field 'async' apps/vm-manager/src/guest-client.ts:423 — Nothing in its class reads or assigns this private field (for a constructor parameter property: it is stored and never read), and no string key or test reaches it by name. Remove it, or use it where it was meant to take effect.
R7 · Dead Code · Unused module-local declaration 'secondsAgo' · ×1
  • Unused module-local declaration 'secondsAgo' apps/web/test/computer-page.test.tsx:56 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation · Not all functions that make a request accept a context.Context or an AbortSignal · ×1
  • Not all functions that make a request accept a context.Context or an AbortSignal — Only 5/6 functions that make a cancellable request (fetch, axios, ky, ofetch; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) 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.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~2.6 `!` null assertions per 1k TypeScript source lines — 96 assertion(s) across the 36899 source line(s) of the 340 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: apps/scheduler/src/testing.ts (11), apps/vm-manager/src/guest-client.ts (7), apps/vm-manager/src/process-file.ts (5). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure invisible_engine_dots/nanobot/agent/tools/search.py:113 — `_entry_mtime` returns `0.0` when `ValueError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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.
Minor — 3 finding(s)
D10 · Test Quality · Skipped (documented) · ×2
  • Skipped (documented): (unnamed test) guest/image-builder/test/guest-files.test.ts:50 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
  • Skipped (documented): (unnamed test) guest/image-builder/test/guest-files.test.ts:87 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: @invisible-dots/shared — @invisible-dots/shared: abstractness 0.22, instability 0.00, distance 0.78 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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-6b204aef70cf4657a08801b485c89dde/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-6b204aef70cf4657a08801b485c89dde/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 .56artifacts/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-update1artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 12 file(s) — `REDACTED`, `apps/cli/src/cli.ts`, `apps/cli/src/host.ts`, `apps/web/src/components/channels/channel-card.tsx`, `apps/web/src/components/setup/CheckList.tsx`, … (+7 more) — 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 01a15a09-7ac6-7146-8ff9-64cb03b5c8ac · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 35 · Warnings: 433 · Recommendations: 73 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 20-10-2026 @ 15:58 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