Public report of cypress-io/cypress, 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Assert 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, 15:59 UTC · Survey ID cd_e94d67f9fec041b89b1dd3072743b7b9
cypress-io/cypress
Measured 26 October 2026, 15:29 UTC, at code version c3d0e39
No regression 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 scoreAt riskNo change 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.
A large codebase: 187,167 lines of product code in 55 projects, tests not counted · Estimated rebuild effort: about 2.9 person-years · Weakest lens: Production Readiness, 35
Findings by how serious they are
440 critical3055 serious689 minor
12 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, 15:29 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 ▸
88of 88 dimensions measured by tools.
4149of 4184 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
88dimensions across 7 lenses, read from 187,167 lines of product code in 55 projects.
cypress-io/cypress is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 40 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 35, is the weakest lens and counts most in the score. The best first steps are rebalancing the test suite towards unit tests and fixing the password or key in the code, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 45.
113 known security holes in the packages the code depends on can be used by attackers. Twelve places in the code run text as code, which an attacker could use, and six passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key, updating the vulnerable packages and replacing text run as code with direct calls would close these risks. Fixing the weaknesses the scanner points to would fix the six security weaknesses in the code, and setting a waiting period for automatic updates would deal with the five automatic dependency updates that take new releases at once. The 228 tests that check nothing need to check the result they produce.
The product code is 187,167 lines, about €420,000 to rebuild.
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 forThe 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.
If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 40 to about 45.
Code composition: what the lines of code are
Product code 38%Tests 62%
New since the last survey: 620 findings
These 620 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.
Test Quality · Skipped test: snapshots an entry, typescripts an intermediate file, and snapshots again tooling/v8-snapshot/test/unit/doctor.spec.ts
Test Quality · Skipped test: passes in parallel with group system-tests/test/record_spec.ts
Test Quality · Skipped test: passes system-tests/test/window_open_spec.js
Test Quality · Skipped test: never runs system-tests/projects/tap-retries/cypress/e2e/hooks.cy.js
Test Quality · Skipped test: skipped test system-tests/projects/studio/cypress/e2e/skipped.cy.js
Test Quality · Skipped test: is pending due to .skip system-tests/projects/e2e/cypress/e2e/config_record.cy.js
Test Quality · Skipped test: is pending system-tests/projects/e2e/cypress/e2e/simple_pending.cy.js
Test Quality · Skipped test: Login demo system-tests/projects/e2e/cypress/e2e/source_rewriting.cy.js
Test Quality · Skipped test: fails with promise system-tests/projects/e2e/cypress/e2e/uncaught_during_test.cy.js
Test Quality · Skipped test: aborts system-tests/projects/e2e/cypress/e2e/xhr.cy.js
Test Quality · Skipped test: t2 system-tests/projects/cloud-debug-filter/cypress/e2e/skip-and-only.cy.js
Test Quality · Skipped test: errors on required props missing system-tests/projects/angular-signals/src/signals-required/signals-required.component.cy.ts
Test Quality · Skipped test: test 1 system-tests/project-fixtures/runner-specs/cypress/e2e/hooks/skip.cy.js
Test Quality · Skipped test: attaches warning to non-chrome browsers when chromeWebSecurity:false packages/server/test/unit/project-base.spec.ts
Test Quality · Skipped test: only attaches warning to non-chrome browsers when chromeWebSecurity:true packages/server/test/unit/project-base.spec.ts
Test Quality · Skipped test: does not call startSpecWatcher if not in interactive mode packages/server/test/unit/project-base.spec.ts
Test Quality · Skipped test: calls startSpecWatcher if in interactive mode packages/server/test/unit/project-base.spec.ts
Test Quality · Skipped test: logs error and exits when project folder has read permissions only and cannot write cypress.config.js packages/server/test/integration/cypress_spec.js
Test Quality · Skipped test: passes filtered options to Project#open and sets cli config packages/server/test/integration/cypress_spec.js
Test Quality · Skipped test: renders and escapes markdown with leading/trailing whitespace packages/reporter/cypress/e2e/test_errors.cy.ts
Test Quality · Skipped test: is active when all children are active packages/reporter/cypress/e2e/unit/suite_model.cy.ts
Test Quality · Skipped test: is active when there are active tests with passing tests packages/reporter/cypress/e2e/unit/suite_model.cy.ts
Test Quality · Skipped test: is active when there are active tests with pending tests packages/reporter/cypress/e2e/unit/suite_model.cy.ts
Test Quality · Skipped test: is active even when children suites are not packages/reporter/cypress/e2e/unit/suite_model.cy.ts
Test Quality · Skipped test: works with Yarn 3 Plug n Play packages/launchpad/cypress/e2e/project-setup.cy.ts
Test Quality · Skipped test: generates valid config file for pristine project without cypress installed packages/launchpad/cypress/e2e/scaffold-project.cy.ts
Test Quality · Skipped test: wraps long code without line numbers packages/frontend-shared/src/components/ShikiHighlight.cy.tsx
Test Quality · Skipped test: wraps long code with line numbers packages/frontend-shared/src/components/ShikiHighlight.cy.tsx
Test Quality · Skipped test: can visit jira packages/driver/cypress/e2e/e2e/aut_window_patches.cy.ts
Test Quality · Skipped test: can set hostOnly cookies packages/driver/cypress/e2e/e2e/e2e_cookies.cy.ts
Test Quality · Skipped test: should be skipped packages/driver/cypress/e2e/e2e/testConfigOverrides.cy.ts
Test Quality · Skipped test: cancels pending requests that are incomplete packages/driver/cypress/e2e/e2e/xhr_abort.cy.ts
Test Quality · Skipped test: reset top packages/driver/cypress/e2e/e2e/origin/basic_login.cy.ts
Test Quality · Skipped test: logs in with primary set via baseurl packages/driver/cypress/e2e/e2e/origin/basic_login.cy.ts
Test Quality · Skipped test: final auth redirects back to localhost - nested packages/driver/cypress/e2e/e2e/origin/basic_login.cy.ts
Test Quality · Skipped test: final auth redirects back to localhost - nested - approval first packages/driver/cypress/e2e/e2e/origin/basic_login.cy.ts
Test Quality · Skipped test: final auth redirects back to approval page - nested packages/driver/cypress/e2e/e2e/origin/basic_login.cy.ts
Test Quality · Skipped test: the runner url updates appropriately packages/driver/cypress/e2e/e2e/origin/navigation.cy.ts
Test Quality · Skipped test: succeeds on an ipv6 address packages/driver/cypress/e2e/e2e/origin/validation.cy.ts
Test Quality · Skipped test: uses cy.origin twice packages/driver/cypress/e2e/e2e/origin/validation.cy.ts
Test Quality · Skipped test: supports nesting a third origin packages/driver/cypress/e2e/e2e/origin/commands/navigation.cy.ts
Test Quality · Skipped test: does not propagate the auth options across tests packages/driver/cypress/e2e/e2e/origin/commands/navigation.cy.ts
Test Quality · Skipped test: returns empty when only hash is present REDACTED
Test Quality · Skipped test: does not fail when using it.skip packages/driver/cypress/e2e/cy/skipping_sync.cy.ts
Test Quality · Skipped test: throws a good error when wrapping mixed types: element + string packages/driver/cypress/e2e/commands/misc.cy.ts
Test Quality · Skipped test: waits for the 4th request before resolving packages/driver/cypress/e2e/commands/waiting.cy.ts
Test Quality · Skipped test: finds elements within shadow roots with cross-boundary selector packages/driver/cypress/e2e/commands/querying/shadow_dom.cy.ts
Test Quality · Skipped test: gets indexed Interception by alias.number packages/driver/cypress/e2e/commands/net_stubbing/waiting_and_aliasing.cy.ts
Test Quality · Skipped test: does not reset the timeout packages/driver/cypress/e2e/commands/navigation/page_load.cy.ts
Test Quality · Skipped test: can cancel multiple dblclicks packages/driver/cypress/e2e/commands/actions/dblclick.cy.ts
Test Quality · Skipped test: slurps up failed promises packages/driver/cypress/e2e/commands/actions/focus.cy.ts
Test Quality · Skipped test: records correct pageX and pageY el scrolled packages/driver/cypress/e2e/commands/actions/trigger.cy.ts
Test Quality · Skipped test: handles higher-order-components packages/data-context/test/unit/actions/CodegenActions.spec.ts
Test Quality · Skipped test: shows copy tooltip when button is focused packages/app/src/runner/selector-playground/SelectorPlayground.cy.tsx
Test Quality · Skipped test: filters the list of specs when searching for specs packages/app/cypress/e2e/reporter_header.cy.ts
Test Quality · Skipped test: when a project is created, injects new projectId into the config file, and sends expected UTM params packages/app/cypress/e2e/runs.cy.ts
Test Quality · Skipped test: opens Connect Project modal after clicking Reconnect Project button packages/app/cypress/e2e/runs.cy.ts
Test Quality · Skipped test: resize nav and persist the state after refresh packages/app/cypress/e2e/sidebar_navigation.cy.ts
Test Quality · Skipped test: shows no icon and file system timestamp for files packages/app/cypress/e2e/specs_list_no_git_repo.cy.ts
Test Quality · Skipped test: creates a new test with a url that changes top packages/app/cypress/e2e/studio/studio-new-tests.cy.ts
Test Quality · Skipped test: opens attempt on each attempt failure for the screenshot, and closes after test passes packages/app/cypress/e2e/runner/retries.ui.cy.ts
Test Quality · Skipped test: imports and applies style npm/vue/cypress/component/basic/style-in-spec/todo.cy.ts
Test Quality · Skipped test: shows two items at the start npm/vue/cypress/component/basic/props/message-list.cy.ts
Test Quality · Skipped test: works with react-router and lazy route npm/vite-plugin-cypress-esm/cypress/component/edgeCases.cy.tsx
Test Quality · Skipped test: parses tag1 but not tag2 npm/grep/test/unit.spec.ts
Test Quality · Skipped test: first test npm/grep/cypress/e2e/omit-and-skip.cy.ts
Test Quality · Skipped test: is pending npm/grep/cypress/e2e/skip.cy.ts
Test Quality · Skipped test: is pending again npm/grep/cypress/e2e/skip.cy.ts
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-config.js
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-config.js
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-fail.js
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-pass.js
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-pass.js
Test Quality · Skipped test: some test npm/eslint-plugin-dev/test/fixtures/skip-comment-pass.js
Test Quality · Skipped test: test cli/types/tests/cypress-tests.ts
Test Quality · Skipped test: test cli/types/tests/cypress-tests.ts
Test Quality · No assertions: errors and exits without projectId system-tests/test/record_spec.ts
Test Quality · No assertions: respects quiet mode system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits on 401 system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: when grouping without parallelization errors and exits with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: does not proceed and exits with error with 1 when posix exit codes are enabled when parallelizing and creating instance system-tests/test/record_spec.ts
Test Quality · No assertions: without parallelization - does not proceed with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: does not proceed and exits with error with 1 when posix exit codes are enabled when parallelizing and updating instance system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits with 1 when posix exit codes are enabled when there is an unknown 422 response system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when on free plan and over recorded tests limit system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits with 1 when posix exit codes are enabled when on free plan and over recorded tests limit system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when attempting parallel run when not available in plan system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits with 1 when posix exit codes are enabled when attempting parallel run when not available in plan system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when attempting parallel run when not available in plan system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when attempting parallel run when not available in plan with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when there's an unknown 402 error system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when there's an unknown 402 error with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when auto cancel not available in plan system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits when auto cancel not available in plan system-tests/test/record_spec.ts
Test Quality · No assertions: errors and exits on createInstance error with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: without parallelization errors and exits with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: with parallelization errors and exits with 1 when posix exit codes are enabled system-tests/test/record_spec.ts
Test Quality · No assertions: exits with code 1 when posix exit codes are enabled system-tests/test/record_spec.ts
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: 804 findings
These 804 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.
Test Quality · No assertions: works npm/react/cypress/component/advanced/app-action-example/counter.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/advanced/custom-command/spec.cy.jsx
Test Quality · No assertions: works using React.createElement npm/react/cypress/component/advanced/custom-command/spec.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/advanced/forward-ref/forward-ref.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/advanced/hooks/counter-with-hooks.cy.jsx
Test Quality · No assertions: counts clicks 2 npm/react/cypress/component/advanced/hooks/counter-with-hooks.cy.jsx
Test Quality · No assertions: renders npm/react/cypress/component/advanced/lazy-loaded/other.cy.jsx
Test Quality · No assertions: renders lazy component npm/react/cypress/component/advanced/lazy-loaded/app.cy.jsx
Test Quality · No assertions: should render children npm/react/cypress/component/advanced/set-timeout-example/loading-indicator.cy.jsx
Test Quality · No assertions: does not retry npm/react/cypress/component/advanced/test-retries/spec.cy.jsx
Test Quality · No assertions: retries npm/react/cypress/component/advanced/test-retries/spec.cy.jsx
Test Quality · No assertions: starts and lets X win npm/react/cypress/component/advanced/tutorial/tic-tac-toe.cy.jsx
Test Quality · No assertions: works by itself npm/react/cypress/component/basic/wrap.cy.jsx
Test Quality · No assertions: works inside a div npm/react/cypress/component/basic/wrap.cy.jsx
Test Quality · No assertions: counts clicks npm/react/cypress/component/basic/transpiled.cy.jsx
Test Quality · No assertions: counts clicks 2 npm/react/cypress/component/basic/transpiled.cy.jsx
Test Quality · No assertions: goes to 3 npm/react/cypress/component/basic/transpiled.cy.jsx
Test Quality · No assertions: shows link npm/react/cypress/component/basic/stateless.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/basic/pure-component.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/basic/hello-x.cy.jsx
Test Quality · No assertions: renders Unicode npm/react/cypress/component/basic/hello-x.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/basic/hello-world.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/basic/hello-world-inline.cy.jsx
Test Quality · No assertions: shows link npm/react/cypress/component/basic/alert.cy.jsx
Test Quality · No assertions: counts clicks npm/react/cypress/component/basic/counter-set-state/counter.cy.jsx
Test Quality · No assertions: goes to 3 npm/react/cypress/component/basic/counter-set-state/counter.cy.jsx
Test Quality · No assertions: works npm/react/cypress/component/basic/counter-use-hooks/counter-hooks.cy.jsx
Test Quality · No assertions: renders npm/react/cypress/component/basic/react-tutorial/shopping-list.cy.jsx
Test Quality · No assertions: says hello to different people npm/react/cypress/component/basic/react-tutorial/hello.cy.jsx
Test Quality · No assertions: shows hello npm/vue/cypress/component/basic/spec.cy.js
Test Quality · No assertions: changes message if data changes npm/vue/cypress/component/basic/spec.cy.js
Test Quality · No assertions: reverses text npm/vue/cypress/component/basic/reverse.cy.js
Test Quality · No assertions: shows hello npm/vue/cypress/component/basic/options.cy.js
Test Quality · No assertions: renders slots npm/vue/cypress/component/basic/slots/Card.cy.js
Test Quality · No assertions: User can type and see output on the screen npm/vue/cypress/component/basic/small-examples/Repeater.cy.js
Test Quality · No assertions: renders correctly npm/vue/cypress/component/basic/small-examples/Counter.cy.js
Test Quality · No assertions: correctly responds to button clicks npm/vue/cypress/component/basic/small-examples/Counter.cy.js
Test Quality · No assertions: renders label npm/vue/cypress/component/basic/small-examples/AppInput.cy.js
Test Quality · No assertions: does not trigger 'viewport:changed' when changing to the default packages/driver/cypress/e2e/commands/window.cy.js
Test Quality · No assertions: does not trigger 'viewport:changed' when changing to the same viewport packages/driver/cypress/e2e/commands/window.cy.js
Test Quality · No assertions: does not throw when passed width equal to 0 packages/driver/cypress/e2e/commands/window.cy.js
Test Quality · No assertions: does not throw when passed width equal to 1000000 packages/driver/cypress/e2e/commands/window.cy.js
Test Quality · No assertions: does not mutate 2nd route methods when using shorthand route packages/driver/cypress/e2e/commands/waiting.cy.js
Test Quality · No assertions: does not retry after 1 alias times out packages/driver/cypress/e2e/commands/waiting.cy.js
Test Quality · No assertions: does not error when querySelectorAll is wrapped and snapshots are off packages/driver/cypress/e2e/commands/traversals_shadow_dom.cy.js
Test Quality · No assertions: queries shadow dom packages/driver/cypress/e2e/commands/traversals_shadow_dom.cy.js
Test Quality · No assertions: also queries shadow dom packages/driver/cypress/e2e/commands/traversals_shadow_dom.cy.js
Test Quality · No assertions: queries shadow dom packages/driver/cypress/e2e/commands/traversals_shadow_dom.cy.js
Test Quality · No assertions: overrides test-level option being false packages/driver/cypress/e2e/commands/traversals_shadow_dom.cy.js
Test Quality · No assertions (empty test): takes screenshot of hook title with test packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: does not error with "offset out of range" when capturing an element packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: can screenshot when element height changes on scroll packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if there is a 0px tall element height packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if padding is not a number packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if padding is not an array of numbers packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if padding is not an array with a length between 1 and 4 packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if padding is a large negative number that causes a 0px tall element height packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if clip is not an object packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if clip is lacking proper keys packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if clip has extraneous keys packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: throws if clip has non-number values packages/driver/cypress/e2e/commands/screenshot.cy.js
Test Quality · No assertions: accepts object with url packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts object with url, method, headers, body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts object with url + timeout packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts string url packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts method + url packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts method + url + body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts url + body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts url + string body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts body equal to true packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts body equal to false packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts (explicitly defined) null body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: uppercases method packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: uses absolute urls and adds trailing slash packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: uses localhost urls packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: uses www urls packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: prefixes with baseUrl when origin is empty packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: prefixes with baseUrl over current origin packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: encode url with ’ character in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: dont re-encode url with ’ escaped in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: encode url with % character in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: dont re-encode url with % escaped in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: encode url with Astral Plane Unicode in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: dont re-encode url with Astral Plane Unicode escaped character in pathname packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: should percent escape Unicode in pathname and convert Unicode in domain name properly packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: should percent escape Unicode in pathname and convert Unicode in domain name with URI encoded URL packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: lowercases encoding packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: defaults encoding to `utf8` packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: can turn off gzipping packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: sends auth when it is an object packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: is true by default packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: can be set to false packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: normalizes followRedirects -> followRedirect packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts an object literal packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts an object literal for body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: accepts a string for body packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: application/x-www-form-urlencoded w/ an object body uses form: true packages/driver/cypress/e2e/commands/request.cy.js
Test Quality · No assertions: url, body and stores Route packages/driver/cypress/e2e/commands/net_stubbing.cy.ts
Test Quality · No assertions: url, HTTPController and stores Route packages/driver/cypress/e2e/commands/net_stubbing.cy.ts
Test Quality · No assertions: regex values stringified and other values copied and stores Route packages/driver/cypress/e2e/commands/net_stubbing.cy.ts
Rebuild cost: about €420,000 · Estimate
Cost to rebuild
€140,000 to €710,000, for 2,348 to 7,449 hours of work, about 2.9 person-years for 1 to 6 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 40. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 187,167 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Inverted test pyramid finding(s) in Test Distribution.
Resolve the 8 Assertions commented out finding(s) in Test Quality — start with click.cy.ts (8).
Raises the score by about 3 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €420,000 to build again, about 2.9 person-years of work. Its weakest lens is Production Readiness, at 35 (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 1 Inverted test pyramid finding(s) in Test Distribution. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Test Distribution findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 125,806 lines over the last 90 days, which is about 510,213 lines a year. At that pace, the extra work comes to an estimated 25.5 to 170.1 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.
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.
692 modules, with 664 dependencies between them. 2 loops run through 39 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 652 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.
cli.lib.tap.types uses packages.cypress-sessions.lib.contracts.pinned, so a change to packages.cypress-sessions.lib.contracts.pinned can break cli.lib.tap.types, while a change to cli.lib.tap.types can't break packages.cypress-sessions.lib.contracts.pinned.
Position
Below the diagonal: cli.lib.tap.types uses a module listed above it, which is the healthy direction.
packages.app.src.runner.event-manager uses packages.types.src.driver, so a change to packages.types.src.driver can break packages.app.src.runner.event-manager, while a change to packages.app.src.runner.event-manager can't break packages.types.src.driver.
Position
Below the diagonal: packages.app.src.runner.event-manager uses a module listed above it, which is the healthy direction.
packages.app.src.tap uses packages.types.src.driver, so a change to packages.types.src.driver can break packages.app.src.tap, while a change to packages.app.src.tap can't break packages.types.src.driver.
Position
Below the diagonal: packages.app.src.tap uses a module listed above it, which is the healthy direction.
packages.data-context.src.data.coreDataShape uses packages.cypress-sessions.lib.generated.graphql, so a change to packages.cypress-sessions.lib.generated.graphql can break packages.data-context.src.data.coreDataShape, while a change to packages.data-context.src.data.coreDataShape can't break packages.cypress-sessions.lib.generated.graphql.
Position
Below the diagonal: packages.data-context.src.data.coreDataShape uses a module listed above it, which is the healthy direction.
packages.proxy.lib.http uses packages.network-interception.lib.ports.http-interception, so a change to packages.network-interception.lib.ports.http-interception can break packages.proxy.lib.http, while a change to packages.proxy.lib.http can't break packages.network-interception.lib.ports.http-interception.
Position
Below the diagonal: packages.proxy.lib.http uses a module listed above it, which is the healthy direction.
packages.proxy.lib.http uses packages.network-tools.lib.remote-states, so a change to packages.network-tools.lib.remote-states can break packages.proxy.lib.http, while a change to packages.proxy.lib.http can't break packages.network-tools.lib.remote-states.
Position
Below the diagonal: packages.proxy.lib.http uses a module listed above it, which is the healthy direction.
packages.proxy.lib.http uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.proxy.lib.http, while a change to packages.proxy.lib.http can't break packages.types.src.protocol.
Position
Below the diagonal: packages.proxy.lib.http uses a module listed above it, which is the healthy direction.
packages.proxy.lib.http uses tooling.electron-mksnapshot.src.config, so a change to tooling.electron-mksnapshot.src.config can break packages.proxy.lib.http, while a change to packages.proxy.lib.http can't break tooling.electron-mksnapshot.src.config.
Position
Below the diagonal: packages.proxy.lib.http uses a module listed above it, which is the healthy direction.
packages.reporter.src.header.stats-store uses packages.types.src.driver, so a change to packages.types.src.driver can break packages.reporter.src.header.stats-store, while a change to packages.reporter.src.header.stats-store can't break packages.types.src.driver.
Position
Below the diagonal: packages.reporter.src.header.stats-store uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables-store uses packages.reporter.src.lib.app-state, so a change to packages.reporter.src.lib.app-state can break packages.reporter.src.runnables.runnables-store, while a change to packages.reporter.src.runnables.runnables-store can't break packages.reporter.src.lib.app-state.
Position
Below the diagonal: packages.reporter.src.runnables.runnables-store uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables-store uses packages.types.src.driver, so a change to packages.types.src.driver can break packages.reporter.src.runnables.runnables-store, while a change to packages.reporter.src.runnables.runnables-store can't break packages.types.src.driver.
Position
Below the diagonal: packages.reporter.src.runnables.runnables-store uses a module listed above it, which is the healthy direction.
packages.server.lib.browsers.cdp-protocol.cri-client uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.server.lib.browsers.cdp-protocol.cri-client, while a change to packages.server.lib.browsers.cdp-protocol.cri-client can't break packages.types.src.protocol.
Position
Below the diagonal: packages.server.lib.browsers.cdp-protocol.cri-client uses a module listed above it, which is the healthy direction.
packages.types.src.server uses packages.types.src.modeOptions, so a change to packages.types.src.modeOptions can break packages.types.src.server, while a change to packages.types.src.server can't break packages.types.src.modeOptions.
Position
Below the diagonal: packages.types.src.server uses a module listed above it, which is the healthy direction.
packages.types.src.server uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.types.src.server, while a change to packages.types.src.server can't break packages.types.src.protocol.
Position
Below the diagonal: packages.types.src.server uses a module listed above it, which is the healthy direction.
cli.lib.tap uses packages.cypress-sessions.lib, so a change to packages.cypress-sessions.lib can break cli.lib.tap, while a change to cli.lib.tap can't break packages.cypress-sessions.lib.
Position
Below the diagonal: cli.lib.tap uses a module listed above it, which is the healthy direction.
cli.lib.tap uses cli.lib.tap.types, so a change to cli.lib.tap.types can break cli.lib.tap, while a change to cli.lib.tap can't break cli.lib.tap.types.
Position
Below the diagonal: cli.lib.tap uses a module listed above it, which is the healthy direction.
cli.lib.tap.commands uses packages.cypress-sessions.lib, so a change to packages.cypress-sessions.lib can break cli.lib.tap.commands, while a change to cli.lib.tap.commands can't break packages.cypress-sessions.lib.
Position
Below the diagonal: cli.lib.tap.commands uses a module listed above it, which is the healthy direction.
cli.lib.tap.commands uses cli.lib.tap.types, so a change to cli.lib.tap.types can break cli.lib.tap.commands, while a change to cli.lib.tap.commands can't break cli.lib.tap.types.
Position
Below the diagonal: cli.lib.tap.commands uses a module listed above it, which is the healthy direction.
cli.lib.tap.render uses packages.cypress-sessions.lib.contracts.pinned, so a change to packages.cypress-sessions.lib.contracts.pinned can break cli.lib.tap.render, while a change to cli.lib.tap.render can't break packages.cypress-sessions.lib.contracts.pinned.
Position
Below the diagonal: cli.lib.tap.render uses a module listed above it, which is the healthy direction.
cli.lib.tap.render uses cli.lib.tap.types, so a change to cli.lib.tap.types can break cli.lib.tap.render, while a change to cli.lib.tap.render can't break cli.lib.tap.types.
Position
Below the diagonal: cli.lib.tap.render uses a module listed above it, which is the healthy direction.
packages.data-context.src.actions.ProjectActions uses packages.types.src.modeOptions, so a change to packages.types.src.modeOptions can break packages.data-context.src.actions.ProjectActions, while a change to packages.data-context.src.actions.ProjectActions can't break packages.types.src.modeOptions.
Position
Below the diagonal: packages.data-context.src.actions.ProjectActions uses a module listed above it, which is the healthy direction.
packages.data-context.src.actions.ProjectActions uses packages.types.src.server, so a change to packages.types.src.server can break packages.data-context.src.actions.ProjectActions, while a change to packages.data-context.src.actions.ProjectActions can't break packages.types.src.server.
Position
Below the diagonal: packages.data-context.src.actions.ProjectActions uses a module listed above it, which is the healthy direction.
27→36 packages.data-context.src.actions.ProjectActions uses packages.data-context.src.DataContextpart of a loop✕
Connections
1 pair of types, where a type in packages.data-context.src.actions.ProjectActions uses a type in packages.data-context.src.DataContext.
packages.data-context.src.actions.ProjectActions uses packages.data-context.src.DataContext, so a change to packages.data-context.src.DataContext can break packages.data-context.src.actions.ProjectActions, while a change to packages.data-context.src.actions.ProjectActions can't break packages.data-context.src.DataContext.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.reporter.src.attempts.attempt-model uses packages.types.src.driver, so a change to packages.types.src.driver can break packages.reporter.src.attempts.attempt-model, while a change to packages.reporter.src.attempts.attempt-model can't break packages.types.src.driver.
Position
Below the diagonal: packages.reporter.src.attempts.attempt-model uses a module listed above it, which is the healthy direction.
packages.reporter.src.attempts.attempt-model uses packages.reporter.src.runnables.runnables-store, so a change to packages.reporter.src.runnables.runnables-store can break packages.reporter.src.attempts.attempt-model, while a change to packages.reporter.src.attempts.attempt-model can't break packages.reporter.src.runnables.runnables-store.
Position
Below the diagonal: packages.reporter.src.attempts.attempt-model uses a module listed above it, which is the healthy direction.
packages.reporter.src.lib.events uses packages.reporter.src.lib.app-state, so a change to packages.reporter.src.lib.app-state can break packages.reporter.src.lib.events, while a change to packages.reporter.src.lib.events can't break packages.reporter.src.lib.app-state.
Position
Below the diagonal: packages.reporter.src.lib.events uses a module listed above it, which is the healthy direction.
packages.reporter.src.lib.events uses packages.reporter.src.header.stats-store, so a change to packages.reporter.src.header.stats-store can break packages.reporter.src.lib.events, while a change to packages.reporter.src.lib.events can't break packages.reporter.src.header.stats-store.
Position
Below the diagonal: packages.reporter.src.lib.events uses a module listed above it, which is the healthy direction.
packages.reporter.src.lib.events uses packages.reporter.src.runnables.runnables-store, so a change to packages.reporter.src.runnables.runnables-store can break packages.reporter.src.lib.events, while a change to packages.reporter.src.lib.events can't break packages.reporter.src.runnables.runnables-store.
Position
Below the diagonal: packages.reporter.src.lib.events uses a module listed above it, which is the healthy direction.
packages.server.lib.automation.automation uses packages.types.src.server, so a change to packages.types.src.server can break packages.server.lib.automation.automation, while a change to packages.server.lib.automation.automation can't break packages.types.src.server.
Position
Below the diagonal: packages.server.lib.automation.automation uses a module listed above it, which is the healthy direction.
packages.data-context.src.sources.ProjectDataSource uses packages.types.src.modeOptions, so a change to packages.types.src.modeOptions can break packages.data-context.src.sources.ProjectDataSource, while a change to packages.data-context.src.sources.ProjectDataSource can't break packages.types.src.modeOptions.
Position
Below the diagonal: packages.data-context.src.sources.ProjectDataSource uses a module listed above it, which is the healthy direction.
packages.data-context.src.sources.ProjectDataSource uses packages.data-context.src.data.coreDataShape, so a change to packages.data-context.src.data.coreDataShape can break packages.data-context.src.sources.ProjectDataSource, while a change to packages.data-context.src.sources.ProjectDataSource can't break packages.data-context.src.data.coreDataShape.
Position
Below the diagonal: packages.data-context.src.sources.ProjectDataSource uses a module listed above it, which is the healthy direction.
packages.data-context.src.sources.ProjectDataSource uses packages.data-context.src.actions.ProjectActions, so a change to packages.data-context.src.actions.ProjectActions can break packages.data-context.src.sources.ProjectDataSource, while a change to packages.data-context.src.sources.ProjectDataSource can't break packages.data-context.src.actions.ProjectActions.
Position
Below the diagonal: packages.data-context.src.sources.ProjectDataSource uses a module listed above it, which is the healthy direction.
31→36 packages.data-context.src.sources.ProjectDataSource uses packages.data-context.src.DataContextpart of a loop✕
Connections
1 pair of types, where a type in packages.data-context.src.sources.ProjectDataSource uses a type in packages.data-context.src.DataContext.
packages.data-context.src.sources.ProjectDataSource uses packages.data-context.src.DataContext, so a change to packages.data-context.src.DataContext can break packages.data-context.src.sources.ProjectDataSource, while a change to packages.data-context.src.sources.ProjectDataSource can't break packages.data-context.src.DataContext.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.reporter.src.main uses packages.reporter.src.lib.app-state, so a change to packages.reporter.src.lib.app-state can break packages.reporter.src.main, while a change to packages.reporter.src.main can't break packages.reporter.src.lib.app-state.
Position
Below the diagonal: packages.reporter.src.main uses a module listed above it, which is the healthy direction.
packages.reporter.src.main uses packages.reporter.src.header.stats-store, so a change to packages.reporter.src.header.stats-store can break packages.reporter.src.main, while a change to packages.reporter.src.main can't break packages.reporter.src.header.stats-store.
Position
Below the diagonal: packages.reporter.src.main uses a module listed above it, which is the healthy direction.
packages.reporter.src.main uses packages.reporter.src.runnables.runnables-store, so a change to packages.reporter.src.runnables.runnables-store can break packages.reporter.src.main, while a change to packages.reporter.src.main can't break packages.reporter.src.runnables.runnables-store.
Position
Below the diagonal: packages.reporter.src.main uses a module listed above it, which is the healthy direction.
packages.reporter.src.main uses packages.reporter.src.lib.events, so a change to packages.reporter.src.lib.events can break packages.reporter.src.main, while a change to packages.reporter.src.main can't break packages.reporter.src.lib.events.
Position
Below the diagonal: packages.reporter.src.main uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables uses packages.reporter.src.lib.app-state, so a change to packages.reporter.src.lib.app-state can break packages.reporter.src.runnables.runnables, while a change to packages.reporter.src.runnables.runnables can't break packages.reporter.src.lib.app-state.
Position
Below the diagonal: packages.reporter.src.runnables.runnables uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables uses packages.reporter.src.header.stats-store, so a change to packages.reporter.src.header.stats-store can break packages.reporter.src.runnables.runnables, while a change to packages.reporter.src.runnables.runnables can't break packages.reporter.src.header.stats-store.
Position
Below the diagonal: packages.reporter.src.runnables.runnables uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables uses packages.reporter.src.runnables.runnables-store, so a change to packages.reporter.src.runnables.runnables-store can break packages.reporter.src.runnables.runnables, while a change to packages.reporter.src.runnables.runnables can't break packages.reporter.src.runnables.runnables-store.
Position
Below the diagonal: packages.reporter.src.runnables.runnables uses a module listed above it, which is the healthy direction.
packages.reporter.src.runnables.runnables uses packages.reporter.src.lib.events, so a change to packages.reporter.src.lib.events can break packages.reporter.src.runnables.runnables, while a change to packages.reporter.src.runnables.runnables can't break packages.reporter.src.lib.events.
Position
Below the diagonal: packages.reporter.src.runnables.runnables uses a module listed above it, which is the healthy direction.
packages.server.lib.browsers uses packages.network-interception.lib.types.external-types, so a change to packages.network-interception.lib.types.external-types can break packages.server.lib.browsers, while a change to packages.server.lib.browsers can't break packages.network-interception.lib.types.external-types.
Position
Below the diagonal: packages.server.lib.browsers uses a module listed above it, which is the healthy direction.
packages.server.lib.browsers uses packages.server.lib.browsers.cdp-protocol.cri-client, so a change to packages.server.lib.browsers.cdp-protocol.cri-client can break packages.server.lib.browsers, while a change to packages.server.lib.browsers can't break packages.server.lib.browsers.cdp-protocol.cri-client.
Position
Below the diagonal: packages.server.lib.browsers uses a module listed above it, which is the healthy direction.
packages.server.lib.browsers uses packages.server.lib.automation.automation, so a change to packages.server.lib.automation.automation can break packages.server.lib.browsers, while a change to packages.server.lib.browsers can't break packages.server.lib.automation.automation.
Position
Below the diagonal: packages.server.lib.browsers uses a module listed above it, which is the healthy direction.
packages.server.lib.server-base uses packages.network-tools.lib.remote-states, so a change to packages.network-tools.lib.remote-states can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.network-tools.lib.remote-states.
Position
Below the diagonal: packages.server.lib.server-base uses a module listed above it, which is the healthy direction.
packages.server.lib.server-base uses packages.types.src.modeOptions, so a change to packages.types.src.modeOptions can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.types.src.modeOptions.
Position
Below the diagonal: packages.server.lib.server-base uses a module listed above it, which is the healthy direction.
packages.server.lib.server-base uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.types.src.protocol.
Position
Below the diagonal: packages.server.lib.server-base uses a module listed above it, which is the healthy direction.
packages.server.lib.server-base uses packages.server.lib.browsers.cdp-protocol.cri-client, so a change to packages.server.lib.browsers.cdp-protocol.cri-client can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.server.lib.browsers.cdp-protocol.cri-client.
Position
Below the diagonal: packages.server.lib.server-base uses a module listed above it, which is the healthy direction.
packages.server.lib.server-base uses packages.server.lib.automation.automation, so a change to packages.server.lib.automation.automation can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.server.lib.automation.automation.
Position
Below the diagonal: packages.server.lib.server-base uses a module listed above it, which is the healthy direction.
35→39 packages.server.lib.server-base uses packages.server.lib.project-basepart of a loop✕
Connections
1 pair of types, where a type in packages.server.lib.server-base uses a type in packages.server.lib.project-base.
packages.server.lib.server-base uses packages.server.lib.project-base, so a change to packages.server.lib.project-base can break packages.server.lib.server-base, while a change to packages.server.lib.server-base can't break packages.server.lib.project-base.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.data-context.src.DataContext uses packages.data-context.src.data.coreDataShape, so a change to packages.data-context.src.data.coreDataShape can break packages.data-context.src.DataContext, while a change to packages.data-context.src.DataContext can't break packages.data-context.src.data.coreDataShape.
Position
Below the diagonal: packages.data-context.src.DataContext uses a module listed above it, which is the healthy direction.
packages.data-context.src.DataContext uses packages.data-context.src.actions.ProjectActions, so a change to packages.data-context.src.actions.ProjectActions can break packages.data-context.src.DataContext, while a change to packages.data-context.src.DataContext can't break packages.data-context.src.actions.ProjectActions.
Position
Below the diagonal: packages.data-context.src.DataContext uses a module listed above it, which is the healthy direction.
packages.data-context.src.DataContext uses packages.data-context.src.sources.ProjectDataSource, so a change to packages.data-context.src.sources.ProjectDataSource can break packages.data-context.src.DataContext, while a change to packages.data-context.src.DataContext can't break packages.data-context.src.sources.ProjectDataSource.
Position
Below the diagonal: packages.data-context.src.DataContext uses a module listed above it, which is the healthy direction.
36→37 packages.data-context.src.DataContext uses packages.data-context.src.DataActionspart of a loop✕
Connections
1 pair of types, where a type in packages.data-context.src.DataContext uses a type in packages.data-context.src.DataActions.
packages.data-context.src.DataContext uses packages.data-context.src.DataActions, so a change to packages.data-context.src.DataActions can break packages.data-context.src.DataContext, while a change to packages.data-context.src.DataContext can't break packages.data-context.src.DataActions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
packages.data-context.src.DataActions uses packages.data-context.src.actions.ProjectActions, so a change to packages.data-context.src.actions.ProjectActions can break packages.data-context.src.DataActions, while a change to packages.data-context.src.DataActions can't break packages.data-context.src.actions.ProjectActions.
Position
Below the diagonal: packages.data-context.src.DataActions uses a module listed above it, which is the healthy direction.
packages.data-context.src.DataActions uses packages.data-context.src.DataContext, so a change to packages.data-context.src.DataContext can break packages.data-context.src.DataActions, while a change to packages.data-context.src.DataActions can't break packages.data-context.src.DataContext.
Position
Below the diagonal: packages.data-context.src.DataActions uses a module listed above it, which is the healthy direction.
packages.server.lib uses packages.cypress-sessions.lib, so a change to packages.cypress-sessions.lib can break packages.server.lib, while a change to packages.server.lib can't break packages.cypress-sessions.lib.
Position
Below the diagonal: packages.server.lib uses a module listed above it, which is the healthy direction.
packages.server.lib uses packages.network-interception.lib.ports.driving-ports, so a change to packages.network-interception.lib.ports.driving-ports can break packages.server.lib, while a change to packages.server.lib can't break packages.network-interception.lib.ports.driving-ports.
Position
Below the diagonal: packages.server.lib uses a module listed above it, which is the healthy direction.
packages.server.lib uses packages.network-interception.lib.ports.http-interception, so a change to packages.network-interception.lib.ports.http-interception can break packages.server.lib, while a change to packages.server.lib can't break packages.network-interception.lib.ports.http-interception.
Position
Below the diagonal: packages.server.lib uses a module listed above it, which is the healthy direction.
packages.server.lib uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.server.lib, while a change to packages.server.lib can't break packages.types.src.protocol.
Position
Below the diagonal: packages.server.lib uses a module listed above it, which is the healthy direction.
packages.server.lib uses packages.data-context.src.DataContext, so a change to packages.data-context.src.DataContext can break packages.server.lib, while a change to packages.server.lib can't break packages.data-context.src.DataContext.
Position
Below the diagonal: packages.server.lib uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.types.src.modeOptions, so a change to packages.types.src.modeOptions can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.types.src.modeOptions.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.types.src.protocol.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.types.src.server, so a change to packages.types.src.server can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.types.src.server.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.server.lib.automation.automation, so a change to packages.server.lib.automation.automation can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.server.lib.automation.automation.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.server.lib.server-base, so a change to packages.server.lib.server-base can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.server.lib.server-base.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.project-base uses packages.data-context.src.DataContext, so a change to packages.data-context.src.DataContext can break packages.server.lib.project-base, while a change to packages.server.lib.project-base can't break packages.data-context.src.DataContext.
Position
Below the diagonal: packages.server.lib.project-base uses a module listed above it, which is the healthy direction.
packages.server.lib.util uses packages.types.src.protocol, so a change to packages.types.src.protocol can break packages.server.lib.util, while a change to packages.server.lib.util can't break packages.types.src.protocol.
Position
Below the diagonal: packages.server.lib.util uses a module listed above it, which is the healthy direction.
packages.server.lib.util uses packages.server.lib.project-base, so a change to packages.server.lib.project-base can break packages.server.lib.util, while a change to packages.server.lib.util can't break packages.server.lib.project-base.
Position
Below the diagonal: packages.server.lib.util uses a module listed above it, which is the healthy direction.
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 category
Findings
Severity
A03:2025 — Software Supply Chain Failures
179
High / Critical
A05:2025 — Injection
121
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
A02:2025 — Security Misconfiguration
4
High / Critical
A01:2025 — Broken Access Control
2
Medium
Roadmap
First, address critical security risks by removing insecure TLS configurations that bypass certificate validation and resolving leaked secrets in configuration files. Next, correct the test distribution imbalance to ensure proper test coverage hierarchy. Finally, establish a robust disaster recovery strategy with documented recovery objectives and clean up the dependency tree by removing unused packages and correcting their scope.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Inverted test pyramid finding(s) in Test Distribution.
Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 4 sites, not one: `packages/proxy/lib/http/send-request-outgoing.ts:28` (`strictSSL: false`), `packages/server/lib/request.ts:23` (`NODE_TLS_REJECT_UNAUTHORIZED = "0"`), `packages/server/lib/request.ts:664` (`strictSSL: false`), `packages/server/lib/request.ts:733` (`strictSSL: false`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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.
Test Quality: No assertions (empty test): throws when not a DOM subject
REDACTED
4.0
Mixed
Static 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 — 440
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 — 3055
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 — 689
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
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. 88 of 88 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 88 dimensions across the health lenses
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
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, 4149 of 4184 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.)
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.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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 cli/ failed in the analyzer sandbox (yarn install v1.22.22), 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. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI 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 cli/ failed in the analyzer sandbox (yarn install v1.22.22), 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 cli/ was NOT MEASURED: the dependency install for cli/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/cypress-schematic/ was NOT MEASURED: the dependency install for npm/cypress-schematic/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/eslint-plugin-dev/ was NOT MEASURED: the dependency install for npm/eslint-plugin-dev/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/grep/ was NOT MEASURED: the dependency install for npm/grep/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/puppeteer/ was NOT MEASURED: the dependency install for npm/puppeteer/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/vite-dev-server/ was NOT MEASURED: the dependency install for npm/vite-dev-server/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/webpack-batteries-included-preprocessor/ was NOT MEASURED: the dependency install for npm/webpack-batteries-included-preprocessor/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/webpack-dev-server/ was NOT MEASURED: the dependency install for npm/webpack-dev-server/ failed in the analyzer sandbox (yarn install v1.22.22), 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 npm/webpack-preprocessor/ was NOT MEASURED: the dependency install for npm/webpack-preprocessor/ failed in the analyzer sandbox (yarn install v1.22.22), 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 packages/agent-info/ was NOT MEASURED: the dependency install for packages/agent-info/ failed in the analyzer sandbox (yarn install v1.22.22), 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.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Dependency Hygiene couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
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.
D32 Data Compliance (PII/GDPR) — 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. `cli/lib/tap/commands/status.ts`, `cli/types/cypress.d.ts`, `packages/cypress-sessions/lib/tap-contract.ts`, `packages/cypress-sessions/lib/tap-errors.ts`, `packages/driver/cypress/e2e/commands/command_option_immutability.cy.ts`, … (+6 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — dev Pulling watch Pulling ci Pulling ci Error Get "https://registry-1.docker.io/v2/": Forbidden dev Error context canceled watch Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: watch Skipped - Image is already being pulled by dev dev Pulling ci Pulling ci Error Get "https://registry-1.docker.io/v2/": Forbidden dev Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'better-sqlite3' is imported (packages/types/src/protocol.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'better-sqlite3' is imported (packages/types/src/protocol.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'better-sqlite3' is imported (packages/types/src/protocol.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'better-sqlite3' is imported (packages/types/src/protocol.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
IC1 Incompleteness & stubs — 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. 74 further occurrence(s) are not listed individually; the score already reflects all 114.
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 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
M4 Documentation accuracy — measured, with a gap in what it reached — 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. 116 further occurrence(s) are not listed individually; the score already reflects all 156.
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. 125 further occurrence(s) are not listed individually; the score already reflects all 165.
R11 Import Boundaries — 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. 144 further occurrence(s) are not listed individually; the score already reflects all 184.
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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
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. 168 further occurrence(s) are not listed individually; the score already reflects all 208.
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. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
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: 63 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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
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.
108 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was $Cypress.action at 85. A further 4 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 ServerBase._onResolveUrl at 23 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/server/lib/server-base.ts (ServerBase._onResolveUrl at 23), packages/packherd-require/src/require.ts (require.packherdRequire at 19), packages/server/lib/browsers/bidi_automation.ts (bidi_automation.normalizeResourceType at 17), packages/server/lib/browsers/webkit-automation.ts (WebKitAutomation.onRequest at 16). 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.
+ 101 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with $Cypress.action (cyclomatic 85), mouse.create (cyclomatic 78), navigation.default (cyclomatic 65). — 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 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce 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.
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.
+ 127 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with mouse.create (cognitive 75), validation.isValidClientCertificatesSet (cognitive 63). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 41 FunctionTooLong finding(s) in God Classes — start with run.ts (3), ci_provider.ts (2), REDACTED (2). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 12 FileTooLong finding(s) in God Classes — start with errors.ts, keyboard.ts, server-base.ts. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 MethodTooLong finding(s) in God Classes — start with event-manager.ts (2), socket-base.ts, cypress.ts. — One of this dimension's main actionable groups (9 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 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.
49 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 10 module(s) off the main sequence, with abstractness counted on 45 of the 49 (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: @packages/agent-info · ×10
What to do
Resolve the 10 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (10 warning-level).
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.
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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with command-model.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution1.7 / 10Critical✓ 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.
16341 test methods: 6675 unit, 431 integration, 0 BDD, 9235 e2e. The JavaScript/TypeScript suite contributes 16341 `it`/`test` case(s) across 1754 test file(s) declaring at least one; its tier split is read from package names and paths only.
Inverted test pyramid
What to do
Resolve the 1 Inverted test pyramid finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.1 / 10Adequategated by 228 critical 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.
111 skipped (35 with a documented reason), 1834 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 16341 tests (7 harness-style project(s) excluded from the assertion penalty).
No assertions (empty test): ...bar · ×220system-tests/projects/webpack-dev-server/src/[...bar].cy.js:1
Assertions commented out: events when element moved on mousedown · ×8packages/driver/cypress/e2e/commands/actions/click.cy.ts:376
No assertions: works with an installed browser path · ×1492system-tests/test/browser_path_spec.js:40
Skipped test: snapshots an entry, typescripts an intermediate file, and snapshots again · ×76tooling/v8-snapshot/test/unit/doctor.spec.ts:389
Test project verifies nothing: system-tests/projects/angular-custom-root · ×5system-tests/projects/angular-custom-root/ui/app/app.component.cy.ts:4
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 220 No assertions (empty test) finding(s) in Test Quality — start with app.cy.js (12), cypress-tests.ts (12), hook_caught_error_failing.cy.js (10). — One of this dimension's main actionable groups (220 issue-level).
Resolve the 8 Assertions commented out finding(s) in Test Quality — start with click.cy.ts (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1492 No assertions finding(s) in Test Quality — start with config.spec.ts (59), net-stubbing-tests.ts (56), type_special_chars.cy.ts (53). — One of this dimension's main actionable groups (1492 warning-level).
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.
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.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 264 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 267 production dependency(ies) this repository's committed lockfile resolves, across 150 product REDACTED manifest(s). Its 1415 `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. 2 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. A further 3 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under ISC / MIT, which is its own choice and is not judged here.
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.
Resolve the 15 Hotspot finding(s) in Churn × Complexity Hotspots — start with cdp-fetch-transport.ts, socket-base.ts, server-base.ts. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ProjectConfigManager.ts. — 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.
Do you agree with this assessment?
D16 · Bus Factor9.1 / 10Exemplary✓ 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.
65 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/driver/src/cy/mouse.ts. Counted over 698 of the 2177 production source files in this repository: 1472 are under the ~2,400-byte size floor this dimension measures over, and the remaining 7 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
599 deducted task-comment markers across 145693 LoC (0.4/KLoC) → score 9.2. 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.
TodoComment repeated across 10 filespackages/launchpad/cypress/e2e/top-nav-launchpad.cy.ts:544
What to do
Resolve the 537 TodoComment finding(s) in Explicit Debt — start with errors.ts (14), REDACTED (11), intercepting_request.cy.ts (11). — One of this dimension's main actionable groups (537 warning-level).
Resolve the 30 FixmeComment finding(s) in Explicit Debt — start with project-base.spec.ts (4), cookie_behavior.cy.ts (4), page_load.cy.ts (4). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 4 HackComment finding(s) in Explicit Debt — start with spec_helper.ts, mocha.ts, assertions.ts. — One of this dimension's main actionable groups (4 warning-level).
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.
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.
1 of 1 documentation facets pass in full. 113 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
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.
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.
49 domain type(s) cross context boundaries across 52 contexts.
Cross-context type TestingType (types → data-context) · ×19packages/data-context/src/sources/ProjectDataSource.ts:299
Cross-context type TestingType (types → config) · ×5packages/config/src/options.ts:99
Cross-context type TestState (types → reporter) · ×5packages/reporter/src/instruments/instrument-model.ts:26
Cross-context type TestingType (types → server) · ×4packages/server/lib/routes.ts:45
Cross-context type TapExecResult (cypress-sessions → app) · ×2packages/app/src/tap/contract.ts:62
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 19 Cross-context type TestingType (types → data-context) finding(s) in Boundary Type-Coupling — start with ProjectLifecycleManager.ts (6), ProjectActions.ts (4), ProjectDataSource.ts (3). — One of this dimension's main actionable groups (19 warning-level).
Resolve the 5 Cross-context type TestingType (types → config) finding(s) in Boundary Type-Coupling — start with browser.ts (3), options.ts, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Cross-context type TestState (types → reporter) finding(s) in Boundary Type-Coupling — start with attempt-model.ts (2), instrument-model.ts, suite-model.ts. — One of this dimension's main actionable groups (5 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 55 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
26 % of calls cross a namespace and 2 % go through an interface, but 69 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
121 finding(s): 0 critical, 29 high, 76 medium, 16 low. semgrep hit a parse error in 35 file(s) — `.circleci/scripts/generate-pipeline-parameters.sh` (line 117, line 169), `cli/lib/tap/commands/status.ts` (line 44), `cli/types/cypress.d.ts` (line 1613), `packages/cypress-sessions/lib/tap-contract.ts` (line 129, line 147, line 162, …), `packages/cypress-sessions/lib/tap-errors.ts` (lines 35–38, lines 42–45, lines 53–56, …), … (+30 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 20 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), 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.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 96 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (77), REDACTED (19). — One of this dimension's main actionable groups (96 issue-level).
Resolve the 14 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (3). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 11 file(s) — `cli/lib/tap/commands/status.ts`, `cli/types/cypress.d.ts`, `packages/cypress-sessions/lib/tap-contract.ts`, `packages/cypress-sessions/lib/tap-errors.ts`, `packages/driver/cypress/e2e/commands/command_option_immutability.cy.ts`, … (+6 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
172 of 705 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is system-tests/__snapshots__/typescript_spec_support_spec.ts.js. Counted over 705 of the 2177 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 172 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (7), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (172 recommendation-level).
Resolve the 1 Orphaned files with no living knowledge 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.
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.
Resolve the 10 Boundary-crossing change coupling finding(s) in Change Coupling — start with SpecRunnerOpenMode.vue (2), studio-app-types.ts (2), options.ts. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 4 Change coupling finding(s) in Change Coupling — start with REDACTED, REDACTED, record_spec.ts.js. — 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.
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.
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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.0 / 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.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — packages/app/src/runner/automation/AutInfo.vue:6, packages/extension/app/newtab.html:10, packages/extension/app/popup.html:8
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.
Do you agree with this assessment?
AC2 · Forms & labels5.4 / 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.
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). (×2) — packages/app/src/debug/DebugSpec.vue:159, packages/reporter/src/lib/switch.tsx:17
This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×4) — packages/app/src/runner/SnapshotHighlightControls.vue:9, packages/app/src/settings/device/NotificationSettings.vue:40, packages/app/src/settings/device/TestingPreferences.vue:14, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — packages/frontend-shared/src/components/Input.vue:29
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — packages/frontend-shared/src/gql-components/ChooseExternalEditor.vue:4, packages/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue:42, packages/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue:75, …
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) — packages/reporter/src/commands/command.tsx:136, packages/reporter/src/commands/command.tsx:560
This <span> 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. — packages/reporter/src/commands/command.tsx:432
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — packages/reporter/src/runnables/runnable-error.tsx:26
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.
Do you agree with this assessment?
AC3 · Page structure4.7 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×6) — packages/driver/index.html:2, packages/extension/app/newtab.html:2, packages/extension/app/popup.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. — packages/driver/src/cy/snapshots.ts:85
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×4) — packages/extension/app/newtab.html:2, packages/extension/app/popup.html:2, packages/server/lib/html/non_proxied_error.html:1, …
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — packages/frontend-shared/src/components/ListRowHeader.vue:15
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×2) — packages/reporter/static/index.html:2, packages/server/lib/util/network_failures.ts:20
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.
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".
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. — packages/app/src/navigation/SidebarNavigationHeader.vue:8
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×2) — packages/frontend-shared/src/components/Card.vue:2, packages/frontend-shared/src/gql-components/error/ErrorCodeFrame.vue:8
This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it. — packages/frontend-shared/src/components/Collapsible.vue:7
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. Give it a role as well, so assistive tech can announce what it is. — packages/frontend-shared/src/components/ShikiHighlight.vue:21
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×5) — packages/reporter/src/commands/command.tsx:130, packages/reporter/src/commands/command.tsx:136, packages/reporter/src/commands/command.tsx:432, …
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. — packages/reporter/src/commands/command.tsx:549
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. (×3) — packages/reporter/src/components/LaunchStudioIcon.tsx:19, REDACTED:52, packages/reporter/src/runnables/runnables.tsx:72
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×2) — packages/reporter/src/lib/file-name-opener.tsx:26, packages/reporter/src/runnables/runnables.tsx:63
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
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.
<button> 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). (×7) — packages/app/src/components/FileMatchButton.vue:2, packages/app/src/runner/SnapshotControls.vue:30, packages/app/src/runner/SnapshotToggle.vue:6, …
<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) — packages/app/src/components/FileMatchInput.vue:2, packages/app/src/runner/SpecRunnerHeaderOpenMode.vue:33
<iconloading> 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:. — packages/app/src/navigation/SidebarNavigationHeader.vue:53
<i-cy-loading_x16> 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:. (×2) — packages/frontend-shared/src/gql-components/ChooseExternalEditorModal.vue:48, packages/launchpad/src/setup/ButtonBar.vue:12
`.componentButton.orange button` sets color: white on background-color: #f5923e — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — npm/react/cypress/component/basic/css-modules/Button.module.css:24
`.component-button.orange button` sets color: white on background-color: #F5923E — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — npm/react/cypress/component/basic/css/Button.css:24
`.reporter .runnable .runnable-wrapper .collapsible-header:focus-visible .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/runnables/runnables.scss:156
`.reporter .runnable .runnable-wrapper .collapsible-header:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/runnables/runnables.scss:152
`.reporter .runnable .runnable-wrapper .collapsible-header .collapsible-header-inner:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/runnables/runnables.scss:183
`.reporter .hooks-container .hook-header .collapsible-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/hooks/hooks.scss:59
`.reporter .hooks-container .hook-header .collapsible-header > .collapsible-header-inner:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/hooks/hooks.scss:63
`.reporter .spec-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/header/header.scss:14
`.reporter .runnable-err-stack-expander .collapsible-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/errors/errors.scss:184
`.reporter .runnable-err-stack-expander .collapsible-header .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/errors/errors.scss:203
`.reporter .runnable-err-stack-expander .runnable-err-print:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/errors/errors.scss:220
`.reporter .command-pin` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/commands/commands.scss:490
`.reporter .attempt-item > .collapsible > .attempt-name > .collapsible-header .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/reporter/src/attempts/attempts.scss:60
`ul>li>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/extension/app/popup.css:37
`.description :deep(a)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/app/src/settings/project/ExperimentRow.vue:74
`.assertion-type:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/app/src/runner/studio/AssertionType.ce.vue:118
`.assertion-type` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/app/src/runner/studio/AssertionType.ce.vue:97
`.square:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — npm/react/cypress/component/basic/react-tutorial/tic-tac-toe.css:37, npm/react/cypress/component/advanced/tutorial/tic-tac-toe.css:37
`.reporter .runnable-loading .runnable-loading-animation div` moves (`animation: scaling 1.65s 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. — packages/reporter/src/runnables/runnables.scss:501
`button.switch span.indicator` moves (`transition: transform 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/reporter/src/lib/switch.scss:98
`.reporter .command-state-pending + .command-progress span` moves (`animation-name: progress-bar`) 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. — packages/reporter/src/commands/commands.scss:273
`.reporter %command-expander-base .command-expander` moves (`transition: transform 150ms 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. — packages/reporter/src/commands/commands.scss:508
`.reporter .collapsible-indicator` moves (`transition: transform 150ms 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. — packages/reporter/src/collapsible/collapsible.scss:7
`.App-logo` moves (`animation: App-logo-spin infinite 20s linear`) 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. — npm/react/cypress/component/advanced/set-timeout-example/App.css:6
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.
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.
Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 282 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-vuejs-accessibility, then run the suite that already asserts accessibility in CI so a regression blocks the merge.
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.
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.
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.
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.
`ProjectApiShape` declares 24 required operations: `openProjectCreate`, `launchProject`, `insertProjectToCache`, `removeProjectFromCache`, `getProjectRootsFromCache`, `insertProjectPreferencesToCache`, `getProjectPreferencesFromCache`, `clearLatestProjectsCache`, `clearProjectPreferences`, `clearAllProjectPreferences`, `closeActiveProject`, `getConfig`, `getRemoteStates`, `getCurrentBrowser`, `getCurrentProjectSavedState`, `setPromptShown`, `setProjectPreferences`, `makeProjectSavedState`, `getDevServer`, `isListening`, `resetBrowserTabsForNextSpec`, `resetServer`, `runSpec`, `routeToDebug`. 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. — packages/data-context/src/actions/ProjectActions.ts:26
`StateFunc` declares 43 required operations under just 2 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, and 3 more. 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. That is an OVERLOAD SET, not 43 separate responsibilities: a caller binds to 2 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 43 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — packages/driver/src/cypress/state.ts:15
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
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.
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.
A placeholder string ("CHANGE_ME_HOST") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — packages/extension/app/v2/init.ts:3, packages/extension/lib/index.ts:24
A placeholder string ("CHANGE_ME_PATH") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — packages/extension/app/v2/init.ts:4, packages/extension/lib/index.ts:25
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
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.
`renderTapFailure` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — cli/lib/tap/output.ts:64
`onSpecsChange` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — npm/webpack-dev-server/src/CypressCTWebpackPlugin.ts:101
`crossOriginOnMessageRef` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/app/src/runner/event-manager.ts:32
`windowsTouch` 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) — REDACTED:23, REDACTED:24
`MaybeEndWithEmptyBody` 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/proxy/lib/http/response-middleware.ts:561
`runChildProcess` 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/server/index.js:1
`onReconnect` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — packages/server/lib/browsers/chrome.ts:409
`closeExtraTargets` 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/server/lib/browsers/firefox.ts:772, packages/server/lib/browsers/webkit.ts:184
`exitAfterAll` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — scripts/gulp/tasks/gulpRegistry.ts:76
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×29) — cli/types/tests/cypress-tests.ts:1049, cli/types/tests/cypress-tests.ts:1051, cli/types/tests/cypress-tests.ts:1055, …
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
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.
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.
899 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 107 of 188 project(s) that lack one — worth up to 1.1 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
npm/react/README.md names React 16, but the manifest declares `react` 18.3.1. 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. — npm/react/README.md:9
npm/react/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — npm/react/README.md:9
npm/svelte/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — npm/svelte/README.md:9
npm/svelte/README.md names Svelte 4, but the manifest declares `svelte` ^5.4.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — npm/svelte/README.md:9
packages/electron/README.md links to `./BUILD.md`, but `packages/electron/BUILD.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/electron/README.md:232
packages/eslint-config/README.md names ESLint 9, but the manifest declares `eslint` ^8.56.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/eslint-config/README.md:125
packages/launchpad/README.md links to `../graphql/gql.png`, but `packages/graphql/gql.png` 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/launchpad/README.md:71
packages/proxy/README.md links to `./lib/http/responseest-middleware.ts`, but `packages/proxy/lib/http/responseest-middleware.ts` 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/proxy/README.md:10
packages/scaffold-config/README.md links to `./src/constants.ts`, but `packages/scaffold-config/src/constants.ts` 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/scaffold-config/README.md:27
packages/server/lib/adapters/README.md links to `../../network-interception/README.md`, but `packages/server/network-interception/README.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/server/lib/adapters/README.md:5
What to do
Reconcile the README with reality: npm/react/README.md names React 16, but the manifest declares `react` 18.3.1; npm/react/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0; npm/svelte/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0; npm/svelte/README.md names Svelte 4, but the manifest declares `svelte` ^5.4.0; packages/electron/README.md links to `./BUILD.md`, but `packages/electron/BUILD.md` does not exist.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P2 · Observability8.6 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 30/35 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `system-tests/projects/next-15-tsconfig-tailwind`, `system-tests/projects/next-16-tsconfig-tailwind`, `system-tests/projects/nextjs-configured`, `system-tests/projects/nextjs-unconfigured`, `system-tests/projects/v8-snapshot/example-express`.
`npm/grep/src/plugin.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:38
`npm/grep/src/plugin.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:44
`npm/grep/src/plugin.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. — npm/grep/src/plugin.ts:53
`npm/grep/src/plugin.ts` reports through `console.*` at line 59 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:59
`npm/grep/src/plugin.ts` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:65
`npm/grep/src/plugin.ts` reports through `console.*` at line 86 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:86
`npm/grep/src/plugin.ts` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:108
`npm/grep/src/plugin.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:109
`npm/grep/src/plugin.ts` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:136
`npm/grep/src/plugin.ts` reports through `console.*` at line 137 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:137
`npm/grep/src/plugin.ts` reports through `console.*` at line 154 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:154
`npm/grep/src/plugin.ts` reports through `console.*` at line 155 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:155
`npm/grep/src/plugin.ts` reports through `console.*` at line 156 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:156
`npm/grep/src/plugin.ts` reports through `console.*` at line 157 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/grep/src/plugin.ts:157
`npm/vite-plugin-cypress-esm/client/moduleCache.js` reports through `console.*` at line 179 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/vite-plugin-cypress-esm/client/moduleCache.js:179
`npm/vite-plugin-cypress-esm/client/moduleCache.js` reports through `console.*` at line 200 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — npm/vite-plugin-cypress-esm/client/moduleCache.js:200
`packages/app/src/runner/event-manager.ts` reports through `console.*` at line 288 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app/src/runner/event-manager.ts:288
`packages/app/src/runner/event-manager.ts` reports through `console.*` at line 315 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app/src/runner/event-manager.ts:315
`packages/app/src/runner/event-manager.ts` reports through `console.*` at line 480 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app/src/runner/event-manager.ts:480
`packages/app/src/runner/logger.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app/src/runner/logger.ts:20
`packages/app/src/runner/logger.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/app/src/runner/logger.ts:24
`packages/data-context/src/DataContext.ts` reports through `console.*` at line 320 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/data-context/src/DataContext.ts:320
`packages/data-context/graphql/makeGraphQLServer.ts` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/data-context/graphql/makeGraphQLServer.ts:108
`packages/driver/src/cypress/runner.ts` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/driver/src/cypress/runner.ts:126
`REDACTED` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — REDACTED:64
`REDACTED` reports through `console.*` at line 75 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:75
`packages/driver/src/cy/commands/screenshot.ts` reports through `console.*` at line 397 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/driver/src/cy/commands/screenshot.ts:397
`packages/driver/src/cy/commands/screenshot.ts` reports through `console.*` at line 398 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/driver/src/cy/commands/screenshot.ts:398
`packages/driver/src/cy/commands/screenshot.ts` reports through `console.*` at line 416 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/driver/src/cy/commands/screenshot.ts:416
`packages/driver/src/cy/commands/screenshot.ts` reports through `console.*` at line 417 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/driver/src/cy/commands/screenshot.ts:417
`packages/electron/src/electron.ts` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/electron.ts:72
`packages/electron/src/install.ts` reports through `console.*` at line 168 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/install.ts:168
`packages/electron/src/install.ts` reports through `console.*` at line 243 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/install.ts:243
`packages/electron/src/open.ts` reports through `console.*` at line 86 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/open.ts:86
`packages/electron/src/open.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/open.ts:110
`packages/electron/src/open.ts` reports through `console.*` at line 131 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/electron/src/open.ts:131
`packages/packherd-require/src/transpile-ts.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/packherd-require/src/transpile-ts.ts:109
`packages/server/lib/cypress.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. — packages/server/lib/cypress.ts:225
`packages/server/lib/cypress.ts` reports through `console.*` at line 253 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/server/lib/cypress.ts:253
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 a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Do you agree with this assessment?
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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. (×7) — packages/data-context/src/sources/UtilDataSource.ts:20, packages/server/lib/cloud/network/fetch.ts:32, packages/server/lib/cloud/network/fetch.ts:41, …
`axios.create(` 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. — packages/server/lib/cloud/api/cloud_request.ts:41
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.
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.readFileSync` in `transformIndexHtml` 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. — npm/vite-plugin-cypress-esm/src/index.ts:275
`utimesSync` in `onSpecsChange` 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. — npm/webpack-dev-server/src/CypressCTWebpackPlugin.ts:113
`fs.readdirSync` in `initGitRepoForTestProject` 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. — packages/app/cypress/tasks/git.ts:9
`fs.writeFileSync` in `initGitRepoForTestProject` 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. — packages/app/cypress/tasks/git.ts:29
`fs.utimesSync` in `windowsTouch` 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) — REDACTED:27, REDACTED:28
`fs.closeSync` in `windowsTouch` 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) — REDACTED:29, REDACTED:30
`fs.openSync` in `windowsTouch` 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) — REDACTED:29, REDACTED:30
`execSync` in `nexusTypegen` 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. (×4) — REDACTED:48, REDACTED:49, REDACTED:49, …
`fs.existsSync` in `runSpec` 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. — packages/data-context/src/actions/ProjectActions.ts:560
`zlib.brotliCompressSync` in `app.get("/encoding/:encodingType/:assetType")` 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. (×4) — REDACTED:477, REDACTED:485, REDACTED:488, …
`zlib.gzipSync` in `app.get("/encoding/:encodingType/:assetType")` 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. (×4) — REDACTED:480, REDACTED:483, REDACTED:490, …
`fs.existsSync` in `scaffoldProjectWithDeps` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:159
`fs.mkdirSync` in `snapshotScaffoldedFiles` 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. — packages/launchpad/cypress/tasks/snapshotsScaffold.ts:24
`fs.existsSync` in `joinPosix` 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. — packages/launchpad/cypress/tasks/snapshotsScaffold.ts:135
`fs.existsSync` in `callback to ROOT_PATHS.some` 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. — packages/scaffold-config/src/ct-detect-third-party.ts:78
`existsSync` in `composeProtocolErrorReportFromOptions` 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. — packages/server/lib/cloud/artifacts/protocol_artifact.ts:63
`fs.existsSync` in `compressRecording` 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. — packages/server/lib/modes/run.ts:377
`fs.existsSync` in `exports` 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. — scripts/after-sign-hook.js:29
`fs.readFileSync` in `callback to filePaths.map` 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. — scripts/github-actions/commit-via-api.mjs:14
`fs.existsSync` in `afterSpec` 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. — system-tests/lib/protocol-stubs/protocolStubWithMissingArchive.ts:119
`fs.rmSync` in `afterSpec` 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. — system-tests/lib/protocol-stubs/protocolStubWithMissingArchive.ts:120
`fs.readFileSync` in `app.get("/gzip-bad.html")` 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. — system-tests/test/js_error_handling_spec.js:17
`fs.readFileSync` in `app.get("/gzip-bad.js")` 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. — system-tests/test/js_error_handling_spec.js:27
`fs.existsSync` in `attemptDownload` 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. — tooling/electron-mksnapshot/src/mksnapshot-download.ts:83
`writeFileSync` in `generateMetadata` 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. — tooling/v8-snapshot/src/setup/generate-metadata.ts:68
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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 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.
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.
12 duplicated blocks under packages/ have copies in at least two of the sibling directories agent-info, app, cypress-sessions, driver, frontend-shared, launchpad (+6 more sibling(s) not listed) — 6 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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-info/vitest.config.ts:3
8 duplicated blocks under the repository root have copies in at least two of the sibling directories cli, npm, packages, scripts, tooling — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:10
6 duplicated blocks under packages/app/src/ have copies in at least two of the sibling directories composables, debug, prompt, runner, runs, studio — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/app/src/debug/DebugRunNavigation.vue:229
packages/app/src/prompt/PromptGetCodeModal.vue:24 · packages/app/src/prompt/PromptMoreInfoNeededModal.vue:24 — these 2 files are line-for-line copies of one another — 62 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/app/src/prompt/PromptGetCodeModal.vue:24
REDACTED:10 · REDACTED:11 — the two spans are one implementation copied and then locally edited — 373 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. — REDACTED:10
cli/lib/exec/open.ts:32 · cli/lib/exec/run.ts:61 — the two spans are one implementation copied and then locally edited — 282 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. — cli/lib/exec/open.ts:32
packages/server/lib/cloud/api/cy-prompt/report_cy_prompt_error.ts:20 · packages/server/lib/cloud/api/studio/report_studio_error.ts:24 — the two spans are one implementation copied and then locally edited — 226 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/server/lib/cloud/api/cy-prompt/report_cy_prompt_error.ts:20
tooling/v8-snapshot/src/generator/snapshot-generator.ts:276 · tooling/v8-snapshot/src/generator/snapshot-generator.ts:389 — the two spans are one implementation copied and then locally edited — 193 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — tooling/v8-snapshot/src/generator/snapshot-generator.ts:276
packages/types/src/cy-prompt/cy-prompt-server-types.ts:42 · packages/types/src/studio/studio-server-types.ts:52 — 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. — packages/types/src/cy-prompt/cy-prompt-server-types.ts:42
packages/telemetry/src/span-exporters/ipc-span-exporter.ts:13 · packages/telemetry/src/span-exporters/websocket-span-exporter.ts:13 — 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. — packages/telemetry/src/span-exporters/ipc-span-exporter.ts:13
packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:288 · packages/server/lib/cloud/studio/StudioLifecycleManager.ts:365 — the two spans are one implementation copied and then locally edited — 206 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/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:288
packages/driver/src/cy/commands/actions/scroll.ts:96 · packages/driver/src/cy/commands/actions/scroll.ts:265 — the two spans are one implementation copied and then locally edited — 221 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/driver/src/cy/commands/actions/scroll.ts:96
packages/v8-snapshot-require/src/types.ts:6 · tooling/v8-snapshot/src/types.ts:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/v8-snapshot-require/src/types.ts:6
packages/server/lib/network-runtime.ts:104 · packages/server/lib/network-runtime.ts:180 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/server/lib/network-runtime.ts:104
scripts/binary/smoke.js:130 · scripts/binary/smoke.js:172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — scripts/binary/smoke.js:130
cli/lib/cli.ts:361 · cli/lib/cli.ts:402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — cli/lib/cli.ts:361
npm/vue/src/index.ts:260 · npm/vue/src/index.ts:332 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — npm/vue/src/index.ts:260
packages/driver/src/dom/elements/nativeProps.ts:21 · packages/driver/src/dom/elements/nativeProps.ts:42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/driver/src/dom/elements/nativeProps.ts:21
scripts/binary/zip.js:88 · scripts/binary/zip.js:166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — scripts/binary/zip.js:88
scripts/unit/binary/util/packages-spec.js:74 · scripts/unit/binary/util/packages-spec.js:111 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — scripts/unit/binary/util/packages-spec.js:74
scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:21 · scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:53 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:21
scripts/unit/semantic-commits/validate-changelog-spec.js:247 · scripts/unit/semantic-commits/validate-changelog-spec.js:285 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/unit/semantic-commits/validate-changelog-spec.js:247
scripts/unit/semantic-commits/validate-changelog-spec.js:383 · scripts/unit/semantic-commits/validate-changelog-spec.js:414 · scripts/unit/semantic-commits/validate-changelog-spec.js:441 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/unit/semantic-commits/validate-changelog-spec.js:383
packages/app/src/debug/DebugRunNavigation.vue:229 · packages/app/src/runs/RunsLayout.vue:136 — 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. — packages/app/src/debug/DebugRunNavigation.vue:229
scripts/unit/binary/util/packages-spec.js:202 · scripts/unit/binary/util/packages-spec.js:224 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/unit/binary/util/packages-spec.js:202
scripts/unit/github-actions/update-browser-version-spec.js:96 · scripts/unit/github-actions/update-browser-version-spec.js:190 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/unit/github-actions/update-browser-version-spec.js:96
packages/server/lib/browsers/chrome.ts:616 · packages/server/lib/browsers/electron.ts:546 — 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. — packages/server/lib/browsers/chrome.ts:616
packages/data-context/src/data/ProjectConfigManager.ts:624 · packages/data-context/src/data/ProjectLifecycleManager.ts:787 — 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/data-context/src/data/ProjectConfigManager.ts:624
packages/errors/src/errors.ts:268 · packages/errors/src/errors.ts:302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/errors/src/errors.ts:268
scripts/sanitize-mocha-results.js:67 · scripts/verify-mocha-results.js:65 — 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. — scripts/sanitize-mocha-results.js:67
tooling/electron-mksnapshot/src/mksnapshot-run.ts:171 · tooling/electron-mksnapshot/src/mksnapshot-run.ts:230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — tooling/electron-mksnapshot/src/mksnapshot-run.ts:171
packages/app/src/prompt/prompt-app-types.ts:8 · packages/app/src/studio/studio-app-types.ts:69 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/app/src/prompt/prompt-app-types.ts:8
packages/driver/src/dom/selection.ts:187 · packages/driver/src/dom/selection.ts:238 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/driver/src/dom/selection.ts:187
REDACTED:123 · REDACTED:269 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — REDACTED:123
scripts/binary/s3-api.ts:97 · scripts/binary/s3-api.ts:157 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/binary/s3-api.ts:97
packages/errors/src/errors.ts:1562 · packages/errors/src/errors.ts:1578 · packages/errors/src/errors.ts:1595 · packages/errors/src/errors.ts:1611 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/errors/src/errors.ts:1562
packages/reporter/src/collapsible/collapsible.tsx:42 · packages/reporter/src/studio/StudioTest.tsx:94 — the two spans are one implementation copied and then locally edited — 90 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/reporter/src/collapsible/collapsible.tsx:42
packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:747 · packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:773 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:747
scripts/binary/index.js:251 · scripts/binary/index.js:267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — scripts/binary/index.js:251
scripts/binary/smoke.js:76 · scripts/binary/smoke.js:205 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — scripts/binary/smoke.js:76
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.
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.
gulpfile.js:2 reaches into another package with a relative path (./scripts/gulp/gulpfile) — import the package by name instead. — gulpfile.js:2
npm/cypress-schematic/src/schematics/ng-generate/component/index.ts:3 imports npm/cypress-schematic/src/schematics/ng-generate/cypress-test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — npm/cypress-schematic/src/schematics/ng-generate/component/index.ts:3
npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.ts:54 imports @cypress/webpack-batteries-included-preprocessor, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.ts:54
packages/app/src/debug/DebugSpec.vue:230 imports packages/app/src/specs/SpecNameDisplay.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app/src/debug/DebugSpec.vue:230
packages/app/src/layouts/default.vue:76 imports packages/app/src/specs/banners/EnableNotificationsBanner.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app/src/layouts/default.vue:76
packages/app/src/runner/SpecRunnerOpenMode.vue:131 imports packages/app/src/specs/InlineSpecList.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app/src/runner/SpecRunnerOpenMode.vue:131
packages/app/src/runs/RunsContainer.vue:88 imports packages/app/src/specs/banners/TrackedBanner.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app/src/runs/RunsContainer.vue:88
packages/app/src/store/run-all-specs-store.ts:7 imports packages/app/src/specs/tree/useCollapsibleTree.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/app/src/store/run-all-specs-store.ts:7
packages/config/src/ast-utils/addToCypressConfig.ts:144 imports cypress, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/config/src/ast-utils/addToCypressConfig.ts:144
packages/data-context/graphql/makeGraphQLServer.ts:18 imports graphql-ws/lib/use/ws, 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/data-context/graphql/makeGraphQLServer.ts:18
packages/data-context/graphql/plugins/nexusSlowGuardPlugin.ts:2 imports nexus/dist/utils, 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/data-context/graphql/plugins/nexusSlowGuardPlugin.ts:2
packages/data-context/src/data/ProjectConfigIpc.ts:33 imports @packages/server/lib/plugins/child/require_async_child.js, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/data-context/src/data/ProjectConfigIpc.ts:33
REDACTED:5 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — REDACTED:5
packages/driver/src/cross-origin/cypress.ts:8 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:8
packages/driver/src/cross-origin/cypress.ts:9 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:9
packages/driver/src/cross-origin/cypress.ts:10 imports packages/driver/src/cypress/commands.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:10
packages/driver/src/cross-origin/cypress.ts:11 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:11
packages/driver/src/cross-origin/cypress.ts:12 imports packages/driver/src/cypress/log.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:12
packages/driver/src/cross-origin/cypress.ts:28 imports packages/driver/src/cypress/mocha.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/cypress.ts:28
packages/driver/src/cross-origin/events/errors.ts:3 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/events/errors.ts:3
packages/driver/src/cross-origin/events/misc.ts:2 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/events/misc.ts:2
packages/driver/src/cross-origin/origin_fn.ts:2 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/origin_fn.ts:2
packages/driver/src/cross-origin/origin_fn.ts:3 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/origin_fn.ts:3
packages/driver/src/cross-origin/origin_fn.ts:4 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/origin_fn.ts:4
packages/driver/src/cross-origin/origin_fn.ts:7 imports packages/driver/src/cypress/log.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/origin_fn.ts:7
packages/driver/src/cross-origin/unsupported_apis.ts:2 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cross-origin/unsupported_apis.ts:2
packages/driver/src/cy/actionability.ts:7 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/actionability.ts:7
packages/driver/src/cy/actionability.ts:10 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/actionability.ts:10
packages/driver/src/cy/aliases.ts:4 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/aliases.ts:4
packages/driver/src/cy/assertions.ts:5 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/assertions.ts:5
packages/driver/src/cy/chai.ts:10 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/chai.ts:10
packages/driver/src/cy/chai.ts:12 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/chai.ts:12
packages/driver/src/cy/chai.ts:13 imports packages/driver/src/cypress/stack_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/chai.ts:13
packages/driver/src/cy/chai.ts:14 imports packages/driver/src/cypress/chai_jquery.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/chai.ts:14
REDACTED:10 imports chai/lib/chai/utils/getEnumerableProperties, 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. — REDACTED:10
packages/driver/src/cy/commands/actions/check.ts:5 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/commands/actions/check.ts:5
packages/driver/src/cy/commands/actions/check.ts:6 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/commands/actions/check.ts:6
packages/driver/src/cy/commands/actions/click.ts:5 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/commands/actions/click.ts:5
packages/driver/src/cy/commands/actions/click.ts:6 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/commands/actions/click.ts:6
packages/driver/src/cy/commands/actions/focus.ts:4 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/driver/src/cy/commands/actions/focus.ts:4
What to do
Fix the listed violations: move the shared test helper into a source directory production code may depend on (139 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (28 rows); declare the workspace packages these files import in the importing package's own REDACTED dependencies (17 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
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.
action has cyclomatic complexity 85 and cognitive complexity 35; 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/driver/src/cypress.ts:484
formatValue has cyclomatic complexity 42 and cognitive complexity 51; 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:73
validateTyping has cyclomatic complexity 38 and cognitive complexity 45; 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/driver/src/cy/keyboard.ts:387
(anonymous) has cyclomatic complexity 37 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:462
request has cyclomatic complexity 37 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/driver/src/cy/commands/request.ts:82
(anonymous) has cyclomatic complexity 34 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. — packages/driver/src/cypress/log.ts:66
(anonymous) has cyclomatic complexity 32 and cognitive complexity 31; 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. — cli/lib/exec/run.ts:38
(anonymous) has cyclomatic complexity 32 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — system-tests/projects/e2e/static/obstructive_code.js:3
getReasonIsHidden has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/driver/src/dom/visibility.ts:527
waitForTestsToFinishRunning has cyclomatic complexity 30 and cognitive complexity 33; 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/server/lib/modes/run.ts:631
_onAttachToTarget has cyclomatic complexity 29 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 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/server/lib/browsers/browser-cri-client.ts:461
(anonymous) has cyclomatic complexity 29 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/server/lib/browsers/cdp-protocol/cdp_automation.ts:506
(anonymous) has cyclomatic complexity 28 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:738
plugin has cyclomatic complexity 28 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 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. — npm/grep/src/plugin.ts:19
(anonymous) has cyclomatic complexity 28 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. — packages/reporter/src/commands/command.tsx:401
(anonymous) has cyclomatic complexity 27 and cognitive complexity 63; 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/config/src/validation.ts:375
maybeHandleRetryOnFailure has cyclomatic complexity 27 and cognitive complexity 41; 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/driver/src/cypress/runner.ts:1450
toObject has cyclomatic complexity 27 and cognitive complexity 33; 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/server/lib/util/args.ts:342
_providerCommitParams has cyclomatic complexity 27 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/server/lib/util/ci_provider.ts:554
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.5 / 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/errors/src/errors.ts has 1431 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/errors/src/errors.ts:1
packages/server/lib/server-base.ts has 1240 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/server/lib/server-base.ts:1
packages/driver/src/cy/keyboard.ts has 1167 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/driver/src/cy/keyboard.ts:1
REDACTED has 1101 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/server/lib/modes/run.ts has 1065 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/server/lib/modes/run.ts:1
packages/packherd-require/src/loader.ts has 975 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/packherd-require/src/loader.ts:1
packages/driver/src/cy/commands/navigation.ts has 964 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/driver/src/cy/commands/navigation.ts:1
packages/server/lib/browsers/cdp-protocol/cri-client.ts has 912 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/server/lib/browsers/cdp-protocol/cri-client.ts:1
packages/server/lib/browsers/browser-cri-client.ts has 911 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/server/lib/browsers/browser-cri-client.ts:1
packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts has 891 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/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:1
tooling/v8-snapshot/src/blueprint/globals.js has 874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tooling/v8-snapshot/src/blueprint/globals.js:1
packages/app/src/runner/event-manager.ts has 873 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/app/src/runner/event-manager.ts:1
packages/driver/src/cypress.ts has 803 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/driver/src/cypress.ts:1
packages/server/lib/util/ci_provider.ts has 800 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/server/lib/util/ci_provider.ts:1
packages/config/src/options.ts has 787 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/config/src/options.ts:1
packages/server/lib/modes/record.ts has 770 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/server/lib/modes/record.ts:1
packages/server/lib/browsers/chrome.ts has 740 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/server/lib/browsers/chrome.ts:1
packages/app/src/runner/aut-iframe.ts has 728 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/app/src/runner/aut-iframe.ts:1
packages/data-context/src/data/ProjectLifecycleManager.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/data-context/src/data/ProjectLifecycleManager.ts:1
packages/server/lib/browsers/bidi_automation.ts has 707 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/server/lib/browsers/bidi_automation.ts:1
packages/server/lib/request.ts has 680 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/server/lib/request.ts:1
packages/server/lib/reporter.ts has 675 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/server/lib/reporter.ts:1
tooling/v8-snapshot/src/doctor/snapshot-doctor.ts has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — tooling/v8-snapshot/src/doctor/snapshot-doctor.ts:1
packages/server/lib/socket-base.ts has 661 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/server/lib/socket-base.ts:1
packages/server/lib/project-base.ts has 659 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/server/lib/project-base.ts:1
packages/driver/src/cy/mouse.ts has 658 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/driver/src/cy/mouse.ts:1
packages/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts has 655 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/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts:1
packages/server/lib/browsers/firefox.ts has 641 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/server/lib/browsers/firefox.ts:1
packages/server/lib/cloud/api/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/server/lib/cloud/api/index.ts:1
packages/driver/src/cy/commands/cookies.ts has 590 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/driver/src/cy/commands/cookies.ts:1
packages/driver/src/dom/selection.ts has 587 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/driver/src/dom/selection.ts:1
packages/data-context/src/data/ProjectConfigManager.ts has 580 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/data-context/src/data/ProjectConfigManager.ts:1
packages/server/lib/util/print-run.ts has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/server/lib/util/print-run.ts:1
packages/proxy/lib/http/response-middleware.ts has 570 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/proxy/lib/http/response-middleware.ts:1
packages/reporter/src/commands/command.tsx has 566 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/reporter/src/commands/command.tsx:1
packages/proxy/lib/http/index.ts has 565 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/proxy/lib/http/index.ts:1
packages/driver/src/cy/commands/actions/type.ts has 561 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/driver/src/cy/commands/actions/type.ts:1
cli/lib/cli.ts has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — cli/lib/cli.ts:1
packages/data-context/src/actions/ProjectActions.ts has 548 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/data-context/src/actions/ProjectActions.ts:1
packages/driver/src/cy/actionability.ts has 548 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/driver/src/cy/actionability.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage8.4 / 10Strong✓ 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/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts:1, npm/angular/src/mount.ts:1, packages/data-context/src/sources/RemoteRequestDataSource.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
R7 · Dead Code7.9 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
12 file(s) (~495 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an REDACTED script) so reachability can see this package.
20 file(s) (~1345 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — npm/cypress-schematic
206 file(s) (~25452 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/data-context/graphql/plugins/nexusRemoteFieldPlugin.ts imports '../../src/gen/nxs.gen', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/data-context
Unreachable from the 516 application, 508 tooling and 3317 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (516 application, 508 tooling, 3317 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 (×11) — packages/app/src/layouts/default.vue, packages/app/src/pages/Debug.vue, npm/webpack-dev-server/src/loader.ts, …
no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/app/src/pages/Runs.vue) — 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) — packages/app/src/runs/useProjectRuns.ts, packages/app/src/runs/useGitTreeRuns.ts
no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/app/src/layouts/default.vue) — 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 — packages/app/src/navigation/SidebarNavigationContainer.vue
no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (npm/webpack-dev-server/src/loader.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 — npm/webpack-dev-server/src/aut-runner.ts
no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/app/src/pages/Runs.vue, packages/app/src/runs/useGitTreeRuns.ts, packages/app/src/runs/useProjectRuns.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 — packages/app/src/runs/RunsComposable.ts
Nothing imports this binding — it is safe to review for removal. (×17) — npm/cypress-schematic/src/schematics/utils/jsonFile.ts:24, npm/webpack-dev-server/src/devServer.ts:144, packages/data-context/src/actions/ElectronActions.ts:27, …
Nothing ultimately consumes this binding: its only referrer is the re-export in npm/react/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in npm/react/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — npm/react/src/createMount.ts:150, npm/react/src/mount.ts:47
No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`. — packages/data-context/src/sources/CloudDataSource.ts:91
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in cli/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)
Every import is type-only — move it to devDependencies. — npm/webpack-dev-server/src/helpers/angularHandler.ts:221
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
packages/app/src/runner/aut-iframe.ts → packages/app/src/store/studio-store.ts → packages/app/src/runner/index.ts → packages/app/src/runner/aut-iframe.ts (one verified cycle inside a mutually-dependent group of 5 files) — packages/app/src/runner/aut-iframe.ts:8
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. 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.
`strictSSL: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose. (×4) — packages/proxy/lib/http/send-request-outgoing.ts:28, packages/server/lib/request.ts:23, packages/server/lib/request.ts:664, …
The value is the MAC key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. (×2) — packages/server/lib/project-base.ts:121, scripts/binary/binary-integrity-check-source.js:130
`minVersion: "TLSv1"` explicitly admits a protocol version that is broken (SSL 3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Remove the pin: Node's default minimum is TLS 1.2, so leaving `minVersion`/`secureProtocol` unset is the strongest setting and picks up TLS 1.3 without a code change. Where a floor must be named, use `minVersion: "TLSv1.2"`. — packages/server/lib/request.ts:398
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×12) — npm/webpack-dev-server/src/helpers/angularHandler.ts:165, packages/data-context/src/sources/CloudDataSource.ts:181, packages/data-context/src/sources/RemoteRequestDataSource.ts:370, …
`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.) — packages/data-context/graphql/makeGraphQLServer.ts:120
What to do
Stop accepting every TLS certificate: delete `rejectUnauthorized: false` / `NODE_TLS_REJECT_UNAUTHORIZED=0` so the chain, hostname and expiry are verified, and trust a self-signed or private server by passing its CA (`ca`, or `NODE_EXTRA_CA_CERTS`) — never by switching verification off. This repository constructs a TLS client that accepts any certificate at 4 sites, not one: `packages/proxy/lib/http/send-request-outgoing.ts:28` (`strictSSL: false`), `packages/server/lib/request.ts:23` (`NODE_TLS_REJECT_UNAUTHORIZED = "0"`), `packages/server/lib/request.ts:664` (`strictSSL: false`), `packages/server/lib/request.ts:733` (`strictSSL: false`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations. This repository constructs key or salt material fixed at compile time at 2 sites, not one: `packages/server/lib/project-base.ts:121` (MAC key), `scripts/binary/binary-integrity-check-source.js:130` (MAC key). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Drop SSL 3.0 and TLS 1.0/1.1: remove the `secureProtocol`/`minVersion` pin so Node's default (TLS 1.2 minimum, TLS 1.3 preferred) applies, or set `minVersion: "TLSv1.2"` explicitly.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 12 sites, not one: `npm/webpack-dev-server/src/helpers/angularHandler.ts:165` (createHash("sha1")), `packages/data-context/src/sources/CloudDataSource.ts:181` (createHash("sha1")), `packages/data-context/src/sources/RemoteRequestDataSource.ts:370` (createHash("sha1")), `packages/driver/src/cy/snapshots_css.ts:127` (md5), `packages/electron/src/install.ts:56` (createHash("sha1")), `packages/frontend-shared/src/graphql/urqlDetailedDebugExchange.ts:58` (md5), `packages/proxy/lib/resourceTypeAndCredentialManager.ts:7` (createHash("md5")), `packages/server/lib/plugins/child/cross_origin.ts:16` (md5), and 4 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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`.
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.
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×2) — packages/server/lib/cypress.ts:113, cli/lib/exec/spawn.ts:66
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.
Do you agree with this assessment?
X13 · Undrained process stream6.1 / 10Adequate✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
`spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `sp.stdout`, while `sp.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`sp.stdout.on('data', …)`, or `sp.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — cli/lib/tasks/unzip.ts:147
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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.
Do you agree with this assessment?
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.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.7 / 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.
`detectVisibility` is exported, takes a document from its caller (line 7) and hands it to `extractTransformInfoFromElements`, which calls itself at line 51 (`extractTransformInfoFromElements`) with a piece of `$el` — and nowhere in `extractTransformInfoFromElements` 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 `extractTransformInfoFromElements` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/driver/src/dom/transform.ts:51
`setPluginResolvedOn` is exported and takes `resolvedObj: Record<string, any>` from its caller, and it calls itself at line 254 (`setPluginResolvedOn`) with a piece of `resolvedObj` — and nowhere in `setPluginResolvedOn` 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 `setPluginResolvedOn` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/config/src/project/utils.ts:254
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.
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.
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.
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 5/11 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.
`getLatestVersionData` 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 })`. — scripts/github-actions/update-browser-versions.js:33
`getLastKnownGoodChromeForTestingStable` 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 })`. — scripts/github-actions/update-browser-versions.js:45
`syncCloudValidations` 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/server/scripts/sync-cloud-validations.ts:29
`fetchCurrentEtag` 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/server/scripts/sync-cloud-validations.ts:60
`dispatchErrors` 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/server/lib/cloud/protocol.ts:458
`getCallbackFn` 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/driver/src/cross-origin/origin_fn.ts:74
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
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.
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.3 / 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.
`scriptError` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. — packages/app/src/runner/ScriptError.vue:5
`css.toString()` 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. — packages/app/src/runner/dom.ts:65
`markdown` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. (×4) — packages/app/src/runs/RunsContainer.vue:42, packages/app/src/settings/project/ExperimentRow.vue:27, packages/frontend-shared/src/gql-components/error/BaseError.vue:62, …
`componentPath` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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. — packages/data-context/src/codegen/templates/react-component/react-component.ejs:6
`componentName` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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. (×4) — packages/data-context/src/codegen/templates/react-component/react-component.ejs:8, packages/data-context/src/codegen/templates/react-component/react-component.ejs:11, packages/data-context/src/codegen/templates/vue-component/vue-component.ejs:5, …
`el.value` 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. — packages/driver/src/util/serialization/log.ts:59
`props.innerHTML` 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. — packages/driver/src/util/serialization/log.ts:96
`highlightedCode` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. — packages/frontend-shared/src/components/ShikiHighlight.vue:56
`baseError.errorStack` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. — packages/frontend-shared/src/gql-components/error/BaseError.vue:99
`dep.description` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. — packages/launchpad/src/setup/ManualInstall.vue:56
`itemValue.icon` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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) — packages/launchpad/src/setup/SelectFrameworkOrBundler.vue:35, packages/launchpad/src/setup/SelectFrameworkOrBundler.vue:75
`md.render(error.message)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/reporter/src/runnables/runnable-error.tsx:32
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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×27) — packages/socket/lib/client/cdp-browser.ts:77, packages/server/lib/cypress-sessions.ts:40, packages/server/lib/errors.ts:16, …
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. (×7) — packages/server/lib/network-runtime.ts:413, packages/server/lib/util/commit-info.ts:48, packages/server/lib/cloud/exception.ts:79, …
`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/server/lib/open_project.ts:282
`catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — packages/server/lib/util/electron-app.ts:8, packages/server/lib/util/electron-app.ts:19, packages/server/lib/util/electron-app.ts:39, …
`.catch(function(){})` 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. — packages/proxy/lib/http/util/disable-navigation-preload.ts:101
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
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.
90/167 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 — 198 assertion(s) across the 154532 source line(s) of the 1116 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: packages/server/lib/request.ts (29), packages/server/lib/reporter.ts (20), packages/driver/src/cypress.ts (6). 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 `?`).
Do you agree with this assessment?
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).
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.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: this repository stores data through 'better-sqlite3' (packages/types/src/protocol.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'better-sqlite3' (packages/types/src/protocol.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'better-sqlite3' (packages/types/src/protocol.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 39 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: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — dev Pulling watch Pulling ci Pulling ci Error Get "https://registry-1.docker.io/v2/": Forbidden dev Error context canceled watch Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: watch Skipped - Image is already being pulled by dev dev Pulling ci Pulling ci Error Get "https://registry-1.docker.io/v2/": Forbidden dev Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'better-sqlite3' (packages/types/src/protocol.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D12 Dependency Hygiene — Dependency Hygiene not included (time budget)
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
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.
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not 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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 440 finding(s)
D10 · Test Quality· No assertions (empty test) · ×220
No assertions (empty test): ...bar system-tests/projects/webpack-dev-server/src/[...bar].cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): サイプレス system-tests/projects/webpack-dev-server/src/サイプレス.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): ok system-tests/projects/unify-plugin-errors/cypress/e2e/spec.js:2— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): foo system-tests/projects/uncaught-support-file/cypress/e2e/spec.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is nested system-tests/projects/todos/tests/sub/sub_test.js:2— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): logs nothing of its own system-tests/projects/tap-retries/cypress/e2e/hooks.cy.js:14— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): t1 system-tests/projects/session-and-origin-e2e-specs/cypress/e2e/session/blank_session.cy.js:4— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): fails in both hooks system-tests/projects/retries-2/cypress/e2e/fail-in-both-hooks.cy.js:17— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): will be skipped #1 system-tests/projects/results/cypress/e2e/spec-2.cy.js:26— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): will be skipped #2 system-tests/projects/results/cypress/e2e/spec-2.cy.js:27— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): passes system-tests/projects/plugins-root-syntax-error/cypress/integration/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): passes system-tests/projects/plugins-root-sync-error/cypress/integration/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): passes system-tests/projects/plugins-function-sync-error/cypress/integration/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-run-events/cypress/e2e/run_events_spec_1.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-run-events/cypress/e2e/run_events_spec_2.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-returns-invalid-browser/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-returns-empty-browsers-list/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-returns-bad-config/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-no-function-return/cypress/integration/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-filter-browsers/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-empty/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): is true system-tests/projects/plugin-browser/cypress/e2e/app.cy.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test system-tests/projects/hooks-after-rerun/cypress/e2e/beforehook-and-test-navigation.cy.js:18— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): test system-tests/projects/hooks-after-rerun/cypress/e2e/beforehook-and-test-navigation.cy.js:34— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): a test system-tests/projects/e2e/cypress/e2e/a_record.cy.js:2— Test method has an empty body — it asserts nothing and exercises no code.
Boundary-crossing change coupling: options.ts ↔ results_spec.ts.js packages/config/src/options.ts:1— `packages/config/src/options.ts` (context config) and `system-tests/__snapshots__/results_spec.ts.js` (context system-tests) sit in DIFFERENT parts of the tree yet change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `2a65ae9f` feat: add trustedCertificates option for the native browser network p…; `d8d61346` breaking: introduce manageBrowserMemory and remove experimentalMemory…; `02aa75de` feat: add removeSRIAttributes config option to strip SRI from first-p… — run `git show` on any of them.
Boundary-crossing change coupling: REDACTED ↔ response-middleware.ts REDACTED:1— `REDACTED` (context network-tools) and `packages/proxy/lib/http/response-middleware.ts` (context proxy) sit in DIFFERENT parts of the tree yet change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `1cefc38b` refactor: rm circular dep by moving remote-states from server to netw…; `23299acc` fix: Disallow `same-superdomain-origin` cy.origin blocks (#24569) (at that commit the file was still `packages/server/lib/remote_states.ts`); `18321f80` chore: refactor originPolicy to use superDomainOrigin nomenclat… (#23… (at that commit the file was still `packages/server/lib/remote_states.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: gql-LocalSettings.ts ↔ preferences.ts packages/data-context/graphql/schemaTypes/objectTypes/gql-LocalSettings.ts:1— `packages/data-context/graphql/schemaTypes/objectTypes/gql-LocalSettings.ts` (context data-context) and `packages/types/src/preferences.ts` (context types) sit in DIFFERENT parts of the tree yet 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7898d0b7` feat: Add option to 'word wrap' for Studio panel code (#33411); `0c718e0e` feat: add toggle to hide fetch requests (#32658); `01775081` chore: set up sharing of react via module federation in studio (#31129) (at that commit the file was still `packages/graphql/src/schemaTypes/objectTypes/gql-LocalSettings.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: SpecRunnerOpenMode.vue ↔ gql-LocalSettings.ts packages/app/src/runner/SpecRunnerOpenMode.vue:1— `packages/app/src/runner/SpecRunnerOpenMode.vue` (context runner) and `packages/data-context/graphql/schemaTypes/objectTypes/gql-LocalSettings.ts` (context data-context) sit in DIFFERENT parts of the tree yet 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, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7898d0b7` feat: Add option to 'word wrap' for Studio panel code (#33411); `0c718e0e` feat: add toggle to hide fetch requests (#32658); `01775081` chore: set up sharing of react via module federation in studio (#31129) (at that commit the file was still `packages/graphql/src/schemaTypes/objectTypes/gql-LocalSettings.ts`) — run `git show` on any of them.
Boundary-crossing change coupling: event-manager.ts ↔ events.ts packages/app/src/runner/event-manager.ts:1— `packages/app/src/runner/event-manager.ts` (context runner) and `packages/reporter/src/lib/events.ts` (context reporter) sit in DIFFERENT parts of the tree yet change together 55% of the time (11 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `e05f8a80` chore: Add links to open login, setup project modals when throwing er…; `7898d0b7` feat: Add option to 'word wrap' for Studio panel code (#33411); `6cd9e54c` internal: (studio) set entry source when user initializes studio (#32… — run `git show` on any of them.
Boundary-crossing change coupling: BrowserDataSource.ts ↔ OpenBrowserList.vue packages/data-context/src/sources/BrowserDataSource.ts:1— `packages/data-context/src/sources/BrowserDataSource.ts` (context data-context) and `packages/launchpad/src/setup/OpenBrowserList.vue` (context launchpad) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `26ae3bde` deprecation: deprecate the Electron browser in the App and run mode (…; `4fd15101` fix: cache last-used browser by project, name, and channel (#20760); `1223ded3` refactor: convert browser status to gql subscription (#20591) — run `git show` on any of them.
Boundary-crossing change coupling: AuthActions.ts ↔ auth.ts packages/data-context/src/actions/AuthActions.ts:1— `packages/data-context/src/actions/AuthActions.ts` (context data-context) and `packages/server/lib/cloud/auth.ts` (context cloud) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6550e9ca` feat: Insert project ID into config after login when cloud provides o…; `023f0324` chore: Pass remoteOrigin to the cloud on login/signup (#33922); `b911a8d3` feat: add signup flow for desktop cloud auth (#33805) — run `git show` on any of them.
Boundary-crossing change coupling: studio-app-types.ts ↔ studio-server-types.ts packages/app/src/studio/studio-app-types.ts:1— `packages/app/src/studio/studio-app-types.ts` (context studio) and `packages/types/src/studio/studio-server-types.ts` (context types) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f7bc706a` internal: (studio) send debugData to studio server (#33338); `a750f911` feat: (cy.prompt/studio) add ability to track on dirty data in studio…; `5260488a` internal: updating studio-server initialization with renderer APIs (#… — run `git show` on any of them.
Boundary-crossing change coupling: studio-app-types.ts ↔ studio.ts packages/app/src/studio/studio-app-types.ts:1— `packages/app/src/studio/studio-app-types.ts` (context studio) and `packages/server/lib/cloud/studio/studio.ts` (context cloud) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f7bc706a` internal: (studio) send debugData to studio server (#33338); `5260488a` internal: updating studio-server initialization with renderer APIs (#…; `ef1a73b1` internal: create cloud studio session ID to group telemetry and error… — run `git show` on any of them.
Boundary-crossing change coupling: SpecRunnerOpenMode.vue ↔ studio-app-types.ts packages/app/src/runner/SpecRunnerOpenMode.vue:1— `packages/app/src/runner/SpecRunnerOpenMode.vue` (context runner) and `packages/app/src/studio/studio-app-types.ts` (context studio) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `18707a00` misc: (studio) warn user of unsaved changes when they navigate away f…; `9d4e9cff` feat: add back selector playground (#33073); `a750f911` feat: (cy.prompt/studio) add ability to track on dirty data in studio… — run `git show` on any of them.
Assertions commented out: events when element moved on mousedown packages/driver/cypress/e2e/commands/actions/click.cy.ts:376— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: events when element moved on mouseup packages/driver/cypress/e2e/commands/actions/click.cy.ts:402— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: events when element moved on click packages/driver/cypress/e2e/commands/actions/click.cy.ts:425— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: click when mouseup el is child of mousedown el packages/driver/cypress/e2e/commands/actions/click.cy.ts:448— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: no click when mouseUpPhase targetEl is detached packages/driver/cypress/e2e/commands/actions/click.cy.ts:498— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: no click when new element at coords is not ancestor packages/driver/cypress/e2e/commands/actions/click.cy.ts:556— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: can target new element after mouseup sequence packages/driver/cypress/e2e/commands/actions/click.cy.ts:3879— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Assertions commented out: responds to changes in move handlers packages/driver/cypress/e2e/commands/actions/click.cy.ts:3919— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×5
Click handler on a non-interactive <div> packages/frontend-shared/src/components/Card.vue:2— 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/frontend-shared/src/gql-components/error/ErrorCodeFrame.vue:8— 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/reporter/src/commands/command.tsx:130— 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/reporter/src/commands/command.tsx:136— 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/reporter/src/commands/command.tsx:560— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <label> that labels no control · ×4
<label> that labels no control packages/app/src/runner/SnapshotHighlightControls.vue:9— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/app/src/settings/device/NotificationSettings.vue:40— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/app/src/settings/device/TestingPreferences.vue:14— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control packages/launchpad/src/setup/ButtonBar.vue:32— This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC2 · Forms & labels· <select> without a programmatic label · ×4
<select> without a programmatic label packages/frontend-shared/src/gql-components/ChooseExternalEditor.vue:4— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<select> without a programmatic label packages/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue:42— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<select> without a programmatic label packages/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue:75— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<select> without a programmatic label packages/launchpad/src/setup/SelectFrameworkOrBundler.vue:2— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<html> without a lang packages/extension/app/newtab.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 packages/extension/app/popup.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 packages/server/lib/html/non_proxied_error.html:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang packages/server/lib/util/network_failures.ts:20— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
TLS certificate validation disabled packages/proxy/lib/http/send-request-outgoing.ts:28— `strictSSL: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose.
TLS certificate validation disabled packages/server/lib/request.ts:23— `strictSSL: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose.
TLS certificate validation disabled packages/server/lib/request.ts:664— `strictSSL: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose.
TLS certificate validation disabled packages/server/lib/request.ts:733— `strictSSL: false` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the option so Node validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: pass its CA as `ca` (or set `NODE_EXTRA_CA_CERTS`), which keeps the chain and hostname checks on. A managed database or broker that documents `rejectUnauthorized: false` publishes a CA bundle for exactly this purpose.
AC1 · Text alternatives· <img> without a text alternative · ×3
<img> without a text alternative packages/app/src/runner/automation/AutInfo.vue:6— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/extension/app/newtab.html:10— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative packages/extension/app/popup.html:8— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D30 · Dependency Vulnerabilities· High vulnerability · ×3
REDACTED
REDACTED
REDACTED
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text packages/app/src/debug/DebugSpec.vue:159— 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 packages/reporter/src/lib/switch.tsx:17— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×2
Custom control with no accessible name on <div> packages/reporter/src/commands/command.tsx:136— 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> packages/reporter/src/commands/command.tsx:560— 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· Document without a <title> · ×2
Document without a <title> packages/reporter/static/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>.
Document without a <title> packages/server/lib/util/network_failures.ts:20— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Focusable <div> isn't keyboard-operable packages/app/src/navigation/SidebarNavigationHeader.vue:8— 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.
Focusable <div> isn't keyboard-operable packages/frontend-shared/src/components/ShikiHighlight.vue:21— 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. Give it a role as well, so assistive tech can announce what it is.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×2
Click handler on a non-interactive <span> packages/reporter/src/commands/command.tsx:432— 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> packages/reporter/src/lib/open-file-in-ide.tsx:16— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
S1 · Web-Security Posture· Cryptographic key material is a compile-time constant · ×2
Cryptographic key material is a compile-time constant packages/server/lib/project-base.ts:121— The value is the MAC key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Cryptographic key material is a compile-time constant scripts/binary/binary-integrity-check-source.js:130— The value is the MAC key and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label packages/frontend-shared/src/components/Input.vue:29— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Custom control with no accessible name on <span> · ×1
Custom control with no accessible name on <span> packages/reporter/src/commands/command.tsx:432— This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name packages/reporter/src/runnables/runnable-error.tsx:26— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title packages/driver/src/cy/snapshots.ts:85— 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.
AC4 · Keyboard semantics· Clickable role="button" that no keyboard user can reach · ×1
Clickable role="button" that no keyboard user can reach packages/frontend-shared/src/components/Collapsible.vue:7— This <div> announces itself as a role="button" and binds a click, but nothing can put focus on it: no tabindex="0" in any spelling, no key handler, and nothing in this file moves focus or sets aria-activedescendant. The role tells assistive tech what the control IS; it does not make the control reachable, so a keyboard user cannot operate it at all (WCAG 2.1.1). Give it tabindex="0"="0" and an Enter/Space key handler, or make it a native <button>. If a parent widget owns the keyboard model, that parent must move focus onto the active role="button" or point aria-activedescendant at it.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×1
Hover-only interaction on <div> packages/reporter/src/commands/command.tsx:549— 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.
No assertions: works with an installed browser path system-tests/test/browser_path_spec.js:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: passes system-tests/test/busted_support_file_spec.js:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: passes system-tests/test/cache_spec.js:49— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fails and displays the message that points users to the cloud system-tests/test/ci_failure_spec.ts:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: executes all of the tests for React v${majorVersion} with Vite system-tests/test/component_testing_spec.ts:49— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: executes all of the tests for React v${majorVersion} with Webpack system-tests/test/component_testing_spec.ts:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: provides various environment details system-tests/test/config_spec.js:9— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: applies defaultCommandTimeout globally system-tests/test/config_spec.js:21— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws error when invalid viewportWidth in the configuration file system-tests/test/config_spec.js:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws error when invalid browser in the configuration file system-tests/test/config_spec.js:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports global shadow dom inclusion system-tests/test/config_spec.js:50— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports custom configFile in JavaScript system-tests/test/config_spec.js:56— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports custom configFile in TypeScript system-tests/test/config_spec.js:63— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports custom configFile in a default JavaScript file system-tests/test/config_spec.js:70— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: supports custom configFile in a default TypeScript file system-tests/test/config_spec.js:76— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws error when multiple default config file are found in project system-tests/test/config_spec.js:82— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if supportFile is set on the root level system-tests/test/config_spec.js:96— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if cypress.env.json specifies invalid property system-tests/test/config_spec.js:107— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if specPattern is set on the root level system-tests/test/config_spec.js:117— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if excludeSpecPattern is set on the root level system-tests/test/config_spec.js:128— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if baseUrl is set on the root level system-tests/test/config_spec.js:139— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if baseUrl is set on the component level system-tests/test/config_spec.js:150— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if indexHtml is set on the root level system-tests/test/config_spec.js:162— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throws an error if indexHtml is set on the e2e level system-tests/test/config_spec.js:173— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: setupNodeEvents modify specPattern for current testing type system-tests/test/config_spec.js:185— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment tooling/v8-snapshot/test/unit/doctor.spec.ts:387— // TODO: We still have a hole where a file moves from healthy to deferred or norewrite. This doesn't happen very frequently and can be solved later: — 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 tooling/v8-snapshot/src/sourcemap/process-sourcemap.ts:18— // TODO(thlorenz): Why is forward slash missing 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.
TodoComment tooling/v8-snapshot/src/setup/force-no-rewrite.ts:34— // TODO: Figure out why these don't properly get flagged as norewrite: https://github.com/cypress-io/cypress/issues/23986
TodoComment tooling/electron-mksnapshot/src/mksnapshot-run.ts:66— // TODO(thlorenz): this manual args parsing was copied from the original module and could be — 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 tooling/electron-mksnapshot/src/process-args-from-file.ts:80— // TODO(thlorenz): shouldn't exit here technically, but I've had it cleaning up the 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.
TodoComment system-tests/test/before_browser_launch_spec.ts:29— // TODO(webkit): fix+unskip, or skip and add a test that this fails with WebKit — 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 system-tests/test/cdp_spec.ts:23— // TODO: Investigate and unskip flaky 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 system-tests/test/component_testing_spec.ts:188— // TODO(webkit): WebKit video recording is flaky, retry to reduce flake (see video_compression_spec) — 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 system-tests/test/cookies_spec.ts:200— // TODO(webkit): fix+unskip — 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 system-tests/test/cookies_spec.ts:254— // TODO(webkit): fix+unskip — 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 system-tests/test/cookies_spec.ts:278— // TODO(webkit): fix+unskip — 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 system-tests/test/cookies_spec.ts:558— // TODO(webkit): fix+unskip — 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 system-tests/test/error_ui_spec.ts:26— // TODO(webkit): fix+unskip — 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 system-tests/test/error_ui_spec.ts:38— // TODO(webkit): fix+unskip — 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 system-tests/test/experimental_csp_allow_list_spec.ts:47— // TODO(webkit): fix+unskip — 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 system-tests/test/experimental_csp_allow_list_spec.ts:60— // TODO(webkit): fix+unskip — 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 system-tests/test/request_spec.ts:171— // TODO(webkit): fix+unskip — 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 system-tests/test/subdomain_injectDocumentDomain_spec.ts:122— // TODO(webkit): fix+unskip — 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 system-tests/test/subdomain_spec.ts:122— // TODO(webkit): fix+unskip — 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/driver/cypress/e2e/cy/timers.cy.ts:428— // TODO(webkit): fix+unskip — 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/driver/cypress/e2e/commands/actions/check.cy.ts:241— // TODO(webkit): fix+unskip — 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 system-tests/test/cookies_spec.ts:352— // TODO(webkit): fix+unskip (needs multidomain support) — 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 system-tests/test/cookies_spec.ts:408— // TODO(webkit): fix+unskip (needs multidomain support) — 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 system-tests/test/cookies_spec.ts:502— // TODO(webkit): fix+unskip (needs multidomain support) — 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 system-tests/test/cy_origin_error_spec.ts:33— // TODO(webkit): fix+unskip (needs multidomain support) — 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.
Skipped test: snapshots an entry, typescripts an intermediate file, and snapshots again tooling/v8-snapshot/test/unit/doctor.spec.ts:389— Skipped — switched off by it.skip
Skipped test: passes in parallel with group system-tests/test/record_spec.ts:370— Skipped — switched off by it.skip
Skipped test: passes system-tests/test/window_open_spec.js:7— Skipped — switched off by it.skip
Skipped test: never runs system-tests/projects/tap-retries/cypress/e2e/hooks.cy.js:25— Skipped — switched off by it.skip
Skipped test: skipped test system-tests/projects/studio/cypress/e2e/skipped.cy.js:2— Skipped — switched off by it.skip
Skipped test: is pending due to .skip system-tests/projects/e2e/cypress/e2e/config_record.cy.js:16— Skipped — switched off by it.skip
Skipped test: is pending system-tests/projects/e2e/cypress/e2e/simple_pending.cy.js:3— Skipped — switched off by it.skip
Skipped test: Login demo system-tests/projects/e2e/cypress/e2e/source_rewriting.cy.js:112— Skipped — switched off by it.skip
Skipped test: fails with promise system-tests/projects/e2e/cypress/e2e/uncaught_during_test.cy.js:72— Skipped — switched off by it.skip
Skipped test: aborts system-tests/projects/e2e/cypress/e2e/xhr.cy.js:173— Skipped — switched off by it.skip
Skipped test: t2 system-tests/projects/cloud-debug-filter/cypress/e2e/skip-and-only.cy.js:7— Skipped — switched off by it.skip
Skipped test: errors on required props missing system-tests/projects/angular-signals/src/signals-required/signals-required.component.cy.ts:9— Skipped — switched off by it.skip
Skipped test: test 1 system-tests/project-fixtures/runner-specs/cypress/e2e/hooks/skip.cy.js:3— Skipped — switched off by it.skip
Skipped test: attaches warning to non-chrome browsers when chromeWebSecurity:false packages/server/test/unit/project-base.spec.ts:315— Skipped — switched off by it.skip
Skipped test: only attaches warning to non-chrome browsers when chromeWebSecurity:true packages/server/test/unit/project-base.spec.ts:350— Skipped — switched off by it.skip
Skipped test: does not call startSpecWatcher if not in interactive mode packages/server/test/unit/project-base.spec.ts:576— Skipped — switched off by it.skip
Skipped test: calls startSpecWatcher if in interactive mode packages/server/test/unit/project-base.spec.ts:592— Skipped — switched off by it.skip
Skipped test: logs error and exits when project folder has read permissions only and cannot write cypress.config.js packages/server/test/integration/cypress_spec.js:926— Skipped — switched off by it.skip
Skipped test: passes filtered options to Project#open and sets cli config packages/server/test/integration/cypress_spec.js:1919— Skipped — switched off by it.skip
Skipped test: renders and escapes markdown with leading/trailing whitespace packages/reporter/cypress/e2e/test_errors.cy.ts:250— Skipped — switched off by it.skip
Skipped test: is active when all children are active packages/reporter/cypress/e2e/unit/suite_model.cy.ts:45— Skipped — switched off by it.skip
Skipped test: is active when there are active tests with passing tests packages/reporter/cypress/e2e/unit/suite_model.cy.ts:52— Skipped — switched off by it.skip
Skipped test: is active when there are active tests with pending tests packages/reporter/cypress/e2e/unit/suite_model.cy.ts:59— Skipped — switched off by it.skip
Skipped test: is active even when children suites are not packages/reporter/cypress/e2e/unit/suite_model.cy.ts:104— Skipped — switched off by it.skip
Skipped test: works with Yarn 3 Plug n Play packages/launchpad/cypress/e2e/project-setup.cy.ts:601— Skipped — switched off by it.skip
+ 51 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×44
FunctionTooLong: mouse.create packages/driver/src/cy/mouse.ts:59— FunctionTooLong — create runs 359 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 259 over it, 3.59× 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: cookies.default packages/driver/src/cy/commands/cookies.ts:103— FunctionTooLong — default runs 347 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 247 over it, 3.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: ci_provider._providerCiParams packages/server/lib/util/ci_provider.ts:192— FunctionTooLong — _providerCiParams runs 287 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 187 over it, 2.87× 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.default packages/driver/src/cy/commands/sessions/index.ts:24— FunctionTooLong — default 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: navigation.default packages/driver/src/cy/commands/navigation.ts:675— FunctionTooLong — default runs 267 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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: inspect.create REDACTED:13— FunctionTooLong — create runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× 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: scroll.default packages/driver/src/cy/commands/actions/scroll.ts:50— FunctionTooLong — default runs 210 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 110 over it, 2.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: request.default packages/driver/src/cy/commands/request.ts:77— FunctionTooLong — default 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.
FunctionTooLong: waiting.default packages/driver/src/cy/commands/waiting.ts:43— FunctionTooLong — default 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.
FunctionTooLong: record.createRunAndRecordSpecs packages/server/lib/modes/record.ts:575— FunctionTooLong — createRunAndRecordSpecs runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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: before-request.onBeforeRequest packages/driver/src/cy/net-stubbing/events/before-request.ts:48— FunctionTooLong — onBeforeRequest runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.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.
FunctionTooLong: connectors.default packages/driver/src/cy/commands/connectors.ts:45— FunctionTooLong — default runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: runnable-popover-options.RunnablePopoverOptions packages/reporter/src/runnables/runnable-popover-options.tsx:21— FunctionTooLong — RunnablePopoverOptions runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: click.default packages/driver/src/cy/commands/actions/click.ts:51— FunctionTooLong — default runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: command.Command packages/reporter/src/commands/command.tsx:401— FunctionTooLong — Command runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.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.
FunctionTooLong: routes.createCommonRoutes packages/server/lib/routes.ts:48— FunctionTooLong — createCommonRoutes runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× 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: querying.default REDACTED:154— FunctionTooLong — default runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: select.default packages/driver/src/cy/commands/actions/select.ts:18— FunctionTooLong — default runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: snapshots.create packages/driver/src/cy/snapshots.ts:13— FunctionTooLong — create runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: firefox.open packages/server/lib/browsers/firefox.ts:466— FunctionTooLong — open runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: service-worker-injector.injectIntoServiceWorker packages/proxy/lib/http/util/service-worker-injector.ts:55— FunctionTooLong — injectIntoServiceWorker runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: makeDataContext.makeDataContext packages/server/lib/makeDataContext.ts:63— FunctionTooLong — makeDataContext runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: selectFile.default packages/driver/src/cy/commands/actions/selectFile.ts:133— FunctionTooLong — default runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: network-runtime.createCdpFetchRuntime packages/server/lib/network-runtime.ts:180— FunctionTooLong — createCdpFetchRuntime runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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.preprocessor npm/webpack-preprocessor/index.ts:228— FunctionTooLong — preprocessor runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.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.
Boundary violation [package:relative-cross-package] gulpfile.js:2— gulpfile.js:2 reaches into another package with a relative path (./scripts/gulp/gulpfile) — import the package by name instead.
Boundary violation [package:test-suite-dependency] npm/cypress-schematic/src/schematics/ng-generate/component/index.ts:3— npm/cypress-schematic/src/schematics/ng-generate/component/index.ts:3 imports npm/cypress-schematic/src/schematics/ng-generate/cypress-test/index.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:undeclared-workspace-dep] npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.ts:54— npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.ts:54 imports @cypress/webpack-batteries-included-preprocessor, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:test-suite-dependency] packages/app/src/debug/DebugSpec.vue:230— packages/app/src/debug/DebugSpec.vue:230 imports packages/app/src/specs/SpecNameDisplay.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/app/src/layouts/default.vue:76— packages/app/src/layouts/default.vue:76 imports packages/app/src/specs/banners/EnableNotificationsBanner.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/app/src/runner/SpecRunnerOpenMode.vue:131— packages/app/src/runner/SpecRunnerOpenMode.vue:131 imports packages/app/src/specs/InlineSpecList.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/app/src/runs/RunsContainer.vue:88— packages/app/src/runs/RunsContainer.vue:88 imports packages/app/src/specs/banners/TrackedBanner.vue, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/app/src/store/run-all-specs-store.ts:7— packages/app/src/store/run-all-specs-store.ts:7 imports packages/app/src/specs/tree/useCollapsibleTree.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:undeclared-workspace-dep] packages/config/src/ast-utils/addToCypressConfig.ts:144— packages/config/src/ast-utils/addToCypressConfig.ts:144 imports cypress, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:third-party-deep-import] packages/data-context/graphql/makeGraphQLServer.ts:18— packages/data-context/graphql/makeGraphQLServer.ts:18 imports graphql-ws/lib/use/ws, 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/data-context/graphql/plugins/nexusSlowGuardPlugin.ts:2— packages/data-context/graphql/plugins/nexusSlowGuardPlugin.ts:2 imports nexus/dist/utils, 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:undeclared-workspace-dep] packages/data-context/src/data/ProjectConfigIpc.ts:33— packages/data-context/src/data/ProjectConfigIpc.ts:33 imports @packages/server/lib/plugins/child/require_async_child.js, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:test-suite-dependency] REDACTED:5— REDACTED:5 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:8— packages/driver/src/cross-origin/cypress.ts:8 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:9— packages/driver/src/cross-origin/cypress.ts:9 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:10— packages/driver/src/cross-origin/cypress.ts:10 imports packages/driver/src/cypress/commands.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:11— packages/driver/src/cross-origin/cypress.ts:11 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:12— packages/driver/src/cross-origin/cypress.ts:12 imports packages/driver/src/cypress/log.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/cypress.ts:28— packages/driver/src/cross-origin/cypress.ts:28 imports packages/driver/src/cypress/mocha.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/events/errors.ts:3— packages/driver/src/cross-origin/events/errors.ts:3 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/events/misc.ts:2— packages/driver/src/cross-origin/events/misc.ts:2 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/origin_fn.ts:2— packages/driver/src/cross-origin/origin_fn.ts:2 imports packages/driver/src/cypress/error_utils.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/origin_fn.ts:3— packages/driver/src/cross-origin/origin_fn.ts:3 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/origin_fn.ts:4— packages/driver/src/cross-origin/origin_fn.ts:4 imports REDACTED, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:test-suite-dependency] packages/driver/src/cross-origin/origin_fn.ts:7— packages/driver/src/cross-origin/origin_fn.ts:7 imports packages/driver/src/cypress/log.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.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 npm/angular/src/mount.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/data-context/src/sources/RemoteRequestDataSource.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/data-context/src/sources/CloudDataSource.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/eslint-config/src/baseConfig.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/data-context/src/actions/WizardActions.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 npm/cypress-schematic/src/schematics/ng-add/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/data-context/src/sources/RelevantRunSpecsDataSource.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/data-context/src/sources/RelevantRunsDataSource.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 npm/vite-plugin-cypress-esm/src/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/gulp/utils/childProcessUtils.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/app/src/studio/studio-app-types.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/driver/src/cross-origin/cypress.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/binary/binary-cleanup.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/data-context/src/sources/VersionsDataSource.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/data-context/graphql/schemaTypes/objectTypes/gql-CurrentProject.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/launchpad/src/Main.vue: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/driver/src/cross-origin/origin_fn.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/scaffold-config/src/detect.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/binary/binary-integrity-check-source.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 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 npm/vite-plugin-cypress-esm/client/moduleCache.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 scripts/gulp/tasks/gulpCypress.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/data-context/graphql/schemaTypes/objectTypes/gql-Subscription.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/data-context/src/sources/GraphQLDataSource.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.
Sync-over-async blocking npm/vite-plugin-cypress-esm/src/index.ts:275— `fs.readFileSync` in `transformIndexHtml` 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 npm/webpack-dev-server/src/CypressCTWebpackPlugin.ts:113— `utimesSync` in `onSpecsChange` 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 packages/app/cypress/tasks/git.ts:9— `fs.readdirSync` in `initGitRepoForTestProject` 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 packages/app/cypress/tasks/git.ts:29— `fs.writeFileSync` in `initGitRepoForTestProject` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:27— `fs.utimesSync` in `windowsTouch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:29— `fs.closeSync` in `windowsTouch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:29— `fs.openSync` in `windowsTouch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:48— `execSync` in `nexusTypegen` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:49— `execSync` in `nexusTypegen` 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 packages/data-context/src/actions/ProjectActions.ts:560— `fs.existsSync` in `runSpec` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:477— `zlib.brotliCompressSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:480— `zlib.gzipSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:483— `zlib.gzipSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:485— `zlib.brotliCompressSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:488— `zlib.brotliCompressSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:490— `zlib.gzipSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:495— `zlib.brotliCompressSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:500— `zlib.gzipSync` in `app.get("/encoding/:encodingType/:assetType")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:159— `fs.existsSync` in `scaffoldProjectWithDeps` 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 packages/launchpad/cypress/tasks/snapshotsScaffold.ts:24— `fs.mkdirSync` in `snapshotScaffoldedFiles` 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 packages/launchpad/cypress/tasks/snapshotsScaffold.ts:135— `fs.existsSync` in `joinPosix` 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 packages/scaffold-config/src/ct-detect-third-party.ts:78— `fs.existsSync` in `callback to ROOT_PATHS.some` 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 packages/server/lib/cloud/artifacts/protocol_artifact.ts:63— `existsSync` in `composeProtocolErrorReportFromOptions` 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 packages/server/lib/modes/run.ts:377— `fs.existsSync` in `compressRecording` 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 scripts/after-sign-hook.js:29— `fs.existsSync` in `exports` 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.
Swallowed exception (empty catch) packages/socket/lib/client/cdp-browser.ts:77— `.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) packages/server/lib/cypress-sessions.ts:40— `.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) packages/server/lib/errors.ts:16— `.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) packages/server/lib/makeDataContext.ts:96— `.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) packages/server/lib/makeDataContext.ts:103— `.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) packages/server/lib/network-runtime.ts:389— `.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) packages/server/lib/network-runtime.ts:413— 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/server/lib/network-runtime.ts:467— `.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) packages/server/lib/socket-base.ts:686— `.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) packages/server/lib/socket-base.ts:690— `.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) packages/server/lib/util/app_data.ts:145— `.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) packages/server/lib/util/commit-info.ts:48— 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/server/lib/util/process_profiler.ts:260— `.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) packages/server/lib/util/server_destroy.ts:17— `.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) packages/server/lib/privileged-commands/privileged-channel.js:228— `.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) packages/server/lib/cloud/exception.ts:79— 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/server/lib/cloud/protocol.ts:510— `.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) packages/server/lib/cloud/protocol.ts:516— `.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) packages/server/lib/cloud/studio/StudioLifecycleManager.ts:343— `.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) packages/server/lib/cloud/studio/StudioLifecycleManager.ts:365— `.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) packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:29— `.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) packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:288— `.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) packages/server/lib/cloud/bundles/cache_root.ts:42— `.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) packages/server/lib/cloud/bundles/ensure_signed_bundle.ts:111— `.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) packages/server/lib/cloud/bundles/stream_download_verify_extract.ts:142— `.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.
FixmeComment system-tests/test/experimental_retries.spec.ts:232— // FIXME: this should be 8 — 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 system-tests/test/experimental_retries.spec.ts:273— // FIXME: this should be 8 — 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 system-tests/projects/angular-signals/src/signals-required/signals-required.component.cy.ts:31— // FIXME: we currently need to allow this as there isn't a great way to set input signals in a component due to how input signals are instantiated. — 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/server/test/unit/project-base.spec.ts:314— // FIXME: NEED TO MOVE TO DATA_CONTEXT PACKAGE — 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/server/test/unit/project-base.spec.ts:350— // FIXME: NEED TO MOVE TO DATA_CONTEXT PACKAGE — 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/server/test/unit/project-base.spec.ts:577— // FIXME: NEED TO MOVE TO DATA_CONTEXT PACKAGE — 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/server/test/unit/project-base.spec.ts:593— // FIXME: NEED TO MOVE TO DATA_CONTEXT PACKAGE — 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/server/lib/browsers/bidi_automation.ts:750— // FIXME: patch this for now just to get clean cookies between tests — 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/launcher/test/unit/detect.spec.ts:201— // FIXME: these tests really should be reworked to run the same regardless of OS/CPU architecture — 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/driver/cypress/e2e/e2e/origin/cookie_behavior.cy.ts:1147— // FIXME: cy.getCookie does not believe this cookie exists, though it is set in the browser. Should be fixed in https://github.com/cypress-io/cypress/pull/23643.
FixmeComment packages/driver/cypress/e2e/e2e/origin/cookie_behavior.cy.ts:1178— // FIXME: cy.getCookie does not believe this cookie exists, though it is set in the browser. Should be fixed in https://github.com/cypress-io/cypress/pull/23643
FixmeComment packages/driver/cypress/e2e/e2e/origin/cookie_behavior.cy.ts:1235— // FIXME: cy.getCookie does not believe this cookie exists, though it is set in the browser. Should be fixed in https://github.com/cypress-io/cypress/pull/23643
FixmeComment packages/driver/cypress/e2e/e2e/origin/cookie_behavior.cy.ts:1271— // FIXME: cy.getCookie does not believe this cookie exists, though it is set in the browser. Should be fixed in https://github.com/cypress-io/cypress/pull/23643
FixmeComment packages/driver/cypress/e2e/e2e/origin/cookie_misc.cy.ts:3— // FIXME: currently cookies aren't cleared properly in headless mode with webkit between tests, as the below tests (excluding cy.origin) pass headfully locally. — 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/driver/cypress/e2e/e2e/origin/commands/actions.cy.ts:661— // FIXME: snapshot shows the primary domain (before type). Should be secondary — 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/driver/cypress/e2e/e2e/origin/commands/actions.cy.ts:686— // FIXME: snapshot shows the primary domain. Should be secondary — 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/driver/cypress/e2e/e2e/origin/commands/actions.cy.ts:851— // FIXME: snapshot of primary is showing for scrollIntoView — 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/driver/cypress/e2e/e2e/origin/commands/navigation.cy.ts:389— // FIXME: flaky — 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/driver/cypress/e2e/commands/waiting.cy.ts:917— // FIXME: failing in CI sometimes https://circleci.com/gh/cypress-io/cypress/5655
FixmeComment packages/driver/cypress/e2e/commands/navigation/form_targets.cy.ts:29— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
FixmeComment packages/driver/cypress/e2e/commands/navigation/page_load.cy.ts:276— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
FixmeComment packages/driver/cypress/e2e/commands/navigation/page_load.cy.ts:293— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
FixmeComment packages/driver/cypress/e2e/commands/navigation/page_load.cy.ts:320— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
FixmeComment packages/driver/cypress/e2e/commands/navigation/page_load.cy.ts:344— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
FixmeComment REDACTED:202— // FIXME: fix flaky test (webkit): https://github.com/cypress-io/cypress/issues/24600
Cross-context type TestingType (types → data-context) packages/data-context/src/sources/ProjectDataSource.ts:299— TestingType (context types) is exposed in data-context's public surface via ProjectDataSource.specPatternsByTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/sources/ProjectDataSource.ts:511— TestingType (context types) is exposed in data-context's public surface via ProjectDataSource.matchesSpecPattern — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/sources/ProjectDataSource.ts:147— TestingType (context types) is exposed in data-context's public surface via ProjectDataSource.getPathFromSpecPattern — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/util/files.ts:9— TestingType (context types) is exposed in data-context's public surface via files.getDefaultSpecFileName — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectConfigIpc.ts:119— TestingType (context types) is exposed in data-context's public surface via ProjectConfigIpc.send — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectConfigIpc.ts:231— TestingType (context types) is exposed in data-context's public surface via ProjectConfigIpc.callSetupNodeEventsWithConfig — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectConfigManager.ts:130— TestingType (context types) is exposed in data-context's public surface via ProjectConfigManager.setTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectConfigManager.ts:624— TestingType (context types) is exposed in data-context's public surface via ProjectConfigManager.isTestingTypeConfigured — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:581— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.setCurrentTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:605— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.setAndLoadCurrentTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:787— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.isTestingTypeConfigured — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:805— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.initializeOpenMode — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:819— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.initializeProjectSetup — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/ProjectLifecycleManager.ts:833— TestingType (context types) is exposed in data-context's public surface via ProjectLifecycleManager.initializeRunMode — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/data/coreDataShape.ts:122— TestingType (context types) is exposed in data-context's public surface via CoreDataShape.currentTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/actions/ProjectActions.ts:65— TestingType (context types) is exposed in data-context's public surface via FindSpecs.testingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/actions/ProjectActions.ts:165— TestingType (context types) is exposed in data-context's public surface via ProjectActions.setAndLoadCurrentTestingType — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/actions/ProjectActions.ts:169— TestingType (context types) is exposed in data-context's public surface via ProjectActions.initializeProjectSetup — couples the contexts.
Cross-context type TestingType (types → data-context) packages/data-context/src/actions/ProjectActions.ts:490— TestingType (context types) is exposed in data-context's public surface via ProjectActions.switchTestingTypesAndRelaunch — couples the contexts.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×19
Untrusted text written into markup unescaped packages/app/src/runner/ScriptError.vue:5— `scriptError` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/app/src/runner/dom.ts:65— `css.toString()` 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/app/src/runs/RunsContainer.vue:42— `markdown` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/app/src/settings/project/ExperimentRow.vue:27— `markdown` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/data-context/src/codegen/templates/react-component/react-component.ejs:6— `componentPath` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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/data-context/src/codegen/templates/react-component/react-component.ejs:8— `componentName` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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/data-context/src/codegen/templates/react-component/react-component.ejs:11— `componentName` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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/data-context/src/codegen/templates/vue-component/vue-component.ejs:5— `componentName` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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/data-context/src/codegen/templates/vue-component/vue-component.ejs:10— `componentName` is text this program did not author, and it is written into the text of an element through EJS's raw `<%- %>` output 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/driver/src/util/serialization/log.ts:59— `el.value` 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/driver/src/util/serialization/log.ts:96— `props.innerHTML` 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/frontend-shared/src/components/ShikiHighlight.vue:56— `highlightedCode` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/frontend-shared/src/gql-components/error/BaseError.vue:62— `markdown` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/frontend-shared/src/gql-components/error/BaseError.vue:99— `baseError.errorStack` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/frontend-shared/src/warning/Warning.vue:14— `markdown` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/launchpad/src/setup/ManualInstall.vue:56— `dep.description` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/launchpad/src/setup/SelectFrameworkOrBundler.vue:35— `itemValue.icon` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/launchpad/src/setup/SelectFrameworkOrBundler.vue:75— `itemValue.icon` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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/reporter/src/runnables/runnable-error.tsx:32— `md.render(error.message)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×17
Focus outline removed in CSS without a :focus replacement packages/reporter/src/runnables/runnables.scss:156— `.reporter .runnable .runnable-wrapper .collapsible-header:focus-visible .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/runnables/runnables.scss:152— `.reporter .runnable .runnable-wrapper .collapsible-header:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/runnables/runnables.scss:183— `.reporter .runnable .runnable-wrapper .collapsible-header .collapsible-header-inner:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/hooks/hooks.scss:59— `.reporter .hooks-container .hook-header .collapsible-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/hooks/hooks.scss:63— `.reporter .hooks-container .hook-header .collapsible-header > .collapsible-header-inner:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/header/header.scss:14— `.reporter .spec-container` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/errors/errors.scss:184— `.reporter .runnable-err-stack-expander .collapsible-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/errors/errors.scss:203— `.reporter .runnable-err-stack-expander .collapsible-header .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/errors/errors.scss:220— `.reporter .runnable-err-stack-expander .runnable-err-print:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/commands/commands.scss:490— `.reporter .command-pin` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/reporter/src/attempts/attempts.scss:60— `.reporter .attempt-item > .collapsible > .attempt-name > .collapsible-header .collapsible-header-inner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/extension/app/popup.css:37— `ul>li>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/app/src/settings/project/ExperimentRow.vue:74— `.description :deep(a)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/app/src/runner/studio/AssertionType.ce.vue:118— `.assertion-type:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/app/src/runner/studio/AssertionType.ce.vue:97— `.assertion-type` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement npm/react/cypress/component/basic/react-tutorial/tic-tac-toe.css:37— `.square:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement npm/react/cypress/component/advanced/tutorial/tic-tac-toe.css:37— `.square:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Hotspot: packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:462— packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in CdpFetchTransport.interceptRequest at line 462. 1 of those changes was a fix/bug commit, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/socket-base.ts packages/server/lib/socket-base.ts:142— packages/server/lib/socket-base.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in SocketBase.startListening at line 142. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/socket-base.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/server-base.ts packages/server/lib/server-base.ts:1228— packages/server/lib/server-base.ts changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in ServerBase._onResolveUrl at line 1228. 6 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/server-base.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/routes.ts packages/server/lib/routes.ts:48— packages/server/lib/routes.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in routes.createCommonRoutes at line 48. 3 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/routes.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/driver/src/cy/commands/navigation.ts packages/driver/src/cy/commands/navigation.ts:675— packages/driver/src/cy/commands/navigation.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in navigation.default at line 675. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/driver/src/cy/commands/navigation.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:154— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in querying.default at line 154. 4 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-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/open_project.ts packages/server/lib/open_project.ts:69— packages/server/lib/open_project.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in OpenProject.launch at line 69. 3 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/open_project.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/browsers/cdp-protocol/cri-client.ts packages/server/lib/browsers/cdp-protocol/cri-client.ts:564— packages/server/lib/browsers/cdp-protocol/cri-client.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in CriClient.send at line 564. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/browsers/cdp-protocol/cri-client.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/browsers/browser-cri-client.ts packages/server/lib/browsers/browser-cri-client.ts:461— packages/server/lib/browsers/browser-cri-client.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BrowserCriClient._onAttachToTarget at line 461. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/browsers/browser-cri-client.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/driver/src/cy/commands/sessions/index.ts packages/driver/src/cy/commands/sessions/index.ts:24— packages/driver/src/cy/commands/sessions/index.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in index.default at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/driver/src/cy/commands/sessions/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/driver/src/cy/commands/request.ts packages/driver/src/cy/commands/request.ts:77— packages/driver/src/cy/commands/request.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in request.default at line 77. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/driver/src/cy/commands/request.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/lib/project-base.ts packages/server/lib/project-base.ts:166— packages/server/lib/project-base.ts changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ProjectBase.open at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/lib/project-base.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/server/test/performance/proxy_performance_spec.ts packages/server/test/performance/proxy_performance_spec.ts:506— packages/server/test/performance/proxy_performance_spec.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in runBrowserTest at line 506. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/server/test/performance/proxy_performance_spec.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/proxy/lib/http/util/service-worker-injector.ts packages/proxy/lib/http/util/service-worker-injector.ts:55— packages/proxy/lib/http/util/service-worker-injector.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in service-worker-injector.injectIntoServiceWorker at line 55. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/proxy/lib/http/util/service-worker-injector.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/driver/src/cypress/command_queue.ts packages/driver/src/cypress/command_queue.ts:437— packages/driver/src/cypress/command_queue.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in CommandQueue.run at line 437. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/driver/src/cypress/command_queue.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: src/errors.ts packages/errors/src/errors.ts— FileTooLong — 1156 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: AllCypressErrors (63-1791). The bar is 500 significant lines; this is 656 over it, 2.31× 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: cy/keyboard.ts packages/driver/src/cy/keyboard.ts— FileTooLong — 855 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 355 over it, 1.71× 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: lib/server-base.ts packages/server/lib/server-base.ts— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: ServerBase (229-1528). The bar is 500 significant lines; this is 272 over it, 1.54× 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: modes/run.ts packages/server/lib/modes/run.ts— FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 258 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/navigation.ts packages/driver/src/cy/commands/navigation.ts— FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/cypress.ts packages/driver/src/cypress.ts— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: $Cypress (118-1011). The bar is 500 significant lines; this is 92 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: modes/record.ts packages/server/lib/modes/record.ts— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 68 over it, 1.14× 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: runner/event-manager.ts packages/app/src/runner/event-manager.ts— FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: EventManager (57-1106). The bar is 500 significant lines; this is 60 over it, 1.12× 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: util/ci_provider.ts packages/server/lib/util/ci_provider.ts— FileTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 47 over it, 1.09× 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/options.ts packages/config/src/options.ts— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× 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: browsers/browser-cri-client.ts packages/server/lib/browsers/browser-cri-client.ts— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: BrowserCriClient (190-1074). 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: src/loader.ts packages/packherd-require/src/loader.ts— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12 over it, 1.02× 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.
Weak hash algorithm npm/webpack-dev-server/src/helpers/angularHandler.ts:165— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/data-context/src/sources/CloudDataSource.ts:181— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/data-context/src/sources/RemoteRequestDataSource.ts:370— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/driver/src/cy/snapshots_css.ts:127— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/electron/src/install.ts:56— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/frontend-shared/src/graphql/urqlDetailedDebugExchange.ts:58— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/proxy/lib/resourceTypeAndCredentialManager.ts:7— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/server/lib/plugins/child/cross_origin.ts:16— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/server/lib/util/app_data.ts:74— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm packages/server/lib/util/file.ts:76— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm scripts/circle-cache.js:108— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm scripts/circle-cache.js:125— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Off the main sequence: @packages/agent-info — @packages/agent-info: 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: @packages/icons — @packages/icons: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @packages/stderr-filtering — @packages/stderr-filtering: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @tooling/electron-mksnapshot — @tooling/electron-mksnapshot: 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: @tooling/packherd — @tooling/packherd: 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: @packages/telemetry — @packages/telemetry: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @packages/cypress-sessions — @packages/cypress-sessions: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @packages/packherd-require — @packages/packherd-require: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @cypress/webpack-preprocessor — @cypress/webpack-preprocessor: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: @packages/socket — @packages/socket: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Focus outline removed inline packages/app/src/components/FileMatchButton.vue:2— <button> 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 packages/app/src/components/FileMatchInput.vue:2— <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 packages/app/src/runner/SnapshotControls.vue:30— <button> 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 packages/app/src/runner/SnapshotToggle.vue:6— <button> 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 packages/app/src/runner/SpecRunnerHeaderOpenMode.vue:33— <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 packages/frontend-shared/src/components/AlertHeader.vue:28— <button> 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 packages/frontend-shared/src/components/StandardModalHeader.vue:23— <button> 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 packages/launchpad/src/global/FileDropzone.vue:40— <button> 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 packages/launchpad/src/global/GlobalProjectCard.vue:18— <button> 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).
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×9
Animation without a prefers-reduced-motion guard packages/app/src/navigation/SidebarNavigationHeader.vue:53— <iconloading> 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 packages/frontend-shared/src/gql-components/ChooseExternalEditorModal.vue:48— <i-cy-loading_x16> 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 packages/launchpad/src/setup/ButtonBar.vue:12— <i-cy-loading_x16> 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 packages/reporter/src/runnables/runnables.scss:501— `.reporter .runnable-loading .runnable-loading-animation div` moves (`animation: scaling 1.65s 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 packages/reporter/src/lib/switch.scss:98— `button.switch span.indicator` moves (`transition: transform 200ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/reporter/src/commands/commands.scss:273— `.reporter .command-state-pending + .command-progress span` moves (`animation-name: progress-bar`) 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 packages/reporter/src/commands/commands.scss:508— `.reporter %command-expander-base .command-expander` moves (`transition: transform 150ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/reporter/src/collapsible/collapsible.scss:7— `.reporter .collapsible-indicator` moves (`transition: transform 150ms ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard npm/react/cypress/component/advanced/set-timeout-example/App.css:6— `.App-logo` moves (`animation: App-logo-spin infinite 20s linear`) 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.
MethodTooLong: SocketBase.startListening packages/server/lib/socket-base.ts:142— MethodTooLong — startListening runs 360 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 260 over it, 3.60× 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: $Cypress.action packages/driver/src/cypress.ts:484— MethodTooLong — action runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ProjectBase.startWebsockets packages/server/lib/project-base.ts:381— MethodTooLong — startWebsockets runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EventManager.addGlobalListeners packages/app/src/runner/event-manager.ts:90— MethodTooLong — addGlobalListeners runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: ServerBase._onResolveUrl packages/server/lib/server-base.ts:1228— MethodTooLong — _onResolveUrl runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: EventManager._addListeners packages/app/src/runner/event-manager.ts:566— MethodTooLong — _addListeners 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: CriClient.send packages/server/lib/browsers/cdp-protocol/cri-client.ts:564— MethodTooLong — send runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: Keyboard.fireSimulatedEvent packages/driver/src/cy/keyboard.ts:880— MethodTooLong — fireSimulatedEvent runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.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.
MethodTooLong: CdpFetchTransport.resolveResponse packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:738— MethodTooLong — resolveResponse 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.
ClassTooLong: ServerBase packages/server/lib/server-base.ts:229— ClassTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 243 over it, 1.61× 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: EventManager packages/app/src/runner/event-manager.ts:57— ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 400 significant lines; this is 121 over it, 1.30× 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: $Cypress packages/driver/src/cypress.ts:118— ClassTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 105 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AutIframe packages/app/src/runner/aut-iframe.ts:20— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 80 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.
ClassTooLong: SocketBase packages/server/lib/socket-base.ts:53— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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: ProjectBase packages/server/lib/project-base.ts:77— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 23 over it, 1.06× 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: ProjectLifecycleManager packages/data-context/src/data/ProjectLifecycleManager.ts:54— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 15 over it, 1.04× 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: BrowserCriClient packages/server/lib/browsers/browser-cri-client.ts:190— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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: CdpFetchTransport packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:182— ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 3 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.
Fake-async — async method never awaits cli/lib/tap/output.ts:64— `renderTapFailure` 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 npm/webpack-dev-server/src/CypressCTWebpackPlugin.ts:101— `onSpecsChange` 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:23— `windowsTouch` 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/proxy/lib/http/response-middleware.ts:561— `MaybeEndWithEmptyBody` 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/server/index.js:1— `runChildProcess` 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/server/lib/browsers/firefox.ts:772— `closeExtraTargets` 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/server/lib/browsers/webkit.ts:184— `closeExtraTargets` 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 scripts/gulp/tasks/gulpRegistry.ts:76— `exitAfterAll` 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:24— `windowsTouch` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Outbound HTTP without resilience packages/data-context/src/sources/UtilDataSource.ts:20— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/lib/cloud/api/cloud_request.ts:41— `axios.create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/lib/cloud/network/fetch.ts:32— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/lib/cloud/network/fetch.ts:41— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/lib/cloud/protocol.ts:488— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/lib/privileged-commands/privileged-channel.js:217— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/scripts/sync-cloud-validations.ts:38— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/server/scripts/sync-cloud-validations.ts:64— `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.
AC3 · Page structure· Page without a main landmark · ×6
Page without a main landmark packages/driver/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/extension/app/newtab.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/extension/app/popup.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/launchpad/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/server/lib/html/non_proxied_error.html:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/server/lib/util/network_failures.ts:20— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
TooManyMethods: ServerBase packages/server/lib/server-base.ts:229— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AutIframe packages/app/src/runner/aut-iframe.ts:20— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProtocolManager packages/server/lib/cloud/protocol.ts:36— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProjectLifecycleManager packages/data-context/src/data/ProjectLifecycleManager.ts:54— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EventManager packages/app/src/runner/event-manager.ts:57— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ProjectActions packages/data-context/src/actions/ProjectActions.ts:93— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.
Duplicated block (20 lines × 2 locations) npm/vue/src/index.ts:260— npm/vue/src/index.ts:260 · npm/vue/src/index.ts:332 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) packages/driver/src/dom/elements/nativeProps.ts:21— packages/driver/src/dom/elements/nativeProps.ts:21 · packages/driver/src/dom/elements/nativeProps.ts:42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) scripts/binary/zip.js:88— scripts/binary/zip.js:88 · scripts/binary/zip.js:166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) scripts/unit/binary/util/packages-spec.js:74— scripts/unit/binary/util/packages-spec.js:74 · scripts/unit/binary/util/packages-spec.js:111 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (20 lines × 2 locations) scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:21— scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:21 · scripts/unit/github-actions/semantic-pull-request/validate-pr-title-spec.js:53 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) scripts/unit/semantic-commits/validate-changelog-spec.js:247— scripts/unit/semantic-commits/validate-changelog-spec.js:247 · scripts/unit/semantic-commits/validate-changelog-spec.js:285 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
X2 · Cancellation propagation· Async function without AbortSignal · ×6
Async function without AbortSignal: getLatestVersionData scripts/github-actions/update-browser-versions.js:33— `getLatestVersionData` 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: getLastKnownGoodChromeForTestingStable scripts/github-actions/update-browser-versions.js:45— `getLastKnownGoodChromeForTestingStable` 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: syncCloudValidations packages/server/scripts/sync-cloud-validations.ts:29— `syncCloudValidations` 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: fetchCurrentEtag packages/server/scripts/sync-cloud-validations.ts:60— `fetchCurrentEtag` 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: dispatchErrors packages/server/lib/cloud/protocol.ts:458— `dispatchErrors` 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: getCallbackFn packages/driver/src/cross-origin/origin_fn.ts:74— `getCallbackFn` 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 })`.
D10 · Test Quality· Test project verifies nothing · ×5
Test project verifies nothing: system-tests/projects/angular-custom-root system-tests/projects/angular-custom-root/ui/app/app.component.cy.ts:4— No conventional assertion call was detected in 1 of 1 tests in `system-tests/projects/angular-custom-root` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: system-tests/projects/nextjs-configured system-tests/projects/nextjs-configured/components/button.cy.jsx:4— No conventional assertion call was detected in 1 of 1 tests in `system-tests/projects/nextjs-configured` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: system-tests/projects/react-vite-ts-configured system-tests/projects/react-vite-ts-configured/src/App.cy.tsx:5— No conventional assertion call was detected in 1 of 1 tests in `system-tests/projects/react-vite-ts-configured` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: system-tests/projects/vite-simple system-tests/projects/vite-simple/src/one.cy.jsx:5— No conventional assertion call was detected in 2 of 2 tests in `system-tests/projects/vite-simple` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Test project verifies nothing: system-tests/projects/vue3-vite-ts-configured system-tests/projects/vue3-vite-ts-configured/src/components/HelloWorld.cy.ts:4— No conventional assertion call was detected in 1 of 1 tests in `system-tests/projects/vue3-vite-ts-configured` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Cross-context type TestingType (types → config) packages/config/src/options.ts:99— TestingType (context types) is exposed in config's public surface via BreakingOption.testingTypes — couples the contexts.
Cross-context type TestingType (types → config) packages/config/src/browser.ts:169— TestingType (context types) is exposed in config's public surface via browser.validate — couples the contexts.
Cross-context type TestingType (types → config) packages/config/src/browser.ts:190— TestingType (context types) is exposed in config's public surface via browser.validateNoBreakingConfigRoot — couples the contexts.
Cross-context type TestingType (types → config) packages/config/src/browser.ts:194— TestingType (context types) is exposed in config's public surface via browser.validateNoBreakingConfig — couples the contexts.
Cross-context type TestingType (types → config) packages/config/src/project/index.ts:49— TestingType (context types) is exposed in config's public surface via index.updateWithPluginValues — couples the contexts.
Cross-context type TestState (types → reporter) packages/reporter/src/instruments/instrument-model.ts:26— TestState (context types) is exposed in reporter's public surface via InstrumentProps.state — couples the contexts.
Cross-context type TestState (types → reporter) packages/reporter/src/runnables/suite-model.ts:33— TestState (context types) is exposed in reporter's public surface via Suite.state — couples the contexts.
Cross-context type TestState (types → reporter) packages/reporter/src/attempts/attempt-model.ts:30— TestState (context types) is exposed in reporter's public surface via Attempt._state — couples the contexts.
Cross-context type TestState (types → reporter) packages/reporter/src/attempts/attempt-model.ts:31— TestState (context types) is exposed in reporter's public surface via Attempt._testOuterStatus — couples the contexts.
Cross-context type TestState (types → reporter) packages/reporter/src/header/stats-store.ts:74— TestState (context types) is exposed in reporter's public surface via StatsStore.incrementCount — couples the contexts.
Swallowed exception (caught, then discarded) packages/server/lib/open_project.ts:282— `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) packages/server/lib/util/electron-app.ts:8— `catch (err)` 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/server/lib/util/electron-app.ts:19— `catch (err)` 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/server/lib/util/electron-app.ts:39— `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:77— `catch (err)` 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.
HackComment system-tests/lib/spec_helper.ts:47— // hack for older version of mocha so that — 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.
HackComment packages/driver/src/cypress/mocha.ts:514— // HACK: we need to dynamically enqueue tests to suite.tests during a test run — 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.
HackComment packages/driver/src/cy/assertions.ts:448— // HACK: bluebird .reduce will not call the callback — 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.
HackComment packages/driver/src/cross-origin/origin_fn.ts:138— // HACK: We're telling the runnable that it has passed to avoid a timeout — 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.
Cross-context type TestingType (types → server) packages/server/lib/routes.ts:45— TestingType (context types) is exposed in server's public surface via InitializeRoutes.testingType — couples the contexts.
Cross-context type TestingType (types → server) packages/server/lib/project-base.ts:52— TestingType (context types) is exposed in server's public surface via Cfg.testingType — couples the contexts.
Cross-context type TestingType (types → server) packages/server/lib/project-base.ts:93— TestingType (context types) is exposed in server's public surface via ProjectBase.testingType — couples the contexts.
Cross-context type TestingType (types → server) packages/server/lib/modes/run.ts:1106— TestingType (context types) is exposed in server's public surface via ReadyOptions.testingType — couples the contexts.
Change coupling: REDACTED ↔ REDACTED REDACTED:1— `REDACTED` and `packages/driver/src/cy/commands/origin/index.ts` change together 81% of the time (17 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 17 shared commits counted here, the most recent 3 are `1c1734b2` fix: remove cross origin window ref in spec-bridge communicator lifec…; `208efbfb` fix: Use post message instead of web sockets for spec bridges. (#24243); `18321f80` chore: refactor originPolicy to use superDomainOrigin nomenclat… (#23… — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED packages/proxy/lib/http/index.ts:1— `packages/proxy/lib/http/index.ts` and `packages/proxy/lib/http/util/cookies.ts` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 9 shared commits counted here, the most recent 3 are `a75b1a81` refactor: consolidate server cookie automation code under lib/automat…; `d682b297` refactor: move resourceTypeAndCredentialManager from @packages/server…; `2e092add` perf: no longer pause every single request through CDP and only pause… — run `git show` on any of them.
Change coupling: record_spec.ts.js ↔ REDACTED system-tests/__snapshots__/record_spec.ts.js:1— `system-tests/__snapshots__/record_spec.ts.js` and `REDACTED` change together 64% of the time (9 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 9 shared commits counted here, the most recent 3 are `9954a153` chore: convert record_spec system test to TypeScript (#35067); `5c3a8dc7` fix: [protocol] throw error verifying sig (#29603) (at that commit the file was still `system-tests/__snapshots__/record_spec.js`); `b62fc3fd` fix: no longer use capture script url as default upload url for test … (at that commit the file was still `system-tests/__snapshots__/record_spec.js`) — run `git show` on any of them.
Change coupling: request-middleware.ts ↔ REDACTED packages/proxy/lib/http/request-middleware.ts:1— `packages/proxy/lib/http/request-middleware.ts` and `packages/proxy/lib/http/util/cookies.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `d682b297` refactor: move resourceTypeAndCredentialManager from @packages/server…; `2e092add` perf: no longer pause every single request through CDP and only pause…; `e02f6bf9` feat: add `resourceType` support to `cy.intercept()` on `req`/`routeM… — run `git show` on any of them.
Duplicated block (17 lines × 2 locations) packages/data-context/src/data/ProjectConfigManager.ts:624— packages/data-context/src/data/ProjectConfigManager.ts:624 · packages/data-context/src/data/ProjectLifecycleManager.ts:787 — 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.
Duplicated block (17 lines × 2 locations) packages/errors/src/errors.ts:268— packages/errors/src/errors.ts:268 · packages/errors/src/errors.ts:302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2 locations) scripts/sanitize-mocha-results.js:67— scripts/sanitize-mocha-results.js:67 · scripts/verify-mocha-results.js:65 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) tooling/electron-mksnapshot/src/mksnapshot-run.ts:171— tooling/electron-mksnapshot/src/mksnapshot-run.ts:171 · tooling/electron-mksnapshot/src/mksnapshot-run.ts:230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2 locations) packages/app/src/prompt/prompt-app-types.ts:8— packages/app/src/prompt/prompt-app-types.ts:8 · packages/app/src/studio/studio-app-types.ts:69 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (16 lines × 2 locations) packages/driver/src/dom/selection.ts:187— packages/driver/src/dom/selection.ts:187 · packages/driver/src/dom/selection.ts:238 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 2 locations) REDACTED:123— REDACTED:123 · REDACTED:269 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (16 lines × 2 locations) scripts/binary/s3-api.ts:97— scripts/binary/s3-api.ts:97 · scripts/binary/s3-api.ts:157 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC4 · Keyboard semantics· Anchor without href · ×3
Anchor without href packages/reporter/src/components/LaunchStudioIcon.tsx:19— 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.
Anchor without href REDACTED:52— 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.
Anchor without href packages/reporter/src/runnables/runnables.tsx:72— 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.
Duplicated block (19 lines × 2 locations) packages/app/src/debug/DebugRunNavigation.vue:229— packages/app/src/debug/DebugRunNavigation.vue:229 · packages/app/src/runs/RunsLayout.vue:136 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (19 lines × 2 locations) scripts/unit/binary/util/packages-spec.js:202— scripts/unit/binary/util/packages-spec.js:202 · scripts/unit/binary/util/packages-spec.js:224 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) scripts/unit/github-actions/update-browser-version-spec.js:96— scripts/unit/github-actions/update-browser-version-spec.js:96 · scripts/unit/github-actions/update-browser-version-spec.js:190 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×2
Link used as a button (placeholder href) packages/reporter/src/lib/file-name-opener.tsx:26— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Link used as a button (placeholder href) packages/reporter/src/runnables/runnables.tsx:63— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Low contrast colour pair in CSS (2.3:1) npm/react/cypress/component/basic/css-modules/Button.module.css:24— `.componentButton.orange button` sets color: white on background-color: #f5923e — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.3:1) npm/react/cypress/component/basic/css/Button.css:24— `.component-button.orange button` sets color: white on background-color: #F5923E — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Cross-context type TapExecResult (cypress-sessions → app) packages/app/src/tap/contract.ts:62— TapExecResult (context cypress-sessions) is exposed in app's public surface via TapBindingContract.exec — couples the contexts.
Cross-context type TapExecResult (cypress-sessions → app) packages/app/src/tap/tap-manager.ts:50— TapExecResult (context cypress-sessions) is exposed in app's public surface via TapManager.exec — couples the contexts.
Cross-context type CloudStatus (app → frontend-shared) packages/frontend-shared/src/utils/isAllowedFeature.ts:38— CloudStatus (context app) is exposed in frontend-shared's public surface via isAllowedFeature.isAllowedFeature — couples the contexts.
Cross-context type CloudStatus (app → frontend-shared) packages/frontend-shared/src/gql-components/composables/usePromptManager.ts:46— CloudStatus (context app) is exposed in frontend-shared's public surface via usePromptManager.usePromptManager.isAllowedFeature — couples the contexts.
Cross-context type TestFilter (types → reporter) packages/reporter/src/runnables/runnables-store.ts:39— TestFilter (context types) is exposed in reporter's public surface via RootRunnable.testFilter — couples the contexts.
Cross-context type TestFilter (types → reporter) packages/reporter/src/runnables/runnables-store.ts:60— TestFilter (context types) is exposed in reporter's public surface via RunnablesStore.testFilter — couples the contexts.
Hollow method — returns a constant without doing the work packages/app/src/runner/event-manager.ts:32— `crossOriginOnMessageRef` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work packages/server/lib/browsers/chrome.ts:409— `onReconnect` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Duplicated block (24 lines × 2 locations) packages/server/lib/network-runtime.ts:104— packages/server/lib/network-runtime.ts:104 · packages/server/lib/network-runtime.ts:180 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) scripts/binary/smoke.js:130— scripts/binary/smoke.js:130 · scripts/binary/smoke.js:172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (15 matched lines × 2 locations) · ×2
Duplicated block with local edits (15 matched lines × 2 locations) packages/reporter/src/collapsible/collapsible.tsx:42— packages/reporter/src/collapsible/collapsible.tsx:42 · packages/reporter/src/studio/StudioTest.tsx:94 — the two spans are one implementation copied and then locally edited — 90 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (15 matched lines × 2 locations) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:747— packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:747 · packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:773 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (15 lines × 2 locations) scripts/binary/index.js:251— scripts/binary/index.js:251 · scripts/binary/index.js:267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) scripts/binary/smoke.js:76— scripts/binary/smoke.js:76 · scripts/binary/smoke.js:205 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~30 LoC) packages/app/src/pages/Settings.vue— no import path from any entry point (516 application, 508 tooling, 3317 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 (~30 LoC) packages/app/src/pages/[...all].vue— no import path from any entry point (516 application, 508 tooling, 3317 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
`async` Promise executor packages/server/lib/cypress.ts:113— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor cli/lib/exec/spawn.ts:66— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap packages/driver/src/dom/transform.ts:51— `detectVisibility` is exported, takes a document from its caller (line 7) and hands it to `extractTransformInfoFromElements`, which calls itself at line 51 (`extractTransformInfoFromElements`) with a piece of `$el` — and nowhere in `extractTransformInfoFromElements` 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 `extractTransformInfoFromElements` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/config/src/project/utils.ts:254— `setPluginResolvedOn` is exported and takes `resolvedObj: Record<string, any>` from its caller, and it calls itself at line 254 (`setPluginResolvedOn`) with a piece of `resolvedObj` — and nowhere in `setPluginResolvedOn` 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 `setPluginResolvedOn` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Empty <h2> heading packages/frontend-shared/src/components/ListRowHeader.vue:15— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
$Cypress.action (cyclomatic 85) packages/driver/src/cypress.ts:484— $Cypress.action has cyclomatic complexity 85 (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.
mouse.create (cyclomatic 78) packages/driver/src/cy/mouse.ts:59— mouse.create has cyclomatic complexity 78 (threshold 15). Of this number, 36 points are the body's own statements and 42 belong to 11 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.
navigation.default (cyclomatic 65) packages/driver/src/cy/commands/navigation.ts:675— navigation.default has cyclomatic complexity 65 (threshold 15). Of this number, 19 points are the body's own statements and 46 belong to 12 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.
SocketBase.startListening (cyclomatic 62) packages/server/lib/socket-base.ts:142— SocketBase.startListening has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 1 of the 62 points is its own statement and the rest belongs to 22 function literals inside it that branch (lines 513, 620, 596, …). 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.
index.default (cyclomatic 56) packages/driver/src/cy/commands/sessions/index.ts:24— index.default has cyclomatic complexity 56 (threshold 15). Of this number, 24 points are the body's own statements and 32 belong to 18 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.
request.default (cyclomatic 52) packages/driver/src/cy/commands/request.ts:77— request.default has cyclomatic complexity 52 (threshold 15). Of this number, 41 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
chai.chai.use() (cyclomatic 50) packages/driver/src/cy/chai.ts:47— chai.chai.use() has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 3 of the 50 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 403, a function literal at line 334, a function literal at line 200, …). 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.
cookies.default (cyclomatic 50) packages/driver/src/cy/commands/cookies.ts:103— cookies.default has cyclomatic complexity 50 (threshold 15). Of this number, 25 points are the body's own statements and 25 belong to 15 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.
scroll.default (cyclomatic 48) packages/driver/src/cy/commands/actions/scroll.ts:50— scroll.default has cyclomatic complexity 48 (threshold 15). Of this number, 36 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
connectors.default (cyclomatic 47) packages/driver/src/cy/commands/connectors.ts:45— connectors.default has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 6 of the 47 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 218, a function literal at line 146, a function literal at line 182, …). 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.
querying.default (cyclomatic 47) REDACTED:154— querying.default has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 235, 183, 342, …). 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.
inspect.create.formatValue (cyclomatic 42) REDACTED:73— inspect.create.formatValue has cyclomatic complexity 42 (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.
jquery.scrollto.scrollTo (cyclomatic 39) packages/driver/src/config/jquery.scrollto.ts:36— jquery.scrollto.scrollTo has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 7 of the 39 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 106, 64, 159). 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.
addToCypressConfigPlugin.addToCypressConfigPlugin (cyclomatic 38) packages/config/src/ast-utils/addToCypressConfigPlugin.ts:22— addToCypressConfigPlugin.addToCypressConfigPlugin has cyclomatic complexity 38 (threshold 15). Of this number, 34 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.
keyboard.validateTyping (cyclomatic 38) packages/driver/src/cy/keyboard.ts:387— keyboard.validateTyping has cyclomatic complexity 38 (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.
register.register (cyclomatic 35) npm/grep/src/register.ts:15— register.register has cyclomatic complexity 35 (threshold 15). Of this number, 24 points are the body's own statements and 11 belong to 2 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.
command.Command (cyclomatic 35) packages/reporter/src/commands/command.tsx:401— command.Command has cyclomatic complexity 35 (threshold 15). Of this number, 28 points are the body's own statements and 7 belong to 5 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.
record.createRun (cyclomatic 35) packages/server/lib/modes/record.ts:236— record.createRun has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 7 of the 35 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 350, 308, 303). 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.
select.default (cyclomatic 34) packages/driver/src/cy/commands/actions/select.ts:18— select.default has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 7 function items inside it that branch (getOptions, a function literal at line 120, a function literal at line 87, …). 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.
files.default (cyclomatic 34) packages/driver/src/cy/commands/files.ts:18— files.default has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 11 of the 34 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 19, 227, 87, …). 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.
service-worker-injector.injectIntoServiceWorker (cyclomatic 34) packages/proxy/lib/http/util/service-worker-injector.ts:55— service-worker-injector.injectIntoServiceWorker has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 2 of the 34 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 160, __cypressInjectIntoServiceWorker, a function literal at line 218, …). 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.
actionability.verify (cyclomatic 33) packages/driver/src/cy/actionability.ts:445— actionability.verify has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 534, addScrollBehaviorFix, a function literal at line 636, …). 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.
type.default::type::type (cyclomatic 33) packages/driver/src/cy/commands/actions/type.ts:177— type.default::type::type has cyclomatic complexity 33 (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.
CdpFetchTransport.interceptRequest (cyclomatic 33) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:462— CdpFetchTransport.interceptRequest has cyclomatic complexity 33 (threshold 15). Of this number, 28 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
run.processRunOptions (cyclomatic 32) cli/lib/exec/run.ts:38— run.processRunOptions has cyclomatic complexity 32 (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.
EventManager._addListeners (cyclomatic 31) packages/app/src/runner/event-manager.ts:566— EventManager._addListeners has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 12 function items inside it that branch (handleBeforeScreenshot, a function literal at line 682, a function literal at line 667, …). 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.
run_require_async_child.run (cyclomatic 31) packages/server/lib/plugins/child/run_require_async_child.ts:24— run_require_async_child.run has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 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 128, getValidDevServer, a function literal at line 112, …). 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.
spawn.createSpawnFunction (cyclomatic 30) cli/lib/exec/spawn.ts:60— spawn.createSpawnFunction has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 66, 261, 152, …). 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.
plugin.plugin (cyclomatic 30) npm/grep/src/plugin.ts:19— plugin.plugin has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.preprocessor (cyclomatic 30) npm/webpack-preprocessor/index.ts:228— index.preprocessor has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 242, 286, 387, …). 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.
EventManager.addGlobalListeners (cyclomatic 30) packages/app/src/runner/event-manager.ts:90— EventManager.addGlobalListeners has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 131, a function literal at line 182, a function literal at line 154, …). 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.
run.waitForTestsToFinishRunning (cyclomatic 30) packages/server/lib/modes/run.ts:631— run.waitForTestsToFinishRunning has cyclomatic complexity 30 (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.
BrowserCriClient._onAttachToTarget (cyclomatic 30) packages/server/lib/browsers/browser-cri-client.ts:461— BrowserCriClient._onAttachToTarget has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
visibility.getReasonIsHidden (cyclomatic 29) packages/driver/src/dom/visibility.ts:527— visibility.getReasonIsHidden has cyclomatic complexity 29 (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.
before-request.onBeforeRequest (cyclomatic 29) packages/driver/src/cy/net-stubbing/events/before-request.ts:48— before-request.onBeforeRequest has cyclomatic complexity 29 (threshold 15). Of this number, 17 points are the body's own statements and 12 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.
CdpAutomation.onRequest (cyclomatic 29) packages/server/lib/browsers/cdp-protocol/cdp_automation.ts:506— CdpAutomation.onRequest has cyclomatic complexity 29 (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.
firefox.open (cyclomatic 29) packages/server/lib/browsers/firefox.ts:466— firefox.open has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 2 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.
focus.default (cyclomatic 28) packages/driver/src/cy/commands/actions/focus.ts:25— focus.default 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.
routes.createCommonRoutes (cyclomatic 28) packages/server/lib/routes.ts:48— routes.createCommonRoutes has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 98, a function literal at line 362, a function literal at line 246, …). 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.
(anonymous) (cyclomatic 28) packages/server/lib/privileged-commands/privileged-channel.js:1— (anonymous) has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 13 function items inside it that branch (onCommandInvocation, stackIsFromSpecFrame, hasCallbackInsideEval, …). 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.
validation.isValidClientCertificatesSet (cyclomatic 27) packages/config/src/validation.ts:367— validation.isValidClientCertificatesSet 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.
traversals.default (cyclomatic 27) packages/driver/src/cy/commands/traversals.ts:12— traversals.default 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 6 function items inside it that branch (getEl, a function literal at line 86, 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.
args.toObject (cyclomatic 27) packages/server/lib/util/args.ts:342— args.toObject has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ci_provider._providerCommitParams (cyclomatic 27) packages/server/lib/util/ci_provider.ts:554— ci_provider._providerCommitParams has cyclomatic complexity 27 (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.
focused.create (cyclomatic 26) packages/driver/src/cy/focused.ts:53— focused.create has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 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.
setup.setup (cyclomatic 25) npm/puppeteer/src/plugin/setup.ts:35— setup.setup has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
selectFile.default (cyclomatic 25) packages/driver/src/cy/commands/actions/selectFile.ts:133— selectFile.default has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 235, getEventTargetFromSubject, handleAlias, …). 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.
install.start (cyclomatic 24) cli/lib/tasks/install.ts:128— install.start has cyclomatic complexity 24 (threshold 15). Of this number, 16 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
upload_artifacts.uploadArtifacts (cyclomatic 24) packages/server/lib/cloud/artifacts/upload_artifacts.ts:153— upload_artifacts.uploadArtifacts has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
click.default (cyclomatic 23) packages/driver/src/cy/commands/actions/click.ts:51— click.default 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 6 function items inside it that branch (mouseAction::flagModifiers, mouseAction::perform, mouseAction::perform::createLog::consoleProps, …). 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.
static-response-utils.validateStaticResponse (cyclomatic 23) packages/driver/src/cy/net-stubbing/static-response-utils.ts:19— static-response-utils.validateStaticResponse has cyclomatic complexity 23 (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.
client-certificates.loadClientCertificateConfig (cyclomatic 23) packages/network/lib/client-certificates.ts:207— client-certificates.loadClientCertificateConfig has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 246, 218, 224). 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.
CriClient.send (cyclomatic 23) packages/server/lib/browsers/cdp-protocol/cri-client.ts:564— CriClient.send has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 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.
CdpFetchTransport.resolveResponse (cyclomatic 23) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:738— CdpFetchTransport.resolveResponse 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.
route-matching.doesRouteMatch (cyclomatic 22) packages/network-interception/lib/core/route-matching.ts:19— route-matching.doesRouteMatch has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 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.
OpenProject.launch (cyclomatic 22) packages/server/lib/open_project.ts:69— OpenProject.launch has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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.
GitDataSource.#loadBulkGitInfo (cyclomatic 21) packages/data-context/src/sources/GitDataSource.ts:267— GitDataSource.#loadBulkGitInfo 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.
index.default (cyclomatic 21) packages/driver/src/cy/commands/origin/index.ts:32— index.default has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 179, 222, 79, …). 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.
add-command.validateRouteMatcherOptions (cyclomatic 21) packages/driver/src/cy/net-stubbing/add-command.ts:112— add-command.validateRouteMatcherOptions 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.
add-command.addCommand (cyclomatic 21) packages/driver/src/cy/net-stubbing/add-command.ts:172— add-command.addCommand has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 4 function items inside it that branch (addRoute, intercept::getMatcherOptions, intercept::checkExtraArguments, …). 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.
ServiceWorkerManager.processBrowserPreRequest (cyclomatic 21) packages/proxy/lib/http/util/service-worker-manager.ts:197— ServiceWorkerManager.processBrowserPreRequest has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 214). 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.
moduleCache.createProxyModule (cyclomatic 20) npm/vite-plugin-cypress-esm/client/moduleCache.js:7— moduleCache.createProxyModule has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.addTypeScriptConfig (cyclomatic 20) REDACTED:80— index.addTypeScriptConfig has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validation.isValidRetriesConfig (cyclomatic 20) packages/config/src/validation.ts:178— validation.isValidRetriesConfig 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.
keyboard.shouldUpdateValue (cyclomatic 20) packages/driver/src/cy/keyboard.ts:313— keyboard.shouldUpdateValue 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.
clock.default (cyclomatic 20) packages/driver/src/cy/commands/clock.ts:15— clock.default has cyclomatic complexity 20 (threshold 15). Of this number, 13 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.
querying.getAlias (cyclomatic 20) REDACTED:20— querying.getAlias has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
sourcemap-support.CallSiteToString (cyclomatic 20) packages/packherd-require/src/sourcemap-support.ts:366— sourcemap-support.CallSiteToString 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.
set-injection-level.setInjectionLevel (cyclomatic 20) packages/proxy/lib/adapters/set-injection-level.ts:20— set-injection-level.setInjectionLevel has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 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.
runnable-popover-options.RunnablePopoverOptions (cyclomatic 20) packages/reporter/src/runnables/runnable-popover-options.tsx:21— runnable-popover-options.RunnablePopoverOptions 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 (getSuiteIdForNewTest, a function literal at line 103, togglePopover, …). 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.
Telemetry.startSpan (cyclomatic 20) packages/telemetry/src/telemetry/index.ts:144— Telemetry.startSpan has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 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.
custom-require.customRequire (cyclomatic 20) tooling/v8-snapshot/src/blueprint/custom-require.js:33— custom-require.customRequire 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.
determine-deferred.determineDeferred (cyclomatic 20) tooling/v8-snapshot/src/doctor/determine-deferred.ts:52— determine-deferred.determineDeferred has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Keyboard.simulatedKeydown (cyclomatic 19) packages/driver/src/cy/keyboard.ts:1149— Keyboard.simulatedKeydown 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.
navigation.stabilityChanged (cyclomatic 19) packages/driver/src/cy/commands/navigation.ts:179— navigation.stabilityChanged has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 321, onPageLoadErr, getRedirectionCount, …). 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.
InterceptedRequest.handleSubscriptions (cyclomatic 19) packages/net-stubbing/lib/server/intercepted-request.ts:121— InterceptedRequest.handleSubscriptions has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
AutIframe.highlightEl (cyclomatic 18) packages/app/src/runner/aut-iframe.ts:331— AutIframe.highlightEl 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 3 function items inside it that branch (processOffsetBatch, a function literal at line 368, a function literal at line 460). 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.
aliases.create (cyclomatic 18) packages/driver/src/cy/aliases.ts:21— aliases.create 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.
assertions.create.verifyUpcomingAssertions (cyclomatic 18) packages/driver/src/cy/assertions.ts:289— assertions.create.verifyUpcomingAssertions 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 (onFailFn, ensureExistence, determineEl, …). 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.
asserting.default (cyclomatic 18) packages/driver/src/cy/commands/asserting.ts:33— asserting.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 6 function items inside it that branch (shouldFn::applyChainer, a function literal at line 183, shouldFn, …). 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.
window.default (cyclomatic 18) packages/driver/src/cy/commands/window.ts:50— window.default has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 6 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.
ProjectBase.startWebsockets (cyclomatic 18) packages/server/lib/project-base.ts:381— ProjectBase.startWebsockets has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function items inside it that branch (a function literal at line 481, a function literal at line 634, destroyStudio, …). 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.
run.ready (cyclomatic 18) packages/server/lib/modes/run.ts:1111— run.ready has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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.
ProjectLifecycleManager.createConfigManager (cyclomatic 17) packages/data-context/src/data/ProjectLifecycleManager.ts:204— ProjectLifecycleManager.createConfigManager 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 219, 249). 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.
ProjectActions.runSpec (cyclomatic 17) packages/data-context/src/actions/ProjectActions.ts:504— ProjectActions.runSpec has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
selection._moveSelectionTo (cyclomatic 17) packages/driver/src/dom/selection.ts:536— selection._moveSelectionTo 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.
screenshot.default (cyclomatic 17) packages/driver/src/cy/commands/screenshot.ts:493— screenshot.default has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 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.
Command.isOpen (cyclomatic 17) packages/reporter/src/commands/command-model.ts:89— Command.isOpen 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.
parse-changelog.parseChangelog (cyclomatic 17) scripts/semantic-commits/parse-changelog.js:6— parse-changelog.parseChangelog 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.
console-props.onOneRow (cyclomatic 16) cli/lib/tap/render/console-props.ts:64— console-props.onOneRow 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.
pin.pinCommand (cyclomatic 16) packages/app/src/tap/commands/pin.ts:103— pin.pinCommand has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils.mergeDefaults (cyclomatic 16) packages/config/src/project/utils.ts:406— utils.mergeDefaults has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 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.
VersionsDataSource.#getLatestVersion (cyclomatic 16) packages/data-context/src/sources/VersionsDataSource.ts:127— VersionsDataSource.#getLatestVersion has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
ProjectLifecycleManager.setInitialActiveBrowser (cyclomatic 16) packages/data-context/src/data/ProjectLifecycleManager.ts:320— ProjectLifecycleManager.setInitialActiveBrowser 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.
Keyboard.fireSimulatedEvent (cyclomatic 16) packages/driver/src/cy/keyboard.ts:880— Keyboard.fireSimulatedEvent has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
check.checkOrUncheck (cyclomatic 16) packages/driver/src/cy/commands/actions/check.ts:9— check.checkOrUncheck has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (checkOrUncheckEl, isNoop, isAcceptableElement, …). 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.
waiting.default::waitString::waitForXhr (cyclomatic 16) packages/driver/src/cy/commands/waiting.ts:116— waiting.default::waitString::waitForXhr 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.
response.onResponse (cyclomatic 16) packages/driver/src/cy/net-stubbing/events/response.ts:21— response.onResponse has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
state-icon.StateIcon (cyclomatic 16) packages/reporter/src/lib/state-icon.tsx:12— state-icon.StateIcon 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.
fetch.fetch (cyclomatic 16) packages/server/lib/cloud/network/fetch.ts:47— fetch.fetch 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.
Reporter.normalizeTest (cyclomatic 16) packages/server/lib/reporter.ts:626— Reporter.normalizeTest has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
ProjectBase.open (cyclomatic 16) packages/server/lib/project-base.ts:166— ProjectBase.open has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
client-hello.scanClientHello (cyclomatic 16) packages/server/lib/mtls/client-hello.ts:32— client-hello.scanClientHello has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: 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.
run.waitForBrowserToConnect (cyclomatic 16) packages/server/lib/modes/run.ts:492— run.waitForBrowserToConnect has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
validate-changelog.validateChangelog (cyclomatic 16) scripts/semantic-commits/validate-changelog.js:129— validate-changelog.validateChangelog has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SnapshotDoctor._processCurrentScript (cyclomatic 16) tooling/v8-snapshot/src/doctor/snapshot-doctor.ts:453— SnapshotDoctor._processCurrentScript has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: appends each script in e2e webkit packages/driver/cypress/e2e/cypress/script_utils.cy.ts:45— This test starts work it did not wait for (`runScriptsPromise`, still running when the sleep starts) and then orders itself against it with `Promise.delay(1)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Repeated repair: packages/data-context/src/data/ProjectConfigManager.ts packages/data-context/src/data/ProjectConfigManager.ts:208— packages/data-context/src/data/ProjectConfigManager.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ProjectConfigManager.checkDependenciesForComponentTesting at line 208), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: fire after:run when a project is closed in global open mode (#34700)”; “fix: bound the teardown work that waits on another process (#34699)”; “fix: keep the run's exit code when graceful-exit teardown fails (#34686)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 20:35:06 -04:00' --until='2026-10-25 20:35:06 -04:00' --full-history --no-merges -- packages/data-context/src/data/ProjectConfigManager.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TodoComment repeated across 10 files packages/launchpad/cypress/e2e/top-nav-launchpad.cy.ts:544— The identical TodoComment appears in 10 files (28 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 28 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// cy.percySnapshot() // TODO: restore when Percy CSS is fixed. See https://github.com/cypress-io/cypress/issues/23435". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
mouse.create (cognitive 75) packages/driver/src/cy/mouse.ts:59— mouse.create has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 34, if/else 29 (34 pts), loops 2 (5 pts), ternaries 2 (nesting depth added 8). Of this number, 41 points are the body's own statements and 34 belong to 11 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.
validation.isValidClientCertificatesSet (cognitive 63) packages/config/src/validation.ts:367— validation.isValidClientCertificatesSet has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (50 pts), loops 3 (6 pts), boolean chains 4, error handling 1 (3 pts) (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.
request.default (cognitive 60) packages/driver/src/cy/commands/request.ts:77— request.default has cognitive complexity 60 (threshold 15). Drivers by points: if/else 37 (47 pts), boolean chains 12, error handling 1 (nesting depth added 10). Of this number, 43 points are the body's own statements and 17 belong to 3 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.
chai.chai.use() (cognitive 56) packages/driver/src/cy/chai.ts:47— chai.chai.use() has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 13, ternaries 5 (8 pts), error handling 5 (7 pts), match/switch 1 (nesting depth added 13). Most of this is not in the body itself: 3 of the 56 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 403, a function literal at line 334, a function literal at line 108, …). 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.
validation.isValidRetriesConfig (cognitive 55) packages/config/src/validation.ts:178— validation.isValidRetriesConfig has cognitive complexity 55 (threshold 15). Drivers by points: if/else 17 (46 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 34). Of this number, 53 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.
index.default (cognitive 54) packages/driver/src/cy/commands/sessions/index.ts:24— index.default has cognitive complexity 54 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 16, loops 1 (2 pts), error handling 1, ternaries 1 (nesting depth added 9). Of this number, 25 points are the body's own statements and 29 belong to 18 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.
addToCypressConfigPlugin.addToCypressConfigPlugin (cognitive 53) packages/config/src/ast-utils/addToCypressConfigPlugin.ts:22— addToCypressConfigPlugin.addToCypressConfigPlugin has cognitive complexity 53 (threshold 15). Drivers by points: if/else 23 (39 pts), boolean chains 9, loops 3 (5 pts) (nesting depth added 18). Of this number, 52 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.
actionability.verify (cognitive 53) packages/driver/src/cy/actionability.ts:445— actionability.verify has cognitive complexity 53 (threshold 15). Drivers by points: if/else 24 (41 pts), boolean chains 4, error handling 3 (4 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 19). Most of this is not in the body itself: 5 of the 53 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 534, a function literal at line 513, addScrollBehaviorFix, …). 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.
cookies.default (cognitive 51) packages/driver/src/cy/commands/cookies.ts:103— cookies.default has cognitive complexity 51 (threshold 15). Drivers by points: if/else 25, boolean chains 20, ternaries 5, error handling 1. Of this number, 27 points are the body's own statements and 24 belong to 15 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
inspect.create.formatValue (cognitive 47) REDACTED:73— inspect.create.formatValue has cognitive complexity 47 (threshold 15). Drivers by points: if/else 26 (34 pts), boolean chains 10, error handling 1 (2 pts), ternaries 1 (nesting depth added 9). 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.
keyboard.validateTyping (cognitive 45) packages/driver/src/cy/keyboard.ts:387— keyboard.validateTyping has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (32 pts), boolean chains 13 (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.
querying.default (cognitive 45) REDACTED:154— querying.default has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (25 pts), boolean chains 15, match/switch 2, ternaries 2, error handling 1 (nesting depth added 4). None of this is in the body itself: all 45 points belong to 10 function literals inside it that branch (lines 183, 235, 313, …). 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.
scroll.default (cognitive 44) packages/driver/src/cy/commands/actions/scroll.ts:50— scroll.default has cognitive complexity 44 (threshold 15). Drivers by points: if/else 30 (32 pts), boolean chains 8, error handling 3, match/switch 1 (nesting depth added 2). Of this number, 30 points are the body's own statements and 14 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
connectors.default (cognitive 44) packages/driver/src/cy/commands/connectors.ts:45— connectors.default has cognitive complexity 44 (threshold 15). Drivers by points: if/else 24 (27 pts), boolean chains 14, ternaries 2, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 44 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 218, a function literal at line 146, a function literal at line 182, …). 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.
client-certificates.loadClientCertificateConfig (cognitive 44) packages/network/lib/client-certificates.ts:207— client-certificates.loadClientCertificateConfig has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (27 pts), error handling 4 (11 pts), boolean chains 6 (nesting depth added 23). Most of this is not in the body itself: 2 of the 44 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 246, 218, 224). 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.
spawn.createSpawnFunction (cognitive 43) cli/lib/exec/spawn.ts:60— spawn.createSpawnFunction has cognitive complexity 43 (threshold 15). Drivers by points: if/else 28 (38 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 11). None of this is in the body itself: all 43 points belong to 6 function literals inside it that branch (lines 66, 152, 209, …). 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.
SocketBase.startListening (cognitive 41) packages/server/lib/socket-base.ts:142— SocketBase.startListening has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (24 pts), error handling 5 (7 pts), boolean chains 6, ternaries 2 (3 pts), match/switch 1 (nesting depth added 8). None of this is in the body itself: all 41 points belong to 22 function literals inside it that branch (lines 620, 513, 596, …). 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.
CdpFetchTransport.interceptRequest (cognitive 41) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:462— CdpFetchTransport.interceptRequest has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 6 (10 pts), boolean chains 4, error handling 3 (4 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.
selection._moveSelectionTo (cognitive 40) packages/driver/src/dom/selection.ts:536— selection._moveSelectionTo has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (32 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 22). 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.
InterceptedRequest.handleSubscriptions (cognitive 39) packages/net-stubbing/lib/server/intercepted-request.ts:121— InterceptedRequest.handleSubscriptions has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (nesting depth added 21). Of this number, 22 points are the body's own statements and 17 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.
jquery.scrollto.scrollTo (cognitive 38) packages/driver/src/config/jquery.scrollto.ts:36— jquery.scrollto.scrollTo has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 13, ternaries 2, match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 38 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 106, 64, 159). 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.
parse-changelog.parseChangelog (cognitive 38) scripts/semantic-commits/parse-changelog.js:6— parse-changelog.parseChangelog has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (33 pts), boolean chains 4, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
run_require_async_child.run (cognitive 37) packages/server/lib/plugins/child/run_require_async_child.ts:24— run_require_async_child.run has cognitive complexity 37 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 9, error handling 1, ternaries 1 (nesting depth added 7). Most of this is not in the body itself: 1 of the 37 points is its own statement and the rest belongs to 9 function items inside it that branch (a function literal at line 112, a function literal at line 128, getValidDevServer, …). 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.
visibility.getReasonIsHidden (cognitive 36) packages/driver/src/dom/visibility.ts:527— visibility.getReasonIsHidden has cognitive complexity 36 (threshold 15). Drivers by points: if/else 23 (30 pts), boolean chains 6 (nesting depth added 7). 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.
transform.elIsBackface (cognitive 35) packages/driver/src/dom/transform.ts:110— transform.elIsBackface has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (30 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 20). 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.
inspect.create.formatProperty (cognitive 35) REDACTED:335— inspect.create.formatProperty has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 1 (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.
$Cypress.action (cognitive 35) packages/driver/src/cypress.ts:484— $Cypress.action has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (34 pts), match/switch 1 (nesting depth added 17). 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.
EventManager._addListeners (cognitive 34) packages/app/src/runner/event-manager.ts:566— EventManager._addListeners has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 8, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 5 of the 34 points are its own statements and the rest belongs to 12 function items inside it that branch (handleBeforeScreenshot, a function literal at line 682, a function literal at line 667, …). 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.
sourcemap-support.CallSiteToString (cognitive 34) packages/packherd-require/src/sourcemap-support.ts:366— sourcemap-support.CallSiteToString has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 6 (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.
keyboard.shouldUpdateValue (cognitive 33) packages/driver/src/cy/keyboard.ts:313— keyboard.shouldUpdateValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 9 (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.
CriClient.send (cognitive 33) packages/server/lib/browsers/cdp-protocol/cri-client.ts:564— CriClient.send has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 12). Of this number, 27 points are the body's own statements and 6 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.
run.waitForTestsToFinishRunning (cognitive 33) packages/server/lib/modes/run.ts:631— run.waitForTestsToFinishRunning has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 11, error handling 3 (7 pts) (nesting depth added 6). 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.
plugin.plugin (cognitive 32) npm/grep/src/plugin.ts:19— plugin.plugin has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 9, ternaries 4 (9 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.
CdpFetchTransport.resolveResponse (cognitive 32) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:738— CdpFetchTransport.resolveResponse has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 4, ternaries 3, error handling 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.
run.processRunOptions (cognitive 31) cli/lib/exec/run.ts:38— run.processRunOptions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 29 (30 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AutIframe.highlightEl (cognitive 31) packages/app/src/runner/aut-iframe.ts:331— AutIframe.highlightEl has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 13). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 3 function items inside it that branch (processOffsetBatch, a function literal at line 368, a function literal at line 460). 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.
select.default (cognitive 31) packages/driver/src/cy/commands/actions/select.ts:18— select.default has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 12 (nesting depth added 2). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (getOptions, a function literal at line 120, a function literal at line 182, …). 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.
command.Command (cognitive 31) packages/reporter/src/commands/command.tsx:401— command.Command has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 17, if/else 9 (10 pts), loops 1 (2 pts), error handling 1, ternaries 1 (nesting depth added 2). Of this number, 21 points are the body's own statements and 10 belong to 5 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.
args.toObject (cognitive 31) packages/server/lib/util/args.ts:342— args.toObject has cognitive complexity 31 (threshold 15). Drivers by points: if/else 19 (23 pts), boolean chains 6, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
BrowserCriClient._onAttachToTarget (cognitive 31) packages/server/lib/browsers/browser-cri-client.ts:461— BrowserCriClient._onAttachToTarget has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (16 pts), error handling 7 (8 pts), boolean chains 7 (nesting depth added 4). Of this number, 28 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
index.preprocessor (cognitive 30) npm/webpack-preprocessor/index.ts:228— index.preprocessor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 7, ternaries 3, error handling 1 (nesting depth added 2). None of this is in the body itself: all 30 points belong to 8 function literals inside it that branch (lines 242, 286, 387, …). 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.
selection._moveCursorUpOrDown (cognitive 30) packages/driver/src/dom/selection.ts:333— selection._moveCursorUpOrDown has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 2 (5 pts), boolean chains 3 (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.
Keyboard.simulatedKeydown (cognitive 30) packages/driver/src/cy/keyboard.ts:1149— Keyboard.simulatedKeydown has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 6 (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.
route-matching.doesRouteMatch (cognitive 30) packages/network-interception/lib/core/route-matching.ts:19— route-matching.doesRouteMatch has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 7, loops 3 (nesting depth added 11). Of this number, 27 points are the body's own statements and 3 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.
customRequire (cognitive 30) tooling/v8-snapshot/src/blueprint/custom-require.js:33— customRequire has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 8, ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
actionability.ensureElIsNotCovered (cognitive 29) packages/driver/src/cy/actionability.ts:199— actionability.ensureElIsNotCovered has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (20 pts), error handling 3 (5 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 14). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (ensureDescendentsAndScroll::scrollContainers::possiblyScrollMultipleTimes, ensureDescendentsAndScroll, ensureDescendentsAndScroll::scrollContainerPastElement, …). 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.
focused.create (cognitive 29) packages/driver/src/cy/focused.ts:53— focused.create has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 6 (nesting depth added 6). Of this number, 28 points are the body's own statements and 1 belongs 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.
routes.createCommonRoutes (cognitive 29) packages/server/lib/routes.ts:48— routes.createCommonRoutes has cognitive complexity 29 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 6, error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 7 of the 29 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 98, a function literal at line 362, a function literal at line 246, …). 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.
firefox.open (cognitive 29) packages/server/lib/browsers/firefox.ts:466— firefox.open has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 5 (7 pts), boolean chains 6, error handling 2 (3 pts) (nesting depth added 5). Of this number, 28 points are the body's own statements and 1 belongs to 2 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.
selection._moveCursorToLineStartOrEnd (cognitive 28) packages/driver/src/dom/selection.ts:427— selection._moveCursorToLineStartOrEnd has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (18 pts), ternaries 2 (7 pts), boolean chains 3 (nesting depth added 16). 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.
createProxyModule (cognitive 28) npm/vite-plugin-cypress-esm/client/moduleCache.js:7— createProxyModule has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 4 (nesting depth added 6). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 36, get, target, …). 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.
EventManager.addGlobalListeners (cognitive 27) packages/app/src/runner/event-manager.ts:90— EventManager.addGlobalListeners has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22, boolean chains 2, ternaries 2, match/switch 1. Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 182, a function literal at line 131, a function literal at line 154, …). 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.
selectFile.default (cognitive 27) packages/driver/src/cy/commands/actions/selectFile.ts:133— selectFile.default has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19 (22 pts), boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 235, getEventTargetFromSubject, handleAlias, …). 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.
files.default (cognitive 27) packages/driver/src/cy/commands/files.ts:18— files.default has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 9, ternaries 3 (4 pts) (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 8 function literals inside it that branch (lines 19, 227, 121, …). 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.
before-request.onBeforeRequest (cognitive 27) packages/driver/src/cy/net-stubbing/events/before-request.ts:48— before-request.onBeforeRequest has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23, boolean chains 2, error handling 1, loops 1. Of this number, 16 points are the body's own statements and 11 belong to 6 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
focus.default (cognitive 26) packages/driver/src/cy/commands/actions/focus.ts:25— focus.default has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 8 (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.
type.default::type::type (cognitive 26) packages/driver/src/cy/commands/actions/type.ts:177— type.default::type::type has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 9 (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.
add-command.validateRouteMatcherOptions (cognitive 26) packages/driver/src/cy/net-stubbing/add-command.ts:112— add-command.validateRouteMatcherOptions has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 7, loops 4 (5 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.
fetch.fetch (cognitive 26) packages/server/lib/cloud/network/fetch.ts:47— fetch.fetch has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 3 (5 pts), boolean chains 4, error handling 2, match/switch 1 (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.
(anonymous) (cognitive 26) packages/server/lib/privileged-commands/privileged-channel.js:1— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12, boolean chains 9, error handling 2, loops 2, match/switch 1. Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 13 function items inside it that branch (onCommandInvocation, stackIsFromSpecFrame, hasCallbackInsideEval, …). 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.
install.start (cognitive 25) cli/lib/tasks/install.ts:128— install.start has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 5, ternaries 3 (4 pts), error handling 1 (nesting depth added 2). Of this number, 16 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
console-props.onOneRow (cognitive 25) cli/lib/tap/render/console-props.ts:64— console-props.onOneRow has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 8, loops 2 (4 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.
VersionsDataSource.#getLatestVersion (cognitive 25) packages/data-context/src/sources/VersionsDataSource.ts:127— VersionsDataSource.#getLatestVersion has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (21 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 8). Of this number, 22 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.
ProjectActions.runSpec (cognitive 25) packages/data-context/src/actions/ProjectActions.ts:504— ProjectActions.runSpec has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (19 pts), ternaries 2 (4 pts), error handling 1, loops 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 3 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.
upload_artifacts.uploadArtifacts (cognitive 25) packages/server/lib/cloud/artifacts/upload_artifacts.ts:153— upload_artifacts.uploadArtifacts has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 6, error handling 3 (4 pts) (nesting depth added 3). 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: 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.
snapshot-require.snapshotRequire (cognitive 25) packages/v8-snapshot-require/src/snapshot-require.ts:172— snapshot-require.snapshotRequire has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 4 (8 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.addTypeScriptConfig (cognitive 24) REDACTED:80— index.addTypeScriptConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 4 (6 pts), boolean chains 5, 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.
setup.setup (cognitive 23) npm/puppeteer/src/plugin/setup.ts:35— setup.setup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14, error handling 4 (5 pts), boolean chains 3, ternaries 1 (nesting depth added 1). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
asserting.default (cognitive 23) packages/driver/src/cy/commands/asserting.ts:33— asserting.default has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 1 (3 pts), ternaries 2 (nesting depth added 6). None of this is in the body itself: all 23 points belong to 6 function items inside it that branch (shouldFn::applyChainer, shouldFn, a function literal at line 183, …). 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.
index.default (cognitive 23) packages/driver/src/cy/commands/origin/index.ts:32— index.default has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 3, ternaries 2, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 222, 179, 79, …). 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.
querying.getAlias (cognitive 23) REDACTED:20— querying.getAlias has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8, ternaries 2 (4 pts), error handling 1 (nesting depth added 4). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
window.default (cognitive 23) packages/driver/src/cy/commands/window.ts:50— window.default has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 9 belong to 6 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.
service-worker-injector.injectIntoServiceWorker (cognitive 23) packages/proxy/lib/http/util/service-worker-injector.ts:55— service-worker-injector.injectIntoServiceWorker has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, ternaries 2, error handling 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 11 function items inside it that branch (__cypressInjectIntoServiceWorker, a function literal at line 115, __cypressInjectIntoServiceWorker::sendHasFetchEventHandlers, …). 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.
ProjectLifecycleManager.createConfigManager (cognitive 22) packages/data-context/src/data/ProjectLifecycleManager.ts:204— ProjectLifecycleManager.createConfigManager has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 22 points belong to 2 function literals inside it that branch (lines 219, 249). 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.
add-command.addCommand (cognitive 22) packages/driver/src/cy/net-stubbing/add-command.ts:172— add-command.addCommand has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 3 (nesting depth added 3). None of this is in the body itself: all 22 points belong to 4 function items inside it that branch (addRoute, intercept::getMatcherOptions, intercept::checkExtraArguments, …). 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.
set-injection-level.setInjectionLevel (cognitive 22) packages/proxy/lib/adapters/set-injection-level.ts:20— set-injection-level.setInjectionLevel has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6 (nesting depth added 4). Of this number, 16 points are the body's own statements and 6 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.
determine-deferred.determineDeferred (cognitive 22) tooling/v8-snapshot/src/doctor/determine-deferred.ts:52— determine-deferred.determineDeferred has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 7. Of this number, 16 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
waiting.default::waitString::waitForXhr (cognitive 21) packages/driver/src/cy/commands/waiting.ts:116— waiting.default::waitString::waitForXhr has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (waiting.default) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
static-response-utils.validateStaticResponse (cognitive 21) packages/driver/src/cy/net-stubbing/static-response-utils.ts:19— static-response-utils.validateStaticResponse has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 13, 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.
PackherdModuleLoader.tryLoad (cognitive 21) packages/packherd-require/src/loader.ts:535— PackherdModuleLoader.tryLoad has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 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.
Reporter.normalizeTest (cognitive 21) packages/server/lib/reporter.ts:626— Reporter.normalizeTest has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (14 pts), boolean chains 5, if/else 2 (nesting depth added 6). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 655). 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.
run.ready (cognitive 21) packages/server/lib/modes/run.ts:1111— run.ready has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 4). Of this number, 17 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body 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.
click.default (cognitive 20) packages/driver/src/cy/commands/actions/click.ts:51— click.default has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 10. None of this is in the body itself: all 20 points belong to 6 function items inside it that branch (mouseAction::flagModifiers, mouseAction::perform, mouseAction, …). 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.
response.onResponse (cognitive 20) packages/driver/src/cy/net-stubbing/events/response.ts:21— response.onResponse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServiceWorkerManager.processBrowserPreRequest (cognitive 20) packages/proxy/lib/http/util/service-worker-manager.ts:197— ServiceWorkerManager.processBrowserPreRequest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, error handling 1 (3 pts) (nesting depth added 5). Of this number, 12 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.
async_retry.asyncRetry (cognitive 20) packages/server/lib/util/async_retry.ts:8— async_retry.asyncRetry has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 12). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 12). 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.
ProjectBase.startWebsockets (cognitive 20) packages/server/lib/project-base.ts:381— ProjectBase.startWebsockets has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). None of this is in the body itself: all 20 points belong to 4 function items inside it that branch (a function literal at line 481, a function literal at line 634, destroyStudio, …). 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.
FilterTaggedContent.processLine (cognitive 20) packages/stderr-filtering/lib/FilterTaggedContent.ts:109— FilterTaggedContent.processLine has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 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.
packages.copyAllToDist (cognitive 20) scripts/binary/util/packages.ts:47— packages.copyAllToDist has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (4 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (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.
mount.setupComponent (cognitive 19) npm/angular/src/mount.ts:356— mount.setupComponent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 8). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 391, 368). 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.
ProjectConfigManager.checkDependenciesForComponentTesting (cognitive 19) packages/data-context/src/data/ProjectConfigManager.ts:208— ProjectConfigManager.checkDependenciesForComponentTesting has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 4 (7 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 3 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.
Keyboard.type (cognitive 19) packages/driver/src/cy/keyboard.ts:715— Keyboard.type has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 773, 805, 856, …). 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.
keyboard.getKeyDetails (cognitive 19) packages/driver/src/cy/keyboard.ts:204— keyboard.getKeyDetails has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 205, 257). 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.
navigation.default::visit (cognitive 19) packages/driver/src/cy/commands/navigation.ts:976— navigation.default::visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, 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. This shape REPEATS in the file: one other method here (navigation.default) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
navigation.default (cognitive 19) packages/driver/src/cy/commands/navigation.ts:675— navigation.default has cognitive complexity 19 (threshold 15). Drivers by points: if/else 46 (59 pts), boolean chains 12, error handling 4 (6 pts), ternaries 3 (5 pts) (nesting depth added 17). 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. This shape REPEATS in the file: one other method here (navigation.default::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
CdpAutomation.onRequest (cognitive 19) packages/server/lib/browsers/cdp-protocol/cdp_automation.ts:506— CdpAutomation.onRequest has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (5 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 10). 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.
record.createRun (cognitive 19) packages/server/lib/modes/record.ts:236— record.createRun has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 4 (6 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 350, 303, 308). 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.
Telemetry.startSpan (cognitive 19) packages/telemetry/src/telemetry/index.ts:144— Telemetry.startSpan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8 (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.
process-args-from-file.processArgsFromFile (cognitive 19) tooling/electron-mksnapshot/src/process-args-from-file.ts:7— process-args-from-file.processArgsFromFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1, ternaries 1 (nesting depth added 8). Of this number, 15 points are the body's own statements and 4 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.
verify.runSmokeTest (cognitive 18) cli/lib/tasks/verify.ts:54— verify.runSmokeTest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, error handling 2 (nesting depth added 4). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function items inside it that branch (spawn, userFriendlySpawn, spawnInXvfb). 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.
register.register (cognitive 18) npm/grep/src/register.ts:15— register.register has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 11, if/else 7. 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.
visibility.isStrictlyHidden (cognitive 18) packages/driver/src/dom/visibility.ts:57— visibility.isStrictlyHidden has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 1 (3 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.
assertions.create.verifyUpcomingAssertions (cognitive 18) packages/driver/src/cy/assertions.ts:289— assertions.create.verifyUpcomingAssertions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 3 (4 pts), boolean chains 3, match/switch 1 (nesting depth added 2). 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 (onFailFn, ensureExistence, determineEl, …). 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.
navigation.stabilityChanged (cognitive 18) packages/driver/src/cy/commands/navigation.ts:179— navigation.stabilityChanged has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, error handling 3, match/switch 1. Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 321, onPageLoadErr, getRedirectionCount, …). 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.
traversals.default::getEl (cognitive 18) packages/driver/src/cy/commands/traversals.ts:21— traversals.default::getEl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 2 (4 pts) (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.
log.preprocessDomElement (cognitive 18) packages/driver/src/util/serialization/log.ts:25— log.preprocessDomElement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 1 (3 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 9). None of this is in the body itself: all 18 points belong to 2 function literals inside it that branch (lines 34, 77). 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.
state-icon.StateIcon (cognitive 18) packages/reporter/src/lib/state-icon.tsx:12— state-icon.StateIcon has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 6, if/else 5 (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.
detect.detectLanguage (cognitive 18) packages/scaffold-config/src/detect.ts:127— detect.detectLanguage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, error handling 2, loops 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
verify_bundle_on_disk.verifyBundleOnDisk (cognitive 18) packages/server/lib/cloud/bundles/verify_bundle_on_disk.ts:25— verify_bundle_on_disk.verifyBundleOnDisk has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 4 (5 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.
ci_provider._providerCommitParams (cognitive 18) packages/server/lib/util/ci_provider.ts:554— ci_provider._providerCommitParams has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 18. 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.
makeWebpackConfig.makeWebpackConfig (cognitive 17) npm/webpack-dev-server/src/makeWebpackConfig.ts:79— makeWebpackConfig.makeWebpackConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 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.
utils.mergeDefaults (cognitive 17) packages/config/src/project/utils.ts:406— utils.mergeDefaults has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4 (nesting depth added 2). Of this number, 11 points are the body's own statements and 6 belong to 2 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.
GitDataSource.#loadBulkGitInfo (cognitive 17) packages/data-context/src/sources/GitDataSource.ts:267— GitDataSource.#loadBulkGitInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 4). 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.
ProjectLifecycleManager.setInitialActiveBrowser (cognitive 17) packages/data-context/src/data/ProjectLifecycleManager.ts:320— ProjectLifecycleManager.setInitialActiveBrowser has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7 (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.
aliases.create (cognitive 17) packages/driver/src/cy/aliases.ts:21— aliases.create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
waiting.default (cognitive 17) packages/driver/src/cy/commands/waiting.ts:43— waiting.default has cognitive complexity 17 (threshold 15). Drivers by points: if/else 31 (41 pts), boolean chains 12, ternaries 4 (7 pts), error handling 3 (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. This shape REPEATS in the file: one other method here (waiting.default::waitString::waitForXhr) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both 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.
errTemplate.prepMessage (cognitive 17) packages/errors/src/errTemplate.ts:296— errTemplate.prepMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), 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.
encryption.maybeDecryptErrorResponse (cognitive 17) packages/server/lib/cloud/api/axios_middleware/encryption.ts:54— encryption.maybeDecryptErrorResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenProject.launch (cognitive 17) packages/server/lib/open_project.ts:69— OpenProject.launch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, ternaries 2 (nesting depth added 2). Of this number, 13 points are the body's own statements and 4 belong to 4 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.
run.waitForBrowserToConnect (cognitive 17) packages/server/lib/modes/run.ts:492— run.waitForBrowserToConnect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 4). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (wait::retryOnError, a function literal at line 588, wait). 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.
validate-changelog.validateChangelog (cognitive 17) scripts/semantic-commits/validate-changelog.js:129— validate-changelog.validateChangelog has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3 (nesting depth added 2). Of this number, 11 points are the body's own statements and 6 belong to 3 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.
npm-release.injectVersions (cognitive 17) scripts/npm-release.js:110— npm-release.injectVersions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 2 (4 pts), boolean chains 2 (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.
create-snapshot-script.makePackherdCreateBundle (cognitive 17) REDACTED:252— create-snapshot-script.makePackherdCreateBundle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 253). 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.
SnapshotDoctor._processCurrentScript (cognitive 17) tooling/v8-snapshot/src/doctor/snapshot-doctor.ts:453— SnapshotDoctor._processCurrentScript has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 4 (7 pts), loops 2 (nesting depth added 8). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 509). 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.
pin.pinCommand (cognitive 16) packages/app/src/tap/commands/pin.ts:103— pin.pinCommand has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
validation.isValidExperimentalRetryOptionsConfig (cognitive 16) packages/config/src/validation.ts:121— validation.isValidExperimentalRetryOptionsConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodegenActions.findAllWithLink (cognitive 16) packages/data-context/src/actions/CodegenActions.ts:201— CodegenActions.findAllWithLink has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 205, 221, 243, …). 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.
check.checkOrUncheck::checkOrUncheckEl (cognitive 16) packages/driver/src/cy/commands/actions/check.ts:59— check.checkOrUncheck::checkOrUncheckEl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
runnable-popover-options.RunnablePopoverOptions (cognitive 16) packages/reporter/src/runnables/runnable-popover-options.tsx:21— runnable-popover-options.RunnablePopoverOptions has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (getSuiteIdForNewTest, togglePopover, a function literal at line 103, …). 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.
Request.sendPromise (cognitive 16) packages/server/lib/request.ts:706— Request.sendPromise has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 2). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
video_capture.start (cognitive 16) packages/server/lib/video_capture.ts:122— video_capture.start has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 1 (nesting depth added 2). None of this is in the body itself: all 16 points belong to 4 function items inside it that branch (writeVideoFrame, endVideoCapture, a function literal at line 242, …). 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.
audit-ci-job-filters.auditDependencies (cognitive 16) scripts/audit-ci-job-filters.js:132— audit-ci-job-filters.auditDependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 5). Of this number, 13 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.
Cross-context type TapExecResult (cypress-sessions → cli) cli/lib/tap/tap-connection.ts:61— TapExecResult (context cypress-sessions) is exposed in cli's public surface via tap-connection.validateExecResult — couples the contexts.
Cross-context type TestState (types → app) packages/app/src/store/studio-store.ts:19— TestState (context types) is exposed in app's public surface via CommandLog.state — couples the contexts.
Cross-context type Instrument (types → app) packages/app/src/store/studio-store.ts:24— Instrument (context types) is exposed in app's public surface via CommandLog.instrument — couples the contexts.
Cross-context type BrowserStatus (cypress-sessions → data-context) packages/data-context/src/actions/AppActions.ts:26— BrowserStatus (context cypress-sessions) is exposed in data-context's public surface via AppActions.setBrowserStatus — couples the contexts.
Cross-context type RelevantRunLocationEnum (cypress-sessions → data-context) packages/data-context/src/sources/RelevantRunsDataSource.ts:278— RelevantRunLocationEnum (context cypress-sessions) is exposed in data-context's public surface via RelevantRunsDataSource.pollForRuns — couples the contexts.
Cross-context type RemoteFetchableStatus (cypress-sessions → data-context) packages/data-context/graphql/schemaTypes/interfaceTypes/gql-RemoteFetchable.ts:7— RemoteFetchableStatus (context cypress-sessions) is exposed in data-context's public surface via RemoteFetchableShape.fetchingStatus — couples the contexts.
Cross-context type CodeGenType (cypress-sessions → data-context) packages/data-context/src/actions/CodegenActions.ts:86— CodeGenType (context cypress-sessions) is exposed in data-context's public surface via CodegenActions.codeGenSpec — couples the contexts.
Cross-context type AssertionArgs (app → driver) packages/driver/src/cypress/assertions/assert.ts:55— AssertionArgs (context app) is exposed in driver's public surface via assert.assert — couples the contexts.
Cross-context type Instrument (types → reporter) packages/reporter/src/instruments/instrument-model.ts:28— Instrument (context types) is exposed in reporter's public surface via InstrumentProps.instrument — couples the contexts.
Cross-context type ProtocolCaptureMethod (types → server) packages/server/lib/cloud/protocol.ts:318— ProtocolCaptureMethod (context types) is exposed in server's public surface via ProtocolManager.addFatalError — couples the contexts.
Low cohesion: Command (LCOM4 4) packages/reporter/src/commands/command-model.ts:46— Command'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.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 899 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
Duplication concentrated across 12 sibling directories (12 clone groups) packages/agent-info/vitest.config.ts:3— 12 duplicated blocks under packages/ have copies in at least two of the sibling directories agent-info, app, cypress-sessions, driver, frontend-shared, launchpad (+6 more sibling(s) not listed) — 6 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 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 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 12 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.
Duplication concentrated across 5 sibling directories (8 clone groups) REDACTED:10— 8 duplicated blocks under the repository root have copies in at least two of the sibling directories cli, npm, packages, scripts, tooling — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (6 clone groups) packages/app/src/debug/DebugRunNavigation.vue:229— 6 duplicated blocks under packages/app/src/ have copies in at least two of the sibling directories composables, debug, prompt, runner, runs, studio — 4 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (62 identical lines × 2 files) packages/app/src/prompt/PromptGetCodeModal.vue:24— packages/app/src/prompt/PromptGetCodeModal.vue:24 · packages/app/src/prompt/PromptMoreInfoNeededModal.vue:24 — these 2 files are line-for-line copies of one another — 62 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 (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) REDACTED:10— REDACTED:10 · REDACTED:11 — the two spans are one implementation copied and then locally edited — 373 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 (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) cli/lib/exec/open.ts:32— cli/lib/exec/open.ts:32 · cli/lib/exec/run.ts:61 — the two spans are one implementation copied and then locally edited — 282 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 (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) packages/server/lib/cloud/api/cy-prompt/report_cy_prompt_error.ts:20— packages/server/lib/cloud/api/cy-prompt/report_cy_prompt_error.ts:20 · packages/server/lib/cloud/api/studio/report_studio_error.ts:24 — the two spans are one implementation copied and then locally edited — 226 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 (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) tooling/v8-snapshot/src/generator/snapshot-generator.ts:276— tooling/v8-snapshot/src/generator/snapshot-generator.ts:276 · tooling/v8-snapshot/src/generator/snapshot-generator.ts:389 — the two spans are one implementation copied and then locally edited — 193 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) packages/types/src/cy-prompt/cy-prompt-server-types.ts:42— packages/types/src/cy-prompt/cy-prompt-server-types.ts:42 · packages/types/src/studio/studio-server-types.ts:52 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (36 lines × 2 locations) packages/telemetry/src/span-exporters/ipc-span-exporter.ts:13— packages/telemetry/src/span-exporters/ipc-span-exporter.ts:13 · packages/telemetry/src/span-exporters/websocket-span-exporter.ts:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (34 matched lines × 2 locations) · ×1
Duplicated block with local edits (34 matched lines × 2 locations) packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:288— packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:288 · packages/server/lib/cloud/studio/StudioLifecycleManager.ts:365 — the two spans are one implementation copied and then locally edited — 206 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 (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) packages/driver/src/cy/commands/actions/scroll.ts:96— packages/driver/src/cy/commands/actions/scroll.ts:96 · packages/driver/src/cy/commands/actions/scroll.ts:265 — the two spans are one implementation copied and then locally edited — 221 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (28 lines × 2 locations) packages/v8-snapshot-require/src/types.ts:6— packages/v8-snapshot-require/src/types.ts:6 · tooling/v8-snapshot/src/types.ts:3 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (22 lines × 2 locations) cli/lib/cli.ts:361— cli/lib/cli.ts:361 · cli/lib/cli.ts:402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 3 locations) scripts/unit/semantic-commits/validate-changelog-spec.js:383— scripts/unit/semantic-commits/validate-changelog-spec.js:383 · scripts/unit/semantic-commits/validate-changelog-spec.js:414 · scripts/unit/semantic-commits/validate-changelog-spec.js:441 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) packages/server/lib/browsers/chrome.ts:616— packages/server/lib/browsers/chrome.ts:616 · packages/server/lib/browsers/electron.ts:546 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (15 lines × 4 locations) packages/errors/src/errors.ts:1562— packages/errors/src/errors.ts:1562 · packages/errors/src/errors.ts:1578 · packages/errors/src/errors.ts:1595 · packages/errors/src/errors.ts:1611 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Complex function action (cyclomatic 85, cognitive 35) packages/driver/src/cypress.ts:484— action has cyclomatic complexity 85 and cognitive complexity 35; 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.
Complex function formatValue (cyclomatic 42, cognitive 51) REDACTED:73— formatValue has cyclomatic complexity 42 and cognitive complexity 51; 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.
Complex function validateTyping (cyclomatic 38, cognitive 45) packages/driver/src/cy/keyboard.ts:387— validateTyping has cyclomatic complexity 38 and cognitive complexity 45; 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.
Complex function (anonymous) (cyclomatic 37, cognitive 47) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:462— (anonymous) has cyclomatic complexity 37 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function request (cyclomatic 37, cognitive 44) packages/driver/src/cy/commands/request.ts:82— request has cyclomatic complexity 37 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 34, cognitive 48) packages/driver/src/cypress/log.ts:66— (anonymous) has cyclomatic complexity 34 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.
Complex function (anonymous) (cyclomatic 32, cognitive 31) cli/lib/exec/run.ts:38— (anonymous) has cyclomatic complexity 32 and cognitive complexity 31; 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.
Complex function (anonymous) (cyclomatic 32, cognitive 29) system-tests/projects/e2e/static/obstructive_code.js:3— (anonymous) has cyclomatic complexity 32 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getReasonIsHidden (cyclomatic 30, cognitive 37) packages/driver/src/dom/visibility.ts:527— getReasonIsHidden has cyclomatic complexity 30 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function waitForTestsToFinishRunning (cyclomatic 30, cognitive 33) packages/server/lib/modes/run.ts:631— waitForTestsToFinishRunning has cyclomatic complexity 30 and cognitive complexity 33; 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.
Complex function _onAttachToTarget (cyclomatic 29, cognitive 32) packages/server/lib/browsers/browser-cri-client.ts:461— _onAttachToTarget has cyclomatic complexity 29 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 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.
Complex function (anonymous) (cyclomatic 29, cognitive 19) packages/server/lib/browsers/cdp-protocol/cdp_automation.ts:506— (anonymous) has cyclomatic complexity 29 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.
Complex function (anonymous) (cyclomatic 28, cognitive 37) packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:738— (anonymous) has cyclomatic complexity 28 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function plugin (cyclomatic 28, cognitive 32) npm/grep/src/plugin.ts:19— plugin has cyclomatic complexity 28 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 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.
Complex function (anonymous) (cyclomatic 28, cognitive 24) packages/reporter/src/commands/command.tsx:401— (anonymous) has cyclomatic complexity 28 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.
Complex function (anonymous) (cyclomatic 27, cognitive 63) packages/config/src/validation.ts:375— (anonymous) has cyclomatic complexity 27 and cognitive complexity 63; 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.
Complex function maybeHandleRetryOnFailure (cyclomatic 27, cognitive 41) packages/driver/src/cypress/runner.ts:1450— maybeHandleRetryOnFailure has cyclomatic complexity 27 and cognitive complexity 41; 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.
Complex function toObject (cyclomatic 27, cognitive 33) packages/server/lib/util/args.ts:342— toObject has cyclomatic complexity 27 and cognitive complexity 33; 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.
Complex function _providerCommitParams (cyclomatic 27, cognitive 18) packages/server/lib/util/ci_provider.ts:554— _providerCommitParams has cyclomatic complexity 27 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/errors/src/errors.ts · ×1
packages/errors/src/errors.ts: 1431 lines of code packages/errors/src/errors.ts:1— packages/errors/src/errors.ts has 1431 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/server/lib/server-base.ts · ×1
packages/server/lib/server-base.ts: 1240 lines of code packages/server/lib/server-base.ts:1— packages/server/lib/server-base.ts has 1240 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/driver/src/cy/keyboard.ts · ×1
packages/driver/src/cy/keyboard.ts: 1167 lines of code packages/driver/src/cy/keyboard.ts:1— packages/driver/src/cy/keyboard.ts has 1167 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: 1101 lines of code REDACTED:1— REDACTED has 1101 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/server/lib/modes/run.ts · ×1
packages/server/lib/modes/run.ts: 1065 lines of code packages/server/lib/modes/run.ts:1— packages/server/lib/modes/run.ts has 1065 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/packherd-require/src/loader.ts · ×1
packages/packherd-require/src/loader.ts: 975 lines of code packages/packherd-require/src/loader.ts:1— packages/packherd-require/src/loader.ts has 975 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/driver/src/cy/commands/navigation.ts · ×1
packages/driver/src/cy/commands/navigation.ts: 964 lines of code packages/driver/src/cy/commands/navigation.ts:1— packages/driver/src/cy/commands/navigation.ts has 964 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/server/lib/browsers/cdp-protocol/cri-client.ts · ×1
packages/server/lib/browsers/cdp-protocol/cri-client.ts: 912 lines of code packages/server/lib/browsers/cdp-protocol/cri-client.ts:1— packages/server/lib/browsers/cdp-protocol/cri-client.ts has 912 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/server/lib/browsers/browser-cri-client.ts · ×1
packages/server/lib/browsers/browser-cri-client.ts: 911 lines of code packages/server/lib/browsers/browser-cri-client.ts:1— packages/server/lib/browsers/browser-cri-client.ts has 911 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/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts · ×1
packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts: 891 lines of code packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:1— packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts has 891 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· tooling/v8-snapshot/src/blueprint/globals.js · ×1
tooling/v8-snapshot/src/blueprint/globals.js: 874 lines of code tooling/v8-snapshot/src/blueprint/globals.js:1— tooling/v8-snapshot/src/blueprint/globals.js has 874 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/app/src/runner/event-manager.ts · ×1
packages/app/src/runner/event-manager.ts: 873 lines of code packages/app/src/runner/event-manager.ts:1— packages/app/src/runner/event-manager.ts has 873 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/driver/src/cypress.ts · ×1
packages/driver/src/cypress.ts: 803 lines of code packages/driver/src/cypress.ts:1— packages/driver/src/cypress.ts has 803 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/server/lib/util/ci_provider.ts · ×1
packages/server/lib/util/ci_provider.ts: 800 lines of code packages/server/lib/util/ci_provider.ts:1— packages/server/lib/util/ci_provider.ts has 800 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/config/src/options.ts · ×1
packages/config/src/options.ts: 787 lines of code packages/config/src/options.ts:1— packages/config/src/options.ts has 787 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/server/lib/modes/record.ts · ×1
packages/server/lib/modes/record.ts: 770 lines of code packages/server/lib/modes/record.ts:1— packages/server/lib/modes/record.ts has 770 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/server/lib/browsers/chrome.ts · ×1
packages/server/lib/browsers/chrome.ts: 740 lines of code packages/server/lib/browsers/chrome.ts:1— packages/server/lib/browsers/chrome.ts has 740 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/app/src/runner/aut-iframe.ts · ×1
packages/app/src/runner/aut-iframe.ts: 728 lines of code packages/app/src/runner/aut-iframe.ts:1— packages/app/src/runner/aut-iframe.ts has 728 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/data-context/src/data/ProjectLifecycleManager.ts · ×1
packages/data-context/src/data/ProjectLifecycleManager.ts: 719 lines of code packages/data-context/src/data/ProjectLifecycleManager.ts:1— packages/data-context/src/data/ProjectLifecycleManager.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/server/lib/browsers/bidi_automation.ts · ×1
packages/server/lib/browsers/bidi_automation.ts: 707 lines of code packages/server/lib/browsers/bidi_automation.ts:1— packages/server/lib/browsers/bidi_automation.ts has 707 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/server/lib/request.ts · ×1
packages/server/lib/request.ts: 680 lines of code packages/server/lib/request.ts:1— packages/server/lib/request.ts has 680 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/server/lib/reporter.ts · ×1
packages/server/lib/reporter.ts: 675 lines of code packages/server/lib/reporter.ts:1— packages/server/lib/reporter.ts has 675 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· tooling/v8-snapshot/src/doctor/snapshot-doctor.ts · ×1
tooling/v8-snapshot/src/doctor/snapshot-doctor.ts: 675 lines of code tooling/v8-snapshot/src/doctor/snapshot-doctor.ts:1— tooling/v8-snapshot/src/doctor/snapshot-doctor.ts has 675 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/server/lib/socket-base.ts · ×1
packages/server/lib/socket-base.ts: 661 lines of code packages/server/lib/socket-base.ts:1— packages/server/lib/socket-base.ts has 661 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/server/lib/project-base.ts · ×1
packages/server/lib/project-base.ts: 659 lines of code packages/server/lib/project-base.ts:1— packages/server/lib/project-base.ts has 659 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/driver/src/cy/mouse.ts · ×1
packages/driver/src/cy/mouse.ts: 658 lines of code packages/driver/src/cy/mouse.ts:1— packages/driver/src/cy/mouse.ts has 658 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/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts · ×1
packages/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts: 655 lines of code packages/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts:1— packages/data-context/graphql/schemaTypes/objectTypes/gql-Mutation.ts has 655 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/server/lib/browsers/firefox.ts · ×1
packages/server/lib/browsers/firefox.ts: 641 lines of code packages/server/lib/browsers/firefox.ts:1— packages/server/lib/browsers/firefox.ts has 641 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/server/lib/cloud/api/index.ts · ×1
packages/server/lib/cloud/api/index.ts: 610 lines of code packages/server/lib/cloud/api/index.ts:1— packages/server/lib/cloud/api/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· packages/driver/src/cy/commands/cookies.ts · ×1
packages/driver/src/cy/commands/cookies.ts: 590 lines of code packages/driver/src/cy/commands/cookies.ts:1— packages/driver/src/cy/commands/cookies.ts has 590 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/driver/src/dom/selection.ts · ×1
packages/driver/src/dom/selection.ts: 587 lines of code packages/driver/src/dom/selection.ts:1— packages/driver/src/dom/selection.ts has 587 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/data-context/src/data/ProjectConfigManager.ts · ×1
packages/data-context/src/data/ProjectConfigManager.ts: 580 lines of code packages/data-context/src/data/ProjectConfigManager.ts:1— packages/data-context/src/data/ProjectConfigManager.ts has 580 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/server/lib/util/print-run.ts · ×1
packages/server/lib/util/print-run.ts: 575 lines of code packages/server/lib/util/print-run.ts:1— packages/server/lib/util/print-run.ts has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/proxy/lib/http/response-middleware.ts · ×1
packages/proxy/lib/http/response-middleware.ts: 570 lines of code packages/proxy/lib/http/response-middleware.ts:1— packages/proxy/lib/http/response-middleware.ts has 570 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/reporter/src/commands/command.tsx · ×1
packages/reporter/src/commands/command.tsx: 566 lines of code packages/reporter/src/commands/command.tsx:1— packages/reporter/src/commands/command.tsx has 566 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/proxy/lib/http/index.ts · ×1
packages/proxy/lib/http/index.ts: 565 lines of code packages/proxy/lib/http/index.ts:1— packages/proxy/lib/http/index.ts has 565 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/driver/src/cy/commands/actions/type.ts · ×1
packages/driver/src/cy/commands/actions/type.ts: 561 lines of code packages/driver/src/cy/commands/actions/type.ts:1— packages/driver/src/cy/commands/actions/type.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
cli/lib/cli.ts: 550 lines of code cli/lib/cli.ts:1— cli/lib/cli.ts has 550 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/data-context/src/actions/ProjectActions.ts · ×1
packages/data-context/src/actions/ProjectActions.ts: 548 lines of code packages/data-context/src/actions/ProjectActions.ts:1— packages/data-context/src/actions/ProjectActions.ts has 548 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/driver/src/cy/actionability.ts · ×1
packages/driver/src/cy/actionability.ts: 548 lines of code packages/driver/src/cy/actionability.ts:1— packages/driver/src/cy/actionability.ts has 548 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~155 LoC) packages/app/src/layouts/default.vue— no import path from any entry point (516 application, 508 tooling, 3317 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 (~132 LoC) packages/app/src/runs/useProjectRuns.ts— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/app/src/pages/Runs.vue) — 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 (~113 LoC) packages/app/src/pages/Debug.vue— no import path from any entry point (516 application, 508 tooling, 3317 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 (~96 LoC) npm/webpack-dev-server/src/loader.ts— no import path from any entry point (516 application, 508 tooling, 3317 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 (~77 LoC) packages/app/src/runs/useGitTreeRuns.ts— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/app/src/pages/Runs.vue) — 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 (~64 LoC) scripts/github-actions/commit-via-api.mjs— no import path from any entry point (516 application, 508 tooling, 3317 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 (~60 LoC) packages/app/src/pages/Runs.vue— no import path from any entry point (516 application, 508 tooling, 3317 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 (~46 LoC) packages/app/src/navigation/SidebarNavigationContainer.vue— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/app/src/layouts/default.vue) — 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 (~17 LoC) cli/lib/index.mts— no import path from any entry point (516 application, 508 tooling, 3317 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 (~11 LoC) npm/webpack-dev-server/src/aut-runner.ts— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (npm/webpack-dev-server/src/loader.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
Dead file (~10 LoC) packages/app/src/runs/RunsComposable.ts— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/app/src/pages/Runs.vue, packages/app/src/runs/useGitTreeRuns.ts, packages/app/src/runs/useProjectRuns.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
Dead file (~5 LoC) npm/webpack-dev-server/src/browser.ts— no import path from any entry point (516 application, 508 tooling, 3317 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~4 LoC) packages/v8-snapshot-require/src/constants.ts— no import path from any entry point (516 application, 508 tooling, 3317 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 (~1 LoC) npm/puppeteer/support/index.js— no import path from any entry point (516 application, 508 tooling, 3317 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
Unused dependency '@cypress/angular' — Declared in cli/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.
Unused dependency '@cypress/grep' — Declared in cli/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.
Unused dependency '@cypress/svelte' — Declared in cli/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.
Obsolete TLS/SSL protocol version enabled packages/server/lib/request.ts:398— `minVersion: "TLSv1"` explicitly admits a protocol version that is broken (SSL 3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Remove the pin: Node's default minimum is TLS 1.2, so leaving `minVersion`/`secureProtocol` unset is the strongest setting and picks up TLS 1.3 without a code change. Where a floor must be named, use `minVersion: "TLSv1.2"`.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) cli/lib/tasks/unzip.ts:147— `spawn` pipes `stdout` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `sp.stdout`, while `sp.stderr` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stdout (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`sp.stdout.on('data', …)`, or `sp.stdout.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot.
Orphaned file system-tests/__snapshots__/typescript_spec_support_spec.ts.js: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/driver/src/cy/commands/screenshot.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/driver/src/cypress/UsKeyboardLayout.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 npm/webpack-dev-server/src/helpers/nextHandler.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/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue: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 system-tests/__snapshots__/test_isolation_spec.ts.js: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/driver/src/cy/commands/actions/scroll.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/telemetry/src/telemetry/index.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/driver/src/cy/commands/actions/select.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 npm/cypress-schematic/src/schematics/ng-add/index.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/driver/src/cy/commands/actions/click.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/frontend-shared/src/gql-components/HeaderBarContent.vue: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/app/src/navigation/SidebarNavigation.vue: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/driver/src/dom/coordinates.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 npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.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/frontend-shared/src/gql-components/topnav/TopNav.vue: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/driver/src/cy/net-stubbing/events/before-request.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/data-context/src/sources/RelevantRunsDataSource.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/data-context/src/actions/DataEmitterActions.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/data-context/src/sources/RelevantRunSpecsDataSource.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/driver/src/cy/net-stubbing/add-command.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/driver/src/cy/focused.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/errors/src/errTemplate.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/https-proxy/lib/ca.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/app/src/debug/DebugRunNavigation.vue: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.
Mock-dominated test: logs and does not attempt to update pull request title if PR cannot be found scripts/unit/github-actions/update-browser-version-spec.js:417— This test sets up 3 test doubles (for example `sinon.stub`) 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: downloads artifacts scripts/unit/binary/get-published-artifacts-spec.js:17— This test sets up 5 test doubles (for example `sinon.stub`) against 0 real object(s) of its own, and its only verification is 9 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: URLs are not fetched if SHOULD_PERSIST_ARTIFACTS is false scripts/unit/binary/get-published-artifacts-spec.js:39— This test sets up 5 test doubles (for example `sinon.stub`) against 0 real object(s) of its own, and its only verification is 7 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: finds and copies latest build for each platform scripts/unit/binary/move-binaries-spec.js:90— This test sets up 7 test doubles (for example `sinon.stub`) 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: initializes StringDecoder and LineDecoder on first call packages/stderr-filtering/lib/__spec__/FilterPrefixedContent.spec.ts:92— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: handles buffer encoding correctly packages/stderr-filtering/lib/__spec__/FilterPrefixedContent.spec.ts:107— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: reuses existing StringDecoder and LineDecoder instances packages/stderr-filtering/lib/__spec__/FilterPrefixedContent.spec.ts:133— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: passes the line to the next stream packages/stderr-filtering/lib/__spec__/FilterPrefixedContent.spec.ts:146— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: writes the line to the waste stream packages/stderr-filtering/lib/__spec__/FilterPrefixedContent.spec.ts:161— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: handles multi-line tagged content packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:316— 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: handles multiple tagged sections across lines packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:336— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: handles content with tags and surrounding text packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:354— 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: handles partial lines across multiple chunks packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:370— 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: handles mixed tagged and untagged content packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:391— 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: handles an end tag followed by a new start tag on the same line packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:411— 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: handles multiple tagged sections on the same line packages/stderr-filtering/lib/__spec__/FilterTaggedContent.spec.ts:429— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 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: handles multi-line content with mixed empty lines packages/stderr-filtering/lib/__spec__/WriteToDebug.spec.ts:262— 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 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: handles content with trailing newlines packages/stderr-filtering/lib/__spec__/WriteToDebug.spec.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 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: closes the previous socket when a new client is attached packages/socket/test/cdp-socket.spec.ts:5— This test sets up 3 test doubles (for example `vi.fn`) against 1 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: sets Origin-Agent-Cluster response header to false packages/server/test/unit/iframes.spec.ts:22— This test sets up 4 test doubles (for example `vi.spyOn`) 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: reset and clearCredentials delegate to networkProxy packages/server/test/unit/network-runtime.spec.ts:301— This test sets up 3 test doubles (for example `vi.spyOn`) 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: createCdpFetchRuntime routes handleHttpRequest through the Express intercept packages/server/test/unit/network-runtime.spec.ts:357— This test sets up 5 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: createCdpFetchRuntime records the AUT URL when the automation layer reports an AUT navigation commit packages/server/test/unit/network-runtime.spec.ts:449— This test sets up 6 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: createCdpFetchRuntime attachExtraTarget does not surface an unhandled rejection when Network.enable fails packages/server/test/unit/network-runtime.spec.ts:1244— This test sets up 7 test doubles (for example `vi.fn`) against 1 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: focuses browser if runner is connected packages/server/test/unit/open_project.spec.ts:407— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
No direct assertions: should mount system-tests/projects/vue3-webpack-ts-configured/src/mount.cy.ts:10— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: error on mount system-tests/projects/vue3-webpack-ts-configured/src/components/Errors.cy.ts:5— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: sync error system-tests/projects/vue3-webpack-ts-configured/src/components/Errors.cy.ts:15— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: async error system-tests/projects/vue3-webpack-ts-configured/src/components/Errors.cy.ts:22— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: command failure system-tests/projects/vue3-webpack-ts-configured/src/components/Errors.cy.ts:30— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: contains the default slot in its h1 system-tests/projects/vue3-webpack-ts-configured/src/components/HelloWorld.cy.ts:5— No conventional assertion call was detected, and 6 of 7 tests in `system-tests/projects/vue3-webpack-ts-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should require a module without deps system-tests/projects/v8-snapshot/stealthy-require/spec/non-native.js:24— No conventional assertion call was detected, and 5 of 6 tests in `system-tests/projects/v8-snapshot/stealthy-require` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should require a module with sync deps system-tests/projects/v8-snapshot/stealthy-require/spec/non-native.js:35— No conventional assertion call was detected, and 5 of 6 tests in `system-tests/projects/v8-snapshot/stealthy-require` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should require a module while keeping a dependency that was required before system-tests/projects/v8-snapshot/stealthy-require/spec/non-native.js:46— No conventional assertion call was detected, and 5 of 6 tests in `system-tests/projects/v8-snapshot/stealthy-require` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should require a module while keeping a dependency that will be required afterwards system-tests/projects/v8-snapshot/stealthy-require/spec/non-native.js:73— No conventional assertion call was detected, and 5 of 6 tests in `system-tests/projects/v8-snapshot/stealthy-require` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should not pollute require cache with dependencies that should be kept but are never required system-tests/projects/v8-snapshot/stealthy-require/spec/non-native.js:111— No conventional assertion call was detected, and 5 of 6 tests in `system-tests/projects/v8-snapshot/stealthy-require` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: mounts system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:15— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: reacts to state changes system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:20— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: accepts props system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:27— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: accepts context system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:32— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: reactive to writables system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:47— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: should mount system-tests/projects/svelte-webpack-configured/src/mount.cy.ts:110— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: error on mount system-tests/projects/svelte-webpack-configured/src/lib/errors.cy.ts:4— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: sync error system-tests/projects/svelte-webpack-configured/src/lib/errors.cy.ts:8— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: async error system-tests/projects/svelte-webpack-configured/src/lib/errors.cy.ts:13— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: command failure system-tests/projects/svelte-webpack-configured/src/lib/errors.cy.ts:18— No conventional assertion call was detected, and 10 of 16 tests in `system-tests/projects/svelte-webpack-configured` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: visits a basic html page system-tests/projects/studio/cypress/e2e/navigation.cy.js:2— No conventional assertion call was detected, and 9 of 13 tests in `system-tests/projects/studio` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: visits a basic html page system-tests/projects/studio/cypress/e2e/spec-w-foobar.cy.js:12— No conventional assertion call was detected, and 9 of 13 tests in `system-tests/projects/studio` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: visits a basic html page with an invisible wrapper system-tests/projects/studio/cypress/e2e/spec-w-invisible-wrapper.cy.js:2— No conventional assertion call was detected, and 9 of 13 tests in `system-tests/projects/studio` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: visits a basic html page with a modal system-tests/projects/studio/cypress/e2e/spec-w-modal.cy.js:2— No conventional assertion call was detected, and 9 of 13 tests in `system-tests/projects/studio` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
+ 89 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel npm/grep/src/plugin.ts:38— `npm/grep/src/plugin.ts` reports through `console.*` at line 38 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 npm/grep/src/plugin.ts:44— `npm/grep/src/plugin.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel npm/grep/src/plugin.ts:53— `npm/grep/src/plugin.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 npm/grep/src/plugin.ts:59— `npm/grep/src/plugin.ts` reports through `console.*` at line 59 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 npm/grep/src/plugin.ts:65— `npm/grep/src/plugin.ts` reports through `console.*` at line 65 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 npm/grep/src/plugin.ts:86— `npm/grep/src/plugin.ts` reports through `console.*` at line 86 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 npm/grep/src/plugin.ts:108— `npm/grep/src/plugin.ts` reports through `console.*` at line 108 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 npm/grep/src/plugin.ts:109— `npm/grep/src/plugin.ts` reports through `console.*` at line 109 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 npm/grep/src/plugin.ts:136— `npm/grep/src/plugin.ts` reports through `console.*` at line 136 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 npm/grep/src/plugin.ts:137— `npm/grep/src/plugin.ts` reports through `console.*` at line 137 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 npm/grep/src/plugin.ts:154— `npm/grep/src/plugin.ts` reports through `console.*` at line 154 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 npm/grep/src/plugin.ts:155— `npm/grep/src/plugin.ts` reports through `console.*` at line 155 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 npm/grep/src/plugin.ts:156— `npm/grep/src/plugin.ts` reports through `console.*` at line 156 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 npm/grep/src/plugin.ts:157— `npm/grep/src/plugin.ts` reports through `console.*` at line 157 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 npm/vite-plugin-cypress-esm/client/moduleCache.js:179— `npm/vite-plugin-cypress-esm/client/moduleCache.js` reports through `console.*` at line 179 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 npm/vite-plugin-cypress-esm/client/moduleCache.js:200— `npm/vite-plugin-cypress-esm/client/moduleCache.js` reports through `console.*` at line 200 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 packages/app/src/runner/event-manager.ts:288— `packages/app/src/runner/event-manager.ts` reports through `console.*` at line 288 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 packages/app/src/runner/event-manager.ts:315— `packages/app/src/runner/event-manager.ts` reports through `console.*` at line 315 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 packages/app/src/runner/event-manager.ts:480— `packages/app/src/runner/event-manager.ts` reports through `console.*` at line 480 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 packages/app/src/runner/logger.ts:20— `packages/app/src/runner/logger.ts` reports through `console.*` at line 20 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 packages/app/src/runner/logger.ts:24— `packages/app/src/runner/logger.ts` reports through `console.*` at line 24 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 packages/data-context/src/DataContext.ts:320— `packages/data-context/src/DataContext.ts` reports through `console.*` at line 320 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 packages/data-context/graphql/makeGraphQLServer.ts:108— `packages/data-context/graphql/makeGraphQLServer.ts` reports through `console.*` at line 108 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 packages/driver/src/cypress/runner.ts:126— `packages/driver/src/cypress/runner.ts` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel REDACTED:64— `REDACTED` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Disabled test cli/types/tests/cypress-tests.ts:1049— 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 cli/types/tests/cypress-tests.ts:1051— 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 cli/types/tests/cypress-tests.ts:1055— 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 cli/types/tests/cypress-tests.ts:1056— 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 cli/types/tests/cypress-tests.ts:1076— 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 cli/types/tests/cypress-tests.ts:1077— 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 npm/grep/cypress/e2e/omit-and-skip.cy.ts:4— 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 npm/grep/cypress/e2e/skip.cy.ts:6— 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 npm/grep/cypress/e2e/skip.cy.ts:9— 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 npm/grep/test/unit.spec.ts:178— 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 npm/react/cypress/component/advanced/mocking-imports/RemotePizza.cy.tsx:10— 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 npm/vite-plugin-cypress-esm/cypress/component/edgeCases.cy.tsx:67— 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 npm/vue/cypress/component/basic/code-coverage/Calculator.cy.ts:6— 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 npm/vue/cypress/component/basic/code-coverage/unit.cy.ts:5— 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 npm/vue/cypress/component/basic/components/spec.cy.ts:9— 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 npm/vue/cypress/component/basic/list.cy.ts:5— 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 npm/vue/cypress/component/basic/options.cy.ts:10— 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 npm/vue/cypress/component/basic/props/message-list.cy.ts:45— 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 npm/vue/cypress/component/basic/props/message-list.cy.ts:92— 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 npm/vue/cypress/component/basic/reverse.cy.ts:4— 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 npm/vue/cypress/component/basic/spec.cy.ts:4— 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 npm/vue/cypress/component/basic/style-in-spec/todo.cy.ts:6— 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 npm/vue/cypress/component/counter-vuex/counter-vuex.cy.js:8— 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 npm/vue/cypress/component/hello/hello-component.cy.js:12— 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 npm/vue/cypress/component/router-example/router.cy.js:6— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Duplicated predicate packages/server/lib/automation/cookie/converters/bidi.ts:96— `!cookie.hostOnly && isHostOnlyCookie(cookie)` appears character-identically in 3 files — packages/server/lib/automation/cookie/converters/bidi.ts, packages/server/lib/automation/cookie/converters/cdp.ts, packages/server/lib/browsers/bidi_automation.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/driver/src/cy/commands/querying/get_by_role.ts:48— `!hidden && isInaccessible(element, cache)` appears character-identically in 2 files — packages/driver/src/cy/commands/querying/get_by_role.ts, packages/driver/src/dom/accessibility/roles.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/driver/src/cy/commands/actions/select.ts:242— `!options.force && activeElement === null` appears character-identically in 2 files — packages/driver/src/cy/commands/actions/select.ts, packages/driver/src/cy/commands/actions/type.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/driver/src/cy/keyboard.ts:319— `$elements.isInput(el) || $elements.isTextarea(el)` appears character-identically in 2 files — packages/driver/src/cy/keyboard.ts, packages/driver/src/dom/selection.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/data-context/src/actions/EventCollectorActions.ts:54— `(await this.ctx.coreData.machineId) || undefined` appears character-identically in 2 files — packages/data-context/src/actions/EventCollectorActions.ts, packages/data-context/src/sources/VersionsDataSource.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 cli/lib/tasks/download.ts:66— `(platform === 'win32') && (arch === 'arm64')` appears character-identically in 2 files — cli/lib/tasks/download.ts, cli/lib/tasks/install.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/server/hook-require.js:34— `['1', 'true'].includes(process.env.DISABLE_SNAPSHOT_REQUIRE) || typeof getSnapshotResult === 'undefined'` appears character-identically in 2 files — packages/server/hook-require.js, packages/ts/registerDir.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/reporter/src/header/header.tsx:26— `appState?.studioActive && appState.studioSingleTestActive` appears character-identically in 3 files — packages/reporter/src/header/header.tsx, packages/reporter/src/runnables/runnable-header.tsx, packages/reporter/src/runnables/runnable-popover-options.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 packages/app/src/runner/event-manager.ts:401— `config.isTextTerminal || config.experimentalInteractiveRunEvents` appears character-identically in 2 files — packages/app/src/runner/event-manager.ts, packages/server/lib/socket-base.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/server/lib/automation/cookie/converters/bidi.ts:100— `cookie.hostOnly && !isHostOnlyCookie(cookie)` appears character-identically in 2 files — packages/server/lib/automation/cookie/converters/bidi.ts, packages/server/lib/browsers/bidi_automation.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/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts:463— `event.responseErrorReason || typeof event.responseStatusCode === 'number'` appears character-identically in 2 files — packages/server/lib/browsers/cdp-protocol/cdp-fetch-transport.ts, packages/server/lib/browsers/cdp-protocol/interception-escape-detector.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/data-context/graphql/plugins/nexusDeferIfNotLoadedPlugin.ts:78— `info.operation.operation === 'mutation' || info.operation.operation === 'subscription'` appears character-identically in 2 files — packages/data-context/graphql/plugins/nexusDeferIfNotLoadedPlugin.ts, packages/data-context/graphql/plugins/nexusSlowGuardPlugin.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/proxy/lib/adapters/inject-html.ts:46— `mw.config.experimentalModifyObstructiveThirdPartyCode && !mw.remoteStates.isPrimarySuperDomainOrigin(mw.req.proxiedUrl)` appears character-identically in 2 files — packages/proxy/lib/adapters/inject-html.ts, packages/proxy/lib/adapters/remove-security.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/proxy/lib/adapters/inject-html.ts:49— `mw.config.removeSRIAttributes && mw.remoteStates.isPrimarySuperDomainOrigin(mw.req.proxiedUrl)` appears character-identically in 2 files — packages/proxy/lib/adapters/inject-html.ts, packages/proxy/lib/adapters/remove-security.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/driver/src/cy/commands/actions/focus.ts:79— `options.$el.length && options.$el.length > 1` appears character-identically in 3 files — packages/driver/src/cy/commands/actions/focus.ts, packages/driver/src/cy/commands/actions/select.ts, packages/driver/src/cy/commands/actions/submit.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/driver/src/cy/commands/navigation.ts:814— `options.retryOnStatusCodeFailure && !options.failOnStatusCode` appears character-identically in 2 files — packages/driver/src/cy/commands/navigation.ts, packages/driver/src/cy/commands/request.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/driver/src/cy/commands/cookies.ts:334— `options.timeout || config('defaultCommandTimeout')` appears character-identically in 2 files — packages/driver/src/cy/commands/cookies.ts, packages/driver/src/cy/commands/storage.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/launcher/lib/utils.ts:10— `os.platform() === 'darwin' && os.arch() === 'arm64'` appears character-identically in 2 files — packages/launcher/lib/utils.ts, scripts/after-pack-hook.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/server/lib/cloud/api/cloud_request.ts:38— `process.env.CYPRESS_CONFIG_ENV || process.env.CYPRESS_INTERNAL_ENV || 'development'` appears character-identically in 3 files — packages/server/lib/cloud/api/cloud_request.ts, packages/server/lib/cloud/routes.ts, packages/telemetry/src/telemetry/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 packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts:111— `process.env.CYPRESS_CONFIG_ENV || process.env.CYPRESS_INTERNAL_ENV || 'production'` appears character-identically in 2 files — packages/server/lib/cloud/cy-prompt/CyPromptLifecycleManager.ts, packages/server/lib/cloud/get_cloud_metadata.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/server/scripts/sync-cloud-validations.ts:12— `process.env.CYPRESS_INTERNAL_ENV || 'production'` appears character-identically in 4 files — packages/server/scripts/sync-cloud-validations.ts, scripts/binary/binary-entry-point-source.js, scripts/gulp/gulpConstants.ts, scripts/gulp/tasks/gulpSyncValidations.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/driver/src/cy/commands/files.ts:240— `relativePath && !relativePath.startsWith('..') && !isAbsolute(relativePath)` appears character-identically in 2 files — packages/driver/src/cy/commands/files.ts, packages/server/lib/util/app_data.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 npm/webpack-dev-server/src/helpers/nextHandler.ts:274— `request === 'webpack' || request.startsWith('webpack/')` appears character-identically in 2 files — npm/webpack-dev-server/src/helpers/nextHandler.ts, npm/webpack-dev-server/src/helpers/sourceRelativeWebpackModules.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/data-context/src/actions/CodegenActions.ts:179— `status === 'add' || status === 'overwrite'` appears character-identically in 2 files — packages/data-context/src/actions/CodegenActions.ts, packages/data-context/src/codegen/code-generator.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 cli/lib/util.ts:174— `str.length > 1 && str[0] === '"' && str[str.length - 1] === '"'` appears character-identically in 2 files — cli/lib/util.ts, packages/server/lib/util/cypress-cache.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.
Silent fallback default in catch cli/lib/tap/aut/single-match.ts:47— `disambiguatingSelectors` 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 npm/webpack-dev-server/src/helpers/nextHandler.ts:215— `getRunWebpackSpan` 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 packages/data-context/src/sources/ProjectDataSource.ts:445— `_makeSpecWatcher` swallows every exception into `return false` — 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 REDACTED:49— `getRemoteLocation` (in `create`) 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 packages/driver/src/cy/snapshots.ts:80— `dimensions` (in `create.replaceIframes`) swallows every exception into `return 0` — 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 packages/driver/src/cypress/log.ts:44— `serializedLength` swallows every exception into `return 0` — 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 packages/proxy/lib/adapters/synthetic-express-context.ts:71— `parseUrlQuery` 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 packages/reporter/src/commands/command.tsx:473— `Command` swallows every exception into `return 'https://on.cypress.io/report-cy-prompt-issue'` — 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 packages/server/lib/browsers/cdp-protocol/cdp-network-error.ts:46— `formatAddress` 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 packages/server/lib/cloud/studio/telemetry/TelemetryManager.ts:61— `getMeasure` swallows every exception into `return -1` — 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 packages/server/lib/cloud/api/index.ts:282— `noProxyPreflightTimeout` swallows every exception into `return 5000` — 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 packages/server/lib/util/net_profiler.ts:33— `getCaller` swallows every exception into `return 'unknown'` — 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 packages/server/lib/makeDataContext.ts:171— `getCurrentProjectSavedState` (in `makeDataContext`) 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.
README/code drift npm/react/README.md:9— npm/react/README.md names React 16, but the manifest declares `react` 18.3.1. 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 npm/react/README.md:9— npm/react/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift npm/svelte/README.md:9— npm/svelte/README.md names Cypress 13, but the manifest declares `cypress` ^16.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift npm/svelte/README.md:9— npm/svelte/README.md names Svelte 4, but the manifest declares `svelte` ^5.4.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/electron/README.md:232— packages/electron/README.md links to `./BUILD.md`, but `packages/electron/BUILD.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/eslint-config/README.md:125— packages/eslint-config/README.md names ESLint 9, but the manifest declares `eslint` ^8.56.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/launchpad/README.md:71— packages/launchpad/README.md links to `../graphql/gql.png`, but `packages/graphql/gql.png` 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/proxy/README.md:10— packages/proxy/README.md links to `./lib/http/responseest-middleware.ts`, but `packages/proxy/lib/http/responseest-middleware.ts` 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/scaffold-config/README.md:27— packages/scaffold-config/README.md links to `./src/constants.ts`, but `packages/scaffold-config/src/constants.ts` 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/server/lib/adapters/README.md:5— packages/server/lib/adapters/README.md links to `../../network-interception/README.md`, but `packages/server/network-interception/README.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 38 significant file(s) lose their only recent owner: packages/driver/src/cy/mouse.ts, packages/driver/src/cy/commands/cookies.ts, packages/proxy/lib/http/util/service-worker-manager.ts, packages/driver/src/cy/assertions.ts, REDACTED, REDACTED, packages/eslint-config/src/baseConfig.ts, packages/driver/src/cy/commands/connectors.ts (+30 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 11 significant file(s) lose their only recent owner: packages/data-context/src/actions/WizardActions.ts, tooling/electron-mksnapshot/src/mksnapshot-run.ts, packages/launchpad/src/setup/EnvironmentSetup.vue, packages/socket/lib/node/cdp-socket.ts, system-tests/lib/fixtures.ts, packages/driver/src/cy/commands/storage.ts, packages/launchpad/src/setup/OpenBrowser.vue, packages/server/scripts/sync-cloud-validations.ts (+3 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 10 significant file(s) lose their only recent owner: packages/proxy/lib/http/util/cookies.ts, packages/server/lib/plugins/child/run_require_async_child.ts, packages/server/lib/plugins/util.ts, npm/vite-dev-server/src/plugins/cypress.ts, npm/vite-dev-server/src/resolveConfig.ts, system-tests/__snapshots__/non_proxied_spec.ts.js, packages/packherd-require/src/transpile-ts.ts, packages/server/lib/automation/cookie/converters/bidi.ts (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 4 significant file(s) lose their only recent owner: packages/network-interception/lib/core/network-interception-core.ts, packages/network-interception/lib/core/document-preparation.ts, packages/proxy/lib/http/send-request-outgoing.ts, packages/server/lib/util/egress-policy.ts. Pair on, review, or document these before any departure.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×4
Placeholder literal left in code packages/extension/app/v2/init.ts:3— A placeholder string ("CHANGE_ME_HOST") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code packages/extension/app/v2/init.ts:4— A placeholder string ("CHANGE_ME_PATH") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code packages/extension/lib/index.ts:24— A placeholder string ("CHANGE_ME_HOST") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code packages/extension/lib/index.ts:25— A placeholder string ("CHANGE_ME_PATH") is still in shipped code — typical of generated boilerplate that was never filled in.
Fat interface: ProjectApiShape (24 required operations) packages/data-context/src/actions/ProjectActions.ts:26— `ProjectApiShape` declares 24 required operations: `openProjectCreate`, `launchProject`, `insertProjectToCache`, `removeProjectFromCache`, `getProjectRootsFromCache`, `insertProjectPreferencesToCache`, `getProjectPreferencesFromCache`, `clearLatestProjectsCache`, `clearProjectPreferences`, `clearAllProjectPreferences`, `closeActiveProject`, `getConfig`, `getRemoteStates`, `getCurrentBrowser`, `getCurrentProjectSavedState`, `setPromptShown`, `setProjectPreferences`, `makeProjectSavedState`, `getDevServer`, `isListening`, `resetBrowserTabsForNextSpec`, `resetServer`, `runSpec`, `routeToDebug`. 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: StateFunc (43 required operations) packages/driver/src/cypress/state.ts:15— `StateFunc` declares 43 required operations under just 2 distinct name(s): `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, `(call)`, and 3 more. 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. That is an OVERLOAD SET, not 43 separate responsibilities: a caller binds to 2 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 43 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 282 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
C2 · Access Controls· No 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) — 2 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 (65 single-owned of 698 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; 698 of the 2177 production source files in this repository met that bar). They are anonymized user #5 (1 file(s)), anonymized user #6 (1 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: packages/frontend-shared/src/gql-components/LoginConnectModalsContent.vue, packages/driver/src/dom/animation.ts.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 55 project(s) overshoot their size bounds, lowering Project Cohesion to 8.6/10. The most over is `packages/driver` (34685 LoC, 313 module-visible types across 31 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
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 172 of 705 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 705 of the 2177 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: system-tests/__snapshots__/typescript_spec_support_spec.ts.js, packages/driver/src/cy/commands/screenshot.ts, packages/driver/src/cypress/UsKeyboardLayout.ts, npm/webpack-dev-server/src/helpers/nextHandler.ts, packages/frontend-shared/src/gql-components/modals/SelectCloudProjectModal.vue, system-tests/__snapshots__/test_isolation_spec.ts.js, packages/driver/src/cy/commands/actions/scroll.ts, packages/telemetry/src/telemetry/index.ts (and 164 more). 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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 30/35 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `system-tests/projects/next-15-tsconfig-tailwind`, `system-tests/projects/next-16-tsconfig-tailwind`, `system-tests/projects/nextjs-configured`, `system-tests/projects/nextjs-unconfigured`, `system-tests/projects/v8-snapshot/example-express`.
R7 · Dead Code· Unused export 'InsertionIndex' · ×1
Unused export 'InsertionIndex' npm/cypress-schematic/src/schematics/utils/jsonFile.ts:24— Nothing imports this binding — it is safe to review for removal.
Unused export 'createMount' npm/react/src/createMount.ts:150— Nothing ultimately consumes this binding: its only referrer is the re-export in npm/react/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in npm/react/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'mount' npm/react/src/mount.ts:47— Nothing ultimately consumes this binding: its only referrer is the re-export in npm/react/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in npm/react/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' npm/webpack-dev-server/src/devServer.ts:144— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'ElectronActions' · ×1
Unused export 'ElectronActions' packages/data-context/src/actions/ElectronActions.ts:27— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'BrowserDataSource' · ×1
Unused export 'BrowserDataSource' packages/data-context/src/sources/BrowserDataSource.ts:43— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CloudDataSource' · ×1
Unused export 'CloudDataSource' packages/data-context/src/sources/CloudDataSource.ts:91— No runtime consumer imports this binding — the only demand on it comes from a type-position import of its module, which asks for the module's type surface rather than for this name. If the value is genuinely unneeded, remove it; if a consumer needs only its TYPE, export that type (e.g. `export type X = typeof x`) and drop the value. A value export — a const, a function, a class — cannot itself be rewritten as `export type`.
R7 · Dead Code· Unused export 'ProjectDataSource' · ×1
Unused export 'ProjectDataSource' packages/data-context/src/sources/ProjectDataSource.ts:226— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'insertValuesInConfigFile' · ×1
Unused export 'insertValuesInConfigFile' packages/data-context/src/util/config-file-updater.ts:20— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'encodeBase64Unicode' · ×1
Unused export 'encodeBase64Unicode' packages/frontend-shared/src/utils/base64.ts:34— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getSourceMapAndContent' · ×1
Unused export 'getSourceMapAndContent' packages/packherd-require/src/sourcemap-support.ts:94— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'hookTranspileTs' · ×1
Unused export 'hookTranspileTs' packages/packherd-require/src/transpile-ts.ts:68— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'detectThirdPartyCTFrameworks' · ×1
Unused export 'detectThirdPartyCTFrameworks' packages/scaffold-config/src/ct-detect-third-party.ts:107— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'CodeGenFramework' · ×1
Unused export 'CodeGenFramework' packages/scaffold-config/src/frameworks.ts:15— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SUPPORT_STATUSES' · ×1
Unused export 'SUPPORT_STATUSES' packages/scaffold-config/src/frameworks.ts:104— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'resolveComponentFrameworkDefinition' · ×1
Unused export 'resolveComponentFrameworkDefinition' packages/scaffold-config/src/frameworks.ts:222— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'supportFileE2E' · ×1
Unused export 'supportFileE2E' packages/scaffold-config/src/supportFile.ts:4— Nothing imports this binding — it is safe to review for removal.
Unused export 'patchFs' packages/server/lib/util/patch-fs.ts:4— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'initializeStartTime' · ×1
Unused export 'initializeStartTime' packages/server/lib/util/performance_benchmark.ts:13— Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene· Type-only dependency 'find-up' in production deps · ×1
Type-only dependency 'find-up' in production deps npm/webpack-dev-server/src/helpers/angularHandler.ts:221— Every import is type-only — move it to devDependencies.
No app-layer HTTPS enforcement detected packages/data-context/graphql/makeGraphQLServer.ts:120— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 5/11 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 — 90/167 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.
Null assertions (`!`) reduce the strict null checking score — ~1.3 `!` null assertions per 1k TypeScript source lines — 198 assertion(s) across the 154532 source line(s) of the 1116 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: packages/server/lib/request.ts (29), packages/server/lib/reporter.ts (20), packages/driver/src/cypress.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Skipped (documented): tests test2 system-tests/projects/todos/tests/test2.js:2— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): does not take a screenshot for a pending test system-tests/projects/screenshots/cypress/e2e/screenshots.cy.js:271— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): tests[abc] system-tests/projects/ids/cypress/e2e/bar.js:2— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): quux [002] system-tests/projects/ids/cypress/e2e/foo.js:6— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): does not have an id system-tests/projects/ids/cypress/e2e/noop.js:2— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): is pending system-tests/projects/e2e/cypress/e2e/config_record.cy.js:13— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): t4 system-tests/projects/e2e/cypress/e2e/only.cy.js:13— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): t4 system-tests/projects/e2e/cypress/e2e/only_multiple.cy.js:13— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): is pending system-tests/projects/e2e/cypress/e2e/record_pass.cy.js:17— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): dummy test 1 system-tests/projects/e2e/cypress/e2e/reload.spec.js:30— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): is pending system-tests/projects/e2e/cypress/e2e/simple_failing_hook.cy.js:11— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) system-tests/project-fixtures/runner-specs/cypress/e2e/support/generate-mocha-tests.js:99— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): t1 system-tests/project-fixtures/runner-specs/cypress/e2e/runner/test-pending.runner.cy.js:2— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): t2 system-tests/project-fixtures/runner-specs/cypress/e2e/runner/test-pending.runner.cy.js:3— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): t3 system-tests/project-fixtures/runner-specs/cypress/e2e/runner/test-pending.runner.cy.js:4— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): has a test system-tests/project-fixtures/runner-specs/cypress/e2e/issues/issue-9162.cy.js:7— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): has another test system-tests/project-fixtures/runner-specs/cypress/e2e/issues/issue-9162.cy.js:8— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): skipped packages/driver/cypress/e2e/e2e/testConfigOverrides.cy.ts:312— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): skipped packages/driver/cypress/e2e/e2e/testConfigOverrides.cy.ts:316— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): is pending 1 packages/driver/cypress/e2e/cypress/runner.cy.ts:19— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): is pending 2 packages/driver/cypress/e2e/cypress/runner.cy.ts:21— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): does not fail packages/driver/cypress/e2e/cy/skipping_async.cy.ts:37— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): does not fail when using this.skip packages/driver/cypress/e2e/cy/skipping_sync.cy.ts:47— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
Skipped (documented): can support an array of fixtures packages/driver/cypress/e2e/commands/fixtures.cy.ts:33— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): can timeout when retrieving upstream response packages/driver/cypress/e2e/commands/net_stubbing/intercepting_response.cy.ts:743— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
+ 10 more in this group — see findings.md.
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.
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.
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.
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.
Run 01a178d4-4931-799d-95cb-97beec6d1158 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 440 · Warnings: 3055 · Recommendations: 654 · Info: 35 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 15:29 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.