Public report of bytedance/UI-TARS-desktop, published 26 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, 26 October 2026, 17:58 UTC · Survey ID cd_cd3aa3e2df1d4609b2318dfbc3019340

bytedance/UI-TARS-desktop

Measured 26 October 2026, 17:40 UTC, at code version 3ac2cb8

Regression: 1 dimension fell since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 45out of 100 At risk Down 3 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.

Performance 73 Strong Maturity 65 Adequate Architecture 65 Adequate Security and Compliance 59 Adequate Code Health 48 Weak Accessibility 41 Weak Production Readiness 40 Weak

A large codebase: 135,777 lines of product code in 74 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Production Readiness, 40

Findings by how serious they are

282 critical 1080 serious 575 minor

10 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
26 October 2026, 17:40 UTC

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

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

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

85of 85 dimensions measured by tools.
1780of 1937 findings point to an exact file and line, so you can open each one in the code. The other 157 concern the repository as a whole, such as missing documentation.
85dimensions across 7 lenses, read from 135,777 lines of product code in 74 projects.
Chapters

Executive summary

bytedance/UI-TARS-desktop is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because 87 of the dependencies are deprecated and it has uses of packages that aren't listed. It scores 45 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 40, is the weakest lens and counts most in the score. The best first step is replacing the 87 deprecated dependencies, worth about 4 points. Tidying the declared packages comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 49.

143 known security holes in the packages the code depends on can be used by attackers. Twenty-four weaknesses in the code could be used by an attacker, and twenty-three controls can't be used without a mouse. Updating the vulnerable packages, fixing the weaknesses the scanner points to and making the controls work with a keyboard would close these risks. Setting a waiting period for automatic updates would fix the five automatic dependency updates that take new releases at once, and the 11 places where the code runs text as code or as a command need a direct call instead. The 24 uses of packages that aren't listed need adding to the project's list of dependencies.

The product code is 135,777 lines, about €150,000 to rebuild.

Code Health 48 Weak, capped by Cognitive Complexity and Dead Code Architecture 65 Adequate, capped by Circular Imports Maturity 65 Adequate Production Readiness 40 Weak, capped by Dependency Hygiene, Dependency Hygiene and Outbound HTTP resilience Security and Compliance 59 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Accessibility 41 Weak, capped by Keyboard semantics Performance 73 Strong

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.
Production Readiness 40 · counts for 46%Accessibility 41 · counts for 25%Code Health 48 · counts for 14%Security and Compliance 59 · counts for 8%Architecture 65 · counts for 4%Maturity 65 · counts for 2%Performance 73 · counts for 1%

If Production Readiness rose from 40 to 70, the lowest score rated Strong, the score would rise from 45 to about 49.

Code composition: what the lines of code are
Product code 81%Tests 19%
New since the last survey: 212 findings

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

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

Fixed since the last survey: 1133 findings

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

  • Secret Scanning · Leaked secret: hardcoded-credential apps/ui-tars/forge.config.ts
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Code Duplication · Duplicated block with local edits (53 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/chat.tsx
  • Code Duplication · Duplicated block with local edits (53 matched lines × 2 locations) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DeliverableRenderer.tsx
  • Code Duplication · Duplicated block with local edits (51 matched lines × 2 locations) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/MessageHandler.ts
  • Code Duplication · Duplicated block with local edits (49 matched lines × 2 locations) multimodal/gui-agent/operator-adb/src/AdbOperator.ts
  • Code Duplication · Duplicated block with local edits (49 matched lines × 2 locations) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/SystemHandler.ts
  • Code Duplication · Duplicated block (46 lines × 2 locations) multimodal/tarko/agent-server-next/src/server.ts
  • Code Duplication · Duplicated block with local edits (46 matched lines × 2 locations) packages/agent-infra/browser-use/src/agent/agents/planner.ts
  • Code Duplication · Duplicated block (45 lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/preset.tsx
  • Code Duplication · Duplicated block (45 lines × 2 locations) apps/ui-tars/src/renderer/src/components/ui/alert-dialog.tsx
  • Code Duplication · Duplicated block (45 lines × 2 locations) multimodal/tarko/agent-server-next/src/controllers/queries.ts
  • Code Duplication · Duplicated block with local edits (45 matched lines × 2 locations) packages/agent-infra/mcp-client/src/index.ts
  • Code Duplication · Duplicated block with local edits (44 matched lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/sqlite/SessionDAO.ts
  • Code Duplication · Duplicated block with local edits (42 matched lines × 2 locations) multimodal/tarko/agent-server-next/src/utils/agent-resolver.ts
  • Code Duplication · Duplicated block (41 lines × 2 locations) apps/ui-tars/src/renderer/src/components/ui/avatar.tsx
  • Code Duplication · Duplicated block (40 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (40 lines × 2 locations) packages/agent-infra/mcp-servers/commands/rslib.config.ts
  • Code Duplication · Duplicated block (39 lines × 2 locations) multimodal/gui-agent/operator-aio/src/AIOBrowser.ts
  • Code Duplication · Duplicated block (39 lines × 2 locations) packages/agent-infra/mcp-servers/browser/src/server.ts
  • Code Duplication · Duplicated block (39 lines × 2 locations) packages/agent-infra/mcp-servers/browser/src/tools/navigate.ts
  • Code Duplication · Duplicated block (38 lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/localBrowser.tsx
  • Code Duplication · Duplicated block (38 lines × 2 locations) multimodal/gui-agent/shared/src/types/archived.ts
  • Code Duplication · Duplicated block (38 lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/mongodb/MongoDBSchemas.ts
  • Code Duplication · Duplicated block (37 lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/mongodb/MongoDAOFactory.ts
  • Code Duplication · Duplicated block (37 lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/mongodb/MongoDAOFactory.ts
  • Code Duplication · Duplicated block with local edits (36 matched lines × 2 locations) apps/ui-tars/src/renderer/src/pages/local/index.tsx
  • Code Duplication · Duplicated block (35 lines × 2 locations) multimodal/tarko/agent-cli/src/config/builder.ts
  • Code Duplication · Duplicated block (34 lines × 2 locations) multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts
  • Code Duplication · Duplicated block (34 lines × 2 locations) multimodal/omni-tars/core/src/utils/streamingParser/extractors.ts
  • Code Duplication · Duplicated block (33 lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/general.tsx
  • Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/local.tsx
  • Code Duplication · Duplicated block (33 lines × 2 locations) multimodal/tarko/agent-server/src/api/controllers/oneshot.ts
Rebuild cost: about €150,000 · Estimate
Cost to rebuild€49,000 to €250,000, for 818 to 2,596 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 45. 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.
SizeLarge: 135,777 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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 87 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (87).
Raises the score by about 4 points · Medium effort · Dependency Hygiene
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 3 points · Medium effort · Dependency Hygiene
3
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 3 points · Medium effort · Keyboard semantics

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 €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Production Readiness, at 40 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 87 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort, because it clears the 87 Dependency Hygiene 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 5.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 6% to 15% on every change. The history of the code shows how much it changes: about 3,373 lines over the last 90 days, which is about 13,679 lines a year. At that pace, the extra work comes to an estimated 2.2 to 13.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch @agent-infra/browser browser @agent-infra/logger logger @agent-infra/browser->@agent-infra/logger @agent-infra/shared shared @agent-infra/browser->@agent-infra/shared @agent-infra/browser-search browser-search @agent-infra/browser-search->@agent-infra/browser @agent-infra/browser-search->@agent-infra/logger @agent-infra/browser-search->@agent-infra/shared @agent-infra/search search @agent-infra/search->@agent-infra/browser-search @agent-infra/search->@agent-infra/logger @agent-infra/search->@agent-infra/shared @agent-tars/core core @tarko/mcp-agent mcp-agent @agent-tars/core->@tarko/mcp-agent @tarko/shared-utils shared-utils @agent-tars/core->@tarko/shared-utils @gui-agent/agent-sdk agent-sdk @gui-agent/shared shared @gui-agent/agent-sdk->@gui-agent/shared @tarko/agent agent @gui-agent/agent-sdk->@tarko/agent @tarko/agent-cli agent-cli @gui-agent/agent-sdk->@tarko/agent-cli @tarko/agent-interface agent-interface @gui-agent/agent-sdk->@tarko/agent-interface @gui-agent/shared->@tarko/agent @gui-agent/shared->@tarko/agent-interface @omni-tars/agent agent @omni-tars/core core @omni-tars/agent->@omni-tars/core @omni-tars/gui-agent gui-agent @omni-tars/agent->@omni-tars/gui-agent @omni-tars/agent->@tarko/agent @omni-tars/core->@tarko/agent @omni-tars/core->@tarko/agent-interface @omni-tars/gui-agent->@gui-agent/shared @omni-tars/gui-agent->@omni-tars/core @omni-tars/gui-agent->@tarko/agent @omni-tars/gui-agent->@tarko/agent-interface @omni-tars/gui-agent->@tarko/shared-utils @tarko/agent->@tarko/agent-interface @tarko/agent->@tarko/shared-utils @tarko/agent-cli->@agent-tars/core @tarko/agent-cli->@omni-tars/agent @tarko/agent-cli->@tarko/agent @tarko/agent-ui-builder agent-ui-builder @tarko/agent-cli->@tarko/agent-ui-builder @tarko/agent-cli->@tarko/mcp-agent @tarko/agent-cli->@tarko/shared-utils @tarko/interface interface @tarko/agent-ui-builder->@tarko/interface @tarko/interface->@tarko/agent-interface @tarko/mcp-agent->@tarko/agent @tarko/mcp-agent->@tarko/shared-utils @tarko/shared-utils->@tarko/agent-interface @ui-tars/sdk sdk @ui-tars/shared shared @ui-tars/sdk->@ui-tars/shared __more__ +52 more projects

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.

722 modules, with 900 dependencies between them. 4 loops run through 14 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 682 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 apps.ui-tars.src.main.store.types2 multimodal.agent-tars.interface.src.core3 multimodal.gui-agent.shared.src.types.actions4 multimodal.gui-agent.shared.src.types.agents5 multimodal.tarko.agent-interface.src.tool6 multimodal.tarko.agent-ui.src.standalone.workspace.types7 multimodal.tarko.agio.src8 multimodal.tarko.interface.src.web-ui-implementation9 multimodal.tarko.llm-client.src.chat10 multimodal.tarko.llm-client.src.handlers.base11 multimodal.tarko.model-provider.src.types12 multimodal.websites.docs.src.components13 packages.agent-infra.browser-use.src.browser.page14 packages.agent-infra.logger.src.types15 multimodal.tarko.agent-interface.src.agent-instance16 multimodal.tarko.agent-interface.src.tool-call-engine17 multimodal.tarko.agent-ui.src.common.state.actions.eventProcessors.types18 multimodal.tarko.agent-ui.src.standalone.workspace.types.panelContent19 multimodal.tarko.interface.src.server20 packages.agent-infra.browser.src.types21 packages.agent-infra.logger.src.console-logger22 packages.ui-tars.sdk.src.types23 multimodal.gui-agent.operator-aio.src.AIOHybridOperator24 multimodal.gui-agent.operator-browser.src.browser-operator25 multimodal.tarko.agent-interface.src.agent-run-options26 multimodal.tarko.agent-server-next.src.dao.interfaces.IDAOFactory27 packages.agent-infra.search.browser-search.src.types28 multimodal.tarko.agent-interface.src.agent-event-stream29 multimodal.agent-tars.core.src.agent-tars30 multimodal.agent-tars.core.src.environments.local.browser.browser-gui-agent31 multimodal.tarko.agent-interface.src.agent32 multimodal.tarko.agent-interface.src.agent-options33 multimodal.agent-tars.core.src.environments.local34 multimodal.tarko.agent-server-next.src.services.session.AgentSession35 multimodal.tarko.agent.src.agent.runner.llm-processor36 packages.agent-infra.browser-use.src.agent.types37 multimodal.tarko.agent-server-next.src.types38 multimodal.tarko.agent.src.agent.agent-runner39 multimodal.tarko.agent-server-next.src.server40 multimodal.tarko.agent.src.agent.agent
1 apps.ui-tars.src.main.store.types
2 multimodal.agent-tars.interface.src.core
3 multimodal.gui-agent.shared.src.types.actions
4 multimodal.gui-agent.shared.src.types.agents
5 multimodal.tarko.agent-interface.src.tool
6 multimodal.tarko.agent-ui.src.standalone.workspace.types
7 multimodal.tarko.agio.src
8 multimodal.tarko.interface.src.web-ui-implementation
9 multimodal.tarko.llm-client.src.chat
10 multimodal.tarko.llm-client.src.handlers.base
11 multimodal.tarko.model-provider.src.types
12 multimodal.websites.docs.src.components
13 packages.agent-infra.browser-use.src.browser.page
14 packages.agent-infra.logger.src.types
15 multimodal.tarko.agent-interface.src.agent-instance2
16 multimodal.tarko.agent-interface.src.tool-call-engine1
17 multimodal.tarko.agent-ui.src.common.state.actions.eventProcessors.types2
18 multimodal.tarko.agent-ui.src.standalone.workspace.types.panelContent1
19 multimodal.tarko.interface.src.server11
20 packages.agent-infra.browser.src.types1
21 packages.agent-infra.logger.src.console-logger2
22 packages.ui-tars.sdk.src.types11
23 multimodal.gui-agent.operator-aio.src.AIOHybridOperator13111
24 multimodal.gui-agent.operator-browser.src.browser-operator131111
25 multimodal.tarko.agent-interface.src.agent-run-options1
26 multimodal.tarko.agent-server-next.src.dao.interfaces.IDAOFactory11
27 packages.agent-infra.search.browser-search.src.types2112
28 multimodal.tarko.agent-interface.src.agent-event-stream111
29 multimodal.agent-tars.core.src.agent-tars11311
30 multimodal.agent-tars.core.src.environments.local.browser.browser-gui-agent11212
31 multimodal.tarko.agent-interface.src.agent1812
32 multimodal.tarko.agent-interface.src.agent-options2111
33 multimodal.agent-tars.core.src.environments.local1111
34 multimodal.tarko.agent-server-next.src.services.session.AgentSession1112
35 multimodal.tarko.agent.src.agent.runner.llm-processor22111
36 packages.agent-infra.browser-use.src.agent.types1
37 multimodal.tarko.agent-server-next.src.types512
38 multimodal.tarko.agent.src.agent.agent-runner13321212
39 multimodal.tarko.agent-server-next.src.server312
40 multimodal.tarko.agent.src.agent.agent112341111
Uses a module listed above itPart of a loopThe module itself
1 apps.ui-tars.src.main.store.types2 multimodal.agent-tars.interface.src.core3 multimodal.gui-agent.shared.src.types.actions4 multimodal.gui-agent.shared.src.types.agents5 multimodal.tarko.agent-interface.src.tool6 multimodal.tarko.agent-ui.src.standalone.workspace.types7 multimodal.tarko.agio.src8 multimodal.tarko.interface.src.web-ui-implementation9 multimodal.tarko.llm-client.src.chat10 multimodal.tarko.llm-client.src.handlers.base11 multimodal.tarko.model-provider.src.types12 multimodal.websites.docs.src.components13 packages.agent-infra.browser-use.src.browser.page14 packages.agent-infra.logger.src.types15 multimodal.tarko.agent-interface.src.agent-instance16 multimodal.tarko.agent-interface.src.tool-call-engine17 multimodal.tarko.agent-ui.src.common.state.actions.eventProcessors.types18 multimodal.tarko.agent-ui.src.standalone.workspace.types.panelContent19 multimodal.tarko.interface.src.server20 packages.agent-infra.browser.src.types21 packages.agent-infra.logger.src.console-logger22 packages.ui-tars.sdk.src.types23 multimodal.gui-agent.operator-aio.src.AIOHybridOperator24 multimodal.gui-agent.operator-browser.src.browser-operator25 multimodal.tarko.agent-interface.src.agent-run-options26 multimodal.tarko.agent-server-next.src.dao.interfaces.IDAOFactory27 packages.agent-infra.search.browser-search.src.types28 multimodal.tarko.agent-interface.src.agent-event-stream29 multimodal.agent-tars.core.src.agent-tars30 multimodal.agent-tars.core.src.environments.local.browser.browser-gui-agent31 multimodal.tarko.agent-interface.src.agent32 multimodal.tarko.agent-interface.src.agent-options33 multimodal.agent-tars.core.src.environments.local34 multimodal.tarko.agent-server-next.src.services.session.AgentSession35 multimodal.tarko.agent.src.agent.runner.llm-processor36 packages.agent-infra.browser-use.src.agent.types37 multimodal.tarko.agent-server-next.src.types38 multimodal.tarko.agent.src.agent.agent-runner39 multimodal.tarko.agent-server-next.src.server40 multimodal.tarko.agent.src.agent.agentapps.ui-tars.src.main.store.types1multimodal.agent-tars.interface.src.core2multimodal.gui-agent.shared.src.types.actions3multimodal.gui-agent.shared.src.types.agents4multimodal.tarko.agent-interface.src.tool5multimodal.tarko.agent-ui.src.standalone.workspace.types6multimodal.tarko.agio.src7multimodal.tarko.interface.src.web-ui-implementation8multimodal.tarko.llm-client.src.chat9multimodal.tarko.llm-client.src.handlers.base10multimodal.tarko.model-provider.src.types11multimodal.websites.docs.src.components12packages.agent-infra.browser-use.src.browser.page13packages.agent-infra.logger.src.types14multimodal.tarko.agent-interface.src.agent-instance15multimodal.tarko.agent-interface.src.tool-call-engine16multimodal.tarko.agent-ui.src.common.state.actions.eventProcessors.types17multimodal.tarko.agent-ui.src.standalone.workspace.types.panelContent18multimodal.tarko.interface.src.server19packages.agent-infra.browser.src.types20packages.agent-infra.logger.src.console-logger21packages.ui-tars.sdk.src.types22multimodal.gui-agent.operator-aio.src.AIOHybridOperator23multimodal.gui-agent.operator-browser.src.browser-operator24multimodal.tarko.agent-interface.src.agent-run-options25multimodal.tarko.agent-server-next.src.dao.interfaces.IDAOFactory26packages.agent-infra.search.browser-search.src.types27multimodal.tarko.agent-interface.src.agent-event-stream28multimodal.agent-tars.core.src.agent-tars29multimodal.agent-tars.core.src.environments.local.browser.browser-gui-agent30multimodal.tarko.agent-interface.src.agent31multimodal.tarko.agent-interface.src.agent-options32multimodal.agent-tars.core.src.environments.local33multimodal.tarko.agent-server-next.src.services.session.AgentSession34multimodal.tarko.agent.src.agent.runner.llm-processor35packages.agent-infra.browser-use.src.agent.types36multimodal.tarko.agent-server-next.src.types37multimodal.tarko.agent.src.agent.agent-runner38multimodal.tarko.agent-server-next.src.server39multimodal.tarko.agent.src.agent.agent4021211112111311113111111121121111131111212181221111111111222111151213321212312112341111+682 more modules (most-connected shown)

At a glance — Code Health · 48% · Weak · gated by D2, R7 ·

The Good
D17 · TypeScript Explicit Debt 9.9 GD1 · Repo Unfinished & placeholder code 10.0 R1 · React / TS Type Safety 9.9 R10 · React / TS Code Duplication 8.5 R3 · React / TS Large Files 8.1 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 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.1 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 8.6
The Bad
D3 · TypeScript God Classes 6.3 IC1 · Repo Incompleteness & stubs 6.4 R2 · React / TS Cyclomatic Complexity 6.0 X2 · Repo Cancellation propagation 6.2 X23 · Repo Unguarded diagnostic materialisation 5.5
The Ugly
D1 · TypeScript Cyclomatic Complexity 4.5 D2 · TypeScript Cognitive Complexity 2.0 R7 · React / TS Dead Code 0.5

At a glance — Architecture · 65% · Adequate · gated by R9 ·

The Good
D5 · TypeScript Coupling 8.9 D6 · TypeScript Cohesion (LCOM4) 9.7 D23 · TypeScript Boundary Type-Coupling 10.0 D26 · TypeScript Project Cohesion 8.9 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 9.3 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.8 R11 · React / TS Import Boundaries 8.9
The Ugly
R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 65% · Adequate ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 9.9 D16 · TypeScript Bus Factor 8.0 D19 · TypeScript Documentation Quality 10.0 M2 · Repo Architecture documentation 7.0 M3 · Repo Folder & project structure 10.0
The Bad
D34 · TypeScript Knowledge Freshness 5.7 M1 · Repo Documentation (README) 6.8
The Ugly
D20 · TypeScript ADR Quality 0.0 M4 · Repo Documentation accuracy 4.4

At a glance — Readiness · 40% · Weak · gated by D12, R8, P7 ·

The Good
D9 · TypeScript Test Distribution 9.9 D10 · TypeScript Test Quality 9.9 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 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R5 · React / TS Dependency Freshness 8.2 R6 · React / TS Tooling 10.0
The Bad
P3 · Repo Security & performance tooling 6.0 R4 · React / TS Test Coverage 5.2
The Ugly
D12 · TypeScript Dependency Hygiene 3.0 P7 · Repo Outbound HTTP resilience 3.0 R8 · React / TS Dependency Hygiene 0.0

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

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

At a glance — Accessibility · 41% · Weak · gated by AC4 ·

The Good
AC5 · Repo ARIA correctness 10.0
The Bad
AC2 · Repo Forms & labels 5.2 AC3 · Repo Page structure 6.4
The Ugly
AC1 · Repo Text alternatives 4.9 AC4 · Repo Keyboard semantics 1.5 AC6 · Repo Visual & motion safety 4.6 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 73% · Strong ·

The Good
PF1 · Repo Benchmark discipline 9.0
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
A03:2025 — Software Supply Chain Failures233High / Critical
A05:2025 — Injection83High / Critical
A02:2025 — Security Misconfiguration10High / Critical
A07:2025 — Authentication Failures3High / Critical

Roadmap

Begin by resolving the 87 deprecated dependencies in REDACTED and cleaning up unused or misclassified packages to ensure a secure and efficient dependency tree. Next, eliminate the significant volume of dead code and unused exports to reduce maintenance overhead and rebuild times, while simultaneously making custom controls fully keyboard-accessible to improve user experience. Finally, implement robust resilience for all outbound HTTP calls by adding timeouts, retries, and circuit breakers to prevent failures from impacting system stability.

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

Do thisHelpsEffortDimension
Resolve the 87 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (87).+4.4 ptsMediumDependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.9 ptsMediumDependency Hygiene
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.6 ptsMediumKeyboard semantics
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+1.8 ptsMediumDead Code
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.+1.7 ptsMediumOutbound HTTP resilience
Resolve the 11 One package at two majors across the workspace finding(s) in Dependency Hygiene.+1.6 ptsMediumDependency Hygiene
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.+1.4 ptsMediumA11y enforcement
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+1.1 ptsMediumVisual & motion safety

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopSecrets (history): High secret: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopSecrets (history): High secret: REDACTED
REDACTED0.7SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED1.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.4SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.6SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 282

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

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

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

Could not be resolved — 10

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. 85 of 85 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — 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 — 85 dimensions across the health lenses
D1D2D3D5D6D9D10D12D13D14D15D16D17D19D20D23D26D28D29D30D31D34D35D36D37D43AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX6C2GD1IC1M1M2M3M4P1P10P2P3P4P6P7PF1PF3R1R10R11R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 1780 of 1937 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 measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a1794d-0cf2-74b0-bd1b-5ce2e27bc9df.

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.

  • D8 Code Coverage — 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. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for apps/ui-tars/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403  GET https://codeload.github.com/electron/node-gyp/tar.gz/06b29aafb7708acef8b3669835c8a7857ebc92d2: Forbidden - 403), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`codecov/codecov-action`) shows coverage is measured in your own CI. Commit the lcov/Cobertura report it produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D11 Test Reliability — 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. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for apps/ui-tars/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403  GET https://codeload.github.com/electron/node-gyp/tar.gz/06b29aafb7708acef8b3669835c8a7857ebc92d2: Forbidden - 403), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in apps/ui-tars/ was NOT MEASURED: the dependency install for apps/ui-tars/ could not reach codeload.github.com, which the analyzer sandbox's egress allowlist does not carry (ERR_PNPM_FETCH_403  GET https://codeload.github.com/electron/node-gyp/tar.gz/06b29aafb7708acef8b3669835c8a7857ebc92d2: Forbidden - 403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in infra/pdk/ was NOT MEASURED: the dependency install for infra/pdk/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/ was NOT MEASURED: the dependency install for multimodal/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/agent-tars/cli/ was NOT MEASURED: the dependency install for multimodal/agent-tars/cli/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/agent-tars/core/ was NOT MEASURED: the dependency install for multimodal/agent-tars/core/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/action-parser/ was NOT MEASURED: the dependency install for multimodal/gui-agent/action-parser/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/agent-sdk/ was NOT MEASURED: the dependency install for multimodal/gui-agent/agent-sdk/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/cli/ was NOT MEASURED: the dependency install for multimodal/gui-agent/cli/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/operator-adb/ was NOT MEASURED: the dependency install for multimodal/gui-agent/operator-adb/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/operator-aio/ was NOT MEASURED: the dependency install for multimodal/gui-agent/operator-aio/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in multimodal/gui-agent/operator-browser/ was NOT MEASURED: the dependency install for multimodal/gui-agent/operator-browser/ failed in the analyzer sandbox (ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D19 Documentation 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — 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 kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — 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.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/ui-tars/src/main/store/create.ts`, `infra/pdk/src/types.ts`, `multimodal/agent-tars/core/src/index.ts`, `multimodal/tarko/agent-interface/src/agent-instance.ts`, `multimodal/tarko/llm-client/src/handlers/gemini.ts`, … (+4 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.
  • D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
  • AC6 Visual & motion safety — 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
  • 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.
  • M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P2 Observability — 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. 347 further occurrence(s) are not listed individually; the score already reflects all 387.
  • PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
  • 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. 380 further occurrence(s) are not listed individually; the score already reflects all 420.
  • R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
  • R4 Test Coverage — 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. 382 further occurrence(s) are not listed individually; the score already reflects all 422.
  • R7 Dead Code — 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. 309 further occurrence(s) are not listed individually; the score already reflects all 349.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 40 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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.
  • 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality 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.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity4.5 / 10Weak✓ 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 4.5 / 10 · rule-coverage 100% · ceiling Prevented

140 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ChatInput.ChatInput at 94. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being BrowserOperator.singleActionExecutor at 20 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: multimodal/gui-agent/operator-browser/src/browser-operator.ts (BrowserOperator.singleActionExecutor at 20). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

buildDomTree.buildDomTree::isInteractiveElement (cyclomatic 37) · ×4packages/agent-infra/browser-use/assets/buildDomTree.js:293
utils.convertToAgentUIAction (cyclomatic 26) · ×2multimodal/gui-agent/agent-sdk/src/utils.ts:16
config-sanitizer.sanitizeAgentOptions (cyclomatic 23) · ×2multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:10
ChatInput.ChatInput (cyclomatic 94)multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46
AgentOptionsSelector.AgentOptionsSelector (cyclomatic 82)multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:158

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with ChatInput.ChatInput (cyclomatic 94), AgentOptionsSelector.AgentOptionsSelector (cyclomatic 82), player.Player (cyclomatic 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 4.5 to about 5.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  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 Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

188 method(s) exceeded the cognitive complexity threshold of 15; the worst was extractCode.extractCodeEnv at 156.

buildDomTree.buildDomTree::buildDomTree (cognitive 42) · ×4packages/agent-infra/browser-use/assets/buildDomTree.js:647
config-sanitizer.sanitizeAgentOptions (cognitive 24) · ×2multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:10
ShareService.findImageReferences (cognitive 17) · ×2multimodal/tarko/agent-server-next/src/services/ShareService.ts:281
SlugGenerator.manualNormalization (cognitive 16) · ×2multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:115
extractCode.extractCodeEnv (cognitive 156)multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14

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

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with extractCode.extractCodeEnv (cognitive 156), extractToolCallT5.extractToolCallT5 (cognitive 150). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 2.1 to about 2.7/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes6.3 / 10Adequate✓ 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 6.3 / 10 · rule-coverage 100% · ceiling Prevented

120 god class(es) detected.

FunctionTooLong: buildDomTree.buildDomTree · ×81packages/agent-infra/browser-use/assets/buildDomTree.js:14
MethodTooLong: GUIAgent.run · ×18packages/ui-tars/sdk/src/GUIAgent.ts:66
ClassTooLong: UIHelper · ×10multimodal/gui-agent/operator-browser/src/ui-helper.ts:13
FileTooLong: src/ui-helper.ts · ×10multimodal/gui-agent/operator-browser/src/ui-helper.ts
TooManyMethods: Pagepackages/agent-infra/browser-use/src/browser/page.ts:71

What to do

  1. Resolve the 81 FunctionTooLong finding(s) in God Classes — start with index.tsx (11), REDACTED (2), server.ts (2). — One of this dimension's main actionable groups (81 warning-level).
  2. Resolve the 18 MethodTooLong finding(s) in God Classes — start with ui-helper.ts (4), REDACTED (2), ToolHandler.ts (2). — One of this dimension's main actionable groups (18 warning-level).
  3. Resolve the 10 ClassTooLong finding(s) in God Classes — start with ui-helper.ts (2), browser-operator.ts (2), page.ts. — One of this dimension's main actionable groups (10 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.

D5 · Coupling8.9 / 10Strong✓ 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 8.9 / 10 · rule-coverage 100% · ceiling Prevented

72 production modules (npm), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 69 of the 72 (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).

Off the main sequence: @tarko/config-loader · ×7
Unstable project @agent-infra/search
Unstable project @omni-tars/gui-agent
Off the main sequence: @tarko/shared-media-utils · ×4

What to do

  1. Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 1 Unstable project @agent-infra/search finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project @omni-tars/gui-agent finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. 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)9.7 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

4 of 142 classes have LCOM4 above 3.

Low cohesion: ApiService (LCOM4 11) · ×4multimodal/tarko/agent-ui/src/common/services/apiService.ts:51

What to do

  1. Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with apiService.ts, proxyClient.ts, agent-generate-snapshot-hook.ts. — One of this dimension's main actionable groups (4 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

1283 test methods: 1265 unit, 9 integration, 0 BDD, 9 e2e. The JavaScript/TypeScript suite contributes 1283 `it`/`test` case(s) across 131 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.9 / 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

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

Skipped test: should handle fish shell command · ×8packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:35
Mock-dominated test: should include the running session ID in the response · ×7multimodal/tarko/agent-server/tests/middleware.test.ts:68

What to do

  1. Resolve the 8 Skipped test finding(s) in Test Quality — start with exec-utils.test.ts (5), tabs.test.ts (2), repomix.test.ts. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 Mock-dominated test finding(s) in Test Quality — start with middleware.test.ts (4), server-access-boundary.test.ts (2), agent-base.test.ts. — One of this dimension's main actionable groups (7 recommendation-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.

D12 · Dependency Hygiene3.0 / 10Weak✓ Tool-verified

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

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

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

120 outdated direct production npm dependency(ies) of 159 graded, 11 pinning defect(s), across 80 REDACTED (76 of them the product) and 6 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 8 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: eslint · ×17REDACTED:111
One package at two majors across the workspace: chalk · ×11
Deprecated: @azure/openai · ×87REDACTED:1865
Outdated (npm): @browserbasehq/stagehand · ×12packages/ui-tars/operators/browserbase/package.json:39
Outdated (npm): @agent-infra/browser · ×108

What to do

  1. Resolve the 87 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (87). — One of this dimension's main actionable groups (87 recommendation-level).
  2. Resolve the 17 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (17). — One of this dimension's main actionable groups (17 warning-level).
  3. Resolve the 11 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (11 warning-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 159 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 159 production dependency(ies) this repository's committed lockfile resolves, across 76 product REDACTED manifest(s). Its 687 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 9 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0 / MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 1 serious finding✓ 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.9 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: REDACTED (2×18=36)

Hotspot: REDACTEDREDACTED:26

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor8.0 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

99 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is multimodal/tarko/agent/src/agent/agent.ts. Counted over 501 of the 1153 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)

What to do

  1. Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt9.9 / 10Stronggated by 85 serious findings✓ Tool-verified

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

85 deducted task-comment markers across 134602 LoC (0.1/KLoC) → score 9.9. 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.

FixmeComment · ×45packages/agent-infra/search/browser-search/src/browser-search.ts:65
TodoComment · ×39packages/ui-tars/visualizer/src/component/detail-panel.tsx:120
HackCommentapps/ui-tars/src/main/utils/updateApp.ts:28

What to do

  1. Resolve the 45 FixmeComment finding(s) in Explicit Debt — start with agent-snapshot.ts (4), useScreenshots.ts (3), REDACTED (3). — One of this dimension's main actionable groups (45 warning-level).
  2. Resolve the 39 TodoComment finding(s) in Explicit Debt — start with operators.ts (5), exec-utils.test.ts (4), server.ts (3). — One of this dimension's main actionable groups (39 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with updateApp.ts. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 227 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.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.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D26 · Project Cohesion8.9 / 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 8.9 / 10 · rule-coverage 100% · ceiling Documented

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

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

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

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

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

83 finding(s): 0 critical, 45 high, 35 medium, 3 low. 1 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 12 file(s) — `apps/ui-tars/src/main/store/create.ts` (line 25), `examples/operator-browserbase/tailwind.config.ts` (line 23), `infra/pdk/src/types.ts` (line 370), `multimodal/agent-tars/core/src/index.ts` (line 14), `multimodal/benchmark/content-extraction/result/github.com_OSU-NLP-Group_GUI-Agents-Paper-List/Optimized/result.md`, … (+7 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
  2. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  3. Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).

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

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

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

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

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

226 finding(s): 24 critical, 119 high, 65 medium, 18 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 117 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (111), REDACTED (6). — One of this dimension's main actionable groups (117 issue-level).
  2. Resolve the 24 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (22), REDACTED (2). — One of this dimension's main actionable groups (24 issue-level).
  3. Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

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

D31 · IaC & Container Security8.4 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D34 · Knowledge Freshness5.7 / 10Adequate✓ 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 5.7 / 10 · rule-coverage 100% · ceiling Documented

210 of 501 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/agent-infra/browser-use/src/browser/page.ts. Counted over 501 of the 1153 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×12packages/agent-infra/browser-use/src/browser/page.ts:1
Orphaned file · ×198packages/ui-tars/visualizer/src/component/timeline.tsx:1
Further orphaned files (smaller)

What to do

  1. Resolve the 198 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (11), index.tsx (8), types.ts (7). — One of this dimension's main actionable groups (198 recommendation-level).
  2. Resolve the 12 Orphaned knowledge finding(s) in Knowledge Freshness — start with prompts.ts (2), page.ts, buildDomTree.js. — One of this dimension's main actionable groups (12 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ 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: REDACTED↔apiService.ts 64%; index.tsx↔REDACTED 60%; builder.ts↔options.ts 50%

Change coupling: REDACTED ↔ apiService.ts · ×4REDACTED:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with index.tsx (2), REDACTED, builder.ts. — One of this dimension's main actionable groups (4 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

+ 2 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 — start with REDACTED. — 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 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.9 / 10Weak✓ Tool-verified

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.

  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×2) — apps/ui-tars/src/renderer/src/components/ScreenRecorder/index.tsx:44, apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448
  • Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). (×3) — multimodal/websites/docs/src/components/IntroAnimation.tsx:250, multimodal/websites/docs/src/components/IntroAnimation.tsx:260, multimodal/websites/main/src/render/components/Home/VideoModal.tsx:28
  • Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — multimodal/websites/docs/src/components/VideoPanel.tsx:55
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — packages/ui-tars/visualizer/src/component/global-hover-preview.tsx:60

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified

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

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

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

  • This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — apps/ui-tars/src/renderer/src/components/ChatInput/index.tsx:217
  • This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — apps/ui-tars/src/renderer/src/components/ImageGallery/index.tsx:193, multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx:258
  • This <canvas> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×4) — multimodal/tarko/agent-ui/src/standalone/app/Layout/MobileBottomSheet.tsx:73, multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:125, multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx:77, …
  • This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:117, multimodal/tarko/ui/src/components/basic/Dropdown.tsx:48
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:438
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:111, multimodal/tarko/agent-ui/src/standalone/replay/ReplayControlPanel.tsx:50, multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:267, …
  • This <video> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×3) — multimodal/websites/docs/src/components/IntroAnimation.tsx:250, multimodal/websites/docs/src/components/IntroAnimation.tsx:260, multimodal/websites/docs/src/components/VideoPanel.tsx:55

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure6.4 / 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.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×2) — apps/ui-tars/src/renderer/index.html:2, multimodal/websites/main/public/index.html:2
  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — apps/ui-tars/src/renderer/src/pages/remote/cast/vnc.tsx:70
  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — multimodal/websites/docs/src/components/Showcase/components/ShowcaseDetail.tsx:220, multimodal/websites/main/src/render/pages/ShowcaseDetail.tsx:227
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — multimodal/websites/main/public/index.html:2
  • An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — multimodal/websites/main/src/render/pages/Docs.tsx:75

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.
AC4 · Keyboard semantics1.5 / 10Critical✓ Tool-verified

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

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

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

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — apps/ui-tars/src/renderer/src/components/CountDown/index.tsx:61
  • A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×18) — multimodal/tarko/agent-ui/src/standalone/chat/ImagePreview.tsx:48, multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ReportFileEntry.tsx:30, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:117, …
  • This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. (×5) — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:120, REDACTED:589, multimodal/tarko/ui/src/components/basic/Tooltip.tsx:147, …
  • This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler. — multimodal/websites/docs/src/components/ActionCard.tsx:169
  • This <svg> carries its own click handler, but it sits inside a <a> that performs a different action. A keyboard user reaches the <a> and activating it runs the <a>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <a> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <a> and make it a sibling <button>, so each action has its own control. — multimodal/websites/main/src/render/components/Markdown/HeaderAnchor.tsx:40

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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 safety4.6 / 10Weak✓ Tool-verified

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

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

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

  • `.loading-spinner` moves (`animation: spin 1s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/ui-tars/src/renderer/index.html:63
  • <canvas> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448
  • <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. (×8) — apps/ui-tars/src/renderer/src/pages/remote/cast/status.tsx:87, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:570, multimodal/tarko/agent-ui/src/standalone/chat/components/OfflineBanner.tsx:55, …
  • <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:111
  • This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade. (×4) — multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx:108, multimodal/tarko/agent-ui/src/standalone/sidebar/ToolBar.tsx:82, multimodal/tarko/agent-ui/src/standalone/workspace/components/FullscreenModal.tsx:76, …
  • <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:267, multimodal/tarko/agent-ui/src/standalone/sidebar/SessionSearch.tsx:62
  • <div> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx:232
  • <div> moves — its inline style sets `animation: spin 1s linear infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — REDACTED:38
  • <div> moves — its inline style sets `animation: pulse 4s ease-in-out infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — multimodal/websites/main/src/render/components/Home/SectionDivider.tsx:8
  • `.terminal-scan-line` moves (`animation: terminal-scan 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — multimodal/websites/docs/src/pages/HomePage/components.css:200, multimodal/websites/docs/src/pages/HomePage/components.css:218
  • `.aurora-beam` moves (`animation: aurora-rise 20s ease-in-out infinite alternate, aurora-flow 25s ease-in-out infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:17
  • `.cyber-grid-bg` moves (`animation: grid-scroll 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:63
  • `.animated-grid` moves (`animation: grid-animation 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:74
  • `.scan-line::before` moves (`animation: scan-line 3s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:85
  • `.glitch-micro` moves (`animation: glitch-micro 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:134
  • `.glitch-text` moves (`animation: minor-glitch 10s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:144
  • `.glitch-intense` moves (`animation: major-glitch 0.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:148
  • `.hologram::before` moves (`animation: hologram-scan 3s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:173
  • `.data-stream` moves (`animation: data-flow 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:238
  • `.particle` moves (`animation: particle-float 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:248
  • `.cyber-particle` moves (`animation: particle-float 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:258
  • `.custom-cursor` moves (`transition: transform 0.05s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:277
  • `.cursor-pointer` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/effects.css:283
  • `.title-glitch` moves (`animation: title-glitch 4s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/pages/HomePage/typography.css:26
  • `.blog-card` moves (`transition: transform 0.2s ease, box-shadow 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/components/BlogIndex.css:50
  • `.blog-card-arrow` moves (`transition: color 0.2s ease, transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/components/BlogIndex.css:128
  • `.card-arrow` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/websites/docs/src/components/QuickStartActionCard.css:80
  • `.animate-border-flow` moves (`animation: animate-border-flow 3s ease infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — multimodal/tarko/agent-ui/src/entry.css:148

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

  • No accessibility enforcement found — 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 270 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 composition9.3 / 10Exemplary✓ Tool-verified

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

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

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

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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.8 / 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.

  • `IAgent` declares 31 required operations: `initialize`, `run`, `run`, `run`, `abort`, `status`, `dispose`, `getEventStream`, `getTools`, `getLLMClient`, `generateSummary`, `getCurrentModel`, `onLLMRequest`, `onLLMResponse`, `onLLMStreamingResponse`, `onBeforeToolCall`, `onAfterToolCall`, `onToolCallError`, `onEachAgentLoopStart`, `onEachAgentLoopEnd`, `onAgentLoopEnd`, `onProcessToolCalls`, `onBeforeLoopTermination`, `requestLoopTermination`, `isLoopTerminationRequested`, `getCurrentLoopIteration`, `getOptions`, `callLLM`, `callLLM`, `callLLM`, `onPrepareRequest`. 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. Those 31 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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. — multimodal/tarko/agent-interface/src/agent.ts:38
  • `IDAOFactory` declares 16 required operations: `initialize`, `isInitialized`, `close`, `getUserConfigDAO`, `getSessionDAO`, `getEventDAO`, `getSandboxAllocationDAO`, `healthCheck`, `createSession`, `updateSessionInfo`, `getSessionInfo`, `getAllSessions`, `getUserSessions`, `deleteSession`, `saveEvent`, `getSessionEvents`. 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. — multimodal/tarko/agent-server-next/src/dao/interfaces/IDAOFactory.ts:20
  • `AgentServer` declares 19 required operations: `getSessionPool`, `getSessionFactory`, `isMultiTenant`, `getMemoryStats`, `start`, `stop`, `isServerRunning`, `getCurrentWorkspace`, `getCurrentAgentName`, `canAcceptNewRequest`, `setRunningSession`, `clearRunningSession`, `getRunningSessionId`, `getCurrentAgentResolution`, `getCustomAgioProvider`, `getAgentConstructorWebConfig`, `getStorageInfo`, `registerHook`, `unregisterHook`. 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. — multimodal/tarko/agent-server-next/src/types.ts:79

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
C2 · Access Controls7.0 / 10Strong✓ Tool-verified

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

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

  • Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.

What to do

  • Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
GD1 · Unfinished & placeholder 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 & stubs6.4 / 10Adequate✓ Tool-verified

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

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

  • `cleanupOldLogs` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/ui-tars/src/main/logger.ts:67
  • `beforeAgentRun` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/ui-tars/src/main/utils/agent.ts:63
  • `showWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/ui-tars/src/main/window/index.ts:63
  • `hideMainWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/ui-tars/src/main/window/index.ts:70
  • `showMainWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — apps/ui-tars/src/main/window/index.ts:81
  • `updateChangelogFile` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — infra/pdk/src/commands/changelog.ts:29, infra/pdk/src/utils/ai-changelog.ts:292
  • `nextVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — infra/pdk/src/commands/next-version.ts:20
  • `restorePackageDependencies` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — infra/pdk/src/utils/dependencies.ts:132
  • `resetConfig` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — multimodal/gui-agent/cli/src/cli/start.ts:162
  • The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×3) — multimodal/omni-tars/gui-agent/src/GuiAgentPlugin.ts:161, multimodal/tarko/agent/src/utils/llm-requester.ts:83, multimodal/tarko/llm-client/src/handlers/anthropic.ts:343
  • `initializeMultiTenantServices` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — multimodal/tarko/agent-server-next/src/server.ts:365
  • `stopMemoryMonitoring` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — multimodal/tarko/agent-server-next/src/services/session/AgentSessionPool.ts:151
  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — multimodal/websites/docs/src/components/IntroAnimation.tsx:190, multimodal/websites/docs/src/components/IntroAnimation.tsx:200
  • `cancel` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/agent-infra/browser-use/src/agent/executor.ts:320
  • `resume` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/agent-infra/browser-use/src/agent/executor.ts:324, packages/agent-infra/browser-use/src/agent/types.ts:110
  • `pause` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/agent-infra/browser-use/src/agent/executor.ts:328, packages/agent-infra/browser-use/src/agent/types.ts:106
  • `stop` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/agent-infra/browser-use/src/agent/types.ts:114
  • `buildReport` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:84
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×11) — multimodal/agent-tars/core/snapshot/index.test.ts:13, multimodal/tarko/agent/tests/agent/llm-processor-thinking.test.ts:11, multimodal/tarko/context-engineer/tests/repomix.test.ts:15, …
  • A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — multimodal/tarko/llm-client/src/handlers/utils.ts:11

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.8 / 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.

  • 46 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 13 of 79 project(s) that lack one — worth up to 0.3 pts.
  • Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Grow the ADR log (currently 1) — reach 8 to raise the maturity tier; document significant decisions as they're made.
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 accuracy4.4 / 10Weak✓ Tool-verified

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.

  • CONTRIBUTING.md links to `.github/workflows/release.yml`, but `.github/workflows/release.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:139
  • docs/archive-1.0/README.md links to `./CONTRIBUTING.md`, but `docs/archive-1.0/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/archive-1.0/README.md:54
  • packages/agent-infra/search/browser-search/README.md links to `./README.zh-CN.md`, but `packages/agent-infra/search/browser-search/README.zh-CN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/agent-infra/search/browser-search/README.md:10

What to do

  • Reconcile the README with reality: CONTRIBUTING.md links to `.github/workflows/release.yml`, but `.github/workflows/release.yml` does not exist; docs/archive-1.0/README.md links to `./CONTRIBUTING.md`, but `docs/archive-1.0/CONTRIBUTING.md` does not exist; packages/agent-infra/search/browser-search/README.md links to `./README.zh-CN.md`, but `packages/agent-infra/search/browser-search/README.zh-CN.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · 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 33/43 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `multimodal/agent-tars/cli`, `multimodal/gui-agent/cli`, `multimodal/tarko/agent-ui-cli`, `packages/agent-infra/create-new-mcp`, `packages/agent-infra/create-new-mcp/template-default` and 5 more.
  • `apps/ui-tars/src/main/window/createWindow.ts` reports through `console.*` at line 87 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/window/createWindow.ts:87
  • `apps/ui-tars/src/main/utils/systemPermissions.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/utils/systemPermissions.ts:21
  • `apps/ui-tars/src/main/ipcRoutes/permission.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/ipcRoutes/permission.ts:22
  • `apps/ui-tars/src/main/ipcRoutes/setting.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/ipcRoutes/setting.ts:29
  • `apps/ui-tars/src/main/ipcRoutes/setting.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/ipcRoutes/setting.ts:53
  • `apps/ui-tars/src/main/electron-updater/GitHubProvider.ts` reports through `console.*` at line 215 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:215
  • `REDACTED` reports through `console.*` at line 342 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:342
  • `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/interactive.ts:47
  • `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/interactive.ts:49
  • `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/interactive.ts:51
  • `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/logger.ts:15
  • `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/logger.ts:16
  • `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/logger.ts:17
  • `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/logger.ts:18
  • `infra/pdk/src/utils/npm.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/npm.ts:46
  • `infra/pdk/src/utils/workspace.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/utils/workspace.ts:55
  • `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/changelog.ts:143
  • `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 144 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/changelog.ts:144
  • `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 145 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/changelog.ts:145
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:31
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:35
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:46
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:96
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:98
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 102 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:102
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 124 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:124
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 165 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:165
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 183 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:183
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 193 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:193
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 209 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:209
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 212 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:212
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 216 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:216
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 223 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:223
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 224 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:224
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 225 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:225
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 230 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:230
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 231 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:231
  • `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 233 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/dev.ts:233
  • `infra/pdk/src/commands/next-version.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — infra/pdk/src/commands/next-version.ts:29

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
P3 · Security & performance tooling6.0 / 10Adequate✓ 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.

  • `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.

What to do

  • Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
  • Enable Dependabot/Renovate or a dependency-review gate.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ 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.

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — multimodal/tarko/agent-server/src/services/ShareService.ts:359

What to do

  • Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

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.

  • `fs.unlinkSync` in `cleanupOldLogs` 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/ui-tars/src/main/logger.ts:73
  • `fs.existsSync` in `genKeyPair` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — apps/ui-tars/src/main/remote/auth.ts:114, apps/ui-tars/src/main/remote/auth.ts:117, apps/ui-tars/src/main/remote/auth.ts:135
  • `generateKeyPairSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:125
  • `fs.mkdirSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:137
  • `fs.writeFileSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:140, apps/ui-tars/src/main/remote/auth.ts:141
  • `fs.existsSync` in `getLocalPubKey` 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/ui-tars/src/main/remote/auth.ts:172
  • `fs.readFileSync` in `getLocalPubKey` 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/ui-tars/src/main/remote/auth.ts:175
  • `fs.existsSync` in `getLocalPrivKey` 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/ui-tars/src/main/remote/auth.ts:187
  • `fs.readFileSync` in `getLocalPrivKey` 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/ui-tars/src/main/remote/auth.ts:190
  • `existsSync` in `updateChangelogFile` 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) — infra/pdk/src/commands/changelog.ts:35, infra/pdk/src/utils/ai-changelog.ts:298
  • `readFileSync` in `updateChangelogFile` 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) — infra/pdk/src/commands/changelog.ts:36, infra/pdk/src/utils/ai-changelog.ts:299
  • `writeFileSync` in `updateChangelogFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — infra/pdk/src/commands/changelog.ts:46, infra/pdk/src/commands/changelog.ts:56, infra/pdk/src/utils/ai-changelog.ts:316
  • `existsSync` in `release` 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. — infra/pdk/src/commands/release.ts:183
  • `fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — multimodal/agent-tars/core/src/environments/local/browser/tools/visual.ts:45
  • `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — multimodal/agent-tars/core/src/environments/local/browser/tools/visual.ts:46
  • `fs.existsSync` in `start` 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. — multimodal/gui-agent/cli/src/cli/start.ts:53
  • `fs.readFileSync` in `start` 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. — multimodal/gui-agent/cli/src/cli/start.ts:55
  • `fs.writeFileSync` in `start` 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. — multimodal/gui-agent/cli/src/cli/start.ts:92
  • `fs.existsSync` in `resetConfig` 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. — multimodal/gui-agent/cli/src/cli/start.ts:166
  • `fs.unlinkSync` in `resetConfig` 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. — multimodal/gui-agent/cli/src/cli/start.ts:167
  • `existsSync` in `logContent` 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. — multimodal/omni-tars/core/examples/openai.ts:82
  • `mkdirSync` in `logContent` 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. — multimodal/omni-tars/core/examples/openai.ts:83
  • `existsSync` in `loadAgentConfig` 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. — multimodal/tarko/agent-cli/src/config/loader.ts:134
  • `fs.existsSync` in `initWorkspace` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:86
  • `fs.mkdirSync` in `initWorkspace` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:98
  • `fs.writeFileSync` in `createTypeScriptConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:203, multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:219, multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:236
  • `fs.writeFileSync` in `git.on("close")` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:292
  • `fs.existsSync` in `openWorkspace` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:306
  • `fs.existsSync` in `enableGlobalWorkspace` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:333
  • `fs.existsSync` in `disableGlobalWorkspace` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:371
  • `fs.existsSync` in `showWorkspaceStatus` 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. — multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:414

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 Duplication8.5 / 10Strong✓ Tool-verified

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

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

  • 45 duplicated blocks under multimodal/tarko/ have copies in at least two of the sibling directories agent, agent-interface, agent-server, agent-server-next, agent-ui, agent-ui-builder (+6 more sibling(s) not listed) — 40 of them are reported below, and 5 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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. — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7
  • 36 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, infra, multimodal, packages — 29 of them are reported below, and 7 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 36 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 36 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 36 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. — multimodal/gui-agent/operator-browser/src/browser-operator.ts:177
  • 20 duplicated blocks under multimodal/ have copies in at least two of the sibling directories agent-tars, gui-agent, omni-tars, tarko, websites — 14 of them are reported below, and 6 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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. — multimodal/gui-agent/agent-sdk/src/utils.ts:16
  • 13 of the duplicated blocks reported below have copies in at least two of the sibling directories components, pages under apps/ui-tars/src/renderer/src/. That concentration is one structural fact, not 13 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 13 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/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39
  • 11 duplicated blocks under multimodal/omni-tars/ have copies in at least two of the sibling directories code-agent, core, gui-agent, mcp-agent, omni-agent — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — multimodal/omni-tars/code-agent/rslib.config.ts:5
  • 7 duplicated blocks under packages/agent-infra/ have copies in at least two of the sibling directories browser, browser-use, create-new-mcp, mcp-client, mcp-servers, search (+1 more sibling(s) not listed) — 5 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — packages/agent-infra/browser/rslib.config.ts:7
  • 6 of the duplicated blocks reported below have copies in at least two of the sibling directories operator-adb, operator-aio, operator-browser, operator-nutjs under multimodal/gui-agent/. 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. — multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82
  • 6 of the duplicated blocks reported below have copies in at least two of the sibling directories mongodb, sqlite under multimodal/tarko/agent-server-next/src/dao/. 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. — multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39
  • 6 duplicated blocks under multimodal/tarko/agent-ui/src/standalone/ have copies in at least two of the sibling directories chat, components, navbar, share, sidebar, workspace — 2 of them are reported below, and 4 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. — multimodal/tarko/agent-ui/src/standalone/sidebar/AgentConfigViewer.tsx:96
  • multimodal/gui-agent/operator-browser/src/browser-operator.ts:177 · packages/ui-tars/operators/browser-operator/src/browser-operator.ts:137 — the two spans are one implementation copied and then locally edited — 1721 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. — multimodal/gui-agent/operator-browser/src/browser-operator.ts:177
  • multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 · multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — the two spans are one implementation copied and then locally edited — 1674 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. — multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14
  • multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7 · multimodal/tarko/agent-server/src/core/AgentSession.ts:7 — these 2 files are line-for-line copies of one another — 248 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7
  • apps/ui-tars/src/renderer/src/pages/remote/free.tsx:1 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:1 — these 2 files are line-for-line copies of one another — 228 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — apps/ui-tars/src/renderer/src/pages/remote/free.tsx:1
  • multimodal/tarko/agent-server-next/src/services/ShareService.ts:6 · multimodal/tarko/agent-server/src/services/ShareService.ts:6 — these 2 files are line-for-line copies of one another — 193 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — multimodal/tarko/agent-server-next/src/services/ShareService.ts:6
  • apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39 · apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:49 — the two spans are one implementation copied and then locally edited — 774 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/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39
  • multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:175 · multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx:46 — the two spans are one implementation copied and then locally edited — 936 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. — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:175
  • multimodal/gui-agent/operator-browser/src/ui-helper.ts:13 · packages/ui-tars/operators/browser-operator/src/ui-helper.ts:13 — the two spans are one implementation copied and then locally edited — 799 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. — multimodal/gui-agent/operator-browser/src/ui-helper.ts:13
  • apps/ui-tars/src/renderer/src/components/ui/dropdown-menu.tsx:11 · apps/ui-tars/src/renderer/src/components/ui/select.tsx:11 — the two spans are one implementation copied and then locally edited — 518 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/ui-tars/src/renderer/src/components/ui/dropdown-menu.tsx:11
  • multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39 · multimodal/tarko/agent-server-next/src/dao/sqlite/UserConfigDAO.ts:44 — the two spans are one implementation copied and then locally edited — 747 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. — multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39
  • apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:64 · apps/ui-tars/src/renderer/src/components/SideBar/share.tsx:57 — the two spans are one implementation copied and then locally edited — 632 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/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:64
  • apps/ui-tars/src/renderer/src/components/Settings/category/preset.tsx:48 · apps/ui-tars/src/renderer/src/pages/settings/PresetImport.tsx:29 — 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/ui-tars/src/renderer/src/components/Settings/category/preset.tsx:48
  • multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:6 · multimodal/tarko/agent-server/src/utils/slug-generator.ts:6 — these 2 files are line-for-line copies of one another — 106 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:6
  • apps/ui-tars/src/renderer/src/components/ui/dialog.tsx:11 · apps/ui-tars/src/renderer/src/components/ui/sheet.tsx:13 — the two spans are one implementation copied and then locally edited — 465 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/ui-tars/src/renderer/src/components/ui/dialog.tsx:11
  • multimodal/gui-agent/operator-browser/src/ui-helper.ts:366 · packages/ui-tars/operators/browser-operator/src/ui-helper.ts:301 — the two spans are one implementation copied and then locally edited — 753 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. — multimodal/gui-agent/operator-browser/src/ui-helper.ts:366
  • packages/agent-infra/search/browser-search/src/engines/baidu-engine.ts:50 · packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:47 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/agent-infra/search/browser-search/src/engines/baidu-engine.ts:50
  • multimodal/tarko/agent-server-next/src/dao/sqlite/SessionDAO.ts:102 · multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:472 — the two spans are one implementation copied and then locally edited — 601 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. — multimodal/tarko/agent-server-next/src/dao/sqlite/SessionDAO.ts:102
  • apps/ui-tars/src/main/remote/operators.ts:102 · packages/ui-tars/operators/nut-js/src/index.ts:96 — the two spans are one implementation copied and then locally edited — 473 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/ui-tars/src/main/remote/operators.ts:102
  • packages/agent-infra/browser/src/browser-finder/chrome-paths.ts:48 · packages/agent-infra/browser/src/browser-finder/firefox-paths.ts:27 — the two spans are one implementation copied and then locally edited — 480 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/agent-infra/browser/src/browser-finder/chrome-paths.ts:48
  • apps/ui-tars/src/renderer/src/pages/local/index.tsx:96 · apps/ui-tars/src/renderer/src/pages/remote/free.tsx:166 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:127 — the 3 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — apps/ui-tars/src/renderer/src/pages/local/index.tsx:96
  • multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82 · multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:114 — the two spans are one implementation copied and then locally edited — 360 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. — multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82
  • multimodal/gui-agent/cli/src/cli/start.ts:38 · packages/ui-tars/cli/src/cli/start.ts:31 — the two spans are one implementation copied and then locally edited — 448 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. — multimodal/gui-agent/cli/src/cli/start.ts:38
  • multimodal/gui-agent/agent-sdk/src/utils.ts:16 · multimodal/omni-tars/gui-agent/src/utils.ts:17 · multimodal/tarko/shared-utils/src/gui-agent.ts:204 — 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. — multimodal/gui-agent/agent-sdk/src/utils.ts:16
  • apps/ui-tars/src/renderer/src/components/Settings/category/remoteComputer.tsx:27 · apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:45 — the two spans are one implementation copied and then locally edited — 381 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/ui-tars/src/renderer/src/components/Settings/category/remoteComputer.tsx:27
  • REDACTED:16 · REDACTED:16 — 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. — REDACTED:16
  • REDACTED:321 · REDACTED:267 — 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. — REDACTED:321
  • multimodal/tarko/agent-server-next/src/controllers/system.ts:63 · REDACTED:55 — the two spans are one implementation copied and then locally edited — 368 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. — multimodal/tarko/agent-server-next/src/controllers/system.ts:63
  • multimodal/tarko/agent-server-next/src/utils/event-stream.ts:46 · multimodal/tarko/agent-server/src/utils/event-stream.ts:47 — 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. — multimodal/tarko/agent-server-next/src/utils/event-stream.ts:46
  • multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:2 · multimodal/tarko/agent-server/src/utils/config-sanitizer.ts:2 — these 2 files are line-for-line copies of one another — 59 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:2
  • packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:5 · packages/agent-infra/search/browser-search/src/engines/google-engine.ts:5 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:5
  • apps/ui-tars/src/renderer/src/pages/local/index.tsx:213 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:224 — 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/ui-tars/src/renderer/src/pages/local/index.tsx:213

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.9 / 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/ui-tars/src/main/electron-updater/GitHubProvider.ts:22 imports electron-updater/out/providers/GitHubProvider, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:22
  • apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:26 imports electron-updater/out/providers/Provider, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:26
  • apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:4 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:4
  • multimodal/agent-tars/core/src/environments/local/index.ts:25 imports @agent-infra/mcp-server-browser/dist/server.cjs, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath. — multimodal/agent-tars/core/src/environments/local/index.ts:25
  • multimodal/tarko/agent/snapshot/runner.ts:7 reaches into another package with a relative path (../../agent-snapshot) — import the package by name instead. — multimodal/tarko/agent/snapshot/runner.ts:7
  • multimodal/tarko/agent/tests/agent/kernel/agent-running.test.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../../agent-snapshot) — 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. — multimodal/tarko/agent/tests/agent/kernel/agent-running.test.ts:7
  • multimodal/tarko/agent/tests/agent/message-history.test.ts:18 reaches past another workspace package's public entry into its internals with a relative path (../../../agent-snapshot/src) — 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. — multimodal/tarko/agent/tests/agent/message-history.test.ts:18
  • multimodal/tarko/llm-client/src/handlers/gemini.ts:32 imports openai/src/resources/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — multimodal/tarko/llm-client/src/handlers/gemini.ts:32
  • multimodal/tarko/llm-client/src/handlers/mistral.ts:25 imports openai/src/resources/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — multimodal/tarko/llm-client/src/handlers/mistral.ts:25
  • packages/agent-infra/browser-use/src/agent/messages/service.ts:24 imports @langchain/core/dist/messages/tool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/agent-infra/browser-use/src/agent/messages/service.ts:24
  • packages/agent-infra/browser-use/src/browser/page.ts:9 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/agent-infra/browser-use/src/browser/page.ts:9
  • packages/agent-infra/browser-use/src/browser/utils.ts:1 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/agent-infra/browser-use/src/browser/utils.ts:1

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

  • getEnhancedContextInfo has cyclomatic complexity 74 and cognitive complexity 122; 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/agent-infra/browser-use/src/dom/views.ts:222
  • extractToolCallT5 has cyclomatic complexity 51 and cognitive complexity 151; 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. — multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17
  • execute has cyclomatic complexity 51 and cognitive complexity 50; 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/ui-tars/src/main/remote/operators.ts:101
  • extractCodeEnv has cyclomatic complexity 50 and cognitive complexity 156; 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. — multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14
  • execute has cyclomatic complexity 47 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — packages/ui-tars/operators/adb/src/index.ts:111
  • ChatInput has cyclomatic complexity 47 and cognitive complexity 40; 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. — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46
  • getToolDescription has cyclomatic complexity 44 and cognitive complexity 48; 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. — multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx:91
  • execute has cyclomatic complexity 44 and cognitive complexity 32; 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. — packages/ui-tars/operators/nut-js/src/index.ts:94
  • isInteractiveElement has cyclomatic complexity 37 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. — packages/agent-infra/browser-use/assets/buildDomTree.js:293
  • parseActionVlm has cyclomatic complexity 35 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:162
  • extractScriptData has cyclomatic complexity 35 and cognitive complexity 60; 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. — multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx:173
  • singleActionExecutor has cyclomatic complexity 35 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:127
  • handleStreamingResponse has cyclomatic complexity 34 and cognitive complexity 54; 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. — multimodal/tarko/agent/src/agent/runner/llm-processor.ts:280
  • convertToNormalizedAction has cyclomatic complexity 34 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. — multimodal/tarko/shared-utils/src/gui-agent.ts:51
  • singleActionExecutor has cyclomatic complexity 34 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:127
  • performJsonSchemaMigration has cyclomatic complexity 33 and cognitive complexity 56; 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. — multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:170
  • isTopElement has cyclomatic complexity 33 and cognitive complexity 32; 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. — packages/agent-infra/browser-use/assets/buildDomTree.js:490
  • execute has cyclomatic complexity 33 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. — packages/ui-tars/operators/browser-operator/src/browser-operator.ts:189
  • validateInputs has cyclomatic complexity 32 and cognitive complexity 61; 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. — multimodal/tarko/llm-client/src/handlers/base.ts:43
  • parseActionVlm has cyclomatic complexity 31 and cognitive complexity 69; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:92

What to do

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

  • packages/agent-infra/browser-use/src/browser/page.ts has 835 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/agent-infra/browser-use/src/browser/page.ts:1
  • apps/ui-tars/src/main/remote/proxyClient.ts has 771 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/ui-tars/src/main/remote/proxyClient.ts:1
  • multimodal/gui-agent/operator-browser/src/ui-helper.ts has 765 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/gui-agent/operator-browser/src/ui-helper.ts:1
  • REDACTED has 736 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/agent-infra/browser-use/assets/buildDomTree.js has 724 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/agent-infra/browser-use/assets/buildDomTree.js:1
  • packages/agent-infra/mcp-servers/browser/src/server.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. — packages/agent-infra/mcp-servers/browser/src/server.ts:1
  • packages/ui-tars/operators/browser-operator/src/browser-operator.ts has 712 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/ui-tars/operators/browser-operator/src/browser-operator.ts:1
  • packages/ui-tars/visualizer/src/component/player.tsx has 708 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/ui-tars/visualizer/src/component/player.tsx:1
  • packages/ui-tars/operators/browser-operator/src/ui-helper.ts has 705 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/ui-tars/operators/browser-operator/src/ui-helper.ts:1
  • apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx has 684 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/ui-tars/src/renderer/src/components/ui/sidebar.tsx:1
  • multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts has 683 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:1
  • multimodal/gui-agent/operator-browser/src/browser-operator.ts has 646 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/gui-agent/operator-browser/src/browser-operator.ts:1
  • multimodal/tarko/agent/src/agent/agent.ts has 625 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent/src/agent/agent.ts:1
  • packages/agent-infra/browser-use/src/dom/views.ts has 616 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/agent-infra/browser-use/src/dom/views.ts:1
  • packages/agent-infra/mcp-client/src/index.ts has 610 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/agent-infra/mcp-client/src/index.ts:1
  • multimodal/tarko/agent-ui/src/common/services/apiService.ts has 605 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-ui/src/common/services/apiService.ts:1
  • multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts:1
  • apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx has 588 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/ui-tars/src/renderer/src/pages/settings/Settings.tsx:1
  • multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts has 588 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:1
  • multimodal/tarko/agent-interface/src/agent-event-stream.ts has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-interface/src/agent-event-stream.ts:1
  • REDACTED has 562 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
  • multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx has 560 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:1
  • multimodal/tarko/llm-client/src/handlers/anthropic.ts has 545 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/llm-client/src/handlers/anthropic.ts:1
  • packages/ui-tars/sdk/src/GUIAgent.ts has 543 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/ui-tars/sdk/src/GUIAgent.ts:1
  • apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx has 538 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/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:1
  • multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:1
  • multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:1
  • multimodal/gui-agent/action-parser/src/ActionParserHelper.ts has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:1
  • multimodal/tarko/agent-server/src/core/AgentSession.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-server/src/core/AgentSession.ts:1
  • packages/ui-tars/visualizer/src/component/timeline.tsx has 491 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/ui-tars/visualizer/src/component/timeline.tsx:1
  • multimodal/tarko/agent/src/agent/runner/llm-processor.ts has 478 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent/src/agent/runner/llm-processor.ts:1
  • multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:1
  • packages/agent-infra/browser-use/src/agent/actions/builder.ts has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/agent-infra/browser-use/src/agent/actions/builder.ts:1
  • multimodal/websites/main/src/render/components/WorkflowNodes.tsx has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/websites/main/src/render/components/WorkflowNodes.tsx:1
  • multimodal/tarko/llm-client/src/handlers/gemini.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/llm-client/src/handlers/gemini.ts:1
  • packages/agent-infra/mcp-servers/filesystem/src/server.ts has 448 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/agent-infra/mcp-servers/filesystem/src/server.ts:1
  • multimodal/tarko/agio/src/index.ts has 432 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agio/src/index.ts:1
  • multimodal/agent-tars/core/src/environments/local/index.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/agent-tars/core/src/environments/local/index.ts:1
  • multimodal/tarko/agent/src/agent/message-history.ts has 423 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent/src/agent/message-history.ts:1
  • multimodal/tarko/agent-server-next/src/server.ts has 422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — multimodal/tarko/agent-server-next/src/server.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 Coverage5.2 / 10Adequate✓ 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.

  • 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. (×40) — packages/ui-tars/operators/browser-operator/src/browser-operator.ts:1, apps/ui-tars/src/main/remote/proxyClient.ts:1, packages/agent-infra/browser-use/assets/buildDomTree.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.2 / 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 REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code0.5 / 10Critical✓ 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.

  • 1 file(s) (~9 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — infra
  • 2 file(s) (~38 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — multimodal
  • 1 file(s) (~71 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — multimodal/websites/tarko
  • Unreachable from the 151 application, 171 tooling and 163 test entry point(s) detected in this repo. Gate removals on `pnpm run typecheck:node` — an undetected custom entry would make these reachable.
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×8) — apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx, REDACTED, apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx, …
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/common/services/apiService.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/navbar/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/renderer/src/pages/remote/paid.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/remote/operators.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/ui-tars/src/main/remote/subscriptionClient.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/hooks/useSession.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts, multimodal/tarko/agent-ui/src/common/hooks/useReplayMode.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — multimodal/tarko/agent-ui/src/standalone/workspace/renderers/LinkReaderRenderer.tsx, multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx, multimodal/tarko/agent-ui/src/standalone/workspace/components/RawModeRenderer.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/sidebar/SidebarContainer.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/EventHandlerRegistry.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts, multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/MessageHandler.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx, multimodal/tarko/agent-ui/src/standalone/share/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/services/runAgent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/ui-tars/src/main/remote/operators.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/utils/agent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/home/HomePage.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/electron-updater/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspacePanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/ui-tars/src/main/menu.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/renderers/SearchResultRenderer.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/common/services/SearchService.ts
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, multimodal/tarko/agent-ui/src/standalone/navbar/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/Message/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/ContextualTags.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/MessageAttachments.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/chat/ContextualSelector.tsx
  • no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — multimodal/tarko/agent-ui/src/standalone/home/WelcomeCards.tsx

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 Hygiene0.0 / 10Critical✓ 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 REDACTED — installs work only by hoisting accident. (×24) — scripts/merge-yml/merge-yml.ts:3, apps/ui-tars/src/main/remote/auth.ts:10, apps/ui-tars/src/main/ipcRoutes/setting.ts:5, …
  • Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED. — packages/agent-infra/browser-use/test/azureBedrockChat.ts:11
  • Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports0.0 / 10Critical✓ 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.

  • multimodal/tarko/agent-interface/src/agent-event-stream.ts → multimodal/tarko/agent-interface/src/agent-instance.ts → multimodal/tarko/agent-interface/src/agent-event-stream.ts — multimodal/tarko/agent-interface/src/agent-event-stream.ts:12
  • multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts → multimodal/tarko/agent-server-next/src/middlewares/index.ts → multimodal/tarko/agent-server-next/src/middlewares/exclusive-mode.ts → multimodal/tarko/agent-server-next/src/server.ts → multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts (one verified cycle inside a mutually-dependent group of 9 files) — multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts:9
  • multimodal/tarko/agent-server/src/api/index.ts → multimodal/tarko/agent-server/src/api/routes/index.ts → multimodal/tarko/agent-server/src/api/routes/oneshot.ts → multimodal/tarko/agent-server/src/api/middleware/index.ts → multimodal/tarko/agent-server/src/api/middleware/exclusive-mode.ts → multimodal/tarko/agent-server/src/server.ts → multimodal/tarko/agent-server/src/api/index.ts (one verified cycle inside a mutually-dependent group of 9 files) — multimodal/tarko/agent-server/src/api/index.ts:3
  • multimodal/tarko/agent/src/agent/agent-runner.ts → multimodal/tarko/agent/src/agent/runner/llm-processor.ts → multimodal/tarko/agent/src/agent/agent.ts → multimodal/tarko/agent/src/agent/agent-runner.ts (one verified cycle inside a mutually-dependent group of 12 files) — multimodal/tarko/agent/src/agent/agent-runner.ts:24
  • multimodal/tarko/llm-client/src/handlers/ai21.ts → multimodal/tarko/llm-client/src/handlers/utils.ts → multimodal/tarko/llm-client/src/handlers/ai21.ts (one verified cycle inside a mutually-dependent group of 5 files) — multimodal/tarko/llm-client/src/handlers/ai21.ts:19
  • multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts → multimodal/tarko/ui/src/components/markdown-renderer/components/useMarkdownComponents.tsx → multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts — multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts:11
  • packages/ui-tars/sdk/src/Model.ts → packages/ui-tars/sdk/src/types.ts → packages/ui-tars/sdk/src/Model.ts — packages/ui-tars/sdk/src/Model.ts:14
  • packages/ui-tars/shared/src/types/data.ts → packages/ui-tars/shared/src/types/index.ts → packages/ui-tars/shared/src/types/data.ts — packages/ui-tars/shared/src/types/data.ts:6

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

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

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

  • `https://www.googletagmanager.com/gtag/js?id=G-J82M1JQ6KF` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 7 such include(s) across the repository's markup. — multimodal/websites/main/public/index.html:5
  • `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — multimodal/tarko/agent-server/src/server.ts:272
  • `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:266

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
  • Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X13 · Undrained process 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 document3.5 / 10Weak✓ 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.

  • `normalize` is exported and takes `obj: any` from its caller, and it calls itself at line 318 (`this.normalize`) with a piece of `obj` (and at line 342) — and nowhere in `normalize` 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 `normalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — multimodal/tarko/agent-snapshot/src/utils/snapshot-normalizer.ts:318

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 propagation6.2 / 10Adequate✓ Tool-verified

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

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

  • Only 11/30 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `send` 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 })`. — packages/ui-tars/utio/src/index.ts:16
  • `search` 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 })`. (×2) — packages/agent-infra/search/search/src/searxng.ts:35, packages/agent-infra/search/bing-search/src/api-client.ts:226
  • `activate` 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 })`. — packages/agent-infra/mcp-client/src/index.ts:212
  • `launch` 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 })`. — packages/agent-infra/browser/src/remote-browser.ts:55
  • `create` 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 })`. — multimodal/tarko/llm-client/src/handlers/ai21.ts:216
  • `fetchImageAsBase64` 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 })`. — multimodal/tarko/llm-client/src/handlers/utils.ts:164
  • `getHtmlContent` 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 })`. — multimodal/tarko/agent-ui-builder/src/builder.ts:85
  • `upload` 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 })`. — multimodal/tarko/agent-ui-builder/src/builder.ts:117
  • `getShareConfig` 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 })`. — multimodal/tarko/agent-ui/src/standalone/share/shareService.ts:33
  • `shareSession` 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 })`. — multimodal/tarko/agent-ui/src/standalone/share/shareService.ts:62
  • `imageToBase64` 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 })`. — multimodal/tarko/agent-ui/src/common/utils/clipboard.ts:9
  • `uploadWorkspaceImage` 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 })`. (×2) — multimodal/tarko/agent-server-next/src/services/ShareService.ts:341, multimodal/tarko/agent-server/src/services/ShareService.ts:337
  • `processServerRun` 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 })`. — multimodal/tarko/agent-cli/src/core/commands/run.ts:66
  • `loadRemoteConfig` 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 })`. — multimodal/tarko/agent-cli/src/config/loader.ts:25
  • `uploadReport` 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/ui-tars/src/renderer/src/utils/share.ts:1
  • `importPresetFromUrl` 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/ui-tars/src/main/store/setting.ts:89
  • `fetchPresetFromUrl` 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/ui-tars/src/main/store/setting.ts:132

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X23 · Unguarded diagnostic materialisation5.5 / 10Adequate✓ Tool-verified

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.

  • `debug` at line 705 is called with an argument built by `JSON.stringify(element.attributes)` (line 705), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/agent-infra/browser-use/src/browser/page.ts:705
  • `debug` at line 94 is called with an argument built by `data.join(', ')` (line 94), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent-cli/src/config/display.ts:94
  • `debug` at line 96 is called with an argument built by `Object.keys(data)` (line 96), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent-cli/src/config/display.ts:96
  • `debug` at line 167 is called with an argument built by `types.join(', ')` (line 167), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/event-stream.ts:167
  • `debug` at line 172 is called with an argument built by `types.join(', ')` (line 172), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/event-stream.ts:172
  • `debug` at line 83 is called with an argument built by `JSON.stringify(args)` (line 83), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/tool-manager.ts:83
  • `debug` at line 92 is called with an argument built by `JSON.stringify(result)` (line 93), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/tool-manager.ts:92
  • `debug` at line 115 is called with an argument built by `JSON.stringify(args)` (line 115), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/runner/tool-processor.ts:115
  • `debug` at line 123 is called with an argument built by `JSON.stringify(result)` (line 124), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/tarko/agent/src/agent/runner/tool-processor.ts:123
  • `debug` at line 42 is called with an argument built by `JSON.stringify(tool)` (line 42), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:42
  • `debug` at line 46 is called with an argument built by `JSON.stringify(operator_action)` (line 47), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:46
  • `debug` at line 50 is called with an argument built by `JSON.stringify(operator_action)` (line 51), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:50
  • `debug` at line 56 is called with an argument built by `JSON.stringify(action_for_gui_render)` (line 57), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:56
  • `debug` at line 70 is called with an argument built by `JSON.stringify(roughAction)` (line 70), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:70
  • `debug` at line 75 is called with an argument built by `JSON.stringify(action)` (line 75), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:75
  • `debug` at line 218 is called with an argument built by `JSON.stringify(roughAction)` (line 218), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:218
  • `debug` at line 223 is called with an argument built by `JSON.stringify(action)` (line 223), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:223
  • `debug` at line 455 is called with an argument built by `JSON.stringify(coords)` (line 455), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:455
  • `debug` at line 141 is called with an argument built by `JSON.stringify(normalizedCoordsAction, null, 2)` (line 145), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:141

What to do

  • Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
X24 · Document value interpolated into markup unescaped4.9 / 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.

  • `actionText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — multimodal/gui-agent/operator-browser/src/ui-helper.ts:395, packages/ui-tars/operators/browser-operator/src/ui-helper.ts:330
  • `thought` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — multimodal/gui-agent/operator-browser/src/ui-helper.ts:396, packages/ui-tars/operators/browser-operator/src/ui-helper.ts:331
  • `href` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — REDACTED:165
  • `sessionId?`?sessionId=${sessionId}`:''` is text this program did not author, and it is written into a URL attribute through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:172
  • `sessionParam` is text this program did not author, and it is written into a URL attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:191
  • `title` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:201
  • `sessionContext` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:217, REDACTED:234
  • `sessionId` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:218, REDACTED:235

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X3 · Exception handling7.1 / 10Strong✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×25) — packages/ui-tars/utio/src/index.ts:31, packages/common/electron-build/src/findUp.ts:46, packages/common/electron-build/src/findUp.ts:77, …
  • `catch (error)` 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. — packages/agent-infra/mcp-servers/filesystem/src/server.ts:158
  • `catch (e)` 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. — packages/agent-infra/browser/src/base-browser.ts:284
  • `.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) — multimodal/agent-tars/core/src/environments/local/browser/browser-manager.ts:151, apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:242, apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:407
  • `catch (cdpError)` 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. — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:245

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.

X5 · Nullable reference types8.6 / 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.

  • 71/80 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~1.3 `!` null assertions per 1k TypeScript source lines — 185 assertion(s) across the 138656 source line(s) of the 1044 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: multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts (17), multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts (13), multimodal/gui-agent/operator-adb/src/AdbOperator.ts (9). 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 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health48%Weak — gated by D2, R7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture65%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity65%AdequateAcceptable, with room to improve.
Readiness40%Weak — gated by D12, R8, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security59%Adequate — gated by D29, D30, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility41%Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance73%StrongStrongest area.
Unscored — 4 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.

  • P12 CI test-gate honesty — 15 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 42 check(s) not relevant to this codebase

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

  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript, html not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .mts, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • 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 — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
  • 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
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `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
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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 — 282 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×117
  • 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
  • + 92 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×24
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×12
  • Orphaned knowledge packages/agent-infra/browser-use/src/browser/page.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/agent-infra/browser-use/assets/buildDomTree.js:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/ui-tars/visualizer/src/component/player.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge multimodal/gui-agent/agent-sdk/src/prompts.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge apps/ui-tars/src/main/remote/proxyClient.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/ui-tars/visualizer/src/utils.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/agent-infra/browser-use/src/dom/views.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge multimodal/omni-tars/core/src/environments/prompt_t5.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge apps/ui-tars/src/main/agent/prompts.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×10
  • Click handler on a non-interactive <div> multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ReportFileEntry.tsx:30 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:117 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:137 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/tarko/agent-ui/src/standalone/workspace/components/WorkspaceFileManager.tsx:194 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/tarko/ui/src/components/basic/Dropdown.tsx:48 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/tarko/ui/src/components/basic/Dropdown.tsx:67 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/websites/main/src/render/components/DocsSidebar.tsx:139 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> multimodal/websites/main/src/render/components/Home/HeroSection.tsx:109 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> packages/ui-tars/visualizer/src/component/player.tsx:773 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <div> packages/ui-tars/visualizer/src/component/sidebar.tsx:42 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
R8 · Dependency Hygiene · Unlisted import 'vite-tsconfig-paths' · ×10
  • Unlisted import 'vite-tsconfig-paths' multimodal/gui-agent/action-parser/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' multimodal/gui-agent/operator-adb/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' multimodal/gui-agent/operator-aio/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' multimodal/gui-agent/operator-nutjs/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' multimodal/gui-agent/shared/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' packages/common/electron-build/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' packages/ui-tars/action-parser/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' packages/ui-tars/cli/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' packages/ui-tars/electron-ipc/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'vite-tsconfig-paths' packages/ui-tars/operators/adb/vitest.config.mts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×5
  • Hover-only interaction on <div> multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:120 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
  • Hover-only interaction on <div> REDACTED:589 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
  • Hover-only interaction on <div> multimodal/tarko/ui/src/components/basic/Tooltip.tsx:147 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
  • Hover-only interaction on <div> packages/ui-tars/visualizer/src/component/detail-side.tsx:79 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
  • Hover-only interaction on <div> packages/ui-tars/visualizer/src/component/env-config.tsx:55 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
R9 · Circular Imports · Import cycle (2 files) · ×5
  • Import cycle (2 files) multimodal/tarko/agent-interface/src/agent-event-stream.ts:12 — multimodal/tarko/agent-interface/src/agent-event-stream.ts → multimodal/tarko/agent-interface/src/agent-instance.ts → multimodal/tarko/agent-interface/src/agent-event-stream.ts
  • Import cycle (2 files) multimodal/tarko/llm-client/src/handlers/ai21.ts:19 — multimodal/tarko/llm-client/src/handlers/ai21.ts → multimodal/tarko/llm-client/src/handlers/utils.ts → multimodal/tarko/llm-client/src/handlers/ai21.ts (one verified cycle inside a mutually-dependent group of 5 files)
  • Import cycle (2 files) multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts:11 — multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts → multimodal/tarko/ui/src/components/markdown-renderer/components/useMarkdownComponents.tsx → multimodal/tarko/ui/src/components/markdown-renderer/components/index.ts
  • Import cycle (2 files) packages/ui-tars/sdk/src/Model.ts:14 — packages/ui-tars/sdk/src/Model.ts → packages/ui-tars/sdk/src/types.ts → packages/ui-tars/sdk/src/Model.ts
  • Import cycle (2 files) packages/ui-tars/shared/src/types/data.ts:6 — packages/ui-tars/shared/src/types/data.ts → packages/ui-tars/shared/src/types/index.ts → packages/ui-tars/shared/src/types/data.ts
AC2 · Forms & labels · <button> with no accessible text · ×4
  • <button> with no accessible text multimodal/tarko/agent-ui/src/standalone/app/Layout/MobileBottomSheet.tsx:73 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:125 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx:77 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
  • <button> with no accessible text multimodal/tarko/ui/src/components/basic/ConfirmDialog.tsx:72 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×3
  • <input> without a programmatic label multimodal/tarko/agent-ui/src/standalone/replay/ReplayControlPanel.tsx:50 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:267 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label multimodal/tarko/agent-ui/src/standalone/sidebar/SessionItem.tsx:88 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · Custom control with no accessible name on <video> · ×3
  • Custom control with no accessible name on <video> multimodal/websites/docs/src/components/IntroAnimation.tsx:250 — This <video> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <video> multimodal/websites/docs/src/components/IntroAnimation.tsx:260 — This <video> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <video> multimodal/websites/docs/src/components/VideoPanel.tsx:55 — This <video> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×3
  • Click handler on a non-interactive <img> multimodal/tarko/agent-ui/src/standalone/chat/ImagePreview.tsx:48 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <img> multimodal/tarko/ui/src/components/markdown-renderer/components/Image.tsx:24 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <img> multimodal/tarko/ui/src/components/markdown-renderer/components/ImageModal.tsx:14 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <video> · ×3
  • Click handler on a non-interactive <video> multimodal/websites/docs/src/components/IntroAnimation.tsx:250 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <video> multimodal/websites/docs/src/components/IntroAnimation.tsx:260 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <video> multimodal/websites/docs/src/components/VideoPanel.tsx:55 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · Custom control with no accessible name on <div> · ×2
  • Custom control with no accessible name on <div> multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:117 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
  • Custom control with no accessible name on <div> multimodal/tarko/ui/src/components/basic/Dropdown.tsx:48 — This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC3 · Page structure · <html> without a lang · ×2
  • <html> without a lang apps/ui-tars/src/renderer/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang multimodal/websites/main/public/index.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×2
  • Click handler on a non-interactive <span> multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx:118 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
  • Click handler on a non-interactive <span> multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx:152 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×2
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'js-yaml' · ×2
  • Unlisted import 'js-yaml' scripts/merge-yml/merge-yml.ts:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'js-yaml' packages/common/electron-build/src/hooks/postMake.ts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'zod' · ×2
  • Unlisted import 'zod' apps/ui-tars/src/main/store/validate.ts:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'zod' packages/ui-tars/electron-ipc/test/index.test.ts:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC1 · Text alternatives · <img> without a text alternative · ×1
  • <img> without a text alternative packages/ui-tars/visualizer/src/component/global-hover-preview.tsx:60 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels · Custom control with no accessible name on <canvas> · ×1
  • Custom control with no accessible name on <canvas> apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448 — This <canvas> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:438 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:111 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title apps/ui-tars/src/renderer/src/pages/remote/cast/vnc.tsx:70 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> multimodal/websites/main/public/index.html:2 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Focusable <div> isn't keyboard-operable · ×1
  • Focusable <div> isn't keyboard-operable multimodal/websites/docs/src/components/ActionCard.tsx:169 — This <div> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its behaviour is bound to the pointer only, with no key handler. A tabindex makes an element focusable, not operable: Enter and Space fire a click on a native <button> or <a href> and nowhere else, so this can be focused and never activated. Use a <button>, or handle Enter/Space in a key handler.
AC4 · Keyboard semantics · Click handler on a <svg> nested inside <a> · ×1
  • Click handler on a <svg> nested inside <a> multimodal/websites/main/src/render/components/Markdown/HeaderAnchor.tsx:40 — This <svg> carries its own click handler, but it sits inside a <a> that performs a different action. A keyboard user reaches the <a> and activating it runs the <a>'s handler, never this one, so this action has no keyboard path at all. Role and tabindex cannot supply one: HTML forbids a <a> from containing interactive content or any descendant with a tabindex, so the browser will not put this element in the tab order however it is marked up. Move it out of the <a> and make it a sibling <button>, so each action has its own control.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'axios' · ×1
  • Unlisted import 'axios' apps/ui-tars/src/main/remote/auth.ts:10 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'openai' · ×1
  • Unlisted import 'openai' apps/ui-tars/src/main/ipcRoutes/setting.ts:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'source-map-support' · ×1
  • Unlisted import 'source-map-support' apps/ui-tars/src/main/main.ts:49 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@rsbuild/plugin-react' · ×1
  • Unlisted import '@rsbuild/plugin-react' multimodal/tarko/ui/rslib.config.ts:1 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'uuid' · ×1
  • Unlisted import 'uuid' packages/agent-infra/browser-use/src/agent/service.ts:10 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'zod-to-json-schema' · ×1
  • Unlisted import 'zod-to-json-schema' packages/agent-infra/browser-use/src/agent/messages/service.ts:16 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@rslib/core' · ×1
  • Unlisted import '@rslib/core' packages/agent-infra/mcp-client/rslib.config.ts:5 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'eventsource' · ×1
  • Unlisted import 'eventsource' packages/agent-infra/mcp-http-server/tests/startServer-mcpServer.test.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'express' · ×1
  • Unlisted import 'express' packages/agent-infra/mcp-servers/browser/tests/server-in-memory.test.ts:16 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'esbuild' · ×1
  • Unlisted import 'esbuild' packages/agent-infra/shared/scripts/build-readability.ts:3 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (4 files) · ×1
  • Import cycle (4 files) multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts:9 — multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts → multimodal/tarko/agent-server-next/src/middlewares/index.ts → multimodal/tarko/agent-server-next/src/middlewares/exclusive-mode.ts → multimodal/tarko/agent-server-next/src/server.ts → multimodal/tarko/agent-server-next/src/hooks/builtInHooks.ts (one verified cycle inside a mutually-dependent group of 9 files)
R9 · Circular Imports · Import cycle (6 files) · ×1
  • Import cycle (6 files) multimodal/tarko/agent-server/src/api/index.ts:3 — multimodal/tarko/agent-server/src/api/index.ts → multimodal/tarko/agent-server/src/api/routes/index.ts → multimodal/tarko/agent-server/src/api/routes/oneshot.ts → multimodal/tarko/agent-server/src/api/middleware/index.ts → multimodal/tarko/agent-server/src/api/middleware/exclusive-mode.ts → multimodal/tarko/agent-server/src/server.ts → multimodal/tarko/agent-server/src/api/index.ts (one verified cycle inside a mutually-dependent group of 9 files)
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) multimodal/tarko/agent/src/agent/agent-runner.ts:24 — multimodal/tarko/agent/src/agent/agent-runner.ts → multimodal/tarko/agent/src/agent/runner/llm-processor.ts → multimodal/tarko/agent/src/agent/agent.ts → multimodal/tarko/agent/src/agent/agent-runner.ts (one verified cycle inside a mutually-dependent group of 12 files)
Serious — 1080 finding(s)
D3 · God Classes · FunctionTooLong · ×81
  • FunctionTooLong: buildDomTree.buildDomTree packages/agent-infra/browser-use/assets/buildDomTree.js:14 — FunctionTooLong — buildDomTree runs 514 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 414 over it, 5.14× 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: player.Player packages/ui-tars/visualizer/src/component/player.tsx:124 — FunctionTooLong — Player runs 483 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 383 over it, 4.83× 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: Settings.Settings apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:69 — FunctionTooLong — Settings runs 465 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 365 over it, 4.65× 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: ChatInput.ChatInput multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46 — FunctionTooLong — ChatInput runs 443 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 343 over it, 4.43× 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: index.HomePageContent multimodal/websites/docs/src/pages/HomePage/index.tsx:23 — FunctionTooLong — HomePageContent runs 365 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 265 over it, 3.65× 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: Navbar.Navbar REDACTED:50 — FunctionTooLong — Navbar runs 341 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 241 over it, 3.41× 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: canvas.CDPBrowser apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:16 — FunctionTooLong — CDPBrowser runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× 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: WorkflowNodes.WorkflowNodes multimodal/websites/main/src/render/components/WorkflowNodes.tsx:75 — FunctionTooLong — WorkflowNodes runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× 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: ShareModal.ShareModal multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:14 — FunctionTooLong — ShareModal runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: server.handleToolCall packages/agent-infra/mcp-servers/browser/src/server.ts:200 — FunctionTooLong — handleToolCall runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.98× 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: vlm.VLMSettings apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:58 — FunctionTooLong — VLMSettings runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× 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: ChatSession.ChatSession multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx:14 — FunctionTooLong — ChatSession runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× 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: timeline.TimelineWidget packages/ui-tars/visualizer/src/component/timeline.tsx:48 — FunctionTooLong — TimelineWidget runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× 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: free.RemoteOperator apps/ui-tars/src/renderer/src/pages/remote/free.tsx:51 — FunctionTooLong — RemoteOperator runs 274 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× 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: ShowcaseDetail.ShowcaseDetail multimodal/websites/main/src/render/pages/ShowcaseDetail.tsx:13 — FunctionTooLong — ShowcaseDetail runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: paid.RemoteOperator apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:50 — FunctionTooLong — RemoteOperator runs 245 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× 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: WelcomePage.WelcomePage multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx:16 — FunctionTooLong — WelcomePage runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× 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: MarkdownRenderer.MarkdownRenderer multimodal/websites/main/src/render/components/Markdown/MarkdownRenderer.tsx:26 — FunctionTooLong — MarkdownRenderer runs 236 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 136 over it, 2.36× 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: ShowcaseDetail.ShowcaseDetail multimodal/websites/docs/src/components/Showcase/components/ShowcaseDetail.tsx:18 — FunctionTooLong — ShowcaseDetail runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× 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: extractToolCallT5.extractToolCallT5 multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — FunctionTooLong — extractToolCallT5 runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× 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.createServer packages/agent-infra/mcp-servers/filesystem/src/server.ts:169 — FunctionTooLong — createServer runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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: AboutModal.AboutModal multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx:17 — FunctionTooLong — AboutModal runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× 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: ChatBottomSettings.ChatBottomSettings multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx:35 — FunctionTooLong — ChatBottomSettings runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× 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: extractCode.extractCodeEnv multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 — FunctionTooLong — extractCodeEnv runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: useReplay.useReplay multimodal/tarko/agent-ui/src/common/hooks/useReplay.ts:18 — FunctionTooLong — useReplay runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× 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.
  • + 56 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×59
  • 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
  • + 34 more in this group — see findings.md.
D17 · Explicit Debt · FixmeComment · ×45
  • FixmeComment packages/agent-infra/search/browser-search/src/browser-search.ts:65 — // FIXME: We should not 100% launch browser here, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/agent-infra/mcp-servers/search/src/server.ts:87 — // @ts-expect-error FIXME: we need a better type design here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment packages/agent-infra/mcp-servers/search/src/server.ts:150 — // FIXME: return original — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/websites/docs/src/components/hooks/useLocaledPath.ts:6 — // FIXME: using `usePageData` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/ui/src/components/gui-agent/useScreenshots.ts:8 — // FIXME: remove implicit type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/ui/src/components/gui-agent/useScreenshots.ts:52 — // @ts-expect-error FIXME: remove implicit type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/ui/src/components/gui-agent/useScreenshots.ts:73 — // @ts-expect-error FIXME: remove implicit type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/mcp-agent-interface/src/index.ts:8 — // FIXME: remove enum-based logger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/mcp-agent/src/mcp-types.ts:6 — // FIXME: remove enum-based logger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/llm-client/src/index.ts:142 — // FIXME: find a better solution for it. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/llm-client/src/handlers/anthropic.ts:451 — // FIXME: Property 'image_url' does not exist on type 'ChatCompletionContentPartImage | ChatCompletionContentPartInputAudio | File'. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/llm-client/src/handlers/utils.ts:11 — // @ts-nocheck FIXME: this file has too many type errors. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-ui/src/standalone/workspace/renderers/FileResultRenderer.tsx:49 — // FIXME: For "str_replace_editor" "create", Found a better solution here, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-ui/src/standalone/workspace/renderers/FileResultRenderer.tsx:119 — // FIXME: For "str_replace_editor" "create", Found a better solution here, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:287 — // FIXME: type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:298 — // FIXME: type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:165 — // @ts-expect-error FIXME: remove string type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:213 — // @ts-expect-error FIXME: remove string type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:345 — // @ts-expect-error FIXME: remove string type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:368 — // @ts-expect-error FIXME: remove string type. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-server-next/src/services/ShareService.ts:360 — // FIXME: Support storage.provider — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-server/src/services/ShareService.ts:356 — // FIXME: Support storage.provider — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-server-next/src/services/session/AgentSessionPool.ts:216 — // FIXME: Rough estimate: ~3MB per session (should be tuned based on actual usage) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-server-next/src/services/sandbox/SandboxManager.ts:99 — //FIXME: Irregular url splicing method, temporary solution — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • FixmeComment multimodal/tarko/agent-server-next/src/controllers/sessions.ts:310 — // FIXME: Use smaller messages to generate summaries — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 20 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking apps/ui-tars/src/main/logger.ts:73 — `fs.unlinkSync` in `cleanupOldLogs` 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/ui-tars/src/main/remote/auth.ts:114 — `fs.existsSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:117 — `fs.existsSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:125 — `generateKeyPairSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:135 — `fs.existsSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:137 — `fs.mkdirSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:140 — `fs.writeFileSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:141 — `fs.writeFileSync` in `genKeyPair` 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/ui-tars/src/main/remote/auth.ts:172 — `fs.existsSync` in `getLocalPubKey` 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/ui-tars/src/main/remote/auth.ts:175 — `fs.readFileSync` in `getLocalPubKey` 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/ui-tars/src/main/remote/auth.ts:187 — `fs.existsSync` in `getLocalPrivKey` 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/ui-tars/src/main/remote/auth.ts:190 — `fs.readFileSync` in `getLocalPrivKey` 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 infra/pdk/src/commands/changelog.ts:35 — `existsSync` in `updateChangelogFile` 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 infra/pdk/src/commands/changelog.ts:36 — `readFileSync` in `updateChangelogFile` 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 infra/pdk/src/commands/changelog.ts:46 — `writeFileSync` in `updateChangelogFile` 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 infra/pdk/src/commands/changelog.ts:56 — `writeFileSync` in `updateChangelogFile` 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 infra/pdk/src/commands/release.ts:183 — `existsSync` in `release` 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 infra/pdk/src/utils/ai-changelog.ts:298 — `existsSync` in `updateChangelogFile` 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 infra/pdk/src/utils/ai-changelog.ts:299 — `readFileSync` in `updateChangelogFile` 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 infra/pdk/src/utils/ai-changelog.ts:316 — `writeFileSync` in `updateChangelogFile` 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 multimodal/agent-tars/core/src/environments/local/browser/tools/visual.ts:45 — `fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking multimodal/agent-tars/core/src/environments/local/browser/tools/visual.ts:46 — `fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking multimodal/gui-agent/cli/src/cli/start.ts:53 — `fs.existsSync` in `start` 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 multimodal/gui-agent/cli/src/cli/start.ts:55 — `fs.readFileSync` in `start` 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 multimodal/gui-agent/cli/src/cli/start.ts:92 — `fs.writeFileSync` in `start` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file packages/ui-tars/operators/browser-operator/src/browser-operator.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/ui-tars/src/main/remote/proxyClient.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 packages/agent-infra/browser-use/assets/buildDomTree.js: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 packages/ui-tars/visualizer/src/component/player.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 packages/ui-tars/operators/browser-operator/src/ui-helper.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/ui-tars/src/renderer/src/components/ui/sidebar.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 multimodal/tarko/agent-ui/src/common/services/apiService.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 REDACTED: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 multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.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/ui-tars/src/renderer/src/pages/settings/Settings.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 REDACTED: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/ui-tars/src/renderer/src/components/Settings/category/vlm.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 multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.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 packages/ui-tars/visualizer/src/component/timeline.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 multimodal/websites/main/src/render/components/WorkflowNodes.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/ui-tars/src/renderer/src/pages/remote/cast/canvas.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/ui-tars/src/main/remote/subscriptionClient.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 packages/ui-tars/visualizer/src/component/replay-scripts.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 infra/pdk/src/commands/release.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 multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.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/ui-tars/src/renderer/src/pages/remote/free.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 multimodal/tarko/agent-ui/src/standalone/workspace/renderers/LinkReaderRenderer.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 packages/ui-tars/visualizer/src/component/detail-side.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 multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.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 multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.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.
  • + 15 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×39
  • TodoComment packages/ui-tars/visualizer/src/component/detail-panel.tsx:120 — // TODO: pretty error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ui-tars/sdk/src/GUIAgent.ts:382 — // TODO: pass executeOutput to onData — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ui-tars/sdk/src/types.ts:64 — // TODO: status: StatusEnum, status should be provided by model — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ui-tars/sdk/src/utils.ts:67 — // TODO: configurable max image length — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ui-tars/operators/browserbase/src/index.ts:102 — // TODO: 需要处理返回的 ObserveResult — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/ui-tars/cli/src/cli/start.ts:104 — // // TODO: implement browser operator — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:45 — // TODO make sure to cover the fish workaround logic, in all its edge cases and then can leave those tests when I remove that or just nuke them — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:94 — // TODO make sure cwd is not already / in the test? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:114 — // TODO add testing of try/catch in runScript block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:121 — // TODO add tests for logging on failures? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:37 — // TODO starts with fish too? "fish -..." PRN use a library to parse the command and determine this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:91 — // most of the time this is gonna match stderr, TODO do I want/need both error and stderr? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/src/server.ts:27 — // TODO use .promises? in node api — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/src/server.ts:89 — // TODO gracefully handle errors and turn them into a prompt message that can be used by LLM to troubleshoot the issue, currently errors result in nothing inserted into the prompt and instead it shows the Zed's chat panel as a failure — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/mcp-servers/commands/src/server.ts:150 — // TODO catch for other errors, not just ExecException — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/agents/navigator.ts:90 — // TODO: don't know why zod can not generate the same schema. Use the json schema exported from browser-use as a workaround for now, need to fix it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/agents/navigator.ts:333 — // TODO: wait for 1 second for now, need to optimize this to avoid unnecessary waiting — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/actions/builder.ts:100 — // TODO: can not make every action optional, don't know why — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/actions/builder.ts:234 — // TODO: could be optimized by chrome extension tab api — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/actions/builder.ts:345 — // TODO: this is not used currently, need to improve on input size — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/actions/json_gemini.ts:9 — // TODO: don't know why zod can not generate the same schema, need to fix it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser-use/src/agent/actions/json_schema.ts:10 — // TODO: don't know why zod can not generate the same schema, need to fix it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/agent-infra/browser/src/browser-finder/chrome-paths.ts:33 — // TODO: scan desktop installation folders, the `grep` operation can be somewhat time-consuming. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment multimodal/tarko/agent-ui/src/standalone/home/HomeAgentOptionsSelector.tsx:60 — // TODO: Extract schema loading logic to be independent of session — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment multimodal/tarko/agent-server-next/src/services/sandbox/SandboxScheduler.ts:47 — //TODO: Here is a temporary comment, do not query the user's strategy from db, and use session exclusively — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 14 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×32
  • Animation without a prefers-reduced-motion guard apps/ui-tars/src/renderer/index.html:63 — `.loading-spinner` moves (`animation: spin 1s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard apps/ui-tars/src/renderer/src/pages/remote/cast/status.tsx:87 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:570 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/chat/components/OfflineBanner.tsx:55 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/chat/components/SessionCreatingState.tsx:32 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx:232 — <div> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/sidebar/ToolBar.tsx:101 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/agent-ui/src/standalone/workspace/components/RawModeRenderer.tsx:112 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/tarko/ui/src/components/basic/LoadingSpinner.tsx:11 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard REDACTED:38 — <div> moves — its inline style sets `animation: spin 1s linear infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/components/Replay/index.tsx:99 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/websites/main/src/render/components/Home/SectionDivider.tsx:8 — <div> moves — its inline style sets `animation: pulse 4s ease-in-out infinite` — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/components.css:200 — `.terminal-scan-line` moves (`animation: terminal-scan 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/components.css:218 — `.terminal-scan-line` moves (`animation: terminal-scan 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:17 — `.aurora-beam` moves (`animation: aurora-rise 20s ease-in-out infinite alternate, aurora-flow 25s ease-in-out infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:63 — `.cyber-grid-bg` moves (`animation: grid-scroll 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:74 — `.animated-grid` moves (`animation: grid-animation 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:85 — `.scan-line::before` moves (`animation: scan-line 3s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:134 — `.glitch-micro` moves (`animation: glitch-micro 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:144 — `.glitch-text` moves (`animation: minor-glitch 10s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:148 — `.glitch-intense` moves (`animation: major-glitch 0.5s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:173 — `.hologram::before` moves (`animation: hologram-scan 3s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:238 — `.data-stream` moves (`animation: data-flow 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:248 — `.particle` moves (`animation: particle-float 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard multimodal/websites/docs/src/pages/HomePage/effects.css:258 — `.cyber-particle` moves (`animation: particle-float 15s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • + 7 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×28
  • Swallowed exception (empty catch) packages/ui-tars/utio/src/index.ts:31 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/common/electron-build/src/findUp.ts:46 — 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/common/electron-build/src/findUp.ts:77 — 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/agent-infra/shared/src/common/promise-queue.ts:50 — 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/agent-infra/browser-use/src/dom/views.ts:519 — 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/agent-infra/browser/src/browser-finder/chrome-paths.ts:40 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/agent-infra/browser/src/browser-finder/firefox-paths.ts:19 — 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) multimodal/tarko/ui/src/components/ai/BrowserShell.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) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/TerminalRenderer.tsx:126 — 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) multimodal/tarko/agent-ui/src/common/services/authToken.ts:38 — 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) multimodal/tarko/agent-ui/src/common/constants/iframeSandbox.ts:44 — 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) multimodal/tarko/agent-server-next/src/dao/sqlite/SQLiteDAOFactory.ts:160 — 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) multimodal/tarko/agent-server-next/src/controllers/system.ts:67 — 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) REDACTED: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) multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:274 — 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) multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:344 — 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) REDACTED:87 — 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) REDACTED: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) multimodal/tarko/agent-cli/src/agio/AgioBatchProcessor.ts:107 — 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) multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:498 — 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) multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:554 — 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) multimodal/agent-tars/core/src/environments/local/browser/browser-manager.ts:151 — `.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) multimodal/agent-tars/core/src/environments/local/browser/browser-manager.ts:153 — 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) REDACTED:364 — 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) REDACTED:417 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 3 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Fake-async · ×19
  • Fake-async — async method never awaits apps/ui-tars/src/main/logger.ts:67 — `cleanupOldLogs` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits apps/ui-tars/src/main/utils/agent.ts:63 — `beforeAgentRun` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits apps/ui-tars/src/main/window/index.ts:63 — `showWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits apps/ui-tars/src/main/window/index.ts:70 — `hideMainWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits apps/ui-tars/src/main/window/index.ts:81 — `showMainWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits infra/pdk/src/commands/changelog.ts:29 — `updateChangelogFile` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits infra/pdk/src/commands/next-version.ts:20 — `nextVersion` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits infra/pdk/src/utils/ai-changelog.ts:292 — `updateChangelogFile` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits infra/pdk/src/utils/dependencies.ts:132 — `restorePackageDependencies` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits multimodal/gui-agent/cli/src/cli/start.ts:162 — `resetConfig` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits multimodal/tarko/agent-server-next/src/server.ts:365 — `initializeMultiTenantServices` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits multimodal/tarko/agent-server-next/src/services/session/AgentSessionPool.ts:151 — `stopMemoryMonitoring` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/executor.ts:320 — `cancel` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/executor.ts:324 — `resume` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/executor.ts:328 — `pause` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/types.ts:106 — `pause` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/types.ts:110 — `resume` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/agent-infra/browser-use/src/agent/types.ts:114 — `stop` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits REDACTED:84 — `buildReport` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
X2 · Cancellation propagation · Async function without AbortSignal · ×19
  • Async function without AbortSignal: send packages/ui-tars/utio/src/index.ts:16 — `send` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: search packages/agent-infra/search/search/src/searxng.ts:35 — `search` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: search packages/agent-infra/search/bing-search/src/api-client.ts:226 — `search` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: activate packages/agent-infra/mcp-client/src/index.ts:212 — `activate` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: launch packages/agent-infra/browser/src/remote-browser.ts:55 — `launch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: create multimodal/tarko/llm-client/src/handlers/ai21.ts:216 — `create` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: fetchImageAsBase64 multimodal/tarko/llm-client/src/handlers/utils.ts:164 — `fetchImageAsBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: getHtmlContent multimodal/tarko/agent-ui-builder/src/builder.ts:85 — `getHtmlContent` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: upload multimodal/tarko/agent-ui-builder/src/builder.ts:117 — `upload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: getShareConfig multimodal/tarko/agent-ui/src/standalone/share/shareService.ts:33 — `getShareConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: shareSession multimodal/tarko/agent-ui/src/standalone/share/shareService.ts:62 — `shareSession` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: imageToBase64 multimodal/tarko/agent-ui/src/common/utils/clipboard.ts:9 — `imageToBase64` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: uploadWorkspaceImage multimodal/tarko/agent-server-next/src/services/ShareService.ts:341 — `uploadWorkspaceImage` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: uploadWorkspaceImage multimodal/tarko/agent-server/src/services/ShareService.ts:337 — `uploadWorkspaceImage` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: processServerRun multimodal/tarko/agent-cli/src/core/commands/run.ts:66 — `processServerRun` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: loadRemoteConfig multimodal/tarko/agent-cli/src/config/loader.ts:25 — `loadRemoteConfig` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: uploadReport apps/ui-tars/src/renderer/src/utils/share.ts:1 — `uploadReport` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: importPresetFromUrl apps/ui-tars/src/main/store/setting.ts:89 — `importPresetFromUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: fetchPresetFromUrl apps/ui-tars/src/main/store/setting.ts:132 — `fetchPresetFromUrl` 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 })`.
D3 · God Classes · MethodTooLong · ×18
  • MethodTooLong: GUIAgent.run packages/ui-tars/sdk/src/GUIAgent.ts:66 — MethodTooLong — run runs 284 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 184 over it, 2.84× 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.
  • MethodTooLong: ActionBuilder.buildDefaultActions packages/agent-infra/browser-use/src/agent/actions/builder.ts:123 — MethodTooLong — buildDefaultActions runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.62× 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.
  • MethodTooLong: UIHelper.injectStyles multimodal/gui-agent/operator-browser/src/ui-helper.ts:609 — MethodTooLong — injectStyles runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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.
  • MethodTooLong: RemoteComputerOperator.execute apps/ui-tars/src/main/remote/operators.ts:101 — MethodTooLong — execute runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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.
  • MethodTooLong: UIHelper.injectStyles packages/ui-tars/operators/browser-operator/src/ui-helper.ts:34 — MethodTooLong — injectStyles runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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.
  • MethodTooLong: NutJSOperator.execute packages/ui-tars/operators/nut-js/src/index.ts:94 — MethodTooLong — execute runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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.
  • MethodTooLong: AdbOperator.execute packages/ui-tars/operators/adb/src/index.ts:111 — MethodTooLong — execute runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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.
  • MethodTooLong: ToolProcessor.processToolCalls multimodal/tarko/agent/src/agent/runner/tool-processor.ts:154 — MethodTooLong — processToolCalls runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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.
  • MethodTooLong: SQLiteStorageProvider.performJsonSchemaMigration multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:170 — MethodTooLong — performJsonSchemaMigration runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.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.
  • MethodTooLong: LLMProcessor.handleStreamingResponse multimodal/tarko/agent/src/agent/runner/llm-processor.ts:280 — MethodTooLong — handleStreamingResponse runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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.
  • MethodTooLong: CustomGitHubProvider.getLatestVersion apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:53 — MethodTooLong — getLatestVersion runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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.
  • MethodTooLong: AIOHybridOperator.singleActionExecutor multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:127 — MethodTooLong — singleActionExecutor runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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.
  • MethodTooLong: NutJSOperator.singleActionExecutor multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:127 — MethodTooLong — singleActionExecutor runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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.
  • MethodTooLong: LoopExecutor.executeLoop multimodal/tarko/agent/src/agent/runner/loop-executor.ts:50 — MethodTooLong — executeLoop 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.
  • MethodTooLong: StreamingToolCallHandler.handle multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:226 — MethodTooLong — handle runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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.
  • MethodTooLong: UIHelper.highlightClickableElements packages/ui-tars/operators/browser-operator/src/ui-helper.ts:492 — MethodTooLong — highlightClickableElements runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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.
  • MethodTooLong: UIHelper.highlightClickableElementsInner multimodal/gui-agent/operator-browser/src/ui-helper.ts:162 — MethodTooLong — highlightClickableElementsInner runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ToolResultHandler.handle multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:59 — MethodTooLong — handle runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D12 · Dependency Hygiene · Deprecated · ×17
  • Deprecated: eslint REDACTED:111 — eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @types/string-width REDACTED:48 — @types/string-width 4.0.1, declared in REDACTED, is marked deprecated by its publisher: "This is a stub types definition. string-width provides its own type definitions, so you do not need this installed.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf REDACTED:50 — rimraf 4.1.0, declared in REDACTED, is marked deprecated by its publisher: "Please upgrade to 4.3.1 or higher to fix a potentially damaging issue regarding symbolic link following. See https://github.com/isaacs/rimraf/issues/259 for details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: uuid multimodal/gui-agent/agent-sdk/package.json:51 — uuid 9.0.1, declared in multimodal/gui-agent/agent-sdk/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: uuid multimodal/tarko/agent-ui/package.json:16 — uuid 9.0.1, declared in multimodal/tarko/agent-ui/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: uuid multimodal/tarko/agent/package.json:44 — uuid 9.0.1, declared in multimodal/tarko/agent/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @nextui-org/button multimodal/websites/main/package.json:10 — @nextui-org/button 2.0.38, declared in multimodal/websites/main/package.json, is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/button instead.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @nextui-org/react multimodal/websites/main/package.json:11 — @nextui-org/react 2.4.8, declared in multimodal/websites/main/package.json, is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/react instead.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint REDACTED:42 — eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: glob packages/agent-infra/mcp-client/package.json:38 — glob 10.4.5, declared in packages/agent-infra/mcp-client/package.json, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: glob packages/agent-infra/mcp-servers/filesystem/package.json:44 — glob 10.4.5, declared in packages/agent-infra/mcp-servers/filesystem/package.json, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf packages/agent-infra/search/bing-search/package.json:33 — rimraf 4.1.0, declared in packages/agent-infra/search/bing-search/package.json, is marked deprecated by its publisher: "Please upgrade to 4.3.1 or higher to fix a potentially damaging issue regarding symbolic link following. See https://github.com/isaacs/rimraf/issues/259 for details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf packages/agent-infra/search/browser-search/package.json:35 — rimraf 4.1.0, declared in packages/agent-infra/search/browser-search/package.json, is marked deprecated by its publisher: "Please upgrade to 4.3.1 or higher to fix a potentially damaging issue regarding symbolic link following. See https://github.com/isaacs/rimraf/issues/259 for details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf packages/agent-infra/search/duckduckgo-search/package.json:36 — rimraf 4.1.0, declared in packages/agent-infra/search/duckduckgo-search/package.json, is marked deprecated by its publisher: "Please upgrade to 4.3.1 or higher to fix a potentially damaging issue regarding symbolic link following. See https://github.com/isaacs/rimraf/issues/259 for details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf packages/agent-infra/search/search/package.json:40 — rimraf 4.1.0, declared in packages/agent-infra/search/search/package.json, is marked deprecated by its publisher: "Please upgrade to 4.3.1 or higher to fix a potentially damaging issue regarding symbolic link following. See https://github.com/isaacs/rimraf/issues/259 for details.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: @browserbasehq/stagehand packages/ui-tars/operators/browserbase/package.json:39 — @browserbasehq/stagehand 1.13.0, declared in packages/ui-tars/operators/browserbase/package.json, is marked deprecated by its publisher: "This version is no longer maintained. Please upgrade to the latest version of @browserbasehq/stagehand.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: rimraf packages/ui-tars/visualizer/package.json:72 — rimraf 3.0.2, declared in packages/ui-tars/visualizer/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
D29 · Static Analysis (SAST) · REDACTED · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×12
  • Workspace package's tests never run by CI packages/agent-infra/create-new-mcp/template-default/package.json:28 — `packages/agent-infra/create-new-mcp/template-default` is a workspace package with 2 test(s) in 1 file(s) (e.g. `packages/agent-infra/create-new-mcp/template-default/tests/server-in-memory.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-client/package.json:31 — `packages/agent-infra/mcp-client` is a workspace package with 30 test(s) in 1 file(s) (e.g. `packages/agent-infra/mcp-client/test/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-http-server/package.json:29 — `packages/agent-infra/mcp-http-server` is a workspace package with 24 test(s) in 3 file(s) (e.g. `packages/agent-infra/mcp-http-server/tests/startServer-mcpServer.test.ts`, `packages/agent-infra/mcp-http-server/tests/startServer-routes.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-servers/browser/package.json:45 — `packages/agent-infra/mcp-servers/browser` is a workspace package with 113 test(s) in 13 file(s) (e.g. `packages/agent-infra/mcp-servers/browser/tests/index.test.ts`, `packages/agent-infra/mcp-servers/browser/tests/server-in-memory.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-servers/commands/package.json:36 — `packages/agent-infra/mcp-servers/commands` is a workspace package with 7 test(s) in 2 file(s) (e.g. `packages/agent-infra/mcp-servers/commands/tests/server-in-memory.test.ts`, `packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-servers/filesystem/package.json:34 — `packages/agent-infra/mcp-servers/filesystem` is a workspace package with 3 test(s) in 1 file(s) (e.g. `packages/agent-infra/mcp-servers/filesystem/tests/server-in-memory.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/mcp-servers/search/package.json:28 — `packages/agent-infra/mcp-servers/search` is a workspace package with 1 test(s) in 1 file(s) (e.g. `packages/agent-infra/mcp-servers/search/tests/server-in-memory.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/agent-infra/shared/package.json:23 — `packages/agent-infra/shared` is a workspace package with 5 test(s) in 2 file(s) (e.g. `packages/agent-infra/shared/src/common/promise-queue.test.ts`, `packages/agent-infra/shared/tests/browser/to-markdown.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ui-tars/action-parser/package.json:26 — `packages/ui-tars/action-parser` is a workspace package with 39 test(s) in 2 file(s) (e.g. `packages/ui-tars/action-parser/test/actionParser.test.ts`, `packages/ui-tars/action-parser/test/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ui-tars/electron-ipc/package.json:35 — `packages/ui-tars/electron-ipc` is a workspace package with 3 test(s) in 1 file(s) (e.g. `packages/ui-tars/electron-ipc/test/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ui-tars/operators/nut-js/package.json:27 — `packages/ui-tars/operators/nut-js` is a workspace package with 6 test(s) in 1 file(s) (e.g. `packages/ui-tars/operators/nut-js/test/execute.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
  • Workspace package's tests never run by CI packages/ui-tars/sdk/package.json:50 — `packages/ui-tars/sdk` is a workspace package with 35 test(s) in 4 file(s) (e.g. `packages/ui-tars/sdk/src/utils.test.ts`, `packages/ui-tars/sdk/tests/GUIAgent.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
R11 · Import Boundaries · Boundary violation [package · ×12
  • Boundary violation [package:third-party-deep-import] apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:22 — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:22 imports electron-updater/out/providers/GitHubProvider, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:26 — apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:26 imports electron-updater/out/providers/Provider, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:4 — apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:4 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:deep-import] multimodal/agent-tars/core/src/environments/local/index.ts:25 — multimodal/agent-tars/core/src/environments/local/index.ts:25 imports @agent-infra/mcp-server-browser/dist/server.cjs, which the target package's REDACTED `exports` does not declare — use a declared entry or declare the subpath.
  • Boundary violation [package:relative-cross-package] multimodal/tarko/agent/snapshot/runner.ts:7 — multimodal/tarko/agent/snapshot/runner.ts:7 reaches into another package with a relative path (../../agent-snapshot) — import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] multimodal/tarko/agent/tests/agent/kernel/agent-running.test.ts:7 — multimodal/tarko/agent/tests/agent/kernel/agent-running.test.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../../agent-snapshot) — 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] multimodal/tarko/agent/tests/agent/message-history.test.ts:18 — multimodal/tarko/agent/tests/agent/message-history.test.ts:18 reaches past another workspace package's public entry into its internals with a relative path (../../../agent-snapshot/src) — 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:third-party-deep-import] multimodal/tarko/llm-client/src/handlers/gemini.ts:32 — multimodal/tarko/llm-client/src/handlers/gemini.ts:32 imports openai/src/resources/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] multimodal/tarko/llm-client/src/handlers/mistral.ts:25 — multimodal/tarko/llm-client/src/handlers/mistral.ts:25 imports openai/src/resources/index.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/agent-infra/browser-use/src/agent/messages/service.ts:24 — packages/agent-infra/browser-use/src/agent/messages/service.ts:24 imports @langchain/core/dist/messages/tool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/agent-infra/browser-use/src/browser/page.ts:9 — packages/agent-infra/browser-use/src/browser/page.ts:9 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/agent-infra/browser-use/src/browser/utils.ts:1 — packages/agent-infra/browser-use/src/browser/utils.ts:1 imports puppeteer-core/lib/esm/puppeteer/puppeteer-core-browser.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×12
  • Untrusted text written into markup unescaped multimodal/gui-agent/operator-browser/src/ui-helper.ts:395 — `actionText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped multimodal/gui-agent/operator-browser/src/ui-helper.ts:396 — `thought` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:165 — `href` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
  • Untrusted text written into markup unescaped REDACTED:172 — `sessionId?`?sessionId=${sessionId}`:''` is text this program did not author, and it is written into a URL attribute through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:191 — `sessionParam` is text this program did not author, and it is written into a URL attribute through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:201 — `title` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:217 — `sessionContext` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:218 — `sessionId` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:234 — `sessionContext` is text this program did not author, and it is written into the text of an element through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:235 — `sessionId` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/ui-tars/operators/browser-operator/src/ui-helper.ts:330 — `actionText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/ui-tars/operators/browser-operator/src/ui-helper.ts:331 — `thought` is text this program did not author, and it is written into the text of an element through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
D12 · Dependency Hygiene · One package at two majors across the workspace · ×11
  • One package at two majors across the workspace: chalk — `chalk` is maintained at 3 different major versions inside this one repository — major 2 in REDACTED; major 4 in multimodal/tarko/agent-snapshot/package.json; major 5 in multimodal/tarko/agent-server-next/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: commander — `commander` is maintained at 2 different major versions inside this one repository — major 13 in packages/agent-infra/mcp-servers/search/package.json, packages/ui-tars/cli/package.json; major 14 in multimodal/gui-agent/agent-sdk/package.json, multimodal/gui-agent/cli/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: dotenv — `dotenv` is maintained at 2 different major versions inside this one repository — major 16 in multimodal/tarko/agent-cli/package.json; major 17 in multimodal/gui-agent/agent-sdk/package.json, multimodal/tarko/agent-server-next/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: execa — `execa` is maintained at 2 different major versions inside this one repository — major 5 in packages/ui-tars/operators/adb/package.json; major 9 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: framer-motion — `framer-motion` is maintained at 2 different major versions inside this one repository — major 11 in REDACTED; major 12 in multimodal/tarko/agent-ui/package.json, multimodal/tarko/ui/package.json, multimodal/websites/main/package.json (+1 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: openai — `openai` is maintained at 2 different major versions inside this one repository — major 4 in multimodal/tarko/llm-client/package.json, multimodal/tarko/model-provider/package.json, REDACTED; major 5 in packages/ui-tars/sdk/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 18 in multimodal/tarko/agent-ui/package.json, multimodal/websites/main/package.json; major 19 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 18 in multimodal/tarko/agent-ui/package.json, multimodal/websites/main/package.json; major 19 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: react-icons — `react-icons` is maintained at 2 different major versions inside this one repository — major 4 in multimodal/tarko/agent-ui/package.json, multimodal/tarko/ui/package.json, multimodal/websites/main/package.json; major 5 in REDACTED, multimodal/websites/tarko/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: react-markdown — `react-markdown` is maintained at 2 different major versions inside this one repository — major 9 in multimodal/websites/main/package.json; major 10 in REDACTED, multimodal/tarko/ui/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
  • One package at two majors across the workspace: uuid — `uuid` is maintained at 2 different major versions inside this one repository — major 9 in multimodal/gui-agent/agent-sdk/package.json, multimodal/tarko/agent-ui/package.json, multimodal/tarko/agent/package.json; major 11 in REDACTED, packages/agent-infra/mcp-client/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: UIHelper multimodal/gui-agent/operator-browser/src/ui-helper.ts:13 — ClassTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 187 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.
  • ClassTooLong: UIHelper packages/ui-tars/operators/browser-operator/src/ui-helper.ts:13 — ClassTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 140 over it, 1.35× 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: Page packages/agent-infra/browser-use/src/browser/page.ts:71 — ClassTooLong — 529 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 129 over it, 1.32× 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: Settings apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:1 — ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 65 over it, 1.16× 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: BrowserOperator multimodal/gui-agent/operator-browser/src/browser-operator.ts:28 — ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 49 over it, 1.12× 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: ChatInput multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:1 — ClassTooLong — 443 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 43 over it, 1.11× 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: MCPClient packages/agent-infra/mcp-client/src/index.ts:48 — ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 34 over it, 1.09× 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: PromptEngineeringToolCallEngine multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:68 — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 12 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.
  • ClassTooLong: SQLiteStorageProvider multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:53 — ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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: BrowserOperator packages/ui-tars/operators/browser-operator/src/browser-operator.ts:32 — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 2 over it, 1.01× 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.
D3 · God Classes · FileTooLong · ×10
  • FileTooLong: src/ui-helper.ts multimodal/gui-agent/operator-browser/src/ui-helper.ts — FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UIHelper (13-868). The bar is 500 significant lines; this is 90 over it, 1.18× 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: remote/proxyClient.ts apps/ui-tars/src/main/remote/proxyClient.ts — FileTooLong — 585 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 85 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: browser/page.ts packages/agent-infra/browser-use/src/browser/page.ts — FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: Page (71-944). The bar is 500 significant lines; this is 82 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: component/player.tsx packages/ui-tars/visualizer/src/component/player.tsx — FileTooLong — 566 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: Player (124-802). The bar is 500 significant lines; this is 66 over it, 1.13× 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: ui/sidebar.tsx apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx — FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 65 over it, 1.13× 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/ui-helper.ts packages/ui-tars/operators/browser-operator/src/ui-helper.ts — FileTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: UIHelper (13-801). The bar is 500 significant lines; this is 43 over it, 1.09× 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/browser-operator.ts packages/ui-tars/operators/browser-operator/src/browser-operator.ts — FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: BrowserOperator (32-706). The bar is 500 significant lines; this is 26 over it, 1.05× 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: settings/Settings.tsx apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Settings (69-619). The bar is 500 significant lines; this is 20 over it, 1.04× 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: assets/buildDomTree.js packages/agent-infra/browser-use/assets/buildDomTree.js — FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× 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/server.ts packages/agent-infra/mcp-servers/browser/src/server.ts — FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 over it, 1.00× 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.
D10 · Test Quality · Skipped test · ×8
  • Skipped test: should handle fish shell command packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:35 — Skipped — switched off by test.skip
  • Skipped test: should handle command errors properly in fish packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:46 — Skipped — switched off by test.skip
  • Skipped test: should execute zsh command packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:56 — Skipped — switched off by test.skip
  • Skipped test: should handle command errors properly in zsh packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:62 — Skipped — switched off by test.skip
  • Skipped test: should handle multiline scripts in zsh packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:72 — Skipped — switched off by test.skip
  • Skipped test: should handle closing last remaining tab packages/agent-infra/mcp-servers/browser/tests/tools/tabs.test.ts:236 — Skipped — switched off by test.skip
  • Skipped test: should maintain tab state during navigation packages/agent-infra/mcp-servers/browser/tests/tools/tabs.test.ts:317 — Skipped — switched off by test.skip
  • Skipped test: repomix multimodal/tarko/context-engineer/tests/repomix.test.ts:15 — Skipped — switched off by it.skip
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D5 · Coupling · Off the main sequence · ×7
  • Off the main sequence: @tarko/config-loader — @tarko/config-loader: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: @tarko/llm-client — @tarko/llm-client: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @tarko/agent-ui-builder — @tarko/agent-ui-builder: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: @agent-infra/logger — @agent-infra/logger: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: @gui-agent/operator-browser — @gui-agent/operator-browser: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @tarko/model-provider — @tarko/model-provider: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @tarko/ui — @tarko/ui: abstractness 0.27, instability 0.00, distance 0.73 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×5
  • Both branches are identical — the condition decides nothing multimodal/omni-tars/gui-agent/src/GuiAgentPlugin.ts:161 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing multimodal/tarko/agent/src/utils/llm-requester.ts:83 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing multimodal/tarko/llm-client/src/handlers/anthropic.ts:343 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
  • Both branches are identical — the condition decides nothing multimodal/websites/docs/src/components/IntroAnimation.tsx:190 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing multimodal/websites/docs/src/components/IntroAnimation.tsx:200 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
AC1 · Text alternatives · <video> without a captions track · ×4
  • <video> without a captions track multimodal/websites/docs/src/components/IntroAnimation.tsx:250 — Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
  • <video> without a captions track multimodal/websites/docs/src/components/IntroAnimation.tsx:260 — Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
  • <video> without a captions track multimodal/websites/docs/src/components/VideoPanel.tsx:55 — Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation).
  • <video> without a captions track multimodal/websites/main/src/render/components/Home/VideoModal.tsx:28 — Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way).
AC6 · Visual & motion safety · Focus outline removed inline · ×4
  • Focus outline removed inline apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448 — <canvas> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline multimodal/tarko/agent-ui/src/standalone/modals/EventStreamModal.tsx:111 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:267 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
  • Focus outline removed inline multimodal/tarko/agent-ui/src/standalone/sidebar/SessionSearch.tsx:62 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
D1 · Cyclomatic Complexity · buildDomTree.buildDomTree · ×4
  • buildDomTree.buildDomTree::isInteractiveElement (cyclomatic 37) packages/agent-infra/browser-use/assets/buildDomTree.js:293 — buildDomTree.buildDomTree::isInteractiveElement has cyclomatic complexity 37 (threshold 15). 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. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::isTopElement, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::isTopElement (cyclomatic 33) packages/agent-infra/browser-use/assets/buildDomTree.js:490 — buildDomTree.buildDomTree::isTopElement has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::isInteractiveElement, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::buildDomTree (cyclomatic 28) packages/agent-infra/browser-use/assets/buildDomTree.js:647 — buildDomTree.buildDomTree::buildDomTree 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. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::isInteractiveElement, buildDomTree.buildDomTree::isTopElement) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::getCssSelector (cyclomatic 22) packages/agent-infra/browser-use/assets/buildDomTree.js:217 — buildDomTree.buildDomTree::getCssSelector 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. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::isInteractiveElement, buildDomTree.buildDomTree::isTopElement, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · buildDomTree.buildDomTree · ×4
  • buildDomTree.buildDomTree::buildDomTree (cognitive 42) packages/agent-infra/browser-use/assets/buildDomTree.js:647 — buildDomTree.buildDomTree::buildDomTree has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 6, ternaries 3, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getXPathTree, buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::isTopElement) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::getCssSelector (cognitive 32) packages/agent-infra/browser-use/assets/buildDomTree.js:217 — buildDomTree.buildDomTree::getCssSelector has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 8, loops 2 (3 pts), ternaries 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. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getXPathTree, buildDomTree.buildDomTree::isTopElement, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::isTopElement (cognitive 32) packages/agent-infra/browser-use/assets/buildDomTree.js:490 — buildDomTree.buildDomTree::isTopElement has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 7, loops 3 (4 pts), error handling 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. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getXPathTree, buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • buildDomTree.buildDomTree::getXPathTree (cognitive 16) packages/agent-infra/browser-use/assets/buildDomTree.js:179 — buildDomTree.buildDomTree::getXPathTree has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (5 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (buildDomTree.buildDomTree::getCssSelector, buildDomTree.buildDomTree::isTopElement, buildDomTree.buildDomTree::buildDomTree) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: REDACTED ↔ apiService.ts REDACTED:1 — `REDACTED` and `multimodal/tarko/agent-ui/src/common/services/apiService.ts` change together 64% of the time (7 of the 11 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a59d33d5` feat(tarko-agent): runtime settings (#1561); `0f4fd410` feat(tarko-agent-server): add `server.models` support (#1488); `4dcc3217` feat(tarko): support switching model at runtime (close: #1057) (#1058) (at that commit the file was still `multimodal/tarko/agent-web-ui/src/common/services/apiService.ts`) — run `git show` on any of them.
  • Change coupling: index.tsx ↔ REDACTED multimodal/tarko/agent-ui/src/standalone/app/Layout/index.tsx:1 — `multimodal/tarko/agent-ui/src/standalone/app/Layout/index.tsx` and `REDACTED` change together 60% of the time (6 of the 10 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, 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 `0a1b7cf0` feat(tarko-agent-ui): mobile ui bottom sheet (#1563); `21d59fb1` feat(tarko-agent-ui): new layout design (#1553); `f865c6df` feat(agent-tars-web-ui): simplify replay state (#989) (at that commit the files were still `multimodal/agent-tars-web-ui/src/standalone/app/Layout/index.tsx` and `multimodal/agent-tars-web-ui/src/standalone/navbar/Navbar.tsx`) — run `git show` on any of them.
  • Change coupling: builder.ts ↔ options.ts multimodal/tarko/agent-cli/src/config/builder.ts:1 — `multimodal/tarko/agent-cli/src/config/builder.ts` and `multimodal/tarko/agent-cli/src/core/options.ts` change together 50% of the time (5 of the 10 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `d634845f` fix(agent-server): require a token once the server leaves loopback (#…; `c3347f8d` fix(agent-server): block request-body injection into agent constructo…; `acfae7c4` feat(tarko): add agent server exclusive mode support (#1149) — run `git show` on any of them.
  • Change coupling: index.tsx ↔ ToolBar.tsx multimodal/tarko/agent-ui/src/standalone/app/Layout/index.tsx:1 — `multimodal/tarko/agent-ui/src/standalone/app/Layout/index.tsx` and `multimodal/tarko/agent-ui/src/standalone/sidebar/ToolBar.tsx` change together 50% of the time (5 of the 10 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `41bf5b97` feat(tarko): add event stream viewer (#1374); `21d59fb1` feat(tarko-agent-ui): new layout design (#1553); `f4510f94` feat(tarko-web-ui): narrow chat mode (#1298) (at that commit the files were still `multimodal/tarko/agent-web-ui/src/standalone/app/Layout/index.tsx` and `multimodal/tarko/agent-web-ui/src/standalone/sidebar/ToolBar.tsx`) — run `git show` on any of them.
D6 · Cohesion (LCOM4) · Low cohesion · ×4
  • Low cohesion: ApiService (LCOM4 11) multimodal/tarko/agent-ui/src/common/services/apiService.ts:51 — ApiService's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ProxyClient (LCOM4 9) apps/ui-tars/src/main/remote/proxyClient.ts:372 — ProxyClient's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AgentGenerateSnapshotHook (LCOM4 5) multimodal/tarko/agent-snapshot/src/agent-generate-snapshot-hook.ts:34 — AgentGenerateSnapshotHook's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: StructuredOutputsToolCallEngine (LCOM4 4) multimodal/tarko/agent/src/tool-call-engine/StructuredOutputsToolCallEngine.ts:34 — StructuredOutputsToolCallEngine's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) packages/agent-infra/mcp-servers/filesystem/src/server.ts:158 — `catch (error)` 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) packages/agent-infra/browser/src/base-browser.ts:284 — `catch (e)` 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) apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:245 — `catch (cdpError)` 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.
AC1 · Text alternatives · <canvas> without a text alternative · ×2
  • <canvas> without a text alternative apps/ui-tars/src/renderer/src/components/ScreenRecorder/index.tsx:44 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×2
  • Heading level jumps from h1 to h3 multimodal/websites/docs/src/components/Showcase/components/ShowcaseDetail.tsx:220 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
  • Heading level jumps from h1 to h3 multimodal/websites/main/src/render/pages/ShowcaseDetail.tsx:227 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
D1 · Cyclomatic Complexity · utils.convertToAgentUIAction (cyclomatic 26) · ×2
  • utils.convertToAgentUIAction (cyclomatic 26) multimodal/gui-agent/agent-sdk/src/utils.ts:16 — utils.convertToAgentUIAction has cyclomatic complexity 26 (threshold 15). 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.
  • utils.convertToAgentUIAction (cyclomatic 26) multimodal/omni-tars/gui-agent/src/utils.ts:17 — utils.convertToAgentUIAction has cyclomatic complexity 26 (threshold 15). 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 · config-sanitizer.sanitizeAgentOptions (cyclomatic 23) · ×2
  • config-sanitizer.sanitizeAgentOptions (cyclomatic 23) multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:10 — config-sanitizer.sanitizeAgentOptions has cyclomatic complexity 23 (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.
  • config-sanitizer.sanitizeAgentOptions (cyclomatic 23) multimodal/tarko/agent-server/src/utils/config-sanitizer.ts:10 — config-sanitizer.sanitizeAgentOptions has cyclomatic complexity 23 (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 · config-sanitizer.sanitizeAgentOptions (cognitive 24) · ×2
  • config-sanitizer.sanitizeAgentOptions (cognitive 24) multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:10 — config-sanitizer.sanitizeAgentOptions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 2 (nesting depth added 2). 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.
  • config-sanitizer.sanitizeAgentOptions (cognitive 24) multimodal/tarko/agent-server/src/utils/config-sanitizer.ts:10 — config-sanitizer.sanitizeAgentOptions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 2 (nesting depth added 2). 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 · ShareService.findImageReferences (cognitive 17) · ×2
  • ShareService.findImageReferences (cognitive 17) multimodal/tarko/agent-server-next/src/services/ShareService.ts:281 — ShareService.findImageReferences has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ShareService.findImageReferences (cognitive 17) multimodal/tarko/agent-server/src/services/ShareService.ts:277 — ShareService.findImageReferences has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SlugGenerator.manualNormalization (cognitive 16) · ×2
  • SlugGenerator.manualNormalization (cognitive 16) multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:115 — SlugGenerator.manualNormalization has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (nesting depth added 3). 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.
  • SlugGenerator.manualNormalization (cognitive 16) multimodal/tarko/agent-server/src/utils/slug-generator.ts:115 — SlugGenerator.manualNormalization has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4 (nesting depth added 3). 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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
R7 · Dead Code · Dead file (~621 LoC) · ×2
  • Dead file (~621 LoC) apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~621 LoC) REDACTED — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/navbar/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~410 LoC) · ×2
  • Dead file (~410 LoC) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/LinkReaderRenderer.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
  • Dead file (~410 LoC) packages/ui-tars/visualizer/src/component/detail-side.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~259 LoC) · ×2
  • Dead file (~259 LoC) apps/ui-tars/src/renderer/src/components/ui/dropdown-menu.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~259 LoC) apps/ui-tars/src/renderer/src/store/session.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC2 · Forms & labels · <Textarea> field component without a label · ×1
  • <Textarea> field component without a label apps/ui-tars/src/renderer/src/components/ChatInput/index.tsx:217 — This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <Slider> field component without a label · ×1
  • <Slider> field component without a label apps/ui-tars/src/renderer/src/components/ImageGallery/index.tsx:193 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <Select> field component without a label · ×1
  • <Select> field component without a label multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx:258 — This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure · Empty <h1> heading · ×1
  • Empty <h1> heading multimodal/websites/main/src/render/pages/Docs.tsx:75 — An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
AC4 · Keyboard semantics · Anchor without href · ×1
  • Anchor without href apps/ui-tars/src/renderer/src/components/CountDown/index.tsx:61 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC4 · Keyboard semantics · Positive tabindex (99) · ×1
  • Positive tabindex (99) apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:448 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.3 · ×1
  • Low contrast Tailwind colour pair (2.3:1) multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx:108 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.5 · ×1
  • Low contrast Tailwind colour pair (2.5:1) multimodal/tarko/agent-ui/src/standalone/sidebar/ToolBar.tsx:82 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (2.4 · ×1
  • Low contrast Tailwind colour pair (2.4:1) multimodal/tarko/agent-ui/src/standalone/workspace/components/FullscreenModal.tsx:76 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
AC6 · Visual & motion safety · Low contrast Tailwind colour pair (4.4 · ×1
  • Low contrast Tailwind colour pair (4.4:1) multimodal/tarko/ui/src/components/viewer/JSONViewer.tsx:157 — This element's Tailwind text/background colour utilities fall below the 4.5:1 WCAG AA minimum for normal text. Pick a darker or lighter shade.
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 270 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 · ChatInput.ChatInput (cyclomatic 94) · ×1
  • ChatInput.ChatInput (cyclomatic 94) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46 — ChatInput.ChatInput has cyclomatic complexity 94 (threshold 15). Of this number, 47 points are the body's own statements and 47 belong to 19 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 · AgentOptionsSelector.AgentOptionsSelector (cyclomatic 82) · ×1
  • AgentOptionsSelector.AgentOptionsSelector (cyclomatic 82) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:158 — AgentOptionsSelector.AgentOptionsSelector has cyclomatic complexity 82 (threshold 15). Most of this is not in the body itself: 13 of the 82 points are its own statements and the rest belongs to 15 function items inside it that branch (renderOptionItem, handleOptionChange, handleOptionRemove, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · player.Player (cyclomatic 77) · ×1
  • player.Player (cyclomatic 77) packages/ui-tars/visualizer/src/component/player.tsx:124 — player.Player has cyclomatic complexity 77 (threshold 15). Most of this is not in the body itself: 11 of the 77 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 563, updatePointer, a function literal at line 362, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · DOMElementNode.getEnhancedContextInfo (cyclomatic 74) · ×1
  • DOMElementNode.getEnhancedContextInfo (cyclomatic 74) packages/agent-infra/browser-use/src/dom/views.ts:222 — DOMElementNode.getEnhancedContextInfo has cyclomatic complexity 74 (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 · RemoteComputerOperator.execute (cyclomatic 55) · ×1
  • RemoteComputerOperator.execute (cyclomatic 55) apps/ui-tars/src/main/remote/operators.ts:101 — RemoteComputerOperator.execute has cyclomatic complexity 55 (threshold 15). Of this number, 51 points are the body's own statements and 4 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 · canvas.CDPBrowser (cyclomatic 54) · ×1
  • canvas.CDPBrowser (cyclomatic 54) apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:16 — canvas.CDPBrowser has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 4 of the 54 points are its own statements and the rest belongs to 16 function items inside it that branch (initPuppeteer::setupPageScreencast, initPuppeteer::handleTarget, handleInteraction, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · extractToolCallT5.extractToolCallT5 (cyclomatic 51) · ×1
  • extractToolCallT5.extractToolCallT5 (cyclomatic 51) multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — extractToolCallT5.extractToolCallT5 has cyclomatic complexity 51 (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 · extractCode.extractCodeEnv (cyclomatic 50) · ×1
  • extractCode.extractCodeEnv (cyclomatic 50) multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 — extractCode.extractCodeEnv 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 · Navbar.Navbar (cyclomatic 50) · ×1
  • Navbar.Navbar (cyclomatic 50) REDACTED:50 — Navbar.Navbar has cyclomatic complexity 50 (threshold 15). Of this number, 20 points are the body's own statements and 30 belong to 9 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 · server.handleToolCall (cyclomatic 47) · ×1
  • server.handleToolCall (cyclomatic 47) packages/agent-infra/mcp-servers/browser/src/server.ts:200 — server.handleToolCall has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 3 of the 47 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 224, 457, 516, …). 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 · NutJSOperator.execute (cyclomatic 47) · ×1
  • NutJSOperator.execute (cyclomatic 47) packages/ui-tars/operators/nut-js/src/index.ts:94 — NutJSOperator.execute has cyclomatic complexity 47 (threshold 15). Of this number, 44 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · AdbOperator.execute (cyclomatic 46) · ×1
  • AdbOperator.execute (cyclomatic 46) packages/ui-tars/operators/adb/src/index.ts:111 — AdbOperator.execute has cyclomatic complexity 46 (threshold 15). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ToolCalls.ToolCalls · ×1
  • ToolCalls.ToolCalls::getToolDescription (cyclomatic 44) multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx:91 — ToolCalls.ToolCalls::getToolDescription 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 · ChatSession.ChatSession (cyclomatic 44) · ×1
  • ChatSession.ChatSession (cyclomatic 44) multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx:14 — ChatSession.ChatSession has cyclomatic complexity 44 (threshold 15). Of this number, 16 points are the body's own statements and 28 belong to 12 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GUIAgent.run (cyclomatic 42) · ×1
  • GUIAgent.run (cyclomatic 42) packages/ui-tars/sdk/src/GUIAgent.ts:66 — GUIAgent.run has cyclomatic complexity 42 (threshold 15). Of this number, 38 points are the body's own statements and 4 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 · replay-scripts.generateAnimationScripts (cyclomatic 38) · ×1
  • replay-scripts.generateAnimationScripts (cyclomatic 38) packages/ui-tars/visualizer/src/component/replay-scripts.tsx:192 — replay-scripts.generateAnimationScripts has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 14 of the 38 points are its own statements and the rest belongs to one function literal inside it that branches (line 269). 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 · vlm.VLMSettings (cyclomatic 37) · ×1
  • vlm.VLMSettings (cyclomatic 37) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:58 — vlm.VLMSettings has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 126, a function literal at line 106, handleResponseApiChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · WorkspaceDetail.WorkspaceDetail (cyclomatic 37) · ×1
  • WorkspaceDetail.WorkspaceDetail (cyclomatic 37) multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx:61 — WorkspaceDetail.WorkspaceDetail has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 89, handleContentAction, getToggleConfig, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · AIOHybridOperator.singleActionExecutor (cyclomatic 36) · ×1
  • AIOHybridOperator.singleActionExecutor (cyclomatic 36) multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:127 — AIOHybridOperator.singleActionExecutor has cyclomatic complexity 36 (threshold 15). 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, 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CustomGitHubProvider.getLatestVersion (cyclomatic 35) · ×1
  • CustomGitHubProvider.getLatestVersion (cyclomatic 35) apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:53 — CustomGitHubProvider.getLatestVersion has cyclomatic complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 belong to one function item 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 · actionParser.parseActionVlm (cyclomatic 35) · ×1
  • actionParser.parseActionVlm (cyclomatic 35) REDACTED:162 — actionParser.parseActionVlm has cyclomatic complexity 35 (threshold 15). Of this number, 33 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 · ScriptResultRenderer.extractScriptData (cyclomatic 35) · ×1
  • ScriptResultRenderer.extractScriptData (cyclomatic 35) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx:173 — ScriptResultRenderer.extractScriptData has cyclomatic complexity 35 (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 · NutJSOperator.singleActionExecutor (cyclomatic 34) · ×1
  • NutJSOperator.singleActionExecutor (cyclomatic 34) multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:127 — NutJSOperator.singleActionExecutor has cyclomatic complexity 34 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · gui-agent.convertToNormalizedAction (cyclomatic 34) · ×1
  • gui-agent.convertToNormalizedAction (cyclomatic 34) multimodal/tarko/shared-utils/src/gui-agent.ts:51 — gui-agent.convertToNormalizedAction has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · SQLiteStorageProvider.performJsonSchemaMigration (cyclomatic 33) · ×1
  • SQLiteStorageProvider.performJsonSchemaMigration (cyclomatic 33) multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:170 — SQLiteStorageProvider.performJsonSchemaMigration has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WorkspaceFileManager.WorkspaceFileManager (cyclomatic 33) · ×1
  • WorkspaceFileManager.WorkspaceFileManager (cyclomatic 33) multimodal/tarko/agent-ui/src/standalone/workspace/components/WorkspaceFileManager.tsx:32 — WorkspaceFileManager.WorkspaceFileManager has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 10 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (getFileTypeBadge, getFileIcon, handleFileClick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · LLMProcessor.handleStreamingResponse (cyclomatic 33) · ×1
  • LLMProcessor.handleStreamingResponse (cyclomatic 33) multimodal/tarko/agent/src/agent/runner/llm-processor.ts:280 — LLMProcessor.handleStreamingResponse has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BrowserOperator.execute (cyclomatic 33) · ×1
  • BrowserOperator.execute (cyclomatic 33) packages/ui-tars/operators/browser-operator/src/browser-operator.ts:189 — BrowserOperator.execute has cyclomatic complexity 33 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · detail-panel.DetailPanel (cyclomatic 33) · ×1
  • detail-panel.DetailPanel (cyclomatic 33) packages/ui-tars/visualizer/src/component/detail-panel.tsx:40 — detail-panel.DetailPanel has cyclomatic complexity 33 (threshold 15). Of this number, 17 points are the body's own statements and 16 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · detail-side.DetailSide (cyclomatic 33) · ×1
  • detail-side.DetailSide (cyclomatic 33) packages/ui-tars/visualizer/src/component/detail-side.tsx:135 — detail-side.DetailSide has cyclomatic complexity 33 (threshold 15). Of this number, 19 points are the body's own statements and 14 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 · index.ChatInput (cyclomatic 32) · ×1
  • index.ChatInput (cyclomatic 32) apps/ui-tars/src/renderer/src/components/ChatInput/index.tsx:30 — index.ChatInput has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 11 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (handleKeyDown, a function literal at line 66, renderButton, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ShareModal.ShareModal (cyclomatic 32) · ×1
  • ShareModal.ShareModal (cyclomatic 32) multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:14 — ShareModal.ShareModal has cyclomatic complexity 32 (threshold 15). Of this number, 19 points are the body's own statements and 13 belong to 6 function items 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 · BaseHandler.validateInputs (cyclomatic 32) · ×1
  • BaseHandler.validateInputs (cyclomatic 32) multimodal/tarko/llm-client/src/handlers/base.ts:43 — BaseHandler.validateInputs has cyclomatic complexity 32 (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 · ImageRenderer.extractImageData (cyclomatic 31) · ×1
  • ImageRenderer.extractImageData (cyclomatic 31) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ImageRenderer.tsx:96 — ImageRenderer.extractImageData has cyclomatic complexity 31 (threshold 15). Of this number, 23 points are the body's own statements and 8 belong to one function literal inside it that branches. 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 · useScreenshots.useScreenshots (cyclomatic 31) · ×1
  • useScreenshots.useScreenshots (cyclomatic 31) multimodal/tarko/ui/src/components/gui-agent/useScreenshots.ts:19 — useScreenshots.useScreenshots has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 1 of the 31 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 26, 69, 74). 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 · actionParser.parseActionVlm (cyclomatic 31) · ×1
  • actionParser.parseActionVlm (cyclomatic 31) REDACTED:92 — actionParser.parseActionVlm has cyclomatic complexity 31 (threshold 15). Of this number, 29 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 · free.RemoteOperator (cyclomatic 30) · ×1
  • free.RemoteOperator (cyclomatic 30) apps/ui-tars/src/renderer/src/pages/remote/free.tsx:51 — free.RemoteOperator has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 153, renderChatList, a function literal at line 274, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ContextualSelector.ContextualSelector (cyclomatic 30) · ×1
  • ContextualSelector.ContextualSelector (cyclomatic 30) multimodal/tarko/agent-ui/src/standalone/chat/ContextualSelector.tsx:35 — ContextualSelector.ContextualSelector has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 100, getItemIcon, a function literal at line 47, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · extractChatContentT5.extractChatContentT5 (cyclomatic 29) · ×1
  • extractChatContentT5.extractChatContentT5 (cyclomatic 29) multimodal/omni-tars/core/src/utils/streamingParserT5/extractChatContentT5.ts:19 — extractChatContentT5.extractChatContentT5 has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function item 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 · WelcomePage.WelcomePage (cyclomatic 29) · ×1
  • WelcomePage.WelcomePage (cyclomatic 29) multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx:16 — WelcomePage.WelcomePage has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 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 · IntroAnimation.IntroAnimation (cyclomatic 29) · ×1
  • IntroAnimation.IntroAnimation (cyclomatic 29) multimodal/websites/docs/src/components/IntroAnimation.tsx:7 — IntroAnimation.IntroAnimation has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 8 function items inside it that branch (getVideoClassName, a function literal at line 34, a function literal at line 46, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · startServer.startSseAndStreamableHttpMcpServer (cyclomatic 29) · ×1
  • startServer.startSseAndStreamableHttpMcpServer (cyclomatic 29) REDACTED:60 — startServer.startSseAndStreamableHttpMcpServer has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 9 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 159, buildPath, a function literal at line 100, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · index.Widget (cyclomatic 28) · ×1
  • index.Widget (cyclomatic 28) apps/ui-tars/src/renderer/src/pages/widget/index.tsx:63 — index.Widget has cyclomatic complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 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 · release.release (cyclomatic 28) · ×1
  • release.release (cyclomatic 28) infra/pdk/src/commands/release.ts:47 — release.release has cyclomatic complexity 28 (threshold 15). Of this number, 27 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 · ModelSelector.NavbarModelSelector (cyclomatic 28) · ×1
  • ModelSelector.NavbarModelSelector (cyclomatic 28) multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx:143 — ModelSelector.NavbarModelSelector has cyclomatic complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 6 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 · paid.RemoteOperator (cyclomatic 27) · ×1
  • paid.RemoteOperator (cyclomatic 27) apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:50 — paid.RemoteOperator has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 6 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 114, renderChatList, a function literal at line 234, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · message.createMessageGroups (cyclomatic 27) · ×1
  • message.createMessageGroups (cyclomatic 27) multimodal/tarko/agent-ui/src/common/state/atoms/message.ts:36 — message.createMessageGroups has cyclomatic complexity 27 (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 · fileCollector.collectFileInfo (cyclomatic 27) · ×1
  • fileCollector.collectFileInfo (cyclomatic 27) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/utils/fileCollector.ts:8 — fileCollector.collectFileInfo has cyclomatic complexity 27 (threshold 15). Of this number, 16 points are the body's own statements and 11 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 · Select.Select (cyclomatic 27) · ×1
  • Select.Select (cyclomatic 27) multimodal/tarko/ui/src/components/basic/Select.tsx:27 — Select.Select has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 65, 157, 40, …). 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 · browser.ensureBrowser (cyclomatic 27) · ×1
  • browser.ensureBrowser (cyclomatic 27) packages/agent-infra/mcp-servers/browser/src/utils/browser.ts:103 — browser.ensureBrowser has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 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 · ShareOptions.ShareOptions (cyclomatic 26) · ×1
  • ShareOptions.ShareOptions (cyclomatic 26) apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:38 — ShareOptions.ShareOptions has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 7 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (processShare, handleShare, a function literal at line 225, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · session.useSessionStore (cyclomatic 26) · ×1
  • session.useSessionStore (cyclomatic 26) apps/ui-tars/src/renderer/src/store/session.ts:56 — session.useSessionStore has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 12 function literals inside it that branch (lines 222, 140, 184, …). 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 · gui-agent.convertToAgentUIAction (cyclomatic 26) · ×1
  • gui-agent.convertToAgentUIAction (cyclomatic 26) multimodal/tarko/shared-utils/src/gui-agent.ts:201 — gui-agent.convertToAgentUIAction has cyclomatic complexity 26 (threshold 15). 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 · WorkflowNodes.WorkflowNodes (cyclomatic 26) · ×1
  • WorkflowNodes.WorkflowNodes (cyclomatic 26) multimodal/websites/main/src/render/components/WorkflowNodes.tsx:75 — WorkflowNodes.WorkflowNodes has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 386, 97, 100, …). 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 · ShareService.shareSession (cyclomatic 25) · ×1
  • ShareService.shareSession (cyclomatic 25) multimodal/tarko/agent-server-next/src/services/ShareService.ts:42 — ShareService.shareSession has cyclomatic complexity 25 (threshold 15). Of this number, 23 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 · MarkdownRenderer.MarkdownRenderer (cyclomatic 25) · ×1
  • MarkdownRenderer.MarkdownRenderer (cyclomatic 25) multimodal/websites/main/src/render/components/Markdown/MarkdownRenderer.tsx:26 — MarkdownRenderer.MarkdownRenderer has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 66, 158, 47, …). 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 · DocsSidebar.DocsSidebar (cyclomatic 25) · ×1
  • DocsSidebar.DocsSidebar (cyclomatic 25) multimodal/websites/main/src/render/components/DocsSidebar.tsx:9 — DocsSidebar.DocsSidebar has cyclomatic complexity 25 (threshold 15). Of this number, 21 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 · StreamingToolCallHandler.handle (cyclomatic 24) · ×1
  • StreamingToolCallHandler.handle (cyclomatic 24) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:226 — StreamingToolCallHandler.handle has cyclomatic complexity 24 (threshold 15). Of this number, 14 points are the body's own statements and 10 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 · WelcomeCards.WelcomeCards (cyclomatic 24) · ×1
  • WelcomeCards.WelcomeCards (cyclomatic 24) multimodal/tarko/agent-ui/src/standalone/home/WelcomeCards.tsx:14 — WelcomeCards.WelcomeCards has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (handleCardClick, a function literal at line 153, a function literal at line 101, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Tooltip.Tooltip (cyclomatic 24) · ×1
  • Tooltip.Tooltip (cyclomatic 24) multimodal/tarko/ui/src/components/basic/Tooltip.tsx:20 — Tooltip.Tooltip has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (getTooltipStyle, updatePosition). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · JSONViewer.JsonItem (cyclomatic 24) · ×1
  • JSONViewer.JsonItem (cyclomatic 24) multimodal/tarko/ui/src/components/viewer/JSONViewer.tsx:58 — JSONViewer.JsonItem 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 · BrowserGUIAgent.parseAction (cyclomatic 23) · ×1
  • BrowserGUIAgent.parseAction (cyclomatic 23) multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:358 — BrowserGUIAgent.parseAction has cyclomatic complexity 23 (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 · AgentSnapshot.replay (cyclomatic 23) · ×1
  • AgentSnapshot.replay (cyclomatic 23) multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:262 — AgentSnapshot.replay has cyclomatic complexity 23 (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 · index.Message (cyclomatic 23) · ×1
  • index.Message (cyclomatic 23) multimodal/tarko/agent-ui/src/standalone/chat/Message/index.tsx:26 — index.Message has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 5 function items inside it that branch (renderContent, getMessageBubbleClasses, handleToolCallClick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ToolBar.ToolBar (cyclomatic 23) · ×1
  • ToolBar.ToolBar (cyclomatic 23) multimodal/tarko/agent-ui/src/standalone/sidebar/ToolBar.tsx:21 — ToolBar.ToolBar has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. 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 · usePageMeta.usePageMeta (cyclomatic 23) · ×1
  • usePageMeta.usePageMeta (cyclomatic 23) multimodal/websites/docs/src/components/hooks/usePageMeta.ts:21 — usePageMeta.usePageMeta has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 22, 41). 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 · Executor.execute (cyclomatic 23) · ×1
  • Executor.execute (cyclomatic 23) packages/agent-infra/browser-use/src/agent/executor.ts:132 — Executor.execute has cyclomatic complexity 23 (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 · index.LocalOperator (cyclomatic 22) · ×1
  • index.LocalOperator (cyclomatic 22) apps/ui-tars/src/renderer/src/pages/local/index.tsx:49 — index.LocalOperator has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 83, renderChatList, a function literal at line 223, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · github.generateReleaseNotes (cyclomatic 22) · ×1
  • github.generateReleaseNotes (cyclomatic 22) REDACTED:106 — github.generateReleaseNotes has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 145, 214, 171, …). 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 · version.selectVersionAndTag (cyclomatic 22) · ×1
  • version.selectVersionAndTag (cyclomatic 22) infra/pdk/src/utils/version.ts:45 — version.selectVersionAndTag has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to 3 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 · McpToolCallEngine.parseContent (cyclomatic 22) · ×1
  • McpToolCallEngine.parseContent (cyclomatic 22) multimodal/omni-tars/mcp-agent/src/McpToolCallEngine.ts:90 — McpToolCallEngine.parseContent 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 · request.processRequestCommand (cyclomatic 22) · ×1
  • request.processRequestCommand (cyclomatic 22) multimodal/tarko/agent-cli/src/core/commands/request.ts:30 — request.processRequestCommand has cyclomatic complexity 22 (threshold 15). Of this number, 20 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 · ShareService.shareSession (cyclomatic 22) · ×1
  • ShareService.shareSession (cyclomatic 22) multimodal/tarko/agent-server/src/services/ShareService.ts:42 — ShareService.shareSession has cyclomatic complexity 22 (threshold 15). Of this number, 20 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 · ContextualTags.ContextualTags (cyclomatic 22) · ×1
  • ContextualTags.ContextualTags (cyclomatic 22) multimodal/tarko/agent-ui/src/standalone/chat/ContextualTags.tsx:21 — ContextualTags.ContextualTags has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (getDisplayText, a function literal at line 113, getItemIcon, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · GUIAgent.guiAgentErrorParser (cyclomatic 22) · ×1
  • GUIAgent.guiAgentErrorParser (cyclomatic 22) packages/ui-tars/sdk/src/GUIAgent.ts:527 — GUIAgent.guiAgentErrorParser has cyclomatic complexity 22 (threshold 15). 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 · PromptEngineeringToolCallEngine.processContentWithStateMachine (cyclomatic 21) · ×1
  • PromptEngineeringToolCallEngine.processContentWithStateMachine (cyclomatic 21) multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:268 — PromptEngineeringToolCallEngine.processContentWithStateMachine 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 · index.init (cyclomatic 21) · ×1
  • index.init (cyclomatic 21) packages/agent-infra/create-new-mcp/src/index.ts:92 — index.init has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.RunMessages (cyclomatic 20) · ×1
  • index.RunMessages (cyclomatic 20) apps/ui-tars/src/renderer/src/components/RunMessages/index.tsx:32 — index.RunMessages has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (renderChatList, a function literal at line 97, a function literal at line 122, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · Settings.Settings (cyclomatic 20) · ×1
  • Settings.Settings (cyclomatic 20) apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:69 — Settings.Settings has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (handleCheckForUpdates, handleUpdatePreset, handleClearSettings, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ThinkingMessageHandler.handle (cyclomatic 20) · ×1
  • ThinkingMessageHandler.handle (cyclomatic 20) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/MessageHandler.ts:238 — ThinkingMessageHandler.handle has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 248). 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 · EnvironmentInputHandler.handle (cyclomatic 20) · ×1
  • EnvironmentInputHandler.handle (cyclomatic 20) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/SystemHandler.ts:48 — EnvironmentInputHandler.handle has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 2 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 · multimodal.extractImageData (cyclomatic 20) · ×1
  • multimodal.extractImageData (cyclomatic 20) multimodal/tarko/agent/src/utils/multimodal.ts:22 — multimodal.extractImageData 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 · ToolProcessor.processToolCalls (cyclomatic 20) · ×1
  • ToolProcessor.processToolCalls (cyclomatic 20) multimodal/tarko/agent/src/agent/runner/tool-processor.ts:154 — ToolProcessor.processToolCalls has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · anthropic.convertMessages (cyclomatic 20) · ×1
  • anthropic.convertMessages (cyclomatic 20) multimodal/tarko/llm-client/src/handlers/anthropic.ts:357 — anthropic.convertMessages has cyclomatic complexity 20 (threshold 15). Of this number, 18 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 · utils.waitForStableNetwork (cyclomatic 20) · ×1
  • utils.waitForStableNetwork (cyclomatic 20) packages/agent-infra/browser-use/src/browser/utils.ts:139 — utils.waitForStableNetwork has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (onRequest, onResponse). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · timeline.TimelineWidget (cyclomatic 20) · ×1
  • timeline.TimelineWidget (cyclomatic 20) packages/ui-tars/visualizer/src/component/timeline.tsx:48 — timeline.TimelineWidget has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 135, a function literal at line 287, closestScreenshotItemOnXY, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · actionParser.actionStringParser (cyclomatic 19) · ×1
  • actionParser.actionStringParser (cyclomatic 19) REDACTED:91 — actionParser.actionStringParser 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 · extractThinkT5.extractThinkT5 (cyclomatic 19) · ×1
  • extractThinkT5.extractThinkT5 (cyclomatic 19) multimodal/omni-tars/core/src/utils/streamingParserT5/extractThinkT5.ts:59 — extractThinkT5.extractThinkT5 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 · sessions.getSessionWorkspaceFiles (cyclomatic 19) · ×1
  • sessions.getSessionWorkspaceFiles (cyclomatic 19) REDACTED:459 — sessions.getSessionWorkspaceFiles has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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 · DeliverableRenderer.DeliverableRenderer (cyclomatic 19) · ×1
  • DeliverableRenderer.DeliverableRenderer (cyclomatic 19) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DeliverableRenderer.tsx:17 — DeliverableRenderer.DeliverableRenderer has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (getDeliverableType, handleDownload). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · TabbedFilesRenderer.parseReadMultipleFilesContent (cyclomatic 19) · ×1
  • TabbedFilesRenderer.parseReadMultipleFilesContent (cyclomatic 19) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/TabbedFilesRenderer.tsx:23 — TabbedFilesRenderer.parseReadMultipleFilesContent has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 30). 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 · WorkspacePanel.WorkspacePanel (cyclomatic 19) · ×1
  • WorkspacePanel.WorkspacePanel (cyclomatic 19) multimodal/tarko/agent-ui/src/standalone/workspace/WorkspacePanel.tsx:79 — WorkspacePanel.WorkspacePanel has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 88, renderWorkspaceContent, a function literal at line 125). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ContextReferenceProcessor.processContextualReferences (cyclomatic 19) · ×1
  • ContextReferenceProcessor.processContextualReferences (cyclomatic 19) multimodal/tarko/context-engineer/src/node/context-reference-processor.ts:68 — ContextReferenceProcessor.processContextualReferences 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 · ActionBuilder.buildDefaultActions (cyclomatic 19) · ×1
  • ActionBuilder.buildDefaultActions (cyclomatic 19) packages/agent-infra/browser-use/src/agent/actions/builder.ts:123 — ActionBuilder.buildDefaultActions has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 195, 474, 271, …). 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 · server.createServer (cyclomatic 19) · ×1
  • server.createServer (cyclomatic 19) packages/agent-infra/mcp-servers/filesystem/src/server.ts:169 — server.createServer has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 351, 213, 419, …). 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 · index.ImageGallery (cyclomatic 18) · ×1
  • index.ImageGallery (cyclomatic 18) apps/ui-tars/src/renderer/src/components/ImageGallery/index.tsx:27 — index.ImageGallery has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 129, a function literal at line 35, a function literal at line 48, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · AdbOperator.singleActionExecutor (cyclomatic 18) · ×1
  • AdbOperator.singleActionExecutor (cyclomatic 18) multimodal/gui-agent/operator-adb/src/AdbOperator.ts:95 — AdbOperator.singleActionExecutor has cyclomatic complexity 18 (threshold 15). 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. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · start.startInteractiveWebUI (cyclomatic 18) · ×1
  • start.startInteractiveWebUI (cyclomatic 18) REDACTED:26 — start.startInteractiveWebUI has cyclomatic complexity 18 (threshold 15). Of this number, 17 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 · DeliverableRenderer.extractDeliverableData (cyclomatic 18) · ×1
  • DeliverableRenderer.extractDeliverableData (cyclomatic 18) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DeliverableRenderer.tsx:149 — DeliverableRenderer.extractDeliverableData 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 · FileResultRenderer.FileResultRenderer (cyclomatic 18) · ×1
  • FileResultRenderer.FileResultRenderer (cyclomatic 18) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/FileResultRenderer.tsx:18 — FileResultRenderer.FileResultRenderer 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 · multimodal.convertToMultimodalToolCallResult (cyclomatic 18) · ×1
  • multimodal.convertToMultimodalToolCallResult (cyclomatic 18) multimodal/tarko/agent/src/utils/multimodal.ts:108 — multimodal.convertToMultimodalToolCallResult 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 · index.loadConfig (cyclomatic 18) · ×1
  • index.loadConfig (cyclomatic 18) multimodal/tarko/config-loader/src/index.ts:96 — index.loadConfig has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ScreenshotDisplay.ScreenshotDisplay (cyclomatic 18) · ×1
  • ScreenshotDisplay.ScreenshotDisplay (cyclomatic 18) multimodal/tarko/ui/src/components/gui-agent/ScreenshotDisplay.tsx:22 — ScreenshotDisplay.ScreenshotDisplay has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (renderImageContent, shouldShowMouseCursor, wrapWithBrowserShell, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SearchClient.search (cyclomatic 18) · ×1
  • SearchClient.search (cyclomatic 18) packages/agent-infra/search/search/src/index.ts:132 — SearchClient.search has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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 · blackboard.Blackboard (cyclomatic 18) · ×1
  • blackboard.Blackboard (cyclomatic 18) packages/ui-tars/visualizer/src/component/blackboard.tsx:73 — blackboard.Blackboard has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 194, a function literal at line 106, a function literal at line 152, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · sidebar.Sidebar (cyclomatic 18) · ×1
  • sidebar.Sidebar (cyclomatic 18) packages/ui-tars/visualizer/src/component/sidebar.tsx:68 — sidebar.Sidebar has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 135, 124). 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 · runAgent.runAgent (cyclomatic 17) · ×1
  • runAgent.runAgent (cyclomatic 17) apps/ui-tars/src/main/services/runAgent.ts:39 — runAgent.runAgent has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (handleData, a function literal at line 61). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · vlm.ModelAvailabilityCheck (cyclomatic 17) · ×1
  • vlm.ModelAvailabilityCheck (cyclomatic 17) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:462 — vlm.ModelAvailabilityCheck has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 3 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 · share.ShareOptions · ×1
  • share.ShareOptions::processShare (cyclomatic 17) apps/ui-tars/src/renderer/src/components/SideBar/share.tsx:43 — share.ShareOptions::processShare 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 · sessions.calculateRelevanceScore (cyclomatic 17) · ×1
  • sessions.calculateRelevanceScore (cyclomatic 17) REDACTED:688 — sessions.calculateRelevanceScore 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 · useReplayMode.ReplayModeProvider (cyclomatic 17) · ×1
  • useReplayMode.ReplayModeProvider (cyclomatic 17) multimodal/tarko/agent-ui/src/common/hooks/useReplayMode.tsx:70 — useReplayMode.ReplayModeProvider has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 101, 175, 83, …). 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 · agentIconUtils.getAgentOptionIcon (cyclomatic 17) · ×1
  • agentIconUtils.getAgentOptionIcon (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/agentIconUtils.tsx:9 — agentIconUtils.getAgentOptionIcon has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ChatBottomSettings.ChatBottomSettings · ×1
  • ChatBottomSettings.ChatBottomSettings::renderChatBottomOption (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx:244 — ChatBottomSettings.ChatBottomSettings::renderChatBottomOption has cyclomatic complexity 17 (threshold 15). 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 · ChatPanel.ChatPanel (cyclomatic 17) · ×1
  • ChatPanel.ChatPanel (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/chat/ChatPanel.tsx:18 — ChatPanel.ChatPanel 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, 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 · CreatingPage.CreatingPage (cyclomatic 17) · ×1
  • CreatingPage.CreatingPage (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/home/CreatingPage.tsx:21 — CreatingPage.CreatingPage has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 39, 32). 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 · AboutModal.AboutModal (cyclomatic 17) · ×1
  • AboutModal.AboutModal (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx:17 — AboutModal.AboutModal has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 4 function items 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 · ScriptResultRenderer.ScriptResultRenderer (cyclomatic 17) · ×1
  • ScriptResultRenderer.ScriptResultRenderer (cyclomatic 17) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx:57 — ScriptResultRenderer.ScriptResultRenderer has cyclomatic complexity 17 (threshold 15). 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 · LoopExecutor.executeLoop (cyclomatic 17) · ×1
  • LoopExecutor.executeLoop (cyclomatic 17) multimodal/tarko/agent/src/agent/runner/loop-executor.ts:50 — LoopExecutor.executeLoop 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 · ShowcasePanels.ShowcasePanels (cyclomatic 17) · ×1
  • ShowcasePanels.ShowcasePanels (cyclomatic 17) multimodal/websites/docs/src/components/ShowcasePanels.tsx:24 — ShowcasePanels.ShowcasePanels has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 75, getResponsiveHeight, isSmallHeight). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · timeline.Timeline (cyclomatic 17) · ×1
  • timeline.Timeline (cyclomatic 17) packages/ui-tars/visualizer/src/component/timeline.tsx:440 — timeline.Timeline has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 456, maskConfigForTask, onHighlightItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · SelectOperator.SelectOperator (cyclomatic 16) · ×1
  • SelectOperator.SelectOperator (cyclomatic 16) apps/ui-tars/src/renderer/src/components/ChatInput/SelectOperator.tsx:57 — SelectOperator.SelectOperator has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 4 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 · FilesystemToolsManager.createSafeDirectoryTreeTool (cyclomatic 16) · ×1
  • FilesystemToolsManager.createSafeDirectoryTreeTool (cyclomatic 16) multimodal/agent-tars/core/src/environments/local/filesystem/filesystem-tools-manager.ts:139 — FilesystemToolsManager.createSafeDirectoryTreeTool has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 191, 170, 232). 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 · ActionParserHelper.standardizeAction (cyclomatic 16) · ×1
  • ActionParserHelper.standardizeAction (cyclomatic 16) multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:313 — ActionParserHelper.standardizeAction 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 · sessions.searchWorkspaceItemsRecursive (cyclomatic 16) · ×1
  • sessions.searchWorkspaceItemsRecursive (cyclomatic 16) REDACTED:603 — sessions.searchWorkspaceItemsRecursive has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (searchInDirectory, a function literal at line 665). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · BrowserResultRenderer.BrowserResultRenderer (cyclomatic 16) · ×1
  • BrowserResultRenderer.BrowserResultRenderer (cyclomatic 16) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/BrowserResultRenderer.tsx:17 — BrowserResultRenderer.BrowserResultRenderer has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function items 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 · ai21.convertMessages (cyclomatic 16) · ×1
  • ai21.convertMessages (cyclomatic 16) multimodal/tarko/llm-client/src/handlers/ai21.ts:70 — ai21.convertMessages has cyclomatic complexity 16 (threshold 15). Of this number, 14 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 · DOMElementNode.enhancedCssSelectorForElement (cyclomatic 16) · ×1
  • DOMElementNode.enhancedCssSelectorForElement (cyclomatic 16) packages/agent-infra/browser-use/src/dom/views.ts:545 — DOMElementNode.enhancedCssSelectorForElement 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 · index.Visualizer (cyclomatic 16) · ×1
  • index.Visualizer (cyclomatic 16) packages/ui-tars/visualizer/src/index.tsx:31 — index.Visualizer has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 111, 58, 67, …). 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: REDACTED REDACTED:26 — REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in start.startInteractiveWebUI at line 26. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-11..2026-10-09, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-11 09:29:51 +08:00' --until='2026-10-09 09:29:51 +08: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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment apps/ui-tars/src/main/utils/updateApp.ts:28 — // hack for custom provider — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · extractCode.extractCodeEnv (cognitive 156) · ×1
  • extractCode.extractCodeEnv (cognitive 156) multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 — extractCode.extractCodeEnv has cognitive complexity 156 (threshold 15). Drivers by points: if/else 38 (130 pts), boolean chains 19, ternaries 1 (6 pts), loops 1 (nesting depth added 97). 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 · extractToolCallT5.extractToolCallT5 (cognitive 150) · ×1
  • extractToolCallT5.extractToolCallT5 (cognitive 150) multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — extractToolCallT5.extractToolCallT5 has cognitive complexity 150 (threshold 15). Drivers by points: if/else 35 (121 pts), boolean chains 22, ternaries 1 (6 pts), loops 1 (nesting depth added 91). 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 · DOMElementNode.getEnhancedContextInfo (cognitive 120) · ×1
  • DOMElementNode.getEnhancedContextInfo (cognitive 120) packages/agent-infra/browser-use/src/dom/views.ts:222 — DOMElementNode.getEnhancedContextInfo has cognitive complexity 120 (threshold 15). Drivers by points: if/else 66 (112 pts), boolean chains 8 (nesting depth added 46). 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 · ChatInput.ChatInput (cognitive 102) · ×1
  • ChatInput.ChatInput (cognitive 102) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46 — ChatInput.ChatInput has cognitive complexity 102 (threshold 15). Drivers by points: if/else 29 (37 pts), ternaries 20 (34 pts), boolean chains 29, error handling 2 (nesting depth added 22). Of this number, 49 points are the body's own statements and 53 belong to 19 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 · player.Player (cognitive 96) · ×1
  • player.Player (cognitive 96) packages/ui-tars/visualizer/src/component/player.tsx:124 — player.Player has cognitive complexity 96 (threshold 15). Drivers by points: if/else 53 (72 pts), boolean chains 15, loops 3 (4 pts), ternaries 4, error handling 1 (nesting depth added 20). Most of this is not in the body itself: 9 of the 96 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 563, updatePointer, a function literal at line 362, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AgentOptionsSelector.AgentOptionsSelector (cognitive 84) · ×1
  • AgentOptionsSelector.AgentOptionsSelector (cognitive 84) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:158 — AgentOptionsSelector.AgentOptionsSelector has cognitive complexity 84 (threshold 15). Drivers by points: if/else 32 (36 pts), boolean chains 31, ternaries 9 (14 pts), error handling 3 (nesting depth added 9). Most of this is not in the body itself: 9 of the 84 points are its own statements and the rest belongs to 15 function items inside it that branch (renderOptionItem, handleOptionChange, handleOptionRemove, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · actionParser.parseActionVlm (cognitive 73) · ×1
  • actionParser.parseActionVlm (cognitive 73) REDACTED:162 — actionParser.parseActionVlm has cognitive complexity 73 (threshold 15). Drivers by points: if/else 21 (50 pts), ternaries 4 (12 pts), boolean chains 7, loops 2 (4 pts) (nesting depth added 39). Of this number, 67 points are the body's own statements and 6 belong to one function literal inside it that branches. 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 · extractThinkT5.extractThinkT5 (cognitive 70) · ×1
  • extractThinkT5.extractThinkT5 (cognitive 70) multimodal/omni-tars/core/src/utils/streamingParserT5/extractThinkT5.ts:59 — extractThinkT5.extractThinkT5 has cognitive complexity 70 (threshold 15). Drivers by points: if/else 16 (53 pts), loops 5 (17 pts) (nesting depth added 49). 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 · actionParser.parseActionVlm (cognitive 67) · ×1
  • actionParser.parseActionVlm (cognitive 67) REDACTED:92 — actionParser.parseActionVlm has cognitive complexity 67 (threshold 15). Drivers by points: if/else 18 (45 pts), ternaries 4 (12 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 37). Of this number, 61 points are the body's own statements and 6 belong to one function literal inside it that branches. 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 · extractChatContentT5.extractChatContentT5 (cognitive 63) · ×1
  • extractChatContentT5.extractChatContentT5 (cognitive 63) multimodal/omni-tars/core/src/utils/streamingParserT5/extractChatContentT5.ts:19 — extractChatContentT5.extractChatContentT5 has cognitive complexity 63 (threshold 15). Drivers by points: if/else 21 (51 pts), loops 4 (7 pts), boolean chains 5 (nesting depth added 33). Of this number, 61 points are the body's own statements and 2 belong to one function item inside it that branches. 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 · server.handleToolCall (cognitive 62) · ×1
  • server.handleToolCall (cognitive 62) packages/agent-infra/mcp-servers/browser/src/server.ts:200 — server.handleToolCall has cognitive complexity 62 (threshold 15). Drivers by points: if/else 24 (29 pts), ternaries 11 (18 pts), error handling 10 (11 pts), boolean chains 4 (nesting depth added 13). Most of this is not in the body itself: 2 of the 62 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 352, 457, 516, …). 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 · GUIAgent.run (cognitive 62) · ×1
  • GUIAgent.run (cognitive 62) packages/ui-tars/sdk/src/GUIAgent.ts:66 — GUIAgent.run has cognitive complexity 62 (threshold 15). Drivers by points: if/else 19 (40 pts), boolean chains 16, error handling 2 (3 pts), loops 2 (3 pts) (nesting depth added 23). Of this number, 55 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 · replay-scripts.generateAnimationScripts (cognitive 62) · ×1
  • replay-scripts.generateAnimationScripts (cognitive 62) packages/ui-tars/visualizer/src/component/replay-scripts.tsx:192 — replay-scripts.generateAnimationScripts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 25 (40 pts), ternaries 5 (11 pts), boolean chains 9, loops 1 (2 pts) (nesting depth added 22). Of this number, 19 points are the body's own statements and 43 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 · BaseHandler.validateInputs (cognitive 61) · ×1
  • BaseHandler.validateInputs (cognitive 61) multimodal/tarko/llm-client/src/handlers/base.ts:43 — BaseHandler.validateInputs has cognitive complexity 61 (threshold 15). Drivers by points: if/else 19 (43 pts), loops 4 (11 pts), boolean chains 7 (nesting depth added 31). 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 · canvas.CDPBrowser (cognitive 59) · ×1
  • canvas.CDPBrowser (cognitive 59) apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:16 — canvas.CDPBrowser has cognitive complexity 59 (threshold 15). Drivers by points: if/else 26 (31 pts), ternaries 6 (12 pts), boolean chains 10, error handling 5, loops 1 (nesting depth added 11). Most of this is not in the body itself: 3 of the 59 points are its own statements and the rest belongs to 16 function items inside it that branch (initPuppeteer::handleTarget, initPuppeteer::setupPageScreencast, initPuppeteer, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · RemoteComputerOperator.execute (cognitive 57) · ×1
  • RemoteComputerOperator.execute (cognitive 57) apps/ui-tars/src/main/remote/operators.ts:101 — RemoteComputerOperator.execute has cognitive complexity 57 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 12, ternaries 6 (12 pts), match/switch 1 (nesting depth added 19). Of this number, 50 points are the body's own statements and 7 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 · SQLiteStorageProvider.performJsonSchemaMigration (cognitive 56) · ×1
  • SQLiteStorageProvider.performJsonSchemaMigration (cognitive 56) multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:170 — SQLiteStorageProvider.performJsonSchemaMigration has cognitive complexity 56 (threshold 15). Drivers by points: if/else 12 (21 pts), error handling 7 (18 pts), ternaries 8 (12 pts), loops 2 (3 pts), boolean chains 2 (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 · PromptEngineeringToolCallEngine.processContentWithStateMachine (cognitive 56) · ×1
  • PromptEngineeringToolCallEngine.processContentWithStateMachine (cognitive 56) multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:268 — PromptEngineeringToolCallEngine.processContentWithStateMachine has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (47 pts), loops 2 (6 pts), match/switch 1 (2 pts), ternaries 1 (nesting depth added 37). 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 · ScriptResultRenderer.extractScriptData (cognitive 55) · ×1
  • ScriptResultRenderer.extractScriptData (cognitive 55) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx:173 — ScriptResultRenderer.extractScriptData has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 7 (21 pts), if/else 10 (18 pts), boolean chains 13, loops 1 (2 pts), error handling 1 (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 · CustomGitHubProvider.getLatestVersion (cognitive 53) · ×1
  • CustomGitHubProvider.getLatestVersion (cognitive 53) apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:53 — CustomGitHubProvider.getLatestVersion has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 15, error handling 4 (5 pts), loops 2 (5 pts) (nesting depth added 18). Of this number, 48 points are the body's own statements and 5 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 · LLMProcessor.handleStreamingResponse (cognitive 51) · ×1
  • LLMProcessor.handleStreamingResponse (cognitive 51) multimodal/tarko/agent/src/agent/runner/llm-processor.ts:280 — LLMProcessor.handleStreamingResponse has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (32 pts), boolean chains 14, loops 2 (5 pts) (nesting depth added 22). 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 · request.processRequestCommand (cognitive 49) · ×1
  • request.processRequestCommand (cognitive 49) multimodal/tarko/agent-cli/src/core/commands/request.ts:30 — request.processRequestCommand has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (42 pts), boolean chains 4, loops 1 (2 pts), error handling 1 (nesting depth added 24). Of this number, 47 points are the body's own statements and 2 belong to one function literal inside it that branches. 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 · message.createMessageGroups (cognitive 49) · ×1
  • message.createMessageGroups (cognitive 49) multimodal/tarko/agent-ui/src/common/state/atoms/message.ts:36 — message.createMessageGroups has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (40 pts), boolean chains 8, loops 1 (nesting depth added 25). 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 · extractors.extractThink (cognitive 46) · ×1
  • extractors.extractThink (cognitive 46) multimodal/omni-tars/core/src/utils/streamingParser/extractors.ts:14 — extractors.extractThink has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (37 pts), loops 3 (9 pts) (nesting depth added 30). 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 · Navbar.Navbar (cognitive 46) · ×1
  • Navbar.Navbar (cognitive 46) REDACTED:50 — Navbar.Navbar has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 16, ternaries 6 (7 pts), error handling 2 (5 pts) (nesting depth added 9). Of this number, 16 points are the body's own statements and 30 belong to 9 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 · extractors.extractAnswer (cognitive 45) · ×1
  • extractors.extractAnswer (cognitive 45) multimodal/omni-tars/core/src/utils/streamingParser/extractors.ts:110 — extractors.extractAnswer has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (36 pts), loops 3 (9 pts) (nesting depth added 30). 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 · ToolCalls.ToolCalls · ×1
  • ToolCalls.ToolCalls::getToolDescription (cognitive 45) multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx:91 — ToolCalls.ToolCalls::getToolDescription has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 13 (30 pts), boolean chains 9, if/else 2 (4 pts), error handling 1, match/switch 1 (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 · SimpleDiffer.groupChangesIntoHunks (cognitive 41) · ×1
  • SimpleDiffer.groupChangesIntoHunks (cognitive 41) multimodal/tarko/agent-snapshot/src/utils/snapshot-normalizer.ts:173 — SimpleDiffer.groupChangesIntoHunks has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (28 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 26). 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 · vlm.VLMSettings (cognitive 40) · ×1
  • vlm.VLMSettings (cognitive 40) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:58 — vlm.VLMSettings has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 13, ternaries 3 (4 pts), error handling 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 40 points are its own statements and the rest belongs to 7 function items inside it that branch (handleResponseApiChange, a function literal at line 126, a function literal at line 106, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ChatSession.ChatSession (cognitive 40) · ×1
  • ChatSession.ChatSession (cognitive 40) multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx:14 — ChatSession.ChatSession has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 13, ternaries 7 (9 pts), error handling 3 (nesting depth added 3). Most of this is not in the body itself: 13 of the 40 points are its own statements and the rest belongs to 12 function literals inside it that branch (lines 201, 115, 306, …). 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 · ContextualSelector.ContextualSelector (cognitive 39) · ×1
  • ContextualSelector.ContextualSelector (cognitive 39) multimodal/tarko/agent-ui/src/standalone/chat/ContextualSelector.tsx:35 — ContextualSelector.ContextualSelector has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 11 (18 pts), if/else 15 (17 pts), boolean chains 2, error handling 1, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 9 of the 39 points are its own statements and the rest belongs to 8 function items inside it that branch (getItemIcon, a function literal at line 47, a function literal at line 100, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Executor.execute (cognitive 39) · ×1
  • Executor.execute (cognitive 39) packages/agent-infra/browser-use/src/agent/executor.ts:132 — Executor.execute has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (30 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1, loops 1 (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 · browser.ensureBrowser (cognitive 39) · ×1
  • browser.ensureBrowser (cognitive 39) packages/agent-infra/mcp-servers/browser/src/utils/browser.ts:103 — browser.ensureBrowser has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 6, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 14). Of this number, 24 points are the body's own statements and 15 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 · release.release (cognitive 38) · ×1
  • release.release (cognitive 38) infra/pdk/src/commands/release.ts:47 — release.release has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (31 pts), boolean chains 5, error handling 1, ternaries 1 (nesting depth added 9). Of this number, 36 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 · multimodal.convertToMultimodalToolCallResult (cognitive 38) · ×1
  • multimodal.convertToMultimodalToolCallResult (cognitive 38) multimodal/tarko/agent/src/utils/multimodal.ts:108 — multimodal.convertToMultimodalToolCallResult has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (29 pts), error handling 2 (4 pts), boolean chains 3, loops 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 · NutJSOperator.execute (cognitive 38) · ×1
  • NutJSOperator.execute (cognitive 38) packages/ui-tars/operators/nut-js/src/index.ts:94 — NutJSOperator.execute has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 7, ternaries 2 (4 pts), match/switch 2 (3 pts) (nesting depth added 15). Of this number, 32 points are the body's own statements and 6 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 · WorkspaceDetail.WorkspaceDetail (cognitive 37) · ×1
  • WorkspaceDetail.WorkspaceDetail (cognitive 37) multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx:61 — WorkspaceDetail.WorkspaceDetail has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 11, match/switch 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 10 function items inside it that branch (getToggleConfig, handleContentAction, renderContent, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AdbOperator.execute (cognitive 37) · ×1
  • AdbOperator.execute (cognitive 37) packages/ui-tars/operators/adb/src/index.ts:111 — AdbOperator.execute has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 9, match/switch 3 (5 pts), ternaries 1 (3 pts), error handling 1 (nesting depth added 14). Of this number, 36 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 · detail-panel.DetailPanel (cognitive 37) · ×1
  • detail-panel.DetailPanel (cognitive 37) packages/ui-tars/visualizer/src/component/detail-panel.tsx:40 — detail-panel.DetailPanel has cognitive complexity 37 (threshold 15). Drivers by points: if/else 23 (26 pts), ternaries 6 (7 pts), boolean chains 4 (nesting depth added 4). Of this number, 19 points are the body's own statements and 18 belong to 6 function literals 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 · ToolProcessor.processToolCalls (cognitive 36) · ×1
  • ToolProcessor.processToolCalls (cognitive 36) multimodal/tarko/agent/src/agent/runner/tool-processor.ts:154 — ToolProcessor.processToolCalls has cognitive complexity 36 (threshold 15). Drivers by points: error handling 7 (17 pts), if/else 7 (12 pts), boolean chains 4, loops 2 (3 pts) (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 · session.useSessionStore (cognitive 35) · ×1
  • session.useSessionStore (cognitive 35) apps/ui-tars/src/renderer/src/store/session.ts:56 — session.useSessionStore has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 11 (21 pts), error handling 9, if/else 3, boolean chains 2 (nesting depth added 10). None of this is in the body itself: all 35 points belong to 12 function literals inside it that branch (lines 222, 140, 184, …). 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 · ShareService.shareSession (cognitive 33) · ×1
  • ShareService.shareSession (cognitive 33) multimodal/tarko/agent-server-next/src/services/ShareService.ts:42 — ShareService.shareSession has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 8, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 10). Of this number, 32 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 · anthropic.convertMessages (cognitive 33) · ×1
  • anthropic.convertMessages (cognitive 33) multimodal/tarko/llm-client/src/handlers/anthropic.ts:357 — anthropic.convertMessages has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 3 (9 pts), boolean chains 3, loops 1 (nesting depth added 14). Of this number, 25 points are the body's own statements and 8 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 · McpToolCallEngine.parseContent (cognitive 32) · ×1
  • McpToolCallEngine.parseContent (cognitive 32) multimodal/omni-tars/mcp-agent/src/McpToolCallEngine.ts:90 — McpToolCallEngine.parseContent has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 4 (9 pts), boolean chains 4 (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 · start.startInteractiveWebUI (cognitive 32) · ×1
  • start.startInteractiveWebUI (cognitive 32) REDACTED:26 — start.startInteractiveWebUI has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 6 (14 pts), boolean chains 3 (nesting depth added 14). Of this number, 29 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 · ContextReferenceProcessor.processContextualReferences (cognitive 32) · ×1
  • ContextReferenceProcessor.processContextualReferences (cognitive 32) multimodal/tarko/context-engineer/src/node/context-reference-processor.ts:68 — ContextReferenceProcessor.processContextualReferences has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 4 (8 pts), error handling 3 (7 pts) (nesting depth added 14). Of this number, 30 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 · ai21.convertMessages (cognitive 32) · ×1
  • ai21.convertMessages (cognitive 32) multimodal/tarko/llm-client/src/handlers/ai21.ts:70 — ai21.convertMessages has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 3 (12 pts), boolean chains 3, loops 1 (nesting depth added 17). Of this number, 22 points are the body's own statements and 10 belong to one function literal inside it that branches. 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 · free.RemoteOperator (cognitive 31) · ×1
  • free.RemoteOperator (cognitive 31) apps/ui-tars/src/renderer/src/pages/remote/free.tsx:51 — free.RemoteOperator has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 8, ternaries 4 (nesting depth added 2). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 153, a function literal at line 274, a function literal at line 96, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · github.generateReleaseNotes (cognitive 31) · ×1
  • github.generateReleaseNotes (cognitive 31) REDACTED:106 — github.generateReleaseNotes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 5 (9 pts), boolean chains 5, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 145, 214, 171, …). 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 · BrowserGUIAgent.parseAction (cognitive 31) · ×1
  • BrowserGUIAgent.parseAction (cognitive 31) multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:358 — BrowserGUIAgent.parseAction has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 6, ternaries 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 · TabbedFilesRenderer.parseReadMultipleFilesContent (cognitive 31) · ×1
  • TabbedFilesRenderer.parseReadMultipleFilesContent (cognitive 31) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/TabbedFilesRenderer.tsx:23 — TabbedFilesRenderer.parseReadMultipleFilesContent has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 4, loops 1 (nesting depth added 14). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to one function literal inside it that branches (line 30). 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 · useScreenshots.useScreenshots (cognitive 31) · ×1
  • useScreenshots.useScreenshots (cognitive 31) multimodal/tarko/ui/src/components/gui-agent/useScreenshots.ts:19 — useScreenshots.useScreenshots has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 10, loops 2, match/switch 1, ternaries 1 (nesting depth added 5). None of this is in the body itself: all 31 points belong to 3 function literals inside it that branch (lines 26, 69, 74). 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 · JSONViewer.JsonItem (cognitive 31) · ×1
  • JSONViewer.JsonItem (cognitive 31) multimodal/tarko/ui/src/components/viewer/JSONViewer.tsx:58 — JSONViewer.JsonItem has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 12 (24 pts), boolean chains 6, if/else 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 · index.Widget (cognitive 30) · ×1
  • index.Widget (cognitive 30) apps/ui-tars/src/renderer/src/pages/widget/index.tsx:63 — index.Widget has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 17, if/else 8 (9 pts), ternaries 3 (4 pts) (nesting depth added 2). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 71, 129, 122). 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 · ShareService.shareSession (cognitive 30) · ×1
  • ShareService.shareSession (cognitive 30) multimodal/tarko/agent-server/src/services/ShareService.ts:42 — ShareService.shareSession has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 6, error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 10). Of this number, 29 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 · TerminalRenderer.formatOutput (cognitive 30) · ×1
  • TerminalRenderer.formatOutput (cognitive 30) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/TerminalRenderer.tsx:111 — TerminalRenderer.formatOutput has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 2 (7 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LoopExecutor.executeLoop (cognitive 30) · ×1
  • LoopExecutor.executeLoop (cognitive 30) multimodal/tarko/agent/src/agent/runner/loop-executor.ts:50 — LoopExecutor.executeLoop has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 5, error handling 2 (5 pts), 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 · startServer.startSseAndStreamableHttpMcpServer (cognitive 30) · ×1
  • startServer.startSseAndStreamableHttpMcpServer (cognitive 30) REDACTED:60 — startServer.startSseAndStreamableHttpMcpServer has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 10, ternaries 4 (5 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 159, buildPath, a function literal at line 141, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · StreamingToolCallHandler.handle (cognitive 29) · ×1
  • StreamingToolCallHandler.handle (cognitive 29) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:226 — StreamingToolCallHandler.handle has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 5, ternaries 2 (5 pts), error handling 2 (3 pts) (nesting depth added 9). Of this number, 17 points are the body's own statements and 12 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 · detail-side.DetailSide (cognitive 29) · ×1
  • detail-side.DetailSide (cognitive 29) packages/ui-tars/visualizer/src/component/detail-side.tsx:135 — detail-side.DetailSide has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (10 pts), ternaries 7 (8 pts) (nesting depth added 2). Of this number, 19 points are the body's own statements and 10 belong to 5 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 · ShareOptions.ShareOptions · ×1
  • ShareOptions.ShareOptions::processShare (cognitive 28) apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:60 — ShareOptions.ShareOptions::processShare has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (7 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 14). 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 · AgentSnapshotRunner.cli (cognitive 28) · ×1
  • AgentSnapshotRunner.cli (cognitive 28) multimodal/tarko/agent-snapshot/src/agent-snapshot-runner.ts:53 — AgentSnapshotRunner.cli has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (28 pts) (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 · index.ChatInput (cognitive 27) · ×1
  • index.ChatInput (cognitive 27) apps/ui-tars/src/renderer/src/components/ChatInput/index.tsx:30 — index.ChatInput has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 12, if/else 10 (11 pts), ternaries 2 (3 pts), match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 7 function items inside it that branch (startRun, renderButton, getInstantInstructions, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · paid.RemoteOperator (cognitive 27) · ×1
  • paid.RemoteOperator (cognitive 27) apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:50 — paid.RemoteOperator has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 7, ternaries 4 (nesting depth added 1). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 114, a function literal at line 234, a function literal at line 89, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ModelSelector.NavbarModelSelector (cognitive 27) · ×1
  • ModelSelector.NavbarModelSelector (cognitive 27) multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx:143 — ModelSelector.NavbarModelSelector has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 10, if/else 10, ternaries 3 (5 pts), error handling 2 (nesting depth added 2). Of this number, 14 points are the body's own statements and 13 belong to 6 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 · ImageRenderer.extractImageData (cognitive 27) · ×1
  • ImageRenderer.extractImageData (cognitive 27) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ImageRenderer.tsx:96 — ImageRenderer.extractImageData has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 10, ternaries 1 (3 pts), error handling 1 (nesting depth added 6). 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 · multimodal.extractImageData (cognitive 27) · ×1
  • multimodal.extractImageData (cognitive 27) multimodal/tarko/agent/src/utils/multimodal.ts:22 — multimodal.extractImageData has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 5 (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 · stream-utils.reconstructCompletion (cognitive 27) · ×1
  • stream-utils.reconstructCompletion (cognitive 27) multimodal/tarko/agent/src/utils/stream-utils.ts:15 — stream-utils.reconstructCompletion has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (4 pts), boolean chains 3, ternaries 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 · anthropic.createCompletionResponseStreaming (cognitive 27) · ×1
  • anthropic.createCompletionResponseStreaming (cognitive 27) multimodal/tarko/llm-client/src/handlers/anthropic.ts:71 — anthropic.createCompletionResponseStreaming has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (24 pts), 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 · AgentSnapshot.replay (cognitive 26) · ×1
  • AgentSnapshot.replay (cognitive 26) multimodal/tarko/agent-snapshot/src/agent-snapshot.ts:262 — AgentSnapshot.replay has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 7, boolean chains 4, loops 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · ThinkingMessageHandler.handle (cognitive 26) · ×1
  • ThinkingMessageHandler.handle (cognitive 26) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/MessageHandler.ts:238 — ThinkingMessageHandler.handle has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (10 pts), ternaries 3 (6 pts) (nesting depth added 6). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 248). 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 · ToolResultHandler.handle (cognitive 26) · ×1
  • ToolResultHandler.handle (cognitive 26) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts:59 — ToolResultHandler.handle has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 6 (nesting depth added 11). Of this number, 20 points are the body's own statements and 6 belong to 3 function literals 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 · clipboard.handleMultimodalPaste (cognitive 26) · ×1
  • clipboard.handleMultimodalPaste (cognitive 26) multimodal/tarko/agent-ui/src/common/utils/clipboard.ts:115 — clipboard.handleMultimodalPaste has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (3 pts), boolean chains 2 (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 · FileResultRenderer.FileResultRenderer (cognitive 26) · ×1
  • FileResultRenderer.FileResultRenderer (cognitive 26) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/FileResultRenderer.tsx:18 — FileResultRenderer.FileResultRenderer has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (18 pts), boolean chains 8 (nesting depth added 10). 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 · usePageMeta.usePageMeta (cognitive 26) · ×1
  • usePageMeta.usePageMeta (cognitive 26) multimodal/websites/docs/src/components/hooks/usePageMeta.ts:21 — usePageMeta.usePageMeta has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 10, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 26 points belong to 2 function literals inside it that branch (lines 22, 41). 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 · DOMElementNode.convertSimpleXPathToCssSelector (cognitive 26) · ×1
  • DOMElementNode.convertSimpleXPathToCssSelector (cognitive 26) packages/agent-infra/browser-use/src/dom/views.ts:484 — DOMElementNode.convertSimpleXPathToCssSelector has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), error handling 1 (5 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.Message (cognitive 25) · ×1
  • index.Message (cognitive 25) multimodal/tarko/agent-ui/src/standalone/chat/Message/index.tsx:26 — index.Message has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 7, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (getMessageBubbleClasses, handleToolCallClick, renderContent, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · LinkReaderRenderer.extractLinkReaderData (cognitive 25) · ×1
  • LinkReaderRenderer.extractLinkReaderData (cognitive 25) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/LinkReaderRenderer.tsx:201 — LinkReaderRenderer.extractLinkReaderData has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 3 (6 pts), boolean chains 4 (nesting depth added 9). Of this number, 24 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 · DeliverableRenderer.extractDeliverableData (cognitive 25) · ×1
  • DeliverableRenderer.extractDeliverableData (cognitive 25) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DeliverableRenderer.tsx:149 — DeliverableRenderer.extractDeliverableData has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 5 (7 pts), boolean chains 5, error handling 1 (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 · WorkflowNodes.WorkflowNodes (cognitive 25) · ×1
  • WorkflowNodes.WorkflowNodes (cognitive 25) multimodal/websites/main/src/render/components/WorkflowNodes.tsx:75 — WorkflowNodes.WorkflowNodes has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, ternaries 11, if/else 2, loops 1. Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 386, 97, 100, …). 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 · DOMElementNode.enhancedCssSelectorForElement (cognitive 25) · ×1
  • DOMElementNode.enhancedCssSelectorForElement (cognitive 25) packages/agent-infra/browser-use/src/dom/views.ts:545 — DOMElementNode.enhancedCssSelectorForElement has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 2 (3 pts), boolean chains 2, 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 · share.ShareOptions · ×1
  • share.ShareOptions::processShare (cognitive 24) apps/ui-tars/src/renderer/src/components/SideBar/share.tsx:43 — share.ShareOptions::processShare has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 2 (6 pts), error handling 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · version.selectVersionAndTag (cognitive 24) · ×1
  • version.selectVersionAndTag (cognitive 24) infra/pdk/src/utils/version.ts:45 — version.selectVersionAndTag has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 10, ternaries 2 (nesting depth added 4). Of this number, 13 points are the body's own statements and 11 belong to 3 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 · loader.loadAgentConfig (cognitive 24) · ×1
  • loader.loadAgentConfig (cognitive 24) multimodal/tarko/agent-cli/src/config/loader.ts:98 — loader.loadAgentConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), error handling 2 (5 pts), boolean chains 2, loops 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 · ShareModal.ShareModal (cognitive 24) · ×1
  • ShareModal.ShareModal (cognitive 24) multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx:14 — ShareModal.ShareModal has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 6, error handling 3 (4 pts), ternaries 2 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (handleDownload, handleUpload, a function literal at line 23, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · gui-agent.convertToNormalizedAction (cognitive 24) · ×1
  • gui-agent.convertToNormalizedAction (cognitive 24) multimodal/tarko/shared-utils/src/gui-agent.ts:51 — gui-agent.convertToNormalizedAction has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 15, if/else 2 (5 pts), error handling 1 (3 pts), match/switch 1 (nesting depth added 5). 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 · webui-routing.createPathMatcher (cognitive 24) · ×1
  • webui-routing.createPathMatcher (cognitive 24) REDACTED:46 — webui-routing.createPathMatcher has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 67, 79, 91, …). 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 · index.ShowcaseDetailPage (cognitive 24) · ×1
  • index.ShowcaseDetailPage (cognitive 24) multimodal/websites/docs/src/components/Showcase/index.tsx:291 — index.ShowcaseDetailPage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 5 (10 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 5 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (getPageContent, a function literal at line 302, handleBackToShowcase, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · NavigatorAgent.doMultiAction (cognitive 24) · ×1
  • NavigatorAgent.doMultiAction (cognitive 24) packages/agent-infra/browser-use/src/agent/agents/navigator.ts:281 — NavigatorAgent.doMultiAction has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (4 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (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 · index.init (cognitive 24) · ×1
  • index.init (cognitive 24) packages/agent-infra/create-new-mcp/src/index.ts:92 — index.init has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 3 (4 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 22 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 · utils.applyFileEdits (cognitive 24) · ×1
  • utils.applyFileEdits (cognitive 24) packages/agent-infra/mcp-servers/filesystem/src/utils.ts:50 — utils.applyFileEdits has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 11). Of this number, 13 points are the body's own statements and 11 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 · actionParser.actionStringParser (cognitive 23) · ×1
  • actionParser.actionStringParser (cognitive 23) REDACTED:91 — actionParser.actionStringParser has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), ternaries 3, boolean chains 2 (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 · sessions.getSessionWorkspaceFiles (cognitive 23) · ×1
  • sessions.getSessionWorkspaceFiles (cognitive 23) REDACTED:459 — sessions.getSessionWorkspaceFiles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 6 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 · config.loadAguiConfig (cognitive 23) · ×1
  • config.loadAguiConfig (cognitive 23) multimodal/tarko/agent-ui-cli/src/config.ts:57 — config.loadAguiConfig has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 4 (7 pts), error handling 2 (6 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ContextualTags.ContextualTags (cognitive 23) · ×1
  • ContextualTags.ContextualTags (cognitive 23) multimodal/tarko/agent-ui/src/standalone/chat/ContextualTags.tsx:21 — ContextualTags.ContextualTags has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 5 (6 pts), error handling 1, match/switch 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 5 function items inside it that branch (getDisplayText, a function literal at line 113, getItemIcon, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CreatingPage.CreatingPage (cognitive 23) · ×1
  • CreatingPage.CreatingPage (cognitive 23) multimodal/tarko/agent-ui/src/standalone/home/CreatingPage.tsx:21 — CreatingPage.CreatingPage has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 3 (7 pts), boolean chains 4, ternaries 2 (nesting depth added 6). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 39, 32). 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 · WelcomePage.WelcomePage (cognitive 23) · ×1
  • WelcomePage.WelcomePage (cognitive 23) multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx:16 — WelcomePage.WelcomePage has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 9, if/else 9, ternaries 3, error handling 2. Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (handleDirectChat, handleChatSubmit, getRandomPrompts, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · StructuredOutputsToolCallEngine.processStreamingChunk (cognitive 23) · ×1
  • StructuredOutputsToolCallEngine.processStreamingChunk (cognitive 23) multimodal/tarko/agent/src/tool-call-engine/StructuredOutputsToolCallEngine.ts:167 — StructuredOutputsToolCallEngine.processStreamingChunk has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 11). 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 · AnthropicHandler.validateInputs (cognitive 23) · ×1
  • AnthropicHandler.validateInputs (cognitive 23) multimodal/tarko/llm-client/src/handlers/anthropic.ts:499 — AnthropicHandler.validateInputs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 2 (4 pts), boolean chains 2 (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 · IntroAnimation.IntroAnimation (cognitive 23) · ×1
  • IntroAnimation.IntroAnimation (cognitive 23) multimodal/websites/docs/src/components/IntroAnimation.tsx:7 — IntroAnimation.IntroAnimation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 4, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 8 function items inside it that branch (getVideoClassName, toggleFullScreen, a function literal at line 34, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · BrowserOperator.execute (cognitive 23) · ×1
  • BrowserOperator.execute (cognitive 23) packages/ui-tars/operators/browser-operator/src/browser-operator.ts:189 — BrowserOperator.execute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 5, ternaries 2, error handling 1, match/switch 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 · index.LocalOperator (cognitive 22) · ×1
  • index.LocalOperator (cognitive 22) apps/ui-tars/src/renderer/src/pages/local/index.tsx:49 — index.LocalOperator has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 6, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 223, a function literal at line 83, renderChatList, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · Settings.Settings (cognitive 22) · ×1
  • Settings.Settings (cognitive 22) apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:69 — Settings.Settings has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 6, boolean chains 5, error handling 3 (nesting depth added 2). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (handleCheckForUpdates, handleUpdatePreset, handleClearSettings, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · AIOHybridOperator.singleActionExecutor (cognitive 22) · ×1
  • AIOHybridOperator.singleActionExecutor (cognitive 22) multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:127 — AIOHybridOperator.singleActionExecutor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, error handling 1, match/switch 1 (nesting depth added 7). Of this number, 21 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 · oneshot.createAndStreamingQuery (cognitive 22) · ×1
  • oneshot.createAndStreamingQuery (cognitive 22) multimodal/tarko/agent-server/src/api/controllers/oneshot.ts:102 — oneshot.createAndStreamingQuery has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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 · AgentSnapshotNormalizer.normalize (cognitive 22) · ×1
  • AgentSnapshotNormalizer.normalize (cognitive 22) multimodal/tarko/agent-snapshot/src/utils/snapshot-normalizer.ts:298 — AgentSnapshotNormalizer.normalize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeliverableRenderer.DeliverableRenderer (cognitive 22) · ×1
  • DeliverableRenderer.DeliverableRenderer (cognitive 22) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DeliverableRenderer.tsx:17 — DeliverableRenderer.DeliverableRenderer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 4, boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (getDeliverableType, handleDownload). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.loadConfig (cognitive 22) · ×1
  • index.loadConfig (cognitive 22) multimodal/tarko/config-loader/src/index.ts:96 — index.loadConfig has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 4 (7 pts), boolean chains 3 (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 · MarkdownRenderer.MarkdownRenderer (cognitive 22) · ×1
  • MarkdownRenderer.MarkdownRenderer (cognitive 22) multimodal/websites/main/src/render/components/Markdown/MarkdownRenderer.tsx:26 — MarkdownRenderer.MarkdownRenderer has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, if/else 6 (8 pts) (nesting depth added 2). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 66, 158, 47, …). 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 · BasePrompt.buildBrowserStateUserMessage (cognitive 22) · ×1
  • BasePrompt.buildBrowserStateUserMessage (cognitive 22) packages/agent-infra/browser-use/src/agent/prompts/base.ts:37 — BasePrompt.buildBrowserStateUserMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, loops 1 (2 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 · UITarsModel.invokeModelProvider (cognitive 22) · ×1
  • UITarsModel.invokeModelProvider (cognitive 22) packages/ui-tars/sdk/src/Model.ts:88 — UITarsModel.invokeModelProvider has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 5, ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 9). Of this number, 18 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 · navigation.createNavigationTools (cognitive 21) · ×1
  • navigation.createNavigationTools (cognitive 21) multimodal/agent-tars/core/src/environments/local/browser/tools/navigation.ts:17 — navigation.createNavigationTools has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (8 pts), error handling 4 (nesting depth added 5). None of this is in the body itself: all 21 points belong to 4 function literals inside it that branch (lines 58, 25, 125, …). 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 · NutJSOperator.singleActionExecutor (cognitive 21) · ×1
  • NutJSOperator.singleActionExecutor (cognitive 21) multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:127 — NutJSOperator.singleActionExecutor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 9). 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 · AgentReplaySnapshotHook.onLLMRequest (cognitive 21) · ×1
  • AgentReplaySnapshotHook.onLLMRequest (cognitive 21) multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts:280 — AgentReplaySnapshotHook.onLLMRequest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 2 (4 pts), boolean chains 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 · BrowserResultRenderer.extractBrowserResultData (cognitive 21) · ×1
  • BrowserResultRenderer.extractBrowserResultData (cognitive 21) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/BrowserResultRenderer.tsx:92 — BrowserResultRenderer.extractBrowserResultData has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 3, boolean chains 1, error handling 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 · PromptEngineeringToolCallEngine.handleParameterExtraction (cognitive 21) · ×1
  • PromptEngineeringToolCallEngine.handleParameterExtraction (cognitive 21) multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:411 — PromptEngineeringToolCallEngine.handleParameterExtraction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ai21.createCompletionResponseStreaming (cognitive 21) · ×1
  • ai21.createCompletionResponseStreaming (cognitive 21) multimodal/tarko/llm-client/src/handlers/ai21.ts:134 — ai21.createCompletionResponseStreaming has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (7 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 · ActionBuilder.buildDefaultActions (cognitive 21) · ×1
  • ActionBuilder.buildDefaultActions (cognitive 21) packages/agent-infra/browser-use/src/agent/actions/builder.ts:123 — ActionBuilder.buildDefaultActions has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 6, error handling 3, if/else 3 (nesting depth added 3). None of this is in the body itself: all 21 points belong to 7 function literals inside it that branch (lines 195, 474, 347, …). 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 · server.createServer (cognitive 21) · ×1
  • server.createServer (cognitive 21) packages/agent-infra/mcp-servers/filesystem/src/server.ts:169 — server.createServer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 4 (6 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 351, 213, 419, …). 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 · sidebar.Sidebar (cognitive 21) · ×1
  • sidebar.Sidebar (cognitive 21) packages/ui-tars/visualizer/src/component/sidebar.tsx:68 — sidebar.Sidebar has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, match/switch 1 (2 pts), ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 89, 135, 124). 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 · timeline.TimelineWidget (cognitive 21) · ×1
  • timeline.TimelineWidget (cognitive 21) packages/ui-tars/visualizer/src/component/timeline.tsx:48 — timeline.TimelineWidget has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, loops 3, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 135, closestScreenshotItemOnXY, a function literal at line 121, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · changelog.changelog (cognitive 20) · ×1
  • changelog.changelog (cognitive 20) infra/pdk/src/commands/changelog.ts:62 — changelog.changelog has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, error handling 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 · FilesystemToolsManager.createSafeDirectoryTreeTool (cognitive 20) · ×1
  • FilesystemToolsManager.createSafeDirectoryTreeTool (cognitive 20) multimodal/agent-tars/core/src/environments/local/filesystem/filesystem-tools-manager.ts:139 — FilesystemToolsManager.createSafeDirectoryTreeTool has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 2 (4 pts), boolean chains 2, error handling 2, loops 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 3 function literals inside it that branch (lines 191, 170, 232). 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 · parser.parseComputerContent (cognitive 20) · ×1
  • parser.parseComputerContent (cognitive 20) REDACTED:181 — parser.parseComputerContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 12). 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 · sessions.calculateRelevanceScore (cognitive 20) · ×1
  • sessions.calculateRelevanceScore (cognitive 20) REDACTED:688 — sessions.calculateRelevanceScore has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · fileCollector.collectFileInfo (cognitive 20) · ×1
  • fileCollector.collectFileInfo (cognitive 20) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/utils/fileCollector.ts:8 — fileCollector.collectFileInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, match/switch 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 5 belong to 3 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 · WelcomeCards.WelcomeCards (cognitive 20) · ×1
  • WelcomeCards.WelcomeCards (cognitive 20) multimodal/tarko/agent-ui/src/standalone/home/WelcomeCards.tsx:14 — WelcomeCards.WelcomeCards has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 4, ternaries 3, error handling 1. Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (handleCardClick, a function literal at line 153, a function literal at line 26, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · extractBrowserControlData.extractBrowserControlData (cognitive 20) · ×1
  • extractBrowserControlData.extractBrowserControlData (cognitive 20) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/browser-control/extractBrowserControlData.ts:12 — extractBrowserControlData.extractBrowserControlData has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 2, boolean chains 1, error handling 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 · gemini.convertMessagesToContents (cognitive 20) · ×1
  • gemini.convertMessagesToContents (cognitive 20) multimodal/tarko/llm-client/src/handlers/gemini.ts:183 — gemini.convertMessagesToContents has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 10). Of this number, 19 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 · TokenJS.extendModelList (cognitive 20) · ×1
  • TokenJS.extendModelList (cognitive 20) multimodal/tarko/llm-client/src/index.ts:132 — TokenJS.extendModelList has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (20 pts) (nesting depth added 8). Of this number, 19 points are the body's own statements and 1 belongs 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 · DOMElementNode.clickableElementsToString · ×1
  • DOMElementNode.clickableElementsToString::processNode (cognitive 20) packages/agent-infra/browser-use/src/dom/views.ts:151 — DOMElementNode.clickableElementsToString::processNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (2 pts) (nesting depth added 11). 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 · DOMElementNode.getFileUploadElement (cognitive 20) · ×1
  • DOMElementNode.getFileUploadElement (cognitive 20) packages/agent-infra/browser-use/src/dom/views.ts:455 — DOMElementNode.getFileUploadElement has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, loops 2 (3 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 · utils.waitForStableNetwork (cognitive 20) · ×1
  • utils.waitForStableNetwork (cognitive 20) packages/agent-infra/browser-use/src/browser/utils.ts:139 — utils.waitForStableNetwork has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 5, loops 1 (nesting depth added 2). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 2 function items inside it that branch (onRequest, onResponse). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · MCPClient.activate (cognitive 20) · ×1
  • MCPClient.activate (cognitive 20) packages/agent-infra/mcp-client/src/index.ts:212 — MCPClient.activate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (4 pts), boolean chains 1, 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 · run.processServerRun (cognitive 19) · ×1
  • run.processServerRun (cognitive 19) multimodal/tarko/agent-cli/src/core/commands/run.ts:66 — run.processServerRun has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 6). Of this number, 12 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 · ScreenshotDisplay.ScreenshotDisplay (cognitive 19) · ×1
  • ScreenshotDisplay.ScreenshotDisplay (cognitive 19) multimodal/tarko/ui/src/components/gui-agent/ScreenshotDisplay.tsx:22 — ScreenshotDisplay.ScreenshotDisplay has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (7 pts), if/else 5 (nesting depth added 3). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (renderImageContent, shouldShowMouseCursor, wrapWithBrowserShell, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.ShowcaseListPage (cognitive 19) · ×1
  • index.ShowcaseListPage (cognitive 19) multimodal/websites/docs/src/components/Showcase/index.tsx:117 — index.ShowcaseListPage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, ternaries 3 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 161, handleCategoryChange, a function literal at line 147, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · utils.parseProxyUrl (cognitive 19) · ×1
  • utils.parseProxyUrl (cognitive 19) packages/agent-infra/mcp-servers/browser/src/utils/utils.ts:38 — utils.parseProxyUrl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (14 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 11). 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 · GUIAgent.guiAgentErrorParser (cognitive 19) · ×1
  • GUIAgent.guiAgentErrorParser (cognitive 19) packages/ui-tars/sdk/src/GUIAgent.ts:527 — GUIAgent.guiAgentErrorParser has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 8. 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 · buildDomTree · ×1
  • buildDomTree::isInteractiveElement (cognitive 19) packages/agent-infra/browser-use/assets/buildDomTree.js:293 — buildDomTree::isInteractiveElement has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 3, ternaries 1. 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 · vlm.ModelAvailabilityCheck (cognitive 18) · ×1
  • vlm.ModelAvailabilityCheck (cognitive 18) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:462 — vlm.ModelAvailabilityCheck has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 3 (5 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (handleCheckModel, a function literal at line 473, a function literal at line 475). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · sessions.searchWorkspaceItemsRecursive · ×1
  • sessions.searchWorkspaceItemsRecursive::searchInDirectory (cognitive 18) REDACTED:617 — sessions.searchWorkspaceItemsRecursive::searchInDirectory has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 3, ternaries 1 (3 pts), error handling 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 · AgentSnapshotNormalizer.normalizeField (cognitive 18) · ×1
  • AgentSnapshotNormalizer.normalizeField (cognitive 18) multimodal/tarko/agent-snapshot/src/utils/snapshot-normalizer.ts:374 — AgentSnapshotNormalizer.normalizeField has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApiService.sendStreamingQuery (cognitive 18) · ×1
  • ApiService.sendStreamingQuery (cognitive 18) multimodal/tarko/agent-ui/src/common/services/apiService.ts:326 — ApiService.sendStreamingQuery has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 2 (5 pts), loops 2 (3 pts), ternaries 1 (3 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 · EnvironmentInputHandler.handle (cognitive 18) · ×1
  • EnvironmentInputHandler.handle (cognitive 18) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/SystemHandler.ts:48 — EnvironmentInputHandler.handle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 8 (nesting depth added 5). Of this number, 16 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 · sessionActions.setActiveSessionAction (cognitive 18) · ×1
  • sessionActions.setActiveSessionAction (cognitive 18) multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts:129 — sessionActions.setActiveSessionAction has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), error handling 3 (4 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). 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: 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 · ChatBottomSettings.ChatBottomSettings · ×1
  • ChatBottomSettings.ChatBottomSettings::renderChatBottomOption (cognitive 18) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx:244 — ChatBottomSettings.ChatBottomSettings::renderChatBottomOption has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (8 pts), if/else 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 · LinkRenderer.extractLinkData (cognitive 18) · ×1
  • LinkRenderer.extractLinkData (cognitive 18) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/LinkRenderer.tsx:49 — LinkRenderer.extractLinkData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (6 pts), boolean chains 4, 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 · MessageManager.mergeSuccessiveMessages (cognitive 18) · ×1
  • MessageManager.mergeSuccessiveMessages (cognitive 18) packages/agent-infra/browser-use/src/agent/messages/service.ts:410 — MessageManager.mergeSuccessiveMessages has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (nesting depth added 10). 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 · PlannerAgent.execute (cognitive 18) · ×1
  • PlannerAgent.execute (cognitive 18) packages/agent-infra/browser-use/src/agent/agents/planner.ts:45 — PlannerAgent.execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 1 (3 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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 · index.RunMessages (cognitive 17) · ×1
  • index.RunMessages (cognitive 17) apps/ui-tars/src/renderer/src/components/RunMessages/index.tsx:32 — index.RunMessages has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 5 (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 97, renderChatList, a function literal at line 42, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · cli.bootstrapCli (cognitive 17) · ×1
  • cli.bootstrapCli (cognitive 17) infra/pdk/src/cli.ts:44 — cli.bootstrapCli has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 4. None of this is in the body itself: all 17 points belong to 5 function literals inside it that branch (lines 63, 195, 130, …). 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 · BrowserGUIAgent.extractImageDimensionsFromBase64 (cognitive 17) · ×1
  • BrowserGUIAgent.extractImageDimensionsFromBase64 (cognitive 17) multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:492 — BrowserGUIAgent.extractImageDimensionsFromBase64 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, loops 1 (2 pts) (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 · ActionParserHelper.parseRoughFromCallString (cognitive 17) · ×1
  • ActionParserHelper.parseRoughFromCallString (cognitive 17) multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:86 — ActionParserHelper.parseRoughFromCallString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), boolean chains 1, error handling 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 · XMLFormatParser.parse (cognitive 17) · ×1
  • XMLFormatParser.parse (cognitive 17) REDACTED:26 — XMLFormatParser.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2, boolean chains 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 · WorkspaceFileManager.WorkspaceFileManager (cognitive 17) · ×1
  • WorkspaceFileManager.WorkspaceFileManager (cognitive 17) multimodal/tarko/agent-ui/src/standalone/workspace/components/WorkspaceFileManager.tsx:32 — WorkspaceFileManager.WorkspaceFileManager has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 4, match/switch 2, ternaries 1. Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (handleFileClick, getFileIcon, getFileTypeBadge, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · DiffRenderer.extractStrReplaceEditorDiffData (cognitive 17) · ×1
  • DiffRenderer.extractStrReplaceEditorDiffData (cognitive 17) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/DiffRenderer.tsx:113 — DiffRenderer.extractStrReplaceEditorDiffData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (6 pts), boolean chains 4, 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 · WorkspacePanel.WorkspacePanel (cognitive 17) · ×1
  • WorkspacePanel.WorkspacePanel (cognitive 17) multimodal/tarko/agent-ui/src/standalone/workspace/WorkspacePanel.tsx:79 — WorkspacePanel.WorkspacePanel has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (4 pts), ternaries 2 (4 pts), match/switch 1 (nesting depth added 3). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 88, renderWorkspaceContent, a function literal at line 125). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.Replay (cognitive 17) · ×1
  • index.Replay (cognitive 17) multimodal/websites/docs/src/components/Replay/index.tsx:36 — index.Replay has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 4 (5 pts), boolean chains 1 (nesting depth added 4). Of this number, 10 points are the body's own statements and 7 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 · MCPClient.listTools (cognitive 17) · ×1
  • MCPClient.listTools (cognitive 17) packages/agent-infra/mcp-client/src/index.ts:499 — MCPClient.listTools has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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 · timeline.Timeline (cognitive 17) · ×1
  • timeline.Timeline (cognitive 17) packages/ui-tars/visualizer/src/component/timeline.tsx:440 — timeline.Timeline has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6, ternaries 1. None of this is in the body itself: all 17 points belong to 5 function items inside it that branch (a function literal at line 456, maskConfigForTask, onHighlightItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · index.ImageGallery (cognitive 16) · ×1
  • index.ImageGallery (cognitive 16) apps/ui-tars/src/renderer/src/components/ImageGallery/index.tsx:27 — index.ImageGallery has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts) (nesting depth added 1). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 35, a function literal at line 129, a function literal at line 81, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · agent-resolver.resolveAgentImplementation (cognitive 16) · ×1
  • agent-resolver.resolveAgentImplementation (cognitive 16) multimodal/tarko/agent-server/src/utils/agent-resolver.ts:23 — agent-resolver.resolveAgentImplementation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sessionActions.sendMessageAction (cognitive 16) · ×1
  • sessionActions.sendMessageAction (cognitive 16) multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts:332 — sessionActions.sendMessageAction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, error handling 2, ternaries 1 (2 pts) (nesting depth added 4). Of this number, 13 points are the body's own statements and 3 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 · useReplayMode.findGeneratedFile (cognitive 16) · ×1
  • useReplayMode.findGeneratedFile (cognitive 16) multimodal/tarko/agent-ui/src/common/hooks/useReplayMode.tsx:43 — useReplayMode.findGeneratedFile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 6, loops 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 · ShareButton.ShareButton (cognitive 16) · ×1
  • ShareButton.ShareButton (cognitive 16) multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx:17 — ShareButton.ShareButton has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 6, boolean chains 3 (nesting depth added 2). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · StreamAdapter.createStreamFromEvents (cognitive 16) · ×1
  • StreamAdapter.createStreamFromEvents (cognitive 16) multimodal/tarko/agent/src/agent/runner/stream-adapter.ts:27 — StreamAdapter.createStreamFromEvents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (16 pts) (nesting depth added 2). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 49, 111). 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 · ShowcasePreview.ShowcasePreview (cognitive 16) · ×1
  • ShowcasePreview.ShowcasePreview (cognitive 16) multimodal/websites/docs/src/components/Showcase/components/ShowcasePreview.tsx:16 — ShowcasePreview.ShowcasePreview has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 6. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function items inside it that branch (handleNavigate, handleExpand, handleShare, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ShowcasePanels.ShowcasePanels (cognitive 16) · ×1
  • ShowcasePanels.ShowcasePanels (cognitive 16) multimodal/websites/docs/src/components/ShowcasePanels.tsx:24 — ShowcasePanels.ShowcasePanels has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, ternaries 6, if/else 4. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 75, getResponsiveHeight, isSmallHeight). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · utils.scrollIntoViewIfNeeded (cognitive 16) · ×1
  • utils.scrollIntoViewIfNeeded (cognitive 16) packages/agent-infra/browser-use/src/browser/utils.ts:13 — utils.scrollIntoViewIfNeeded has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 5). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 22). 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 · Page._updateState (cognitive 16) · ×1
  • Page._updateState (cognitive 16) packages/agent-infra/browser-use/src/browser/page.ts:269 — Page._updateState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, error handling 2, ternaries 1 (nesting depth added 3). 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 · Page.isFileUploader (cognitive 16) · ×1
  • Page.isFileUploader (cognitive 16) packages/agent-infra/browser-use/src/browser/page.ts:894 — Page.isFileUploader has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1 (2 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 · transform.transformComputerUseDataToDump (cognitive 16) · ×1
  • transform.transformComputerUseDataToDump (cognitive 16) packages/ui-tars/visualizer/src/transform.ts:20 — transform.transformComputerUseDataToDump has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), boolean chains 6, if/else 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 35). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: Page packages/agent-infra/browser-use/src/browser/page.ts:71 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D5 · Coupling · Unstable project @agent-infra/search · ×1
  • Unstable project @agent-infra/search — @agent-infra/search has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project @omni-tars/gui-agent · ×1
  • Unstable project @omni-tars/gui-agent — @omni-tars/gui-agent has instability 0.89 with 1 dependents.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 46 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty · Changed-file filter skips the test gate for code the tests depend on · ×1
  • Changed-file filter skips the test gate for code the tests depend on .github/workflows/agent_tars_test.yml:6 — `paths` runs `pnpm test` (the tests of `multimodal/agent-tars/core`) only when a change touches `multimodal/**`, `.github/workflows/agent_tars_build.yml`, but those tests also depend on `packages/agent-infra/browser`, `packages/agent-infra/browser-use`, `packages/agent-infra/logger`, `packages/agent-infra/mcp-client`, `packages/agent-infra/mcp-http-server`, `packages/agent-infra/mcp-shared`, `packages/agent-infra/shared`, `packages/common/configs`, `packages/ui-tars/action-parser`, `packages/ui-tars/shared`, `packages/agent-infra/mcp-servers/browser`, `packages/agent-infra/mcp-servers/commands`, `packages/agent-infra/mcp-servers/filesystem`, `packages/agent-infra/search/bing-search`, `packages/agent-infra/search/browser-search`, `packages/agent-infra/search/duckduckgo-search`, `packages/agent-infra/search/search` (e.g. `packages/agent-infra/browser/rslib.config.ts`, `packages/agent-infra/browser/vitest.e2e.config.ts`) — a change there merges with them not run, and no unfiltered gate runs them. List the package's tests and its workspace dependencies in the filter, or drop it.
P12 · CI test-gate honesty · Pull-request path filter skips the test gate for source changes · ×1
  • Pull-request path filter skips the test gate for source changes REDACTED:7 — `paths-ignore: multimodal/**` matches compiled source (`multimodal/pdk.config.ts`, `multimodal/vitest.config.mts`, `multimodal/agent-tars/cli/rslib.config.ts`) — a pull request that changes only those files merges without running the tests. Ignore only documentation and other files no build reads.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
P3 · Security & performance tooling · SAST runs, but gates no merge · ×1
  • SAST runs, but gates no merge — `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience multimodal/tarko/agent-server/src/services/ShareService.ts:359 — `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication · Duplication concentrated across 12 sibling directories (45 clone groups) · ×1
  • Duplication concentrated across 12 sibling directories (45 clone groups) multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7 — 45 duplicated blocks under multimodal/tarko/ have copies in at least two of the sibling directories agent, agent-interface, agent-server, agent-server-next, agent-ui, agent-ui-builder (+6 more sibling(s) not listed) — 40 of them are reported below, and 5 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 45 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 45 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 45 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 4 sibling directories (36 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (36 clone groups) multimodal/gui-agent/operator-browser/src/browser-operator.ts:177 — 36 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, infra, multimodal, packages — 29 of them are reported below, and 7 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 36 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 36 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 36 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 5 sibling directories (20 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (20 clone groups) multimodal/gui-agent/agent-sdk/src/utils.ts:16 — 20 duplicated blocks under multimodal/ have copies in at least two of the sibling directories agent-tars, gui-agent, omni-tars, tarko, websites — 14 of them are reported below, and 6 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 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 20 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 2 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (13 clone groups) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39 — 13 of the duplicated blocks reported below have copies in at least two of the sibling directories components, pages under apps/ui-tars/src/renderer/src/. That concentration is one structural fact, not 13 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 13 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 5 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (11 clone groups) multimodal/omni-tars/code-agent/rslib.config.ts:5 — 11 duplicated blocks under multimodal/omni-tars/ have copies in at least two of the sibling directories code-agent, core, gui-agent, mcp-agent, omni-agent — 8 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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 7 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (7 clone groups) packages/agent-infra/browser/rslib.config.ts:7 — 7 duplicated blocks under packages/agent-infra/ have copies in at least two of the sibling directories browser, browser-use, create-new-mcp, mcp-client, mcp-servers, search (+1 more sibling(s) not listed) — 5 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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 4 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (6 clone groups) multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories operator-adb, operator-aio, operator-browser, operator-nutjs under multimodal/gui-agent/. 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 · Duplication concentrated across 2 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (6 clone groups) multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39 — 6 of the duplicated blocks reported below have copies in at least two of the sibling directories mongodb, sqlite under multimodal/tarko/agent-server-next/src/dao/. 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 · Duplication concentrated across 6 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (6 clone groups) multimodal/tarko/agent-ui/src/standalone/sidebar/AgentConfigViewer.tsx:96 — 6 duplicated blocks under multimodal/tarko/agent-ui/src/standalone/ have copies in at least two of the sibling directories chat, components, navbar, share, sidebar, workspace — 2 of them are reported below, and 4 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 (272 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (272 matched lines × 2 locations) multimodal/gui-agent/operator-browser/src/browser-operator.ts:177 — multimodal/gui-agent/operator-browser/src/browser-operator.ts:177 · packages/ui-tars/operators/browser-operator/src/browser-operator.ts:137 — the two spans are one implementation copied and then locally edited — 1721 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 (251 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (251 matched lines × 2 locations) multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 — multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 · multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — the two spans are one implementation copied and then locally edited — 1674 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 · Wholesale file copy (248 identical lines × 2 files) · ×1
  • Wholesale file copy (248 identical lines × 2 files) multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7 — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:7 · multimodal/tarko/agent-server/src/core/AgentSession.ts:7 — these 2 files are line-for-line copies of one another — 248 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (228 identical lines × 2 files) · ×1
  • Wholesale file copy (228 identical lines × 2 files) apps/ui-tars/src/renderer/src/pages/remote/free.tsx:1 — apps/ui-tars/src/renderer/src/pages/remote/free.tsx:1 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:1 — these 2 files are line-for-line copies of one another — 228 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (193 identical lines × 2 files) · ×1
  • Wholesale file copy (193 identical lines × 2 files) multimodal/tarko/agent-server-next/src/services/ShareService.ts:6 — multimodal/tarko/agent-server-next/src/services/ShareService.ts:6 · multimodal/tarko/agent-server/src/services/ShareService.ts:6 — these 2 files are line-for-line copies of one another — 193 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (150 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (150 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39 — apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:39 · apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:49 — the two spans are one implementation copied and then locally edited — 774 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 (136 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (136 matched lines × 2 locations) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:175 — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:175 · multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx:46 — the two spans are one implementation copied and then locally edited — 936 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 (135 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (135 matched lines × 2 locations) multimodal/gui-agent/operator-browser/src/ui-helper.ts:13 — multimodal/gui-agent/operator-browser/src/ui-helper.ts:13 · packages/ui-tars/operators/browser-operator/src/ui-helper.ts:13 — the two spans are one implementation copied and then locally edited — 799 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 (129 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (129 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/ui/dropdown-menu.tsx:11 — apps/ui-tars/src/renderer/src/components/ui/dropdown-menu.tsx:11 · apps/ui-tars/src/renderer/src/components/ui/select.tsx:11 — the two spans are one implementation copied and then locally edited — 518 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 (122 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (122 matched lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39 — multimodal/tarko/agent-server-next/src/dao/mongodb/UserConfigDAO.ts:39 · multimodal/tarko/agent-server-next/src/dao/sqlite/UserConfigDAO.ts:44 — the two spans are one implementation copied and then locally edited — 747 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 (117 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (117 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:64 — apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:64 · apps/ui-tars/src/renderer/src/components/SideBar/share.tsx:57 — the two spans are one implementation copied and then locally edited — 632 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 (114 lines × 2 locations) · ×1
  • Duplicated block (114 lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/preset.tsx:48 — apps/ui-tars/src/renderer/src/components/Settings/category/preset.tsx:48 · apps/ui-tars/src/renderer/src/pages/settings/PresetImport.tsx:29 — 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.
R10 · Code Duplication · Wholesale file copy (106 identical lines × 2 files) · ×1
  • Wholesale file copy (106 identical lines × 2 files) multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:6 — multimodal/tarko/agent-server-next/src/utils/slug-generator.ts:6 · multimodal/tarko/agent-server/src/utils/slug-generator.ts:6 — these 2 files are line-for-line copies of one another — 106 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (100 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (100 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/ui/dialog.tsx:11 — apps/ui-tars/src/renderer/src/components/ui/dialog.tsx:11 · apps/ui-tars/src/renderer/src/components/ui/sheet.tsx:13 — the two spans are one implementation copied and then locally edited — 465 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 (99 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (99 matched lines × 2 locations) multimodal/gui-agent/operator-browser/src/ui-helper.ts:366 — multimodal/gui-agent/operator-browser/src/ui-helper.ts:366 · packages/ui-tars/operators/browser-operator/src/ui-helper.ts:301 — the two spans are one implementation copied and then locally edited — 753 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 (96 lines × 2 locations) · ×1
  • Duplicated block (96 lines × 2 locations) packages/agent-infra/search/browser-search/src/engines/baidu-engine.ts:50 — packages/agent-infra/search/browser-search/src/engines/baidu-engine.ts:50 · packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:47 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (93 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (93 matched lines × 2 locations) multimodal/tarko/agent-server-next/src/dao/sqlite/SessionDAO.ts:102 — multimodal/tarko/agent-server-next/src/dao/sqlite/SessionDAO.ts:102 · multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:472 — the two spans are one implementation copied and then locally edited — 601 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 (91 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (91 matched lines × 2 locations) apps/ui-tars/src/main/remote/operators.ts:102 — apps/ui-tars/src/main/remote/operators.ts:102 · packages/ui-tars/operators/nut-js/src/index.ts:96 — the two spans are one implementation copied and then locally edited — 473 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 (85 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (85 matched lines × 2 locations) packages/agent-infra/browser/src/browser-finder/chrome-paths.ts:48 — packages/agent-infra/browser/src/browser-finder/chrome-paths.ts:48 · packages/agent-infra/browser/src/browser-finder/firefox-paths.ts:27 — the two spans are one implementation copied and then locally edited — 480 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 (84 lines × 3 locations) · ×1
  • Duplicated block (84 lines × 3 locations) apps/ui-tars/src/renderer/src/pages/local/index.tsx:96 — apps/ui-tars/src/renderer/src/pages/local/index.tsx:96 · apps/ui-tars/src/renderer/src/pages/remote/free.tsx:166 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:127 — the 3 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block with local edits (74 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (74 matched lines × 2 locations) multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82 — multimodal/gui-agent/operator-adb/src/AdbOperator.ts:82 · multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:114 — the two spans are one implementation copied and then locally edited — 360 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 (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) multimodal/gui-agent/cli/src/cli/start.ts:38 — multimodal/gui-agent/cli/src/cli/start.ts:38 · packages/ui-tars/cli/src/cli/start.ts:31 — the two spans are one implementation copied and then locally edited — 448 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 (68 lines × 3 locations) · ×1
  • Duplicated block (68 lines × 3 locations) multimodal/gui-agent/agent-sdk/src/utils.ts:16 — multimodal/gui-agent/agent-sdk/src/utils.ts:16 · multimodal/omni-tars/gui-agent/src/utils.ts:17 · multimodal/tarko/shared-utils/src/gui-agent.ts:204 — 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 with local edits (67 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (67 matched lines × 2 locations) apps/ui-tars/src/renderer/src/components/Settings/category/remoteComputer.tsx:27 — apps/ui-tars/src/renderer/src/components/Settings/category/remoteComputer.tsx:27 · apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:45 — the two spans are one implementation copied and then locally edited — 381 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 (65 lines × 2 locations) · ×1
  • Duplicated block (65 lines × 2 locations) REDACTED:16 — REDACTED:16 · REDACTED:16 — 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.
R10 · Code Duplication · Duplicated block (64 lines × 2 locations) · ×1
  • Duplicated block (64 lines × 2 locations) REDACTED:321 — REDACTED:321 · REDACTED:267 — 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.
R10 · Code Duplication · Duplicated block with local edits (60 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (60 matched lines × 2 locations) multimodal/tarko/agent-server-next/src/controllers/system.ts:63 — multimodal/tarko/agent-server-next/src/controllers/system.ts:63 · REDACTED:55 — the two spans are one implementation copied and then locally edited — 368 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 (60 lines × 2 locations) · ×1
  • Duplicated block (60 lines × 2 locations) multimodal/tarko/agent-server-next/src/utils/event-stream.ts:46 — multimodal/tarko/agent-server-next/src/utils/event-stream.ts:46 · multimodal/tarko/agent-server/src/utils/event-stream.ts:47 — 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.
R10 · Code Duplication · Wholesale file copy (59 identical lines × 2 files) · ×1
  • Wholesale file copy (59 identical lines × 2 files) multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:2 — multimodal/tarko/agent-server-next/src/utils/config-sanitizer.ts:2 · multimodal/tarko/agent-server/src/utils/config-sanitizer.ts:2 — these 2 files are line-for-line copies of one another — 59 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (56 identical lines × 2 files) · ×1
  • Wholesale file copy (56 identical lines × 2 files) packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:5 — packages/agent-infra/search/browser-search/src/engines/bing-engine.ts:5 · packages/agent-infra/search/browser-search/src/engines/google-engine.ts:5 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (54 lines × 2 locations) · ×1
  • Duplicated block (54 lines × 2 locations) apps/ui-tars/src/renderer/src/pages/local/index.tsx:213 — apps/ui-tars/src/renderer/src/pages/local/index.tsx:213 · apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:224 — 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.
R2 · Cyclomatic Complexity · Complex function getEnhancedContextInfo (cyclomatic 74, cognitive 122) · ×1
  • Complex function getEnhancedContextInfo (cyclomatic 74, cognitive 122) packages/agent-infra/browser-use/src/dom/views.ts:222 — getEnhancedContextInfo has cyclomatic complexity 74 and cognitive complexity 122; 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 extractToolCallT5 (cyclomatic 51, cognitive 151) · ×1
  • Complex function extractToolCallT5 (cyclomatic 51, cognitive 151) multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:17 — extractToolCallT5 has cyclomatic complexity 51 and cognitive complexity 151; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 51, cognitive 50) · ×1
  • Complex function execute (cyclomatic 51, cognitive 50) apps/ui-tars/src/main/remote/operators.ts:101 — execute has cyclomatic complexity 51 and cognitive complexity 50; 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 extractCodeEnv (cyclomatic 50, cognitive 156) · ×1
  • Complex function extractCodeEnv (cyclomatic 50, cognitive 156) multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:14 — extractCodeEnv has cyclomatic complexity 50 and cognitive complexity 156; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 47, cognitive 44) · ×1
  • Complex function execute (cyclomatic 47, cognitive 44) packages/ui-tars/operators/adb/src/index.ts:111 — execute has cyclomatic complexity 47 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ChatInput (cyclomatic 47, cognitive 40) · ×1
  • Complex function ChatInput (cyclomatic 47, cognitive 40) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:46 — ChatInput has cyclomatic complexity 47 and cognitive complexity 40; 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 getToolDescription (cyclomatic 44, cognitive 48) · ×1
  • Complex function getToolDescription (cyclomatic 44, cognitive 48) multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx:91 — getToolDescription has cyclomatic complexity 44 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 44, cognitive 32) · ×1
  • Complex function execute (cyclomatic 44, cognitive 32) packages/ui-tars/operators/nut-js/src/index.ts:94 — execute has cyclomatic complexity 44 and cognitive complexity 32; 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 isInteractiveElement (cyclomatic 37, cognitive 19) · ×1
  • Complex function isInteractiveElement (cyclomatic 37, cognitive 19) packages/agent-infra/browser-use/assets/buildDomTree.js:293 — isInteractiveElement has cyclomatic complexity 37 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 parseActionVlm (cyclomatic 35, cognitive 75) · ×1
  • Complex function parseActionVlm (cyclomatic 35, cognitive 75) REDACTED:162 — parseActionVlm has cyclomatic complexity 35 and cognitive complexity 75; 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 extractScriptData (cyclomatic 35, cognitive 60) · ×1
  • Complex function extractScriptData (cyclomatic 35, cognitive 60) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx:173 — extractScriptData has cyclomatic complexity 35 and cognitive complexity 60; 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 singleActionExecutor (cyclomatic 35, cognitive 21) · ×1
  • Complex function singleActionExecutor (cyclomatic 35, cognitive 21) multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:127 — singleActionExecutor has cyclomatic complexity 35 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 handleStreamingResponse (cyclomatic 34, cognitive 54) · ×1
  • Complex function handleStreamingResponse (cyclomatic 34, cognitive 54) multimodal/tarko/agent/src/agent/runner/llm-processor.ts:280 — handleStreamingResponse has cyclomatic complexity 34 and cognitive complexity 54; 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 convertToNormalizedAction (cyclomatic 34, cognitive 24) · ×1
  • Complex function convertToNormalizedAction (cyclomatic 34, cognitive 24) multimodal/tarko/shared-utils/src/gui-agent.ts:51 — convertToNormalizedAction has cyclomatic complexity 34 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 singleActionExecutor (cyclomatic 34, cognitive 21) · ×1
  • Complex function singleActionExecutor (cyclomatic 34, cognitive 21) multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:127 — singleActionExecutor has cyclomatic complexity 34 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 performJsonSchemaMigration (cyclomatic 33, cognitive 56) · ×1
  • Complex function performJsonSchemaMigration (cyclomatic 33, cognitive 56) multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:170 — performJsonSchemaMigration has cyclomatic complexity 33 and cognitive complexity 56; 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 isTopElement (cyclomatic 33, cognitive 32) · ×1
  • Complex function isTopElement (cyclomatic 33, cognitive 32) packages/agent-infra/browser-use/assets/buildDomTree.js:490 — isTopElement has cyclomatic complexity 33 and cognitive complexity 32; 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 execute (cyclomatic 33, cognitive 23) · ×1
  • Complex function execute (cyclomatic 33, cognitive 23) packages/ui-tars/operators/browser-operator/src/browser-operator.ts:189 — execute has cyclomatic complexity 33 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 validateInputs (cyclomatic 32, cognitive 61) · ×1
  • Complex function validateInputs (cyclomatic 32, cognitive 61) multimodal/tarko/llm-client/src/handlers/base.ts:43 — validateInputs has cyclomatic complexity 32 and cognitive complexity 61; 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 parseActionVlm (cyclomatic 31, cognitive 69) · ×1
  • Complex function parseActionVlm (cyclomatic 31, cognitive 69) REDACTED:92 — parseActionVlm has cyclomatic complexity 31 and cognitive complexity 69; 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 · packages/agent-infra/browser-use/src/browser/page.ts · ×1
  • packages/agent-infra/browser-use/src/browser/page.ts: 835 lines of code packages/agent-infra/browser-use/src/browser/page.ts:1 — packages/agent-infra/browser-use/src/browser/page.ts has 835 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/ui-tars/src/main/remote/proxyClient.ts · ×1
  • apps/ui-tars/src/main/remote/proxyClient.ts: 771 lines of code apps/ui-tars/src/main/remote/proxyClient.ts:1 — apps/ui-tars/src/main/remote/proxyClient.ts has 771 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 · multimodal/gui-agent/operator-browser/src/ui-helper.ts · ×1
  • multimodal/gui-agent/operator-browser/src/ui-helper.ts: 765 lines of code multimodal/gui-agent/operator-browser/src/ui-helper.ts:1 — multimodal/gui-agent/operator-browser/src/ui-helper.ts has 765 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: 736 lines of code REDACTED:1 — REDACTED has 736 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/agent-infra/browser-use/assets/buildDomTree.js · ×1
  • packages/agent-infra/browser-use/assets/buildDomTree.js: 724 lines of code packages/agent-infra/browser-use/assets/buildDomTree.js:1 — packages/agent-infra/browser-use/assets/buildDomTree.js has 724 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/agent-infra/mcp-servers/browser/src/server.ts · ×1
  • packages/agent-infra/mcp-servers/browser/src/server.ts: 719 lines of code packages/agent-infra/mcp-servers/browser/src/server.ts:1 — packages/agent-infra/mcp-servers/browser/src/server.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/ui-tars/operators/browser-operator/src/browser-operator.ts · ×1
  • packages/ui-tars/operators/browser-operator/src/browser-operator.ts: 712 lines of code packages/ui-tars/operators/browser-operator/src/browser-operator.ts:1 — packages/ui-tars/operators/browser-operator/src/browser-operator.ts has 712 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/ui-tars/visualizer/src/component/player.tsx · ×1
  • packages/ui-tars/visualizer/src/component/player.tsx: 708 lines of code packages/ui-tars/visualizer/src/component/player.tsx:1 — packages/ui-tars/visualizer/src/component/player.tsx has 708 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/ui-tars/operators/browser-operator/src/ui-helper.ts · ×1
  • packages/ui-tars/operators/browser-operator/src/ui-helper.ts: 705 lines of code packages/ui-tars/operators/browser-operator/src/ui-helper.ts:1 — packages/ui-tars/operators/browser-operator/src/ui-helper.ts has 705 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/ui-tars/src/renderer/src/components/ui/sidebar.tsx · ×1
  • apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx: 684 lines of code apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx:1 — apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx has 684 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 · multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts · ×1
  • multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts: 683 lines of code multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:1 — multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts has 683 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 · multimodal/gui-agent/operator-browser/src/browser-operator.ts · ×1
  • multimodal/gui-agent/operator-browser/src/browser-operator.ts: 646 lines of code multimodal/gui-agent/operator-browser/src/browser-operator.ts:1 — multimodal/gui-agent/operator-browser/src/browser-operator.ts has 646 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 · multimodal/tarko/agent/src/agent/agent.ts · ×1
  • multimodal/tarko/agent/src/agent/agent.ts: 625 lines of code multimodal/tarko/agent/src/agent/agent.ts:1 — multimodal/tarko/agent/src/agent/agent.ts has 625 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/agent-infra/browser-use/src/dom/views.ts · ×1
  • packages/agent-infra/browser-use/src/dom/views.ts: 616 lines of code packages/agent-infra/browser-use/src/dom/views.ts:1 — packages/agent-infra/browser-use/src/dom/views.ts has 616 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/agent-infra/mcp-client/src/index.ts · ×1
  • packages/agent-infra/mcp-client/src/index.ts: 610 lines of code packages/agent-infra/mcp-client/src/index.ts:1 — packages/agent-infra/mcp-client/src/index.ts has 610 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 · multimodal/tarko/agent-ui/src/common/services/apiService.ts · ×1
  • multimodal/tarko/agent-ui/src/common/services/apiService.ts: 605 lines of code multimodal/tarko/agent-ui/src/common/services/apiService.ts:1 — multimodal/tarko/agent-ui/src/common/services/apiService.ts has 605 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 · multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts · ×1
  • multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts: 600 lines of code multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts:1 — multimodal/tarko/agent-snapshot/src/agent-replay-snapshot-hook.ts has 600 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/ui-tars/src/renderer/src/pages/settings/Settings.tsx · ×1
  • apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx: 588 lines of code apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx:1 — apps/ui-tars/src/renderer/src/pages/settings/Settings.tsx has 588 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 · multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts · ×1
  • multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts: 588 lines of code multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts:1 — multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts has 588 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 · multimodal/tarko/agent-interface/src/agent-event-stream.ts · ×1
  • multimodal/tarko/agent-interface/src/agent-event-stream.ts: 562 lines of code multimodal/tarko/agent-interface/src/agent-event-stream.ts:1 — multimodal/tarko/agent-interface/src/agent-event-stream.ts has 562 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: 562 lines of code REDACTED:1 — REDACTED has 562 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 · multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx · ×1
  • multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx: 560 lines of code multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx:1 — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx has 560 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 · multimodal/tarko/llm-client/src/handlers/anthropic.ts · ×1
  • multimodal/tarko/llm-client/src/handlers/anthropic.ts: 545 lines of code multimodal/tarko/llm-client/src/handlers/anthropic.ts:1 — multimodal/tarko/llm-client/src/handlers/anthropic.ts has 545 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/ui-tars/sdk/src/GUIAgent.ts · ×1
  • packages/ui-tars/sdk/src/GUIAgent.ts: 543 lines of code packages/ui-tars/sdk/src/GUIAgent.ts:1 — packages/ui-tars/sdk/src/GUIAgent.ts has 543 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/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx · ×1
  • apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx: 538 lines of code apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:1 — apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx has 538 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 · multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts · ×1
  • multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts: 529 lines of code multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:1 — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts has 529 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 · multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx · ×1
  • multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx: 521 lines of code multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:1 — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx has 521 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 · multimodal/gui-agent/action-parser/src/ActionParserHelper.ts · ×1
  • multimodal/gui-agent/action-parser/src/ActionParserHelper.ts: 518 lines of code multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:1 — multimodal/gui-agent/action-parser/src/ActionParserHelper.ts has 518 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 · multimodal/tarko/agent-server/src/core/AgentSession.ts · ×1
  • multimodal/tarko/agent-server/src/core/AgentSession.ts: 509 lines of code multimodal/tarko/agent-server/src/core/AgentSession.ts:1 — multimodal/tarko/agent-server/src/core/AgentSession.ts has 509 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/ui-tars/visualizer/src/component/timeline.tsx · ×1
  • packages/ui-tars/visualizer/src/component/timeline.tsx: 491 lines of code packages/ui-tars/visualizer/src/component/timeline.tsx:1 — packages/ui-tars/visualizer/src/component/timeline.tsx has 491 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 · multimodal/tarko/agent/src/agent/runner/llm-processor.ts · ×1
  • multimodal/tarko/agent/src/agent/runner/llm-processor.ts: 478 lines of code multimodal/tarko/agent/src/agent/runner/llm-processor.ts:1 — multimodal/tarko/agent/src/agent/runner/llm-processor.ts has 478 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 · multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts · ×1
  • multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts: 472 lines of code multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:1 — multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts has 472 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/agent-infra/browser-use/src/agent/actions/builder.ts · ×1
  • packages/agent-infra/browser-use/src/agent/actions/builder.ts: 461 lines of code packages/agent-infra/browser-use/src/agent/actions/builder.ts:1 — packages/agent-infra/browser-use/src/agent/actions/builder.ts has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · multimodal/websites/main/src/render/components/WorkflowNodes.tsx · ×1
  • multimodal/websites/main/src/render/components/WorkflowNodes.tsx: 460 lines of code multimodal/websites/main/src/render/components/WorkflowNodes.tsx:1 — multimodal/websites/main/src/render/components/WorkflowNodes.tsx has 460 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 · multimodal/tarko/llm-client/src/handlers/gemini.ts · ×1
  • multimodal/tarko/llm-client/src/handlers/gemini.ts: 459 lines of code multimodal/tarko/llm-client/src/handlers/gemini.ts:1 — multimodal/tarko/llm-client/src/handlers/gemini.ts has 459 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/agent-infra/mcp-servers/filesystem/src/server.ts · ×1
  • packages/agent-infra/mcp-servers/filesystem/src/server.ts: 448 lines of code packages/agent-infra/mcp-servers/filesystem/src/server.ts:1 — packages/agent-infra/mcp-servers/filesystem/src/server.ts has 448 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 · multimodal/tarko/agio/src/index.ts · ×1
  • multimodal/tarko/agio/src/index.ts: 432 lines of code multimodal/tarko/agio/src/index.ts:1 — multimodal/tarko/agio/src/index.ts has 432 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 · multimodal/agent-tars/core/src/environments/local/index.ts · ×1
  • multimodal/agent-tars/core/src/environments/local/index.ts: 429 lines of code multimodal/agent-tars/core/src/environments/local/index.ts:1 — multimodal/agent-tars/core/src/environments/local/index.ts has 429 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 · multimodal/tarko/agent/src/agent/message-history.ts · ×1
  • multimodal/tarko/agent/src/agent/message-history.ts: 423 lines of code multimodal/tarko/agent/src/agent/message-history.ts:1 — multimodal/tarko/agent/src/agent/message-history.ts has 423 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 · multimodal/tarko/agent-server-next/src/server.ts · ×1
  • multimodal/tarko/agent-server-next/src/server.ts: 422 lines of code multimodal/tarko/agent-server-next/src/server.ts:1 — multimodal/tarko/agent-server-next/src/server.ts has 422 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~738 LoC) · ×1
  • Dead file (~738 LoC) apps/ui-tars/src/renderer/src/components/ui/sidebar.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~689 LoC) · ×1
  • Dead file (~689 LoC) multimodal/tarko/agent-ui/src/common/services/apiService.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~651 LoC) · ×1
  • Dead file (~651 LoC) REDACTED — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~631 LoC) · ×1
  • Dead file (~631 LoC) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~584 LoC) · ×1
  • Dead file (~584 LoC) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~466 LoC) · ×1
  • Dead file (~466 LoC) apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/renderer/src/pages/remote/paid.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~451 LoC) · ×1
  • Dead file (~451 LoC) apps/ui-tars/src/main/remote/subscriptionClient.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/remote/operators.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~433 LoC) · ×1
  • Dead file (~433 LoC) multimodal/tarko/agent-ui/src/common/state/actions/sessionActions.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/hooks/useSession.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~389 LoC) · ×1
  • Dead file (~389 LoC) multimodal/tarko/agent-ui/src/standalone/sidebar/ChatSession.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/sidebar/SidebarContainer.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~387 LoC) · ×1
  • Dead file (~387 LoC) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/ToolHandler.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/EventHandlerRegistry.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~383 LoC) · ×1
  • Dead file (~383 LoC) multimodal/tarko/agent-ui/src/common/hooks/useReplay.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~371 LoC) · ×1
  • Dead file (~371 LoC) apps/ui-tars/src/renderer/src/pages/remote/paid.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~369 LoC) · ×1
  • Dead file (~369 LoC) multimodal/tarko/agent-ui/src/standalone/share/ShareModal.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/share/ShareButton.tsx, multimodal/tarko/agent-ui/src/standalone/share/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~365 LoC) · ×1
  • Dead file (~365 LoC) apps/ui-tars/src/main/remote/operators.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/services/runAgent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~338 LoC) · ×1
  • Dead file (~338 LoC) REDACTED — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/utils/agent.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~337 LoC) · ×1
  • Dead file (~337 LoC) multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~322 LoC) · ×1
  • Dead file (~322 LoC) multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/MessageHandler.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/EventHandlerRegistry.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~315 LoC) · ×1
  • Dead file (~315 LoC) multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/home/HomePage.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~309 LoC) · ×1
  • Dead file (~309 LoC) apps/ui-tars/src/main/electron-updater/GitHubProvider.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/ui-tars/src/main/electron-updater/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~308 LoC) · ×1
  • Dead file (~308 LoC) multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspacePanel.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~305 LoC) · ×1
  • Dead file (~305 LoC) apps/ui-tars/src/main/menu.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~303 LoC) · ×1
  • Dead file (~303 LoC) multimodal/tarko/agent-ui/src/common/services/SearchService.ts — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/renderers/SearchResultRenderer.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~294 LoC) · ×1
  • Dead file (~294 LoC) multimodal/tarko/agent-ui/src/standalone/navbar/ModelSelector.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (REDACTED, multimodal/tarko/agent-ui/src/standalone/navbar/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~292 LoC) · ×1
  • Dead file (~292 LoC) multimodal/tarko/agent-ui/src/standalone/workspace/renderers/ScriptResultRenderer.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~283 LoC) · ×1
  • Dead file (~283 LoC) multimodal/tarko/agent-ui/src/common/hooks/useReplayMode.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/common/hooks/useSession.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~277 LoC) · ×1
  • Dead file (~277 LoC) multimodal/tarko/agent-ui/src/standalone/chat/Message/components/ToolCalls.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/Message/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~273 LoC) · ×1
  • Dead file (~273 LoC) multimodal/tarko/agent-ui/src/standalone/navbar/AboutModal.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (REDACTED) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~267 LoC) · ×1
  • Dead file (~267 LoC) multimodal/tarko/agent-ui/src/standalone/workspace/components/RawModeRenderer.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/workspace/WorkspaceDetail.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~266 LoC) · ×1
  • Dead file (~266 LoC) multimodal/tarko/agent-ui/src/standalone/chat/ContextualSelector.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/chat/ContextualTags.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/MessageAttachments.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~265 LoC) · ×1
  • Dead file (~265 LoC) multimodal/tarko/agent-ui/src/standalone/home/WelcomeCards.tsx — no import path from any entry point (151 application, 171 tooling, 163 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (multimodal/tarko/agent-ui/src/standalone/home/WelcomePage.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unlisted import '@aws-sdk/client-bedrock-runtime' · ×1
  • Unlisted import '@aws-sdk/client-bedrock-runtime' packages/agent-infra/browser-use/test/azureBedrockChat.ts:11 — Imported only as a TYPE and declared in no reachable REDACTED. 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 REDACTED.
R8 · Dependency Hygiene · Unused dependency '@electron-forge/maker-pkg' · ×1
  • Unused dependency '@electron-forge/maker-pkg' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@electron-forge/plugin-base' · ×1
  • Unused dependency '@electron-forge/plugin-base' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@electron-forge/plugin-vite' · ×1
  • Unused dependency '@electron-forge/plugin-vite' — Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity multimodal/websites/main/public/index.html:5 — `https://www.googletagmanager.com/gtag/js?id=G-J82M1JQ6KF` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 7 such include(s) across the repository's markup.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1
  • Recursive walk over a caller-supplied document has no depth cap multimodal/tarko/agent-snapshot/src/utils/snapshot-normalizer.ts:318 — `normalize` is exported and takes `obj: any` from its caller, and it calls itself at line 318 (`this.normalize`) with a piece of `obj` (and at line 342) — and nowhere in `normalize` 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 `normalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Minor — 463 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×198
  • Orphaned file packages/ui-tars/visualizer/src/component/timeline.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/agent-infra/browser-use/src/agent/actions/builder.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/agent-infra/mcp-servers/filesystem/src/server.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/agent-infra/browser-use/src/agent/messages/service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/tarko/agent-server-next/src/services/ShareService.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/renderer/src/pages/remote/cast/canvas.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/tarko/agent-cli/src/core/commands/global-workspace.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/main/remote/subscriptionClient.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/gui-agent/operator-adb/src/AdbOperator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/renderer/src/pages/remote/free.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/gui-agent/operator-aio/src/AIOHybridOperator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/agent-infra/browser-use/src/agent/agents/navigator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ui-tars/visualizer/src/component/replay-scripts.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/tarko/agent-server-next/src/dao/mongodb/SandboxAllocationDAO.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/ui-tars/visualizer/src/component/store.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/main/remote/operators.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file apps/ui-tars/src/renderer/src/pages/remote/paid.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file multimodal/tarko/agent-server-next/src/dao/sqlite/SandboxAllocationDAO.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 173 more in this group — see findings.md.
D12 · Dependency Hygiene · Deprecated · ×87
  • Deprecated: @azure/openai REDACTED:1865 — @azure/openai 1.0.0-beta.13 is resolved in REDACTED and is marked deprecated by its publisher: "The Azure OpenAI client library for JavaScript beta has been retired. Please migrate to the stable OpenAI SDK for JavaScript using the migration guide: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/openai/openai/MIGRATION.md.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @humanwhocodes/config-array REDACTED:2966 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @humanwhocodes/object-schema REDACTED:2975 — @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @npmcli/move-file REDACTED:3524 — @npmcli/move-file 2.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: boolean REDACTED:5932 — boolean 3.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: crypto REDACTED:6359 — crypto 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:7370 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:7374 — glob 8.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:7618 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: lodash.get REDACTED:8201 — lodash.get 4.4.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: lodash.isequal REDACTED:8205 — lodash.isequal 4.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: node-domexception REDACTED:8725 — node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: phin REDACTED:9124 — phin 3.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: puppeteer REDACTED:9303 — puppeteer 24.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "< 24.15.0 is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:9598 — rimraf 2.6.3 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:9603 — rimraf 2.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:9608 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: sudo-prompt REDACTED:10219 — sudo-prompt 9.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: xterm-addon-fit REDACTED:11140 — xterm-addon-fit 0.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is now deprecated. Move to @xterm/addon-fit instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: xterm-addon-search REDACTED:11146 — xterm-addon-search 0.8.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is now deprecated. Move to @xterm/addon-search instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: xterm REDACTED:11152 — xterm 4.19.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is now deprecated. Move to @xterm/xterm instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: node-domexception REDACTED:1277 — node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @nextui-org/accordion REDACTED:3610 — @nextui-org/accordion 2.0.40 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/accordion instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @nextui-org/autocomplete REDACTED:3626 — @nextui-org/autocomplete 2.1.7 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/autocomplete instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @nextui-org/avatar REDACTED:3636 — @nextui-org/avatar 2.0.33 is resolved in REDACTED and is marked deprecated by its publisher: "This package has been deprecated. Please use @heroui/avatar instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 62 more in this group — see findings.md.
P2 · Observability · Console output used as the logging channel · ×39
  • Console output used as the logging channel apps/ui-tars/src/main/window/createWindow.ts:87 — `apps/ui-tars/src/main/window/createWindow.ts` reports through `console.*` at line 87 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel apps/ui-tars/src/main/utils/systemPermissions.ts:21 — `apps/ui-tars/src/main/utils/systemPermissions.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel apps/ui-tars/src/main/ipcRoutes/permission.ts:22 — `apps/ui-tars/src/main/ipcRoutes/permission.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel apps/ui-tars/src/main/ipcRoutes/setting.ts:29 — `apps/ui-tars/src/main/ipcRoutes/setting.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel apps/ui-tars/src/main/ipcRoutes/setting.ts:53 — `apps/ui-tars/src/main/ipcRoutes/setting.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel apps/ui-tars/src/main/electron-updater/GitHubProvider.ts:215 — `apps/ui-tars/src/main/electron-updater/GitHubProvider.ts` reports through `console.*` at line 215 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel REDACTED:342 — `REDACTED` reports through `console.*` at line 342 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/interactive.ts:47 — `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/interactive.ts:49 — `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/interactive.ts:51 — `infra/pdk/src/utils/interactive.ts` reports through `console.*` at line 51 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/logger.ts:15 — `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/logger.ts:16 — `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/logger.ts:17 — `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/logger.ts:18 — `infra/pdk/src/utils/logger.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/npm.ts:46 — `infra/pdk/src/utils/npm.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/utils/workspace.ts:55 — `infra/pdk/src/utils/workspace.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/changelog.ts:143 — `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 143 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/changelog.ts:144 — `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 144 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/changelog.ts:145 — `infra/pdk/src/commands/changelog.ts` reports through `console.*` at line 145 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:31 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:35 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:46 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:96 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 96 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:98 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel infra/pdk/src/commands/dev.ts:102 — `infra/pdk/src/commands/dev.ts` reports through `console.*` at line 102 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 14 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate multimodal/tarko/agent-server-next/src/controllers/sessions.ts:298 — `!Array.isArray(messages) || messages.length === 0` appears character-identically in 2 files — multimodal/tarko/agent-server-next/src/controllers/sessions.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx:184 — `!activeSessionId || isReplayMode || hasLoaded` appears character-identically in 2 files — multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatBottomSettings.tsx. 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 multimodal/gui-agent/cli/src/cli/start.ts:61 — `!config.baseURL || !config.apiKey || !config.model` appears character-identically in 2 files — multimodal/gui-agent/cli/src/cli/start.ts, packages/ui-tars/cli/src/cli/start.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 multimodal/tarko/mcp-agent/src/mcp-agent.ts:27 — `!filterOptions || (!filterOptions.include && !filterOptions.exclude)` appears character-identically in 2 files — multimodal/tarko/mcp-agent/src/mcp-agent.ts, multimodal/tarko/shared-utils/src/filter.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 multimodal/tarko/agent-server-next/src/controllers/system.ts:171 — `!sessionId || !model || !model.provider || !model.id` appears character-identically in 2 files — multimodal/tarko/agent-server-next/src/controllers/system.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx:147 — `!settings?.reportStorageBaseUrl || !uploadSuccess` appears character-identically in 2 files — apps/ui-tars/src/renderer/src/components/RunMessages/ShareOptions.tsx, apps/ui-tars/src/renderer/src/components/SideBar/share.tsx. 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 multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts:143 — `!state.currentParameters || Object.keys(state.currentParameters).length === 0` appears character-identically in 2 files — multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts, multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.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/ui-tars/src/renderer/src/components/SideBar/share.tsx:50 — `(await chatManager.getSessionMessages(sessionId)) || []` appears character-identically in 2 files — apps/ui-tars/src/renderer/src/components/SideBar/share.tsx, apps/ui-tars/src/renderer/src/store/session.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 multimodal/gui-agent/operator-browser/src/ui-helper.ts:267 — `(el as HTMLElement).hasAttribute('disabled') || (el as HTMLElement).getAttribute('aria-disabled') === 'true'` appears character-identically in 2 files — multimodal/gui-agent/operator-browser/src/ui-helper.ts, packages/ui-tars/operators/browser-operator/src/ui-helper.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/ui-tars/src/renderer/src/components/ImageGallery/index.tsx:130 — `ActionIconMap[action.type] || MousePointerClick` appears character-identically in 2 files — apps/ui-tars/src/renderer/src/components/ImageGallery/index.tsx, apps/ui-tars/src/renderer/src/pages/widget/index.tsx. 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 multimodal/gui-agent/agent-sdk/src/utils.ts:79 — `action_inputs.url || action_inputs.content || ''` appears character-identically in 3 files — multimodal/gui-agent/agent-sdk/src/utils.ts, multimodal/omni-tars/gui-agent/src/utils.ts, multimodal/tarko/shared-utils/src/gui-agent.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/ui-tars/src/main/remote/operators.ts:307 — `action_inputs?.key || action_inputs?.hotkey` appears character-identically in 2 files — apps/ui-tars/src/main/remote/operators.ts, packages/ui-tars/operators/nut-js/src/index.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 multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts:249 — `agentOptions.agio?.provider && this.agioProviderConstructor` appears character-identically in 2 files — multimodal/tarko/agent-server-next/src/services/session/AgentSession.ts, multimodal/tarko/agent-server/src/core/AgentSession.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/ui-tars/src/renderer/src/pages/remote/free.tsx:206 — `agentStatus === StatusEnum.RUNNING || agentStatus === StatusEnum.CALL_USER || agentStatus === StatusEnum.PAUSE` appears character-identically in 2 files — apps/ui-tars/src/renderer/src/pages/remote/free.tsx, apps/ui-tars/src/renderer/src/pages/remote/paid.tsx. 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 multimodal/tarko/agent-server-next/src/utils/model-utils.ts:41 — `appConfig.model || appConfig.server?.models?.[0]` appears character-identically in 2 files — multimodal/tarko/agent-server-next/src/utils/model-utils.ts, multimodal/tarko/agent-server/src/utils/model-utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:348 — `argsStr.match(/([^,']|'[^']*')+/g) || []` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate apps/ui-tars/src/main/remote/proxyClient.ts:634 — `browser.status === 'ready' && browser.id === browserId` appears character-identically in 2 files — apps/ui-tars/src/main/remote/proxyClient.ts, apps/ui-tars/src/main/remote/subscriptionClient.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 multimodal/tarko/llm-client/src/handlers/anthropic.ts:371 — `clonedMessages.length > 0 && clonedMessages[0].role === 'system'` appears character-identically in 2 files — multimodal/tarko/llm-client/src/handlers/anthropic.ts, multimodal/tarko/llm-client/src/handlers/gemini.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 infra/pdk/src/commands/next-version.ts:26 — `config.rootPackageJson.version || '0.0.0'` appears character-identically in 2 files — infra/pdk/src/commands/next-version.ts, infra/pdk/src/commands/release.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 multimodal/gui-agent/operator-browser/src/browser-operator.ts:403 — `content.endsWith('\n') || content.endsWith('\\n')` appears character-identically in 4 files — multimodal/gui-agent/operator-browser/src/browser-operator.ts, multimodal/gui-agent/operator-nutjs/src/NutJSOperator.ts, packages/ui-tars/operators/browser-operator/src/browser-operator.ts, packages/ui-tars/operators/nut-js/src/index.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 multimodal/gui-agent/agent-sdk/src/ToolCallEngine.ts:211 — `currentLoopAssistantEvent.rawContent || currentLoopAssistantEvent.content` appears character-identically in 4 files — multimodal/gui-agent/agent-sdk/src/ToolCallEngine.ts, multimodal/omni-tars/code-agent/src/CodeToolCallEngine.ts, multimodal/omni-tars/gui-agent/src/GUIAgentToolCallEngine.ts, multimodal/omni-tars/mcp-agent/src/McpToolCallEngine.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 multimodal/tarko/agent-server-next/src/server.ts:95 — `directories?.globalWorkspaceDir || TARKO_CONSTANTS.GLOBAL_WORKSPACE_DIR` appears character-identically in 2 files — multimodal/tarko/agent-server-next/src/server.ts, multimodal/tarko/agent-server/src/server.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 packages/agent-infra/browser-use/src/dom/service.ts:169 — `elementTree !== null && elementTree instanceof DOMElementNode` appears character-identically in 2 files — packages/agent-infra/browser-use/src/dom/service.ts, packages/agent-infra/mcp-servers/browser/src/context.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 packages/agent-infra/browser-use/src/browser/page.ts:402 — `error instanceof Error && error.message.includes('timeout')` appears character-identically in 2 files — packages/agent-infra/browser-use/src/browser/page.ts, packages/agent-infra/mcp-servers/browser/src/tools/navigate.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 multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/SystemHandler.ts:65 — `event.description || 'Environment Input'` appears character-identically in 2 files — multimodal/tarko/agent-ui/src/common/state/actions/eventProcessors/handlers/SystemHandler.ts, multimodal/tarko/agent/src/agent/message-history.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.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×19
  • Diagnostic log message is built whether or not it is wanted packages/agent-infra/browser-use/src/browser/page.ts:705 — `debug` at line 705 is called with an argument built by `JSON.stringify(element.attributes)` (line 705), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent-cli/src/config/display.ts:94 — `debug` at line 94 is called with an argument built by `data.join(', ')` (line 94), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent-cli/src/config/display.ts:96 — `debug` at line 96 is called with an argument built by `Object.keys(data)` (line 96), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/event-stream.ts:167 — `debug` at line 167 is called with an argument built by `types.join(', ')` (line 167), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/event-stream.ts:172 — `debug` at line 172 is called with an argument built by `types.join(', ')` (line 172), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/tool-manager.ts:83 — `debug` at line 83 is called with an argument built by `JSON.stringify(args)` (line 83), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/tool-manager.ts:92 — `debug` at line 92 is called with an argument built by `JSON.stringify(result)` (line 93), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/runner/tool-processor.ts:115 — `debug` at line 115 is called with an argument built by `JSON.stringify(args)` (line 115), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/tarko/agent/src/agent/runner/tool-processor.ts:123 — `debug` at line 123 is called with an argument built by `JSON.stringify(result)` (line 124), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:42 — `debug` at line 42 is called with an argument built by `JSON.stringify(tool)` (line 42), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:46 — `debug` at line 46 is called with an argument built by `JSON.stringify(operator_action)` (line 47), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:50 — `debug` at line 50 is called with an argument built by `JSON.stringify(operator_action)` (line 51), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/omni-tars/gui-agent/src/GUIAgentT5Adapter.ts:56 — `debug` at line 56 is called with an argument built by `JSON.stringify(action_for_gui_render)` (line 57), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:70 — `debug` at line 70 is called with an argument built by `JSON.stringify(roughAction)` (line 70), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:75 — `debug` at line 75 is called with an argument built by `JSON.stringify(action)` (line 75), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:218 — `debug` at line 218 is called with an argument built by `JSON.stringify(roughAction)` (line 218), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:223 — `debug` at line 223 is called with an argument built by `JSON.stringify(action)` (line 223), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:455 — `debug` at line 455 is called with an argument built by `JSON.stringify(coords)` (line 455), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
  • Diagnostic log message is built whether or not it is wanted multimodal/agent-tars/core/src/environments/local/browser/browser-gui-agent.ts:141 — `debug` at line 141 is called with an argument built by `JSON.stringify(normalizedCoordsAction, null, 2)` (line 145), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
D30 · Dependency Vulnerabilities · Low CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×13
  • Hand-rolled JSON/XML parsing via regex multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:494 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex multimodal/tarko/agent/src/tool-call-engine/PromptEngineeringToolCallEngine.ts:508 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex multimodal/gui-agent/action-parser/src/ActionParserHelper.ts:388 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:137 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:142 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:316 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:318 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:99 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:145 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:147 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:215 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:217 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:228 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
D12 · Dependency Hygiene · Outdated (npm) · ×12
  • Outdated (npm): @browserbasehq/stagehand packages/ui-tars/operators/browserbase/package.json:39 — @browserbasehq/stagehand is pinned at 1.13.0; registry.npmjs.org publishes 4.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mistralai/mistralai multimodal/tarko/llm-client/package.json:32 — @mistralai/mistralai is pinned at 0.5.0; registry.npmjs.org publishes 3.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/icons-material multimodal/websites/docs/package.json:18 — @mui/icons-material is pinned at 5.17.1; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @mui/material multimodal/websites/docs/package.json:19 — @mui/material is pinned at 5.17.1; registry.npmjs.org publishes 9.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ai examples/operator-browserbase/package.json:16 — ai is pinned at 4.3.19; registry.npmjs.org publishes 7.0.153 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): appium-adb multimodal/gui-agent/operator-adb/package.json:43 — appium-adb is pinned at 13.0.3; registry.npmjs.org publishes 16.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): boxen REDACTED:27 — boxen is pinned at 4.2.0; registry.npmjs.org publishes 9.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): chokidar REDACTED:30 — chokidar is pinned at 3.4.0; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): glob packages/agent-infra/mcp-client/package.json:38 — glob is pinned at 10.4.5; registry.npmjs.org publishes 13.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): inquirer REDACTED:34 — inquirer is pinned at 8.2.7; registry.npmjs.org publishes 14.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): string-width REDACTED:37 — string-width is pinned at 4.2.3; registry.npmjs.org publishes 8.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): uuid REDACTED:53 — uuid is pinned at 11.1.0; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
IC1 · Incompleteness & stubs · Disabled test · ×11
  • Disabled test multimodal/agent-tars/core/snapshot/index.test.ts:13 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test multimodal/tarko/agent/tests/agent/llm-processor-thinking.test.ts:11 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test multimodal/tarko/context-engineer/tests/repomix.test.ts:15 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test multimodal/tarko/mcp-agent/snapshot/index.test.ts:13 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/browser/tests/tools/tabs.test.ts:236 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/browser/tests/tools/tabs.test.ts:317 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:35 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:56 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:62 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/agent-infra/mcp-servers/commands/tests/integration/exec-utils.test.ts:72 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D10 · Test Quality · Mock-dominated test · ×7
  • Mock-dominated test: should include the running session ID in the response multimodal/tarko/agent-server/tests/middleware.test.ts:68 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should handle null running session ID multimodal/tarko/agent-server/tests/middleware.test.ts:80 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should work correctly in a typical middleware chain multimodal/tarko/agent-server/tests/middleware.test.ts:118 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should short-circuit middleware chain when blocking requests multimodal/tarko/agent-server/tests/middleware.test.ts:136 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: checks the token for workspace files multimodal/tarko/agent-server/tests/api/server-access-boundary.test.ts:272 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: lets web UI routes through without a check multimodal/tarko/agent-server/tests/api/server-access-boundary.test.ts:278 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should call LLM client with correct parameters when available multimodal/tarko/agent/tests/agent/kernel/agent-base.test.ts:129 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch examples/operator-browserbase/app/api/session/route.ts:74 — `getClosestRegion` swallows every exception into `return 'us-west-2'` — 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 infra/pdk/src/utils/git.ts:152 — `getCommitAuthorMap` 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 infra/pdk/src/utils/npm.ts:25 — `fetchPackageVersion` swallows every exception into `return '- (1st release)'` — 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 infra/pdk/src/utils/ai-changelog.ts:134 — `getRepoUrl` 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 multimodal/omni-tars/core/src/utils/hepler.ts:22 — `extractAioPort` swallows every exception into `return 8080` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
AX6 · Interface segregation · Fat interface · ×3
  • Fat interface: IAgent (31 required operations) multimodal/tarko/agent-interface/src/agent.ts:38 — `IAgent` declares 31 required operations: `initialize`, `run`, `run`, `run`, `abort`, `status`, `dispose`, `getEventStream`, `getTools`, `getLLMClient`, `generateSummary`, `getCurrentModel`, `onLLMRequest`, `onLLMResponse`, `onLLMStreamingResponse`, `onBeforeToolCall`, `onAfterToolCall`, `onToolCallError`, `onEachAgentLoopStart`, `onEachAgentLoopEnd`, `onAgentLoopEnd`, `onProcessToolCalls`, `onBeforeLoopTermination`, `requestLoopTermination`, `isLoopTerminationRequested`, `getCurrentLoopIteration`, `getOptions`, `callLLM`, `callLLM`, `callLLM`, `onPrepareRequest`. 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. Those 31 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. 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.
  • Fat interface: IDAOFactory (16 required operations) multimodal/tarko/agent-server-next/src/dao/interfaces/IDAOFactory.ts:20 — `IDAOFactory` declares 16 required operations: `initialize`, `isInitialized`, `close`, `getUserConfigDAO`, `getSessionDAO`, `getEventDAO`, `getSandboxAllocationDAO`, `healthCheck`, `createSession`, `updateSessionInfo`, `getSessionInfo`, `getAllSessions`, `getUserSessions`, `deleteSession`, `saveEvent`, `getSessionEvents`. 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.
  • Fat interface: AgentServer (19 required operations) multimodal/tarko/agent-server-next/src/types.ts:79 — `AgentServer` declares 19 required operations: `getSessionPool`, `getSessionFactory`, `isMultiTenant`, `getMemoryStats`, `start`, `stop`, `isServerRunning`, `getCurrentWorkspace`, `getCurrentAgentName`, `canAcceptNewRequest`, `setRunningSession`, `clearRunningSession`, `getRunningSessionId`, `getCurrentAgentResolution`, `getCustomAgioProvider`, `getAgentConstructorWebConfig`, `getStorageInfo`, `registerHook`, `unregisterHook`. 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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
M4 · Documentation accuracy · README/code drift · ×3
  • README/code drift CONTRIBUTING.md:139 — CONTRIBUTING.md links to `.github/workflows/release.yml`, but `.github/workflows/release.yml` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/archive-1.0/README.md:54 — docs/archive-1.0/README.md links to `./CONTRIBUTING.md`, but `docs/archive-1.0/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/agent-infra/search/browser-search/README.md:10 — packages/agent-infra/search/browser-search/README.md links to `./README.zh-CN.md`, but `packages/agent-infra/search/browser-search/README.zh-CN.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 89 significant file(s) lose their only recent owner: multimodal/tarko/agent/src/agent/agent.ts, REDACTED, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/ChatInput.tsx, multimodal/tarko/agent-server/src/storage/SQLiteStorageProvider.ts, multimodal/tarko/agent-ui/src/standalone/chat/MessageInput/AgentOptionsSelector.tsx, multimodal/tarko/agent-server/src/core/AgentSession.ts, multimodal/tarko/agent-ui/src/common/services/apiService.ts, multimodal/tarko/agent-interface/src/agent-event-stream.ts (+81 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: multimodal/omni-tars/mcp-agent/src/McpToolCallEngine.ts, multimodal/omni-tars/core/src/environments/code.ts, multimodal/omni-tars/code-agent/src/CodeToolCallEngine.ts. Pair on, review, or document these before any departure.
D30 · Dependency Vulnerabilities · Low vulnerability · ×2
  • REDACTED
  • REDACTED
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected multimodal/tarko/agent-server/src/server.ts:272 — `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected REDACTED:266 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (99 single-owned of 501 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 501 of the 1153 production source files in this repository met that bar). They are anonymized user #3 (3 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: REDACTED, apps/ui-tars/forge.config.ts, packages/agent-infra/mcp-servers/filesystem/src/index.ts, multimodal/gui-agent/operator-aio/src/AIOBrowser.ts, multimodal/gui-agent/agent-sdk/src/GUIAgent.ts, apps/ui-tars/src/renderer/src/pages/widget/index.tsx, apps/ui-tars/src/renderer/src/pages/remote/cast/vnc.tsx.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. The recognised ADR directories in this tree were read — `rfcs` — and none of their files is a decision record (a README, index or template page does not count). 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 · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 5 of 74 project(s) overshoot their size bounds, lowering Project Cohesion to 8.9/10. The most over is `multimodal/tarko/agent-ui` (17339 LoC, 180 module-visible types across 37 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 198 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/ui-tars/visualizer/src/component/timeline.tsx, packages/agent-infra/browser-use/src/agent/actions/builder.ts, apps/ui-tars/src/renderer/src/components/Settings/category/vlm.tsx, packages/agent-infra/mcp-servers/filesystem/src/server.ts, multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts, multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts, packages/agent-infra/browser-use/src/agent/messages/service.ts, multimodal/tarko/agent-server-next/src/services/ShareService.ts (and 190 more) (210 orphaned of 501 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 501 of the 1153 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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
IC1 · Incompleteness & stubs · Blanket warning suppression · ×1
  • Blanket warning suppression multimodal/tarko/llm-client/src/handlers/utils.ts:11 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 33/43 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `multimodal/agent-tars/cli`, `multimodal/gui-agent/cli`, `multimodal/tarko/agent-ui-cli`, `packages/agent-infra/create-new-mcp`, `packages/agent-infra/create-new-mcp/template-default` and 5 more.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 11/30 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 71/80 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~1.3 `!` null assertions per 1k TypeScript source lines — 185 assertion(s) across the 138656 source line(s) of the 1044 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: multimodal/omni-tars/core/src/utils/streamingParserT5/extractToolCallT5.ts (17), multimodal/omni-tars/core/src/utils/streamingParser/extractCode.ts (13), multimodal/gui-agent/operator-adb/src/AdbOperator.ts (9). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 112 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×108
  • Outdated (npm): @agent-infra/browser — @agent-infra/browser is pinned at 0.1.1; registry.npmjs.org publishes 0.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @agent-infra/browser-context — @agent-infra/browser-context is pinned at 0.1.2; registry.npmjs.org publishes 0.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @agent-infra/mcp-client — @agent-infra/mcp-client is pinned at 1.2.20; registry.npmjs.org publishes 1.2.29 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @agent-infra/media-utils — @agent-infra/media-utils is pinned at 0.1.5; registry.npmjs.org publishes 0.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @agent-infra/sandbox — @agent-infra/sandbox is pinned at 0.0.6; registry.npmjs.org publishes 1.0.17 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @anthropic-ai/sdk — @anthropic-ai/sdk is pinned at 0.24.3; registry.npmjs.org publishes 1.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @browserbasehq/sdk — @browserbasehq/sdk is pinned at 2.6.0; registry.npmjs.org publishes 2.22.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @clack/prompts — @clack/prompts is pinned at 0.11.0; registry.npmjs.org publishes 1.8.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @dqbd/tiktoken — @dqbd/tiktoken is pinned at 1.0.21; registry.npmjs.org publishes 1.0.22 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @emotion/styled — @emotion/styled is pinned at 11.14.0; registry.npmjs.org publishes 11.14.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @google/generative-ai — @google/generative-ai is pinned at 0.14.1; registry.npmjs.org publishes 0.24.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @headlessui/react — @headlessui/react is pinned at 1.7.19; registry.npmjs.org publishes 2.2.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @hono/node-server — @hono/node-server is pinned at 1.19.3; registry.npmjs.org publishes 2.1.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @hookform/resolvers — @hookform/resolvers is pinned at 5.0.1; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @langchain/core — @langchain/core is pinned at 0.3.42; registry.npmjs.org publishes 1.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.15.1; registry.npmjs.org publishes 1.32.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @nextui-org/react — @nextui-org/react is pinned at 2.4.8; registry.npmjs.org publishes 2.6.11 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @octokit/rest — @octokit/rest is pinned at 20.1.2; registry.npmjs.org publishes 22.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-alert-dialog — @radix-ui/react-alert-dialog is pinned at 1.1.7; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-avatar — @radix-ui/react-avatar is pinned at 1.1.4; registry.npmjs.org publishes 1.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-checkbox — @radix-ui/react-checkbox is pinned at 1.3.2; registry.npmjs.org publishes 1.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-collapsible — @radix-ui/react-collapsible is pinned at 1.1.4; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-dialog — @radix-ui/react-dialog is pinned at 1.1.7; registry.npmjs.org publishes 1.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-dropdown-menu — @radix-ui/react-dropdown-menu is pinned at 2.1.7; registry.npmjs.org publishes 2.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-hover-card — @radix-ui/react-hover-card is pinned at 1.1.14; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • + 83 more in this group — see findings.md.
D5 · Coupling · Off the main sequence · ×4
  • Off the main sequence: @tarko/shared-media-utils — @tarko/shared-media-utils: abstractness 0.00, instability 0.00, distance 1.00 — 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.
  • Off the main sequence: @ui-tars/shared — @ui-tars/shared: abstractness 0.00, instability 0.00, distance 1.00 — 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.
  • Off the main sequence: @agent-infra/shared — @agent-infra/shared: abstractness 0.14, instability 0.00, distance 0.86 — 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.
  • Off the main sequence: @tarko/shared-utils — @tarko/shared-utils: abstractness 0.00, instability 0.14, distance 0.86 — 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-0f03e44e0e224aee923e18537e1b80a4/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-0f03e44e0e224aee923e18537e1b80a4/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 --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .83artifacts/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-update226artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .10artifacts/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 9 file(s) — `apps/ui-tars/src/main/store/create.ts`, `infra/pdk/src/types.ts`, `multimodal/agent-tars/core/src/index.ts`, `multimodal/tarko/agent-interface/src/agent-instance.ts`, `multimodal/tarko/llm-client/src/handlers/gemini.ts`, … (+4 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 01a1794d-0cf2-74b0-bd1b-5ce2e27bc9df · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 282 · Warnings: 1080 · Recommendations: 463 · Info: 112 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 17:40 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