Executive summary
DevExpress/testcafe falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies, and it has uses of packages that aren't listed. It scores 43 out of 100 and is rated Weak, and 104 of its 224 critical findings are security problems.
Production Readiness, at 27, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 11 points. Making the 1,501 tests that check nothing check their results comes next, worth about 13 points. Raising Production Readiness to 70 would lift the score to about 56.
Sixty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen secrets can leak from the build pipeline, and twelve places in the code run text as code, which an attacker could use. Pinning each tool to an exact version, limiting each secret to its own step and replacing text run as code with direct calls would close these risks. Passing outside input through environment variables would fix the seven pipeline steps that put outside input straight into a shell command, and giving the pull-request workflow read-only access would deal with the three pipelines that outsiders can trigger with write access. The 112 tests that check nothing need to check the result they produce.
The product code is 41,740 lines, about €96,000 to rebuild.
If Production Readiness rose from 27 to 70, the lowest score rated Strong, the score would rise from 43 to about 56.
New since the last survey: 60 findings
- Test Quality · Skipped test: Should compile test defined in separate module if option is enabled test/server/compiler-test.js
- Test Quality · Skipped test: 2 test/server/data/test-suites/live/test-with-skipped.js
- Test Quality · Skipped test: fixture2test4 test/server/data/test-suites/fixture-and-test-hooks/testfile.js
- Test Quality · Skipped test: Test report should contains correct duration time (GH-22) test/functional/legacy-fixtures/page-js-errors/test.js
- Test Quality · Skipped test: Skipped test 1 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js
- Test Quality · Skipped test: Skipped test 2 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js
- Test Quality · Skipped test: Skipped test 3 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js
- Test Quality · Skipped test: Skipped test 4 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js
- Test Quality · Skipped test: Fixture5Test1 test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/skip-test.js
- Test Quality · Skipped test: Test4 test/functional/fixtures/api/es-next/hooks/testcafe-fixtures/fixture-hooks.js
- Dependency Hygiene · Deprecated: eslint package.json
- Dependency Hygiene · Deprecated: sinon package.json
- Secret Scanning · REDACTED
- Static Analysis (SAST) · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Tooling · The declared test suite includes a file that cannot be loaded test/server/data/test-suites/live/test-external-unexisting-module.js
- Exception handling · Swallowed exception (empty catch) src/client/automation/playback/press/utils.js
- Exception handling · Swallowed exception (caught, then discarded) REDACTED
- Incompleteness & stubs · Fake-async — async method never awaits src/browser/provider/plugin-host.js
- Incompleteness & stubs · Fake-async — async method never awaits src/browser/provider/plugin-host.js
- Incompleteness & stubs · Fake-async — async method never awaits src/browser/provider/plugin-host.js
- Incompleteness & stubs · Fake-async — async method never awaits src/browser/provider/plugin-host.js
- Incompleteness & stubs · Both branches are identical — the condition decides nothing src/client/automation/playback/click/select-child.js
- Incompleteness & stubs · Both branches are identical — the condition decides nothing src/client/core/select/index.ts
- Incompleteness & stubs · Fake-async — async method never awaits src/utils/temp-directory/index.js
- Async & latency hygiene · Sync-over-async blocking test/client/config-qunit-server-app.js
- Async & latency hygiene · Sync-over-async blocking test/functional/site/api.js
Fixed since the last survey: 239 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Change Coupling · Boundary-crossing change coupling: driver.js ↔ input.ts src/client/driver/driver.js
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
- Code Duplication · Duplicated block (5 lines × 2 locations) src/browser/connection/index.ts
- Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) REDACTED
- Code Duplication · Duplicated block (5 lines × 2 locations) src/client/ui/progress-panel/index.js
- Code Duplication · Duplicated block (5 lines × 2 locations) src/utils/get-options/quarantine.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/command-executors/browser-manipulation/index.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/command-executors/client-functions/client-function-executor.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/command-executors/client-functions/selector-executor/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/driver.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/driver.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/driver.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/client/driver/process-skip-js-errors.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/compiler/babel/load-libs.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/errors/runtime/index.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/live/bootstrapper.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/live/test-run.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/live/test-run.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/live/test-run.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/api-base.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/client/input.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/cookie-provider.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/cookie-provider.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/request-pipeline/resendAuthRequest.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/request-pipeline/resendAuthRequest.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/request-pipeline/test-run-bridge.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] REDACTED
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/session-storage/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/native-automation/storages-provider.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/notifications/warning-log.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/command/command-formatter.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/command/command-formatter.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/command/command-formatter.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/command/command-formatter.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/command/format-command.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/plugin-host.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/reporter/report-data-log.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/role/role.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/browser-job.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/browser-job.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/fixture-hook-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/fixture-hook-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/index.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/interfaces.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/interfaces.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/task/index.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/test-run-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/test-run-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/test-run-hook-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/runner/test-run-hook-controller.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/screenshots/crop.js
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/execute-fn-with-timeout.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/get-options/get-assertion-timeout.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/get-options/quarantine.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/get-renderes.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/get-test-and-fixture-info.ts
- Import Boundaries · Boundary violation [package:test-suite-dependency] src/utils/handle-errors.js
- Test Coverage · This test file cannot be loaded test/functional/setup.js
- Test Coverage · No test reaches this file src/client/driver/iframe-driver.js
- Test Coverage · No test reaches this file src/client/ui/modal-background.js
- Test Coverage · No test reaches this file src/client/ui/cursor/index.js
- Test Coverage · No test reaches this file src/client/driver/storage.js
- Test Coverage · No test reaches this file src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js
- Test Coverage · No test reaches this file src/client/ui/selector-inspector-panel/tooltip.js
- Test Coverage · No test reaches this file src/client/automation/playback/dispatch-event.ts
- Test Coverage · No test reaches this file src/client/automation/playback/move/drag-move.js
- Test Coverage · No test reaches this file src/client/driver/command-executors/client-functions/selector-executor/filter.ts
- Test Coverage · No test reaches this file src/client/driver/driver-link/iframe/child.js
- Test Coverage · No test reaches this file src/client/driver/command-executors/client-functions/selector-executor/node-snapshots.ts
- Test Coverage · No test reaches this file src/client/core/select/index.ts
- Test Coverage · No test reaches this file src/client/driver/barriers/request.ts
- Test Coverage · No test reaches this file src/client/core/index.js
- Test Coverage · No test reaches this file src/client/driver/command-executors/client-functions/selector-executor/index.ts
- Test Coverage · No test reaches this file src/client/ui/selector-inspector-panel/selectors-list.js
- Test Coverage · No test reaches this file src/client/core/utils/scroll.ts
- Test Coverage · No test reaches this file src/client/driver/barriers/script-execution.ts
- Test Coverage · No test reaches this file src/client/ui/selector-inspector-panel/element-picker.js
- Test Coverage · No test reaches this file src/client/automation/playback/rclick.js
- Test Coverage · No test reaches this file src/client/automation/utils/key-identifier-maps.js
- Test Coverage · No test reaches this file src/client/automation/playback/click/index.ts
- Test Coverage · No test reaches this file src/client/automation/playback/dblclick.js
- Test Coverage · No test reaches this file src/client/core/barriers/page-unload-barrier.ts
- Test Coverage · No test reaches this file src/client/core/utils/style.js
- Test Coverage · No test reaches this file src/client/automation/cursor/cursor.ts
- Test Coverage · No test reaches this file src/client/core/utils/event.js
- Test Coverage · No test reaches this file src/client/ui/index.js
- Test Coverage · No test reaches this file src/native-automation/client/input.ts
- Test Coverage · No test reaches this file gulp/helpers/test-functional.js
- Test Coverage · No test reaches this file src/client/ui/selector-inspector-panel/descriptors.js
- Test Coverage · No test reaches this file src/client/automation/index.js
- Test Coverage · No test reaches this file src/client/driver/utils/ensure-elements.js
- Test Coverage · No test reaches this file src/client/core/scroll/controller.js
- Test Coverage · No test reaches this file src/client/automation/playback/set-scroll.ts
- Test Coverage · No test reaches this file src/client/automation/get-element.ts
Rebuild cost: about €96,000 · Estimate
| Cost to rebuild | €32,000 to €160,000, for 532 to 1,688 hours of work, about 0.7 person-years for 1 to 2 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,740 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 api.structure.test-file | 2 client.core.utils.values.axis-values | 3 configuration.types | 4 native-automation.client.types | 5 native-automation.types | 6 notifications.warning-log | 7 utils.async-event-emitter | 8 api.structure.testing-unit | 9 browser.provider.built-in.dedicated.chrome.interfaces | 10 client.automation.cursor.cursor | 11 configuration.interfaces | 12 utils.message-bus | 13 api.request-hooks.request-logger | 14 api.structure.fixture | 15 api.structure.test | 16 browser.provider | 17 browser.provider.built-in.dedicated.chrome.cdp-client | 18 client.automation.visible-element-automation | 19 client.core.utils.event-emitter | 20 configuration.configuration-base | 21 video-recorder.videos | 22 browser.connection.remotes-queue | 23 client.automation.playback.click | 24 configuration.testcafe-configuration | 25 live.controller | 26 runner.fixture-hook-controller | 27 browser.connection.gateway | 28 runner.interfaces | 29 runner.test-run-controller | 30 runner.browser-job | 31 browser.connection | 32 runner.task | 33 cli.remotes-wizard | 34 native-automation.request-pipeline.test-run-bridge | 35 reporter | 36 runner.browser-set | 37 utils | 38 native-automation.request-pipeline.context-info | 39 runner.bootstrapper | 40 native-automation.request-pipeline |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 api.structure.test-file | ||||||||||||||||||||||||||||||||||||||||
| 2 client.core.utils.values.axis-values | ||||||||||||||||||||||||||||||||||||||||
| 3 configuration.types | ||||||||||||||||||||||||||||||||||||||||
| 4 native-automation.client.types | ||||||||||||||||||||||||||||||||||||||||
| 5 native-automation.types | ||||||||||||||||||||||||||||||||||||||||
| 6 notifications.warning-log | ||||||||||||||||||||||||||||||||||||||||
| 7 utils.async-event-emitter | ||||||||||||||||||||||||||||||||||||||||
| 8 api.structure.testing-unit | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 browser.provider.built-in.dedicated.chrome.interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 client.automation.cursor.cursor | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 configuration.interfaces | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 utils.message-bus | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 api.request-hooks.request-logger | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 api.structure.fixture | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 api.structure.test | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 browser.provider | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 browser.provider.built-in.dedicated.chrome.cdp-client | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 client.automation.visible-element-automation | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 client.core.utils.event-emitter | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 configuration.configuration-base | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 video-recorder.videos | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 browser.connection.remotes-queue | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 23 client.automation.playback.click | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 24 configuration.testcafe-configuration | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 live.controller | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 runner.fixture-hook-controller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 browser.connection.gateway | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 runner.interfaces | 4 | 5 | 4 | 4 | 2 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 29 runner.test-run-controller | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||
| 30 runner.browser-job | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 31 browser.connection | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 32 runner.task | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||
| 33 cli.remotes-wizard | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 native-automation.request-pipeline.test-run-bridge | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 reporter | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 36 runner.browser-set | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 utils | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 native-automation.request-pipeline.context-info | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 39 runner.bootstrapper | 1 | 1 | 1 | 2 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 40 native-automation.request-pipeline | 7 | 1 | 1 |
8→1 api.structure.testing-unit uses api.structure.test-file✕
- Connections
- 1 pair of types, where a type in api.structure.testing-unit uses a type in api.structure.test-file.
- The types involved
src.api.structure.testing-unit.TestingUnit→src.api.structure.test-file.TestFile
- Direction
- api.structure.testing-unit uses api.structure.test-file, so a change to api.structure.test-file can break api.structure.testing-unit, while a change to api.structure.testing-unit can't break api.structure.test-file.
- Position
- Below the diagonal: api.structure.testing-unit uses a module listed above it, which is the healthy direction.
9→17 browser.provider.built-in.dedicated.chrome.interfaces uses browser.provider.built-in.dedicated.chrome.cdp-client part of a loop✕
- Connections
- 1 pair of types, where a type in browser.provider.built-in.dedicated.chrome.interfaces uses a type in browser.provider.built-in.dedicated.chrome.cdp-client.
- The types involved
src.browser.provider.built-in.dedicated.chrome.interfaces.RuntimeInfo→src.browser.provider.built-in.dedicated.chrome.cdp-client.BrowserClient
- Direction
- browser.provider.built-in.dedicated.chrome.interfaces uses browser.provider.built-in.dedicated.chrome.cdp-client, so a change to browser.provider.built-in.dedicated.chrome.cdp-client can break browser.provider.built-in.dedicated.chrome.interfaces, while a change to browser.provider.built-in.dedicated.chrome.interfaces can't break browser.provider.built-in.dedicated.chrome.cdp-client.
- 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.
10→2 client.automation.cursor.cursor uses client.core.utils.values.axis-values✕
- Connections
- 2 pairs of types, where a type in client.automation.cursor.cursor uses a type in client.core.utils.values.axis-values.
- The types involved
src.client.automation.cursor.cursor.Cursor→src.client.core.utils.values.axis-values.AxisValuessrc.client.automation.cursor.cursor.Cursor→src.client.core.utils.values.axis-values.AxisValuesData
- Direction
- client.automation.cursor.cursor uses client.core.utils.values.axis-values, so a change to client.core.utils.values.axis-values can break client.automation.cursor.cursor, while a change to client.automation.cursor.cursor can't break client.core.utils.values.axis-values.
- Position
- Below the diagonal: client.automation.cursor.cursor uses a module listed above it, which is the healthy direction.
11→3 configuration.interfaces uses configuration.types✕
- Connections
- 1 pair of types, where a type in configuration.interfaces uses a type in configuration.types.
- The types involved
src.configuration.interfaces.RunnerRunOptions→src.configuration.types.GlobalHooks
- Direction
- configuration.interfaces uses configuration.types, so a change to configuration.types can break configuration.interfaces, while a change to configuration.interfaces can't break configuration.types.
- Position
- Below the diagonal: configuration.interfaces uses a module listed above it, which is the healthy direction.
12→7 utils.message-bus uses utils.async-event-emitter✕
- Connections
- 1 pair of types, where a type in utils.message-bus uses a type in utils.async-event-emitter.
- The types involved
src.utils.message-bus.MessageBus→src.utils.async-event-emitter.AsyncEventEmitter
- Direction
- utils.message-bus uses utils.async-event-emitter, so a change to utils.async-event-emitter can break utils.message-bus, while a change to utils.message-bus can't break utils.async-event-emitter.
- Position
- Below the diagonal: utils.message-bus uses a module listed above it, which is the healthy direction.
13→11 api.request-hooks.request-logger uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in api.request-hooks.request-logger uses a type in configuration.interfaces.
- The types involved
src.api.request-hooks.request-logger.RequestLoggerImplementation→src.configuration.interfaces.Dictionary
- Direction
- api.request-hooks.request-logger uses configuration.interfaces, so a change to configuration.interfaces can break api.request-hooks.request-logger, while a change to api.request-hooks.request-logger can't break configuration.interfaces.
- Position
- Below the diagonal: api.request-hooks.request-logger uses a module listed above it, which is the healthy direction.
14→1 api.structure.fixture uses api.structure.test-file✕
- Connections
- 2 pairs of types, where a type in api.structure.fixture uses a type in api.structure.test-file.
- The types involved
src.api.structure.fixture.Fixture→src.api.structure.test-file.TestFilesrc.api.structure.fixture.FixtureInitOptions→src.api.structure.test-file.TestFile
- Direction
- api.structure.fixture uses api.structure.test-file, so a change to api.structure.test-file can break api.structure.fixture, while a change to api.structure.fixture can't break api.structure.test-file.
- Position
- Below the diagonal: api.structure.fixture uses a module listed above it, which is the healthy direction.
14→8 api.structure.fixture uses api.structure.testing-unit✕
- Connections
- 1 pair of types, where a type in api.structure.fixture uses a type in api.structure.testing-unit.
- The types involved
src.api.structure.fixture.Fixture→src.api.structure.testing-unit.TestingUnit
- Direction
- api.structure.fixture uses api.structure.testing-unit, so a change to api.structure.testing-unit can break api.structure.fixture, while a change to api.structure.fixture can't break api.structure.testing-unit.
- Position
- Below the diagonal: api.structure.fixture uses a module listed above it, which is the healthy direction.
15→1 api.structure.test uses api.structure.test-file✕
- Connections
- 2 pairs of types, where a type in api.structure.test uses a type in api.structure.test-file.
- The types involved
src.api.structure.test.Test→src.api.structure.test-file.TestFilesrc.api.structure.test.TestInitOptions→src.api.structure.test-file.TestFile
- Direction
- api.structure.test uses api.structure.test-file, so a change to api.structure.test-file can break api.structure.test, while a change to api.structure.test can't break api.structure.test-file.
- Position
- Below the diagonal: api.structure.test uses a module listed above it, which is the healthy direction.
15→8 api.structure.test uses api.structure.testing-unit✕
- Connections
- 1 pair of types, where a type in api.structure.test uses a type in api.structure.testing-unit.
- The types involved
src.api.structure.test.Test→src.api.structure.testing-unit.TestingUnit
- Direction
- api.structure.test uses api.structure.testing-unit, so a change to api.structure.testing-unit can break api.structure.test, while a change to api.structure.test can't break api.structure.testing-unit.
- Position
- Below the diagonal: api.structure.test uses a module listed above it, which is the healthy direction.
16→5 browser.provider uses native-automation.types✕
- Connections
- 1 pair of types, where a type in browser.provider uses a type in native-automation.types.
- The types involved
src.browser.provider.BrowserProvider→src.native-automation.types.EventType
- Direction
- browser.provider uses native-automation.types, so a change to native-automation.types can break browser.provider, while a change to browser.provider can't break native-automation.types.
- Position
- Below the diagonal: browser.provider uses a module listed above it, which is the healthy direction.
16→11 browser.provider uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in browser.provider uses a type in configuration.interfaces.
- The types involved
src.browser.provider.BrowserProvider→src.configuration.interfaces.Dictionary
- Direction
- browser.provider uses configuration.interfaces, so a change to configuration.interfaces can break browser.provider, while a change to browser.provider can't break configuration.interfaces.
- Position
- Below the diagonal: browser.provider uses a module listed above it, which is the healthy direction.
16→31 browser.provider uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in browser.provider uses a type in browser.connection.
- The types involved
src.browser.provider.BrowserProvider→src.browser.connection.BrowserClosingInfo
- Direction
- browser.provider uses browser.connection, so a change to browser.connection can break browser.provider, while a change to browser.provider can't break browser.connection.
- 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.
17→9 browser.provider.built-in.dedicated.chrome.cdp-client uses browser.provider.built-in.dedicated.chrome.interfaces✕
- Connections
- 3 pairs of types, where a type in browser.provider.built-in.dedicated.chrome.cdp-client uses a type in browser.provider.built-in.dedicated.chrome.interfaces.
- The types involved
src.browser.provider.built-in.dedicated.chrome.cdp-client.BrowserClient→src.browser.provider.built-in.dedicated.chrome.interfaces.Configsrc.browser.provider.built-in.dedicated.chrome.cdp-client.BrowserClient→src.browser.provider.built-in.dedicated.chrome.interfaces.RuntimeInfosrc.browser.provider.built-in.dedicated.chrome.cdp-client.BrowserClient→src.browser.provider.built-in.dedicated.chrome.interfaces.Size
- Direction
- browser.provider.built-in.dedicated.chrome.cdp-client uses browser.provider.built-in.dedicated.chrome.interfaces, so a change to browser.provider.built-in.dedicated.chrome.interfaces can break browser.provider.built-in.dedicated.chrome.cdp-client, while a change to browser.provider.built-in.dedicated.chrome.cdp-client can't break browser.provider.built-in.dedicated.chrome.interfaces.
- Position
- Below the diagonal: browser.provider.built-in.dedicated.chrome.cdp-client uses a module listed above it, which is the healthy direction.
17→11 browser.provider.built-in.dedicated.chrome.cdp-client uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in browser.provider.built-in.dedicated.chrome.cdp-client uses a type in configuration.interfaces.
- The types involved
src.browser.provider.built-in.dedicated.chrome.cdp-client.BrowserClient→src.configuration.interfaces.Dictionary
- Direction
- browser.provider.built-in.dedicated.chrome.cdp-client uses configuration.interfaces, so a change to configuration.interfaces can break browser.provider.built-in.dedicated.chrome.cdp-client, while a change to browser.provider.built-in.dedicated.chrome.cdp-client can't break configuration.interfaces.
- Position
- Below the diagonal: browser.provider.built-in.dedicated.chrome.cdp-client uses a module listed above it, which is the healthy direction.
18→2 client.automation.visible-element-automation uses client.core.utils.values.axis-values✕
- Connections
- 1 pair of types, where a type in client.automation.visible-element-automation uses a type in client.core.utils.values.axis-values.
- The types involved
src.client.automation.visible-element-automation.VisibleElementAutomation→src.client.core.utils.values.axis-values.AxisValues
- Direction
- client.automation.visible-element-automation uses client.core.utils.values.axis-values, so a change to client.core.utils.values.axis-values can break client.automation.visible-element-automation, while a change to client.automation.visible-element-automation can't break client.core.utils.values.axis-values.
- Position
- Below the diagonal: client.automation.visible-element-automation uses a module listed above it, which is the healthy direction.
18→4 client.automation.visible-element-automation uses native-automation.client.types✕
- Connections
- 1 pair of types, where a type in client.automation.visible-element-automation uses a type in native-automation.client.types.
- The types involved
src.client.automation.visible-element-automation.VisibleElementAutomation→src.native-automation.client.types.DispatchEventFn
- Direction
- client.automation.visible-element-automation uses native-automation.client.types, so a change to native-automation.client.types can break client.automation.visible-element-automation, while a change to client.automation.visible-element-automation can't break native-automation.client.types.
- Position
- Below the diagonal: client.automation.visible-element-automation uses a module listed above it, which is the healthy direction.
18→10 client.automation.visible-element-automation uses client.automation.cursor.cursor✕
- Connections
- 1 pair of types, where a type in client.automation.visible-element-automation uses a type in client.automation.cursor.cursor.
- The types involved
src.client.automation.visible-element-automation.VisibleElementAutomation→src.client.automation.cursor.cursor.Cursor
- Direction
- client.automation.visible-element-automation uses client.automation.cursor.cursor, so a change to client.automation.cursor.cursor can break client.automation.visible-element-automation, while a change to client.automation.visible-element-automation can't break client.automation.cursor.cursor.
- Position
- Below the diagonal: client.automation.visible-element-automation uses a module listed above it, which is the healthy direction.
19→11 client.core.utils.event-emitter uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in client.core.utils.event-emitter uses a type in configuration.interfaces.
- The types involved
src.client.core.utils.event-emitter.EventEmitter→src.configuration.interfaces.Dictionary
- Direction
- client.core.utils.event-emitter uses configuration.interfaces, so a change to configuration.interfaces can break client.core.utils.event-emitter, while a change to client.core.utils.event-emitter can't break configuration.interfaces.
- Position
- Below the diagonal: client.core.utils.event-emitter uses a module listed above it, which is the healthy direction.
20→3 configuration.configuration-base uses configuration.types✕
- Connections
- 1 pair of types, where a type in configuration.configuration-base uses a type in configuration.types.
- The types involved
src.configuration.configuration-base.Configuration→src.configuration.types.OptionValue
- Direction
- configuration.configuration-base uses configuration.types, so a change to configuration.types can break configuration.configuration-base, while a change to configuration.configuration-base can't break configuration.types.
- Position
- Below the diagonal: configuration.configuration-base uses a module listed above it, which is the healthy direction.
20→11 configuration.configuration-base uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in configuration.configuration-base uses a type in configuration.interfaces.
- The types involved
src.configuration.configuration-base.Configuration→src.configuration.interfaces.Dictionary
- Direction
- configuration.configuration-base uses configuration.interfaces, so a change to configuration.interfaces can break configuration.configuration-base, while a change to configuration.configuration-base can't break configuration.interfaces.
- Position
- Below the diagonal: configuration.configuration-base uses a module listed above it, which is the healthy direction.
21→6 video-recorder.videos uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in video-recorder.videos uses a type in notifications.warning-log.
- The types involved
src.video-recorder.videos.Videos→src.notifications.warning-log.WarningLog
- Direction
- video-recorder.videos uses notifications.warning-log, so a change to notifications.warning-log can break video-recorder.videos, while a change to video-recorder.videos can't break notifications.warning-log.
- Position
- Below the diagonal: video-recorder.videos uses a module listed above it, which is the healthy direction.
21→11 video-recorder.videos uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in video-recorder.videos uses a type in configuration.interfaces.
- The types involved
src.video-recorder.videos.Videos→src.configuration.interfaces.Dictionary
- Direction
- video-recorder.videos uses configuration.interfaces, so a change to configuration.interfaces can break video-recorder.videos, while a change to video-recorder.videos can't break configuration.interfaces.
- Position
- Below the diagonal: video-recorder.videos uses a module listed above it, which is the healthy direction.
22→11 browser.connection.remotes-queue uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in browser.connection.remotes-queue uses a type in configuration.interfaces.
- The types involved
src.browser.connection.remotes-queue.RemotesQueue→src.configuration.interfaces.Dictionary
- Direction
- browser.connection.remotes-queue uses configuration.interfaces, so a change to configuration.interfaces can break browser.connection.remotes-queue, while a change to browser.connection.remotes-queue can't break configuration.interfaces.
- Position
- Below the diagonal: browser.connection.remotes-queue uses a module listed above it, which is the healthy direction.
22→19 browser.connection.remotes-queue uses client.core.utils.event-emitter✕
- Connections
- 1 pair of types, where a type in browser.connection.remotes-queue uses a type in client.core.utils.event-emitter.
- The types involved
src.browser.connection.remotes-queue.RemotesQueue→src.client.core.utils.event-emitter.EventEmitter
- Direction
- browser.connection.remotes-queue uses client.core.utils.event-emitter, so a change to client.core.utils.event-emitter can break browser.connection.remotes-queue, while a change to browser.connection.remotes-queue can't break client.core.utils.event-emitter.
- Position
- Below the diagonal: browser.connection.remotes-queue uses a module listed above it, which is the healthy direction.
22→31 browser.connection.remotes-queue uses browser.connection part of a loop✕
- Connections
- 2 pairs of types, where a type in browser.connection.remotes-queue uses a type in browser.connection.
- The types involved
src.browser.connection.remotes-queue.PendingConnection→src.browser.connection.BrowserConnectionsrc.browser.connection.remotes-queue.RemotesQueue→src.browser.connection.BrowserConnection
- Direction
- browser.connection.remotes-queue uses browser.connection, so a change to browser.connection can break browser.connection.remotes-queue, while a change to browser.connection.remotes-queue can't break browser.connection.
- 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.
23→4 client.automation.playback.click uses native-automation.client.types✕
- Connections
- 1 pair of types, where a type in client.automation.playback.click uses a type in native-automation.client.types.
- The types involved
src.client.automation.playback.click.ClickAutomation→src.native-automation.client.types.DispatchEventFn
- Direction
- client.automation.playback.click uses native-automation.client.types, so a change to native-automation.client.types can break client.automation.playback.click, while a change to client.automation.playback.click can't break native-automation.client.types.
- Position
- Below the diagonal: client.automation.playback.click uses a module listed above it, which is the healthy direction.
23→10 client.automation.playback.click uses client.automation.cursor.cursor✕
- Connections
- 1 pair of types, where a type in client.automation.playback.click uses a type in client.automation.cursor.cursor.
- The types involved
src.client.automation.playback.click.ClickAutomation→src.client.automation.cursor.cursor.Cursor
- Direction
- client.automation.playback.click uses client.automation.cursor.cursor, so a change to client.automation.cursor.cursor can break client.automation.playback.click, while a change to client.automation.playback.click can't break client.automation.cursor.cursor.
- Position
- Below the diagonal: client.automation.playback.click uses a module listed above it, which is the healthy direction.
23→18 client.automation.playback.click uses client.automation.visible-element-automation✕
- Connections
- 2 pairs of types, where a type in client.automation.playback.click uses a type in client.automation.visible-element-automation.
- The types involved
src.client.automation.playback.click.ClickAutomation→src.client.automation.visible-element-automation.MouseEventArgssrc.client.automation.playback.click.ClickAutomation→src.client.automation.visible-element-automation.VisibleElementAutomation
- Direction
- client.automation.playback.click uses client.automation.visible-element-automation, so a change to client.automation.visible-element-automation can break client.automation.playback.click, while a change to client.automation.playback.click can't break client.automation.visible-element-automation.
- Position
- Below the diagonal: client.automation.playback.click uses a module listed above it, which is the healthy direction.
24→6 configuration.testcafe-configuration uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in configuration.testcafe-configuration uses a type in notifications.warning-log.
- The types involved
src.configuration.testcafe-configuration.TestCafeConfiguration→src.notifications.warning-log.WarningLog
- Direction
- configuration.testcafe-configuration uses notifications.warning-log, so a change to notifications.warning-log can break configuration.testcafe-configuration, while a change to configuration.testcafe-configuration can't break notifications.warning-log.
- Position
- Below the diagonal: configuration.testcafe-configuration uses a module listed above it, which is the healthy direction.
24→11 configuration.testcafe-configuration uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in configuration.testcafe-configuration uses a type in configuration.interfaces.
- The types involved
src.configuration.testcafe-configuration.TestCafeConfiguration→src.configuration.interfaces.Dictionary
- Direction
- configuration.testcafe-configuration uses configuration.interfaces, so a change to configuration.interfaces can break configuration.testcafe-configuration, while a change to configuration.testcafe-configuration can't break configuration.interfaces.
- Position
- Below the diagonal: configuration.testcafe-configuration uses a module listed above it, which is the healthy direction.
24→20 configuration.testcafe-configuration uses configuration.configuration-base✕
- Connections
- 1 pair of types, where a type in configuration.testcafe-configuration uses a type in configuration.configuration-base.
- The types involved
src.configuration.testcafe-configuration.TestCafeConfiguration→src.configuration.configuration-base.Configuration
- Direction
- configuration.testcafe-configuration uses configuration.configuration-base, so a change to configuration.configuration-base can break configuration.testcafe-configuration, while a change to configuration.testcafe-configuration can't break configuration.configuration-base.
- Position
- Below the diagonal: configuration.testcafe-configuration uses a module listed above it, which is the healthy direction.
24→27 configuration.testcafe-configuration uses browser.connection.gateway part of a loop✕
- Connections
- 1 pair of types, where a type in configuration.testcafe-configuration uses a type in browser.connection.gateway.
- The types involved
src.configuration.testcafe-configuration.TestCafeConfiguration→src.browser.connection.gateway.BrowserConnectionGatewayOptions
- Direction
- configuration.testcafe-configuration uses browser.connection.gateway, so a change to browser.connection.gateway can break configuration.testcafe-configuration, while a change to configuration.testcafe-configuration can't break browser.connection.gateway.
- 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.
24→31 configuration.testcafe-configuration uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in configuration.testcafe-configuration uses a type in browser.connection.
- The types involved
src.configuration.testcafe-configuration.TestCafeConfiguration→src.browser.connection.BrowserConnectionOptions
- Direction
- configuration.testcafe-configuration uses browser.connection, so a change to browser.connection can break configuration.testcafe-configuration, while a change to configuration.testcafe-configuration can't break browser.connection.
- 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.
25→19 live.controller uses client.core.utils.event-emitter✕
- Connections
- 1 pair of types, where a type in live.controller uses a type in client.core.utils.event-emitter.
- The types involved
src.live.controller.LiveModeController→src.client.core.utils.event-emitter.EventEmitter
- Direction
- live.controller uses client.core.utils.event-emitter, so a change to client.core.utils.event-emitter can break live.controller, while a change to live.controller can't break client.core.utils.event-emitter.
- Position
- Below the diagonal: live.controller uses a module listed above it, which is the healthy direction.
26→14 runner.fixture-hook-controller uses api.structure.fixture✕
- Connections
- 1 pair of types, where a type in runner.fixture-hook-controller uses a type in api.structure.fixture.
- The types involved
src.runner.fixture-hook-controller.FixtureHookController→src.api.structure.fixture.Fixture
- Direction
- runner.fixture-hook-controller uses api.structure.fixture, so a change to api.structure.fixture can break runner.fixture-hook-controller, while a change to runner.fixture-hook-controller can't break api.structure.fixture.
- Position
- Below the diagonal: runner.fixture-hook-controller uses a module listed above it, which is the healthy direction.
26→15 runner.fixture-hook-controller uses api.structure.test✕
- Connections
- 1 pair of types, where a type in runner.fixture-hook-controller uses a type in api.structure.test.
- The types involved
src.runner.fixture-hook-controller.FixtureHookController→src.api.structure.test.Test
- Direction
- runner.fixture-hook-controller uses api.structure.test, so a change to api.structure.test can break runner.fixture-hook-controller, while a change to runner.fixture-hook-controller can't break api.structure.test.
- Position
- Below the diagonal: runner.fixture-hook-controller uses a module listed above it, which is the healthy direction.
27→11 browser.connection.gateway uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in browser.connection.gateway uses a type in configuration.interfaces.
- The types involved
src.browser.connection.gateway.BrowserConnectionGateway→src.configuration.interfaces.Dictionary
- Direction
- browser.connection.gateway uses configuration.interfaces, so a change to configuration.interfaces can break browser.connection.gateway, while a change to browser.connection.gateway can't break configuration.interfaces.
- Position
- Below the diagonal: browser.connection.gateway uses a module listed above it, which is the healthy direction.
27→19 browser.connection.gateway uses client.core.utils.event-emitter✕
- Connections
- 1 pair of types, where a type in browser.connection.gateway uses a type in client.core.utils.event-emitter.
- The types involved
src.browser.connection.gateway.BrowserConnectionGateway→src.client.core.utils.event-emitter.EventEmitter
- Direction
- browser.connection.gateway uses client.core.utils.event-emitter, so a change to client.core.utils.event-emitter can break browser.connection.gateway, while a change to browser.connection.gateway can't break client.core.utils.event-emitter.
- Position
- Below the diagonal: browser.connection.gateway uses a module listed above it, which is the healthy direction.
27→22 browser.connection.gateway uses browser.connection.remotes-queue✕
- Connections
- 1 pair of types, where a type in browser.connection.gateway uses a type in browser.connection.remotes-queue.
- The types involved
src.browser.connection.gateway.BrowserConnectionGateway→src.browser.connection.remotes-queue.RemotesQueue
- Direction
- browser.connection.gateway uses browser.connection.remotes-queue, so a change to browser.connection.remotes-queue can break browser.connection.gateway, while a change to browser.connection.gateway can't break browser.connection.remotes-queue.
- Position
- Below the diagonal: browser.connection.gateway uses a module listed above it, which is the healthy direction.
27→24 browser.connection.gateway uses configuration.testcafe-configuration✕
- Connections
- 1 pair of types, where a type in browser.connection.gateway uses a type in configuration.testcafe-configuration.
- The types involved
src.browser.connection.gateway.BrowserConnectionGateway→src.configuration.testcafe-configuration.TestCafeStartOptions
- Direction
- browser.connection.gateway uses configuration.testcafe-configuration, so a change to configuration.testcafe-configuration can break browser.connection.gateway, while a change to browser.connection.gateway can't break configuration.testcafe-configuration.
- Position
- Below the diagonal: browser.connection.gateway uses a module listed above it, which is the healthy direction.
27→31 browser.connection.gateway uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in browser.connection.gateway uses a type in browser.connection.
- The types involved
src.browser.connection.gateway.BrowserConnectionGateway→src.browser.connection.BrowserConnection
- Direction
- browser.connection.gateway uses browser.connection, so a change to browser.connection can break browser.connection.gateway, while a change to browser.connection.gateway can't break browser.connection.
- 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.
28→3 runner.interfaces uses configuration.types✕
- Connections
- 4 pairs of types, where a type in runner.interfaces uses a type in configuration.types.
- The types involved
src.runner.interfaces.BrowserJobInit→src.configuration.types.OptionValuesrc.runner.interfaces.TaskInit→src.configuration.types.OptionValuesrc.runner.interfaces.TestRunControllerInit→src.configuration.types.OptionValuesrc.runner.interfaces.TestRunInit→src.configuration.types.OptionValue
- Direction
- runner.interfaces uses configuration.types, so a change to configuration.types can break runner.interfaces, while a change to runner.interfaces can't break configuration.types.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→6 runner.interfaces uses notifications.warning-log✕
- Connections
- 5 pairs of types, where a type in runner.interfaces uses a type in notifications.warning-log.
- The types involved
src.runner.interfaces.BrowserJobInit→src.notifications.warning-log.WarningLogsrc.runner.interfaces.BrowserSetOptions→src.notifications.warning-log.WarningLogsrc.runner.interfaces.TaskInit→src.notifications.warning-log.WarningLogsrc.runner.interfaces.TestRunControllerInit→src.notifications.warning-log.WarningLogsrc.runner.interfaces.TestRunInit→src.notifications.warning-log.WarningLog
- Direction
- runner.interfaces uses notifications.warning-log, so a change to notifications.warning-log can break runner.interfaces, while a change to runner.interfaces can't break notifications.warning-log.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→11 runner.interfaces uses configuration.interfaces✕
- Connections
- 4 pairs of types, where a type in runner.interfaces uses a type in configuration.interfaces.
- The types involved
src.runner.interfaces.BrowserJobInit→src.configuration.interfaces.Dictionarysrc.runner.interfaces.TaskInit→src.configuration.interfaces.Dictionarysrc.runner.interfaces.TestRunControllerInit→src.configuration.interfaces.Dictionarysrc.runner.interfaces.TestRunInit→src.configuration.interfaces.Dictionary
- Direction
- runner.interfaces uses configuration.interfaces, so a change to configuration.interfaces can break runner.interfaces, while a change to runner.interfaces can't break configuration.interfaces.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→12 runner.interfaces uses utils.message-bus✕
- Connections
- 4 pairs of types, where a type in runner.interfaces uses a type in utils.message-bus.
- The types involved
src.runner.interfaces.BootstrapperInit→src.utils.message-bus.MessageBussrc.runner.interfaces.BrowserJobInit→src.utils.message-bus.MessageBussrc.runner.interfaces.TaskInit→src.utils.message-bus.MessageBussrc.runner.interfaces.TestRunControllerInit→src.utils.message-bus.MessageBus
- Direction
- runner.interfaces uses utils.message-bus, so a change to utils.message-bus can break runner.interfaces, while a change to runner.interfaces can't break utils.message-bus.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→15 runner.interfaces uses api.structure.test✕
- Connections
- 2 pairs of types, where a type in runner.interfaces uses a type in api.structure.test.
- The types involved
src.runner.interfaces.TestRunControllerInit→src.api.structure.test.Testsrc.runner.interfaces.TestRunInit→src.api.structure.test.Test
- Direction
- runner.interfaces uses api.structure.test, so a change to api.structure.test can break runner.interfaces, while a change to runner.interfaces can't break api.structure.test.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→24 runner.interfaces uses configuration.testcafe-configuration✕
- Connections
- 1 pair of types, where a type in runner.interfaces uses a type in configuration.testcafe-configuration.
- The types involved
src.runner.interfaces.BootstrapperInit→src.configuration.testcafe-configuration.TestCafeConfiguration
- Direction
- runner.interfaces uses configuration.testcafe-configuration, so a change to configuration.testcafe-configuration can break runner.interfaces, while a change to runner.interfaces can't break configuration.testcafe-configuration.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→26 runner.interfaces uses runner.fixture-hook-controller✕
- Connections
- 2 pairs of types, where a type in runner.interfaces uses a type in runner.fixture-hook-controller.
- The types involved
src.runner.interfaces.BrowserJobInit→src.runner.fixture-hook-controller.FixtureHookControllersrc.runner.interfaces.TestRunControllerInit→src.runner.fixture-hook-controller.FixtureHookController
- Direction
- runner.interfaces uses runner.fixture-hook-controller, so a change to runner.fixture-hook-controller can break runner.interfaces, while a change to runner.interfaces can't break runner.fixture-hook-controller.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→27 runner.interfaces uses browser.connection.gateway✕
- Connections
- 1 pair of types, where a type in runner.interfaces uses a type in browser.connection.gateway.
- The types involved
src.runner.interfaces.BootstrapperInit→src.browser.connection.gateway.BrowserConnectionGateway
- Direction
- runner.interfaces uses browser.connection.gateway, so a change to browser.connection.gateway can break runner.interfaces, while a change to runner.interfaces can't break browser.connection.gateway.
- Position
- Below the diagonal: runner.interfaces uses a module listed above it, which is the healthy direction.
28→31 runner.interfaces uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in runner.interfaces uses a type in browser.connection.
- The types involved
src.runner.interfaces.TestRunInit→src.browser.connection.BrowserConnection
- Direction
- runner.interfaces uses browser.connection, so a change to browser.connection can break runner.interfaces, while a change to runner.interfaces can't break browser.connection.
- 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.
29→3 runner.test-run-controller uses configuration.types✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in configuration.types.
- The types involved
src.runner.test-run-controller.TestRunController→src.configuration.types.OptionValue
- Direction
- runner.test-run-controller uses configuration.types, so a change to configuration.types can break runner.test-run-controller, while a change to runner.test-run-controller can't break configuration.types.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→6 runner.test-run-controller uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in notifications.warning-log.
- The types involved
src.runner.test-run-controller.TestRunController→src.notifications.warning-log.WarningLog
- Direction
- runner.test-run-controller uses notifications.warning-log, so a change to notifications.warning-log can break runner.test-run-controller, while a change to runner.test-run-controller can't break notifications.warning-log.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→7 runner.test-run-controller uses utils.async-event-emitter✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in utils.async-event-emitter.
- The types involved
src.runner.test-run-controller.TestRunController→src.utils.async-event-emitter.AsyncEventEmitter
- Direction
- runner.test-run-controller uses utils.async-event-emitter, so a change to utils.async-event-emitter can break runner.test-run-controller, while a change to runner.test-run-controller can't break utils.async-event-emitter.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→11 runner.test-run-controller uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in configuration.interfaces.
- The types involved
src.runner.test-run-controller.TestRunController→src.configuration.interfaces.Dictionary
- Direction
- runner.test-run-controller uses configuration.interfaces, so a change to configuration.interfaces can break runner.test-run-controller, while a change to runner.test-run-controller can't break configuration.interfaces.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→12 runner.test-run-controller uses utils.message-bus✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in utils.message-bus.
- The types involved
src.runner.test-run-controller.TestRunController→src.utils.message-bus.MessageBus
- Direction
- runner.test-run-controller uses utils.message-bus, so a change to utils.message-bus can break runner.test-run-controller, while a change to runner.test-run-controller can't break utils.message-bus.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→15 runner.test-run-controller uses api.structure.test✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in api.structure.test.
- The types involved
src.runner.test-run-controller.TestRunController→src.api.structure.test.Test
- Direction
- runner.test-run-controller uses api.structure.test, so a change to api.structure.test can break runner.test-run-controller, while a change to runner.test-run-controller can't break api.structure.test.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→26 runner.test-run-controller uses runner.fixture-hook-controller✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in runner.fixture-hook-controller.
- The types involved
src.runner.test-run-controller.TestRunController→src.runner.fixture-hook-controller.FixtureHookController
- Direction
- runner.test-run-controller uses runner.fixture-hook-controller, so a change to runner.fixture-hook-controller can break runner.test-run-controller, while a change to runner.test-run-controller can't break runner.fixture-hook-controller.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→28 runner.test-run-controller uses runner.interfaces✕
- Connections
- 2 pairs of types, where a type in runner.test-run-controller uses a type in runner.interfaces.
- The types involved
src.runner.test-run-controller.TestRunController→src.runner.interfaces.ActionEventArgsrc.runner.test-run-controller.TestRunController→src.runner.interfaces.TestRunControllerInit
- Direction
- runner.test-run-controller uses runner.interfaces, so a change to runner.interfaces can break runner.test-run-controller, while a change to runner.test-run-controller can't break runner.interfaces.
- Position
- Below the diagonal: runner.test-run-controller uses a module listed above it, which is the healthy direction.
29→31 runner.test-run-controller uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in runner.test-run-controller uses a type in browser.connection.
- The types involved
src.runner.test-run-controller.TestRunController→src.browser.connection.BrowserConnection
- Direction
- runner.test-run-controller uses browser.connection, so a change to browser.connection can break runner.test-run-controller, while a change to runner.test-run-controller can't break browser.connection.
- 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.
30→3 runner.browser-job uses configuration.types✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in configuration.types.
- The types involved
src.runner.browser-job.BrowserJob→src.configuration.types.OptionValue
- Direction
- runner.browser-job uses configuration.types, so a change to configuration.types can break runner.browser-job, while a change to runner.browser-job can't break configuration.types.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→6 runner.browser-job uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in notifications.warning-log.
- The types involved
src.runner.browser-job.BrowserJob→src.notifications.warning-log.WarningLog
- Direction
- runner.browser-job uses notifications.warning-log, so a change to notifications.warning-log can break runner.browser-job, while a change to runner.browser-job can't break notifications.warning-log.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→7 runner.browser-job uses utils.async-event-emitter✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in utils.async-event-emitter.
- The types involved
src.runner.browser-job.BrowserJob→src.utils.async-event-emitter.AsyncEventEmitter
- Direction
- runner.browser-job uses utils.async-event-emitter, so a change to utils.async-event-emitter can break runner.browser-job, while a change to runner.browser-job can't break utils.async-event-emitter.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→11 runner.browser-job uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in configuration.interfaces.
- The types involved
src.runner.browser-job.BrowserJob→src.configuration.interfaces.Dictionary
- Direction
- runner.browser-job uses configuration.interfaces, so a change to configuration.interfaces can break runner.browser-job, while a change to runner.browser-job can't break configuration.interfaces.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→12 runner.browser-job uses utils.message-bus✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in utils.message-bus.
- The types involved
src.runner.browser-job.BrowserJob→src.utils.message-bus.MessageBus
- Direction
- runner.browser-job uses utils.message-bus, so a change to utils.message-bus can break runner.browser-job, while a change to runner.browser-job can't break utils.message-bus.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→15 runner.browser-job uses api.structure.test✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in api.structure.test.
- The types involved
src.runner.browser-job.BrowserJob→src.api.structure.test.Test
- Direction
- runner.browser-job uses api.structure.test, so a change to api.structure.test can break runner.browser-job, while a change to runner.browser-job can't break api.structure.test.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→26 runner.browser-job uses runner.fixture-hook-controller✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in runner.fixture-hook-controller.
- The types involved
src.runner.browser-job.BrowserJob→src.runner.fixture-hook-controller.FixtureHookController
- Direction
- runner.browser-job uses runner.fixture-hook-controller, so a change to runner.fixture-hook-controller can break runner.browser-job, while a change to runner.browser-job can't break runner.fixture-hook-controller.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→28 runner.browser-job uses runner.interfaces✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in runner.interfaces.
- The types involved
src.runner.browser-job.BrowserJob→src.runner.interfaces.BrowserJobInit
- Direction
- runner.browser-job uses runner.interfaces, so a change to runner.interfaces can break runner.browser-job, while a change to runner.browser-job can't break runner.interfaces.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→29 runner.browser-job uses runner.test-run-controller✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in runner.test-run-controller.
- The types involved
src.runner.browser-job.BrowserJob→src.runner.test-run-controller.TestRunController
- Direction
- runner.browser-job uses runner.test-run-controller, so a change to runner.test-run-controller can break runner.browser-job, while a change to runner.browser-job can't break runner.test-run-controller.
- Position
- Below the diagonal: runner.browser-job uses a module listed above it, which is the healthy direction.
30→31 runner.browser-job uses browser.connection part of a loop✕
- Connections
- 1 pair of types, where a type in runner.browser-job uses a type in browser.connection.
- The types involved
src.runner.browser-job.BrowserJob→src.browser.connection.BrowserConnection
- Direction
- runner.browser-job uses browser.connection, so a change to browser.connection can break runner.browser-job, while a change to runner.browser-job can't break browser.connection.
- 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.
31→5 browser.connection uses native-automation.types✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in native-automation.types.
- The types involved
src.browser.connection.BrowserConnection→src.native-automation.types.EventType
- Direction
- browser.connection uses native-automation.types, so a change to native-automation.types can break browser.connection, while a change to browser.connection can't break native-automation.types.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→6 browser.connection uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in notifications.warning-log.
- The types involved
src.browser.connection.BrowserConnection→src.notifications.warning-log.WarningLog
- Direction
- browser.connection uses notifications.warning-log, so a change to notifications.warning-log can break browser.connection, while a change to browser.connection can't break notifications.warning-log.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→12 browser.connection uses utils.message-bus✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in utils.message-bus.
- The types involved
src.browser.connection.BrowserConnection→src.utils.message-bus.MessageBus
- Direction
- browser.connection uses utils.message-bus, so a change to utils.message-bus can break browser.connection, while a change to browser.connection can't break utils.message-bus.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→16 browser.connection uses browser.provider✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in browser.provider.
- The types involved
src.browser.connection.BrowserInfo→src.browser.provider.BrowserProvider
- Direction
- browser.connection uses browser.provider, so a change to browser.provider can break browser.connection, while a change to browser.connection can't break browser.provider.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→19 browser.connection uses client.core.utils.event-emitter✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in client.core.utils.event-emitter.
- The types involved
src.browser.connection.BrowserConnection→src.client.core.utils.event-emitter.EventEmitter
- Direction
- browser.connection uses client.core.utils.event-emitter, so a change to client.core.utils.event-emitter can break browser.connection, while a change to browser.connection can't break client.core.utils.event-emitter.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→27 browser.connection uses browser.connection.gateway✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in browser.connection.gateway.
- The types involved
src.browser.connection.BrowserConnection→src.browser.connection.gateway.BrowserConnectionGateway
- Direction
- browser.connection uses browser.connection.gateway, so a change to browser.connection.gateway can break browser.connection, while a change to browser.connection can't break browser.connection.gateway.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→28 browser.connection uses runner.interfaces✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in runner.interfaces.
- The types involved
src.browser.connection.get-hints→src.runner.interfaces.BrowserSetOptions
- Direction
- browser.connection uses runner.interfaces, so a change to runner.interfaces can break browser.connection, while a change to browser.connection can't break runner.interfaces.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
31→30 browser.connection uses runner.browser-job✕
- Connections
- 1 pair of types, where a type in browser.connection uses a type in runner.browser-job.
- The types involved
src.browser.connection.BrowserConnection→src.runner.browser-job.BrowserJob
- Direction
- browser.connection uses runner.browser-job, so a change to runner.browser-job can break browser.connection, while a change to browser.connection can't break runner.browser-job.
- Position
- Below the diagonal: browser.connection uses a module listed above it, which is the healthy direction.
32→3 runner.task uses configuration.types✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in configuration.types.
- The types involved
src.runner.task.Task→src.configuration.types.OptionValue
- Direction
- runner.task uses configuration.types, so a change to configuration.types can break runner.task, while a change to runner.task can't break configuration.types.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→6 runner.task uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in notifications.warning-log.
- The types involved
src.runner.task.Task→src.notifications.warning-log.WarningLog
- Direction
- runner.task uses notifications.warning-log, so a change to notifications.warning-log can break runner.task, while a change to runner.task can't break notifications.warning-log.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→7 runner.task uses utils.async-event-emitter✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in utils.async-event-emitter.
- The types involved
src.runner.task.Task→src.utils.async-event-emitter.AsyncEventEmitter
- Direction
- runner.task uses utils.async-event-emitter, so a change to utils.async-event-emitter can break runner.task, while a change to runner.task can't break utils.async-event-emitter.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→11 runner.task uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in configuration.interfaces.
- The types involved
src.runner.task.Task→src.configuration.interfaces.Dictionary
- Direction
- runner.task uses configuration.interfaces, so a change to configuration.interfaces can break runner.task, while a change to runner.task can't break configuration.interfaces.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→12 runner.task uses utils.message-bus✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in utils.message-bus.
- The types involved
src.runner.task.Task→src.utils.message-bus.MessageBus
- Direction
- runner.task uses utils.message-bus, so a change to utils.message-bus can break runner.task, while a change to runner.task can't break utils.message-bus.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→21 runner.task uses video-recorder.videos✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in video-recorder.videos.
- The types involved
src.runner.task.Task→src.video-recorder.videos.Videos
- Direction
- runner.task uses video-recorder.videos, so a change to video-recorder.videos can break runner.task, while a change to runner.task can't break video-recorder.videos.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→26 runner.task uses runner.fixture-hook-controller✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in runner.fixture-hook-controller.
- The types involved
src.runner.task.Task→src.runner.fixture-hook-controller.FixtureHookController
- Direction
- runner.task uses runner.fixture-hook-controller, so a change to runner.fixture-hook-controller can break runner.task, while a change to runner.task can't break runner.fixture-hook-controller.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→28 runner.task uses runner.interfaces✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in runner.interfaces.
- The types involved
src.runner.task.Task→src.runner.interfaces.TaskInit
- Direction
- runner.task uses runner.interfaces, so a change to runner.interfaces can break runner.task, while a change to runner.task can't break runner.interfaces.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
32→30 runner.task uses runner.browser-job✕
- Connections
- 1 pair of types, where a type in runner.task uses a type in runner.browser-job.
- The types involved
src.runner.task.Task→src.runner.browser-job.BrowserJob
- Direction
- runner.task uses runner.browser-job, so a change to runner.browser-job can break runner.task, while a change to runner.task can't break runner.browser-job.
- Position
- Below the diagonal: runner.task uses a module listed above it, which is the healthy direction.
33→24 cli.remotes-wizard uses configuration.testcafe-configuration✕
- Connections
- 1 pair of types, where a type in cli.remotes-wizard uses a type in configuration.testcafe-configuration.
- The types involved
src.cli.remotes-wizard.TestCafe→src.configuration.testcafe-configuration.TestCafeConfiguration
- Direction
- cli.remotes-wizard uses configuration.testcafe-configuration, so a change to configuration.testcafe-configuration can break cli.remotes-wizard, while a change to cli.remotes-wizard can't break configuration.testcafe-configuration.
- Position
- Below the diagonal: cli.remotes-wizard uses a module listed above it, which is the healthy direction.
33→27 cli.remotes-wizard uses browser.connection.gateway✕
- Connections
- 1 pair of types, where a type in cli.remotes-wizard uses a type in browser.connection.gateway.
- The types involved
src.cli.remotes-wizard.TestCafe→src.browser.connection.gateway.BrowserConnectionGateway
- Direction
- cli.remotes-wizard uses browser.connection.gateway, so a change to browser.connection.gateway can break cli.remotes-wizard, while a change to cli.remotes-wizard can't break browser.connection.gateway.
- Position
- Below the diagonal: cli.remotes-wizard uses a module listed above it, which is the healthy direction.
33→31 cli.remotes-wizard uses browser.connection✕
- Connections
- 1 pair of types, where a type in cli.remotes-wizard uses a type in browser.connection.
- The types involved
src.cli.remotes-wizard.TestCafe→src.browser.connection.BrowserConnection
- Direction
- cli.remotes-wizard uses browser.connection, so a change to browser.connection can break cli.remotes-wizard, while a change to cli.remotes-wizard can't break browser.connection.
- Position
- Below the diagonal: cli.remotes-wizard uses a module listed above it, which is the healthy direction.
34→5 native-automation.request-pipeline.test-run-bridge uses native-automation.types✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline.test-run-bridge uses a type in native-automation.types.
- The types involved
src.native-automation.request-pipeline.test-run-bridge.TestRunBridge→src.native-automation.types.InjectableResourcesOptions
- Direction
- native-automation.request-pipeline.test-run-bridge uses native-automation.types, so a change to native-automation.types can break native-automation.request-pipeline.test-run-bridge, while a change to native-automation.request-pipeline.test-run-bridge can't break native-automation.types.
- Position
- Below the diagonal: native-automation.request-pipeline.test-run-bridge uses a module listed above it, which is the healthy direction.
34→31 native-automation.request-pipeline.test-run-bridge uses browser.connection✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline.test-run-bridge uses a type in browser.connection.
- The types involved
src.native-automation.request-pipeline.test-run-bridge.TestRunBridge→src.browser.connection.BrowserConnection
- Direction
- native-automation.request-pipeline.test-run-bridge uses browser.connection, so a change to browser.connection can break native-automation.request-pipeline.test-run-bridge, while a change to native-automation.request-pipeline.test-run-bridge can't break browser.connection.
- Position
- Below the diagonal: native-automation.request-pipeline.test-run-bridge uses a module listed above it, which is the healthy direction.
35→11 reporter uses configuration.interfaces✕
- Connections
- 2 pairs of types, where a type in reporter uses a type in configuration.interfaces.
- The types involved
src.reporter.TestInfo→src.configuration.interfaces.Dictionarysrc.reporter.TestRunInfo→src.configuration.interfaces.Dictionary
- Direction
- reporter uses configuration.interfaces, so a change to configuration.interfaces can break reporter, while a change to reporter can't break configuration.interfaces.
- Position
- Below the diagonal: reporter uses a module listed above it, which is the healthy direction.
35→12 reporter uses utils.message-bus✕
- Connections
- 2 pairs of types, where a type in reporter uses a type in utils.message-bus.
- The types involved
src.reporter.Reporter→src.utils.message-bus.MessageBussrc.reporter.ReporterOptions→src.utils.message-bus.MessageBus
- Direction
- reporter uses utils.message-bus, so a change to utils.message-bus can break reporter, while a change to reporter can't break utils.message-bus.
- Position
- Below the diagonal: reporter uses a module listed above it, which is the healthy direction.
35→14 reporter uses api.structure.fixture✕
- Connections
- 1 pair of types, where a type in reporter uses a type in api.structure.fixture.
- The types involved
src.reporter.TestInfo→src.api.structure.fixture.Fixture
- Direction
- reporter uses api.structure.fixture, so a change to api.structure.fixture can break reporter, while a change to reporter can't break api.structure.fixture.
- Position
- Below the diagonal: reporter uses a module listed above it, which is the healthy direction.
35→15 reporter uses api.structure.test✕
- Connections
- 2 pairs of types, where a type in reporter uses a type in api.structure.test.
- The types involved
src.reporter.Reporter→src.api.structure.test.Testsrc.reporter.TestInfo→src.api.structure.test.Test
- Direction
- reporter uses api.structure.test, so a change to api.structure.test can break reporter, while a change to reporter can't break api.structure.test.
- Position
- Below the diagonal: reporter uses a module listed above it, which is the healthy direction.
35→32 reporter uses runner.task✕
- Connections
- 1 pair of types, where a type in reporter uses a type in runner.task.
- The types involved
src.reporter.Reporter→src.runner.task.Task
- Direction
- reporter uses runner.task, so a change to runner.task can break reporter, while a change to reporter can't break runner.task.
- Position
- Below the diagonal: reporter uses a module listed above it, which is the healthy direction.
36→19 runner.browser-set uses client.core.utils.event-emitter✕
- Connections
- 1 pair of types, where a type in runner.browser-set uses a type in client.core.utils.event-emitter.
- The types involved
src.runner.browser-set.BrowserSet→src.client.core.utils.event-emitter.EventEmitter
- Direction
- runner.browser-set uses client.core.utils.event-emitter, so a change to client.core.utils.event-emitter can break runner.browser-set, while a change to runner.browser-set can't break client.core.utils.event-emitter.
- Position
- Below the diagonal: runner.browser-set uses a module listed above it, which is the healthy direction.
36→28 runner.browser-set uses runner.interfaces✕
- Connections
- 1 pair of types, where a type in runner.browser-set uses a type in runner.interfaces.
- The types involved
src.runner.browser-set.BrowserSet→src.runner.interfaces.BrowserSetOptions
- Direction
- runner.browser-set uses runner.interfaces, so a change to runner.interfaces can break runner.browser-set, while a change to runner.browser-set can't break runner.interfaces.
- Position
- Below the diagonal: runner.browser-set uses a module listed above it, which is the healthy direction.
36→31 runner.browser-set uses browser.connection✕
- Connections
- 1 pair of types, where a type in runner.browser-set uses a type in browser.connection.
- The types involved
src.runner.browser-set.BrowserSet→src.browser.connection.BrowserConnection
- Direction
- runner.browser-set uses browser.connection, so a change to browser.connection can break runner.browser-set, while a change to runner.browser-set can't break browser.connection.
- Position
- Below the diagonal: runner.browser-set uses a module listed above it, which is the healthy direction.
37→11 utils uses configuration.interfaces✕
- Connections
- 2 pairs of types, where a type in utils uses a type in configuration.interfaces.
- The types involved
src.utils.diff→src.configuration.interfaces.Dictionarysrc.utils.lowercase-object-keys→src.configuration.interfaces.Dictionary
- Direction
- utils uses configuration.interfaces, so a change to configuration.interfaces can break utils, while a change to utils can't break configuration.interfaces.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
37→31 utils uses browser.connection✕
- Connections
- 1 pair of types, where a type in utils uses a type in browser.connection.
- The types involved
src.utils.get-browser→src.browser.connection.BrowserConnection
- Direction
- utils uses browser.connection, so a change to browser.connection can break utils, while a change to utils can't break browser.connection.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
38→11 native-automation.request-pipeline.context-info uses configuration.interfaces✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline.context-info uses a type in configuration.interfaces.
- The types involved
src.native-automation.request-pipeline.context-info.NativeAutomationRequestContextInfo→src.configuration.interfaces.Dictionary
- Direction
- native-automation.request-pipeline.context-info uses configuration.interfaces, so a change to configuration.interfaces can break native-automation.request-pipeline.context-info, while a change to native-automation.request-pipeline.context-info can't break configuration.interfaces.
- Position
- Below the diagonal: native-automation.request-pipeline.context-info uses a module listed above it, which is the healthy direction.
38→34 native-automation.request-pipeline.context-info uses native-automation.request-pipeline.test-run-bridge✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline.context-info uses a type in native-automation.request-pipeline.test-run-bridge.
- The types involved
src.native-automation.request-pipeline.context-info.NativeAutomationRequestContextInfo→src.native-automation.request-pipeline.test-run-bridge.TestRunBridge
- Direction
- native-automation.request-pipeline.context-info uses native-automation.request-pipeline.test-run-bridge, so a change to native-automation.request-pipeline.test-run-bridge can break native-automation.request-pipeline.context-info, while a change to native-automation.request-pipeline.context-info can't break native-automation.request-pipeline.test-run-bridge.
- Position
- Below the diagonal: native-automation.request-pipeline.context-info uses a module listed above it, which is the healthy direction.
39→3 runner.bootstrapper uses configuration.types✕
- Connections
- 1 pair of types, where a type in runner.bootstrapper uses a type in configuration.types.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.configuration.types.GlobalHooks
- Direction
- runner.bootstrapper uses configuration.types, so a change to configuration.types can break runner.bootstrapper, while a change to runner.bootstrapper can't break configuration.types.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→6 runner.bootstrapper uses notifications.warning-log✕
- Connections
- 1 pair of types, where a type in runner.bootstrapper uses a type in notifications.warning-log.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.notifications.warning-log.WarningLog
- Direction
- runner.bootstrapper uses notifications.warning-log, so a change to notifications.warning-log can break runner.bootstrapper, while a change to runner.bootstrapper can't break notifications.warning-log.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→12 runner.bootstrapper uses utils.message-bus✕
- Connections
- 1 pair of types, where a type in runner.bootstrapper uses a type in utils.message-bus.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.utils.message-bus.MessageBus
- Direction
- runner.bootstrapper uses utils.message-bus, so a change to utils.message-bus can break runner.bootstrapper, while a change to runner.bootstrapper can't break utils.message-bus.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→24 runner.bootstrapper uses configuration.testcafe-configuration✕
- Connections
- 2 pairs of types, where a type in runner.bootstrapper uses a type in configuration.testcafe-configuration.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.configuration.testcafe-configuration.BrowserInfoSourcesrc.runner.bootstrapper.Bootstrapper→src.configuration.testcafe-configuration.TestCafeConfiguration
- Direction
- runner.bootstrapper uses configuration.testcafe-configuration, so a change to configuration.testcafe-configuration can break runner.bootstrapper, while a change to runner.bootstrapper can't break configuration.testcafe-configuration.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→27 runner.bootstrapper uses browser.connection.gateway✕
- Connections
- 1 pair of types, where a type in runner.bootstrapper uses a type in browser.connection.gateway.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.browser.connection.gateway.BrowserConnectionGateway
- Direction
- runner.bootstrapper uses browser.connection.gateway, so a change to browser.connection.gateway can break runner.bootstrapper, while a change to runner.bootstrapper can't break browser.connection.gateway.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→28 runner.bootstrapper uses runner.interfaces✕
- Connections
- 2 pairs of types, where a type in runner.bootstrapper uses a type in runner.interfaces.
- The types involved
src.runner.bootstrapper.Bootstrapper→src.runner.interfaces.BootstrapperInitsrc.runner.bootstrapper.Bootstrapper→src.runner.interfaces.BrowserSetOptions
- Direction
- runner.bootstrapper uses runner.interfaces, so a change to runner.interfaces can break runner.bootstrapper, while a change to runner.bootstrapper can't break runner.interfaces.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
39→36 runner.bootstrapper uses runner.browser-set✕
- Connections
- 2 pairs of types, where a type in runner.bootstrapper uses a type in runner.browser-set.
- The types involved
src.runner.bootstrapper.BasicRuntimeResources→src.runner.browser-set.BrowserSetsrc.runner.bootstrapper.Bootstrapper→src.runner.browser-set.BrowserSet
- Direction
- runner.bootstrapper uses runner.browser-set, so a change to runner.browser-set can break runner.bootstrapper, while a change to runner.bootstrapper can't break runner.browser-set.
- Position
- Below the diagonal: runner.bootstrapper uses a module listed above it, which is the healthy direction.
40→5 native-automation.request-pipeline uses native-automation.types✕
- Connections
- 7 pairs of types, where a type in native-automation.request-pipeline uses a type in native-automation.types.
- The types involved
src.native-automation.request-pipeline.NativeAutomationRequestPipeline→src.native-automation.types.ContinueRequestArgssrc.native-automation.request-pipeline.NativeAutomationRequestPipeline→src.native-automation.types.SessionIdsrc.native-automation.request-pipeline.NativeAutomationRequestPipeline→src.native-automation.types.SpecialServiceRoutessrc.native-automation.request-pipeline.safe-api→src.native-automation.types.ContinueRequestArgssrc.native-automation.request-pipeline.safe-api→src.native-automation.types.SessionIdsrc.native-automation.request-pipeline.special-handlers→src.native-automation.types.SessionIdsrc.native-automation.request-pipeline.special-handlers→src.native-automation.types.SpecialServiceRoutes
- Direction
- native-automation.request-pipeline uses native-automation.types, so a change to native-automation.types can break native-automation.request-pipeline, while a change to native-automation.request-pipeline can't break native-automation.types.
- Position
- Below the diagonal: native-automation.request-pipeline uses a module listed above it, which is the healthy direction.
40→34 native-automation.request-pipeline uses native-automation.request-pipeline.test-run-bridge✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline uses a type in native-automation.request-pipeline.test-run-bridge.
- The types involved
src.native-automation.request-pipeline.NativeAutomationRequestPipeline→src.native-automation.request-pipeline.test-run-bridge.TestRunBridge
- Direction
- native-automation.request-pipeline uses native-automation.request-pipeline.test-run-bridge, so a change to native-automation.request-pipeline.test-run-bridge can break native-automation.request-pipeline, while a change to native-automation.request-pipeline can't break native-automation.request-pipeline.test-run-bridge.
- Position
- Below the diagonal: native-automation.request-pipeline uses a module listed above it, which is the healthy direction.
40→38 native-automation.request-pipeline uses native-automation.request-pipeline.context-info✕
- Connections
- 1 pair of types, where a type in native-automation.request-pipeline uses a type in native-automation.request-pipeline.context-info.
- The types involved
src.native-automation.request-pipeline.NativeAutomationRequestPipeline→src.native-automation.request-pipeline.context-info.NativeAutomationRequestContextInfo
- Direction
- native-automation.request-pipeline uses native-automation.request-pipeline.context-info, so a change to native-automation.request-pipeline.context-info can break native-automation.request-pipeline, while a change to native-automation.request-pipeline can't break native-automation.request-pipeline.context-info.
- Position
- Below the diagonal: native-automation.request-pipeline uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 127 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 41 | High / Critical |
| A02:2025 — Security Misconfiguration | 2 | Medium |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Begin by addressing the single leaked secret in REDACTED to immediately secure the codebase. Next, update the 14 deprecated and 14 outdated dependencies in REDACTED and package.json to maintain system hygiene. Finally, improve test reliability by adding assertions to the 1501 empty test cases, prioritizing REDACTED, api-test.js, and REDACTED, and then resolve the 112 empty test files starting with testfile.js.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +11.4 pts | Low | Secret Scanning |
| Resolve the 1501 No assertions finding(s) in Test Quality — start with REDACTED (735), api-test.js (80), REDACTED (59). | +13.0 pts | High | Test Quality |
| Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (14). | +6.5 pts | Medium | Dependency Hygiene |
| Resolve the 14 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (14). | +6.5 pts | Medium | Dependency Hygiene |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +2.7 pts | Low | Project Cohesion |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +4.6 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +4.6 pts | Medium | Dependency Hygiene |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.1 pts | Low | ADR Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 0.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| test/functional/fixtures/regression/gh-2568/testcafe-fixtures/index.js | 5.0 | Mixed | Test Quality: No assertions (empty test): custom methods |
| test/functional/fixtures/regression/gh-2011/testcafe-fixtures/concurrency-mode-with-disable-concurrency-fixture-test.js | 5.0 | Mixed | Test Quality: No assertions (empty test): concurrent test ${i} |
| test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/skip-test.js | 5.0 | Mixed | Test Quality: No assertions (empty test): Fixture5Test5 |
| test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/only-test.js | 5.0 | Mixed | Test Quality: No assertions (empty test): Fixture5Test5 |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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. 72 of 72 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 72 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2346 of 2404 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, 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.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- 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 JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — examples/basic/ (testcafe), examples/running-tests-in-chrome-using-bitbucket-pipelines-ci/ (testcafe), examples/running-tests-in-firefox-and-chrome-using-travis-ci/ (testcafe) — a gap in the analyzer, not something this repository is missing. 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 source is present (.ts, .js, .jsx, .tsx, .mjs) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but every JavaScript/TypeScript test package this repository declares runs its suite in a real browser, which the re-runner has no way to launch. `examples/basic` declares `testcafe` and its `scripts.test` is `testcafe all REDACTED`; `examples/running-tests-in-chrome-using-bitbucket-pipelines-ci` declares `testcafe` and its `scripts.test` is `testcafe 'chromium:headless --disable-setuid-sandbox --window-size=1920x1080' tests/index-test.js --app "node server.js"`; `examples/running-tests-in-firefox-and-chrome-using-travis-ci` declares `testcafe` and its `scripts.test` is `testcafe chrome,firefox tests/index-test.js --app "node server.js"`; `examples/running-tests-using-travis-and-saucelabs` declares `testcafe` and its `scripts.test` is `testcafe "saucelabs:Chrome@beta:Windows 10" tests/index-test.js --app "node server.js"`; `examples/using-assertions` declares `testcafe` and its `scripts.test` is `testcafe all REDACTED`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's browser-driven test support, not a missing .ts/.js/.jsx/.tsx/.mjs runner and not a finding about this repository.
- 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.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `@types/indent-string/index.d.ts`, `@types/promisify-event/index.d.ts`, `@types/time-limit-promise/index.d.ts`, `@types/unquote/index.d.ts`, `src/configuration/types.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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 REDACTED (REDACTED). docker build failed (exit 1) — 3 | 4 | COPY ${packageId} /opt/testcafe/${packageId} 5 | >>> COPY docker/testcafe-docker.sh /opt/testcafe/docker/testcafe-docker.sh 6 | 7 | ENV ALPINE_REPOS="\ -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 5ce6b7a7-ab88-443e-8e41-87c8e7b7baca::l8gyfbn5y8n5j8e7rzckgljyw: "/docker/testcafe-docker.sh": not found; runtime evidence skipped.
- 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
- 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), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- 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. 54 further occurrence(s) are not listed individually; the score already reflects all 94.
- 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. 174 further occurrence(s) are not listed individually; the score already reflects all 214.
- 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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 508 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
- 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 make no call through a named logger, 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.
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
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was addHierarchicalSelectors at 31. A further 2 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 add-api.addHierarchicalSelectors at 31 — they are counted neither in the figure above nor in this dimension's score. 2 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: REDACTED (add-api.addHierarchicalSelectors at 31), src/assertions/get-fn.ts (get-fn.getFn at 17). 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.
What to do
- Bring the 23 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with addHierarchicalSelectors (cyclomatic 31), Driver._executeCommand (cyclomatic 28), _executeCommand (cyclomatic 28). — 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 23 together lifts Cyclomatic Complexity from 7.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
36 method(s) exceeded the cognitive complexity threshold of 15; the worst was correctContentEditableSelectionBeforeDelete at 41.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with correctContentEditableSelectionBeforeDelete (cognitive 41), text-selection.correctContentEditableSelectionBeforeDelete (cognitive 37), addHierarchicalSelectors (cognitive 36). — 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 3 together lifts Cognitive Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
11 god class(es) detected.
What to do
- Resolve the 6 TooManyMethods finding(s) in God Classes — start with REDACTED (3), driver.js, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with driver.js, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with driver.js, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
3 of 156 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with fixture.ts, test.ts, live-test.js. — One of this dimension's main actionable groups (3 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.
D9 · Test Distribution
3530 test methods: 3530 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 3530 `it`/`test` case(s) across 858 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
29 skipped (19 with a documented reason), 1613 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3529 tests.
What to do
- Resolve the 1501 No assertions finding(s) in Test Quality — start with REDACTED (735), api-test.js (80), REDACTED (59). — One of this dimension's main actionable groups (1501 warning-level).
- Resolve the 112 No assertions (empty test) finding(s) in Test Quality — start with testfile.js (47), REDACTED (7), execution-timeout-test.js (5). — One of this dimension's main actionable groups (112 issue-level).
- Resolve the 10 Skipped test finding(s) in Test Quality — start with skipped-tests.js (4), compiler-test.js, test-with-skipped.js. — One of this dimension's main actionable groups (10 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.
D12 · Dependency Hygiene
53 outdated direct production npm dependency(ies) of 98 graded, 0 pinning defect(s), across 6 package.json (1 of them the product) and 6 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 14 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (14). — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 14 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (14). — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 98 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 98 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 75 `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. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/reporter/command/command-formatter.ts. Counted over 187 of the 616 production source files in this repository: 417 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.
D17 · Explicit Debt
16 deducted task-comment markers across 17339 LoC (0.1/KLoC) → score 9.8. 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.
What to do
- Resolve the 12 TodoComment finding(s) in Explicit Debt — start with REDACTED (10), re-executable-promise.ts, test-file.ts. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 4 HackComment finding(s) in Explicit Debt — start with marker-symbol.ts (2), function-transform.ts, REDACTED. — 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
127 finding(s): 0 critical, 98 high, 29 medium, 0 low. 66 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `@types/indent-string/index.d.ts` (line 2), `@types/promisify-event/index.d.ts` (line 4), `@types/time-limit-promise/index.d.ts` (line 2), `@types/unquote/index.d.ts` (line 2), `src/configuration/types.ts` (line 34, line 35) — 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 2 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.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 issue-level).
- No action in Static Analysis (SAST) — all 66 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (66 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 2 high, 1 medium, 2 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
2 finding(s): 0 critical, 0 high, 1 medium, 1 low.
What to do
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
172 of 199 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/client/driver/driver.js. Counted over 199 of the 616 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 169 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (24), REDACTED (13), utils.js (5). — One of this dimension's main actionable groups (169 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with driver.js, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: REDACTED↔option-names.ts 80%; base.js↔REDACTED 80%; REDACTED↔plugin-host.js 61%
What to do
- Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with REDACTED, capturer.js. — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with base.js, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 21 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (21 warning-level).
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 96 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×8) — src/browser/provider/plugin-host.js:72, src/browser/provider/plugin-host.js:76, src/browser/provider/plugin-host.js:91, …
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `setClientInactive` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:286
- `openBrowser` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/browser/provider/plugin-host.js:72
- `closeBrowser` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/browser/provider/plugin-host.js:76
- `init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:81
- `dispose` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:85
- `getBrowserList` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/browser/provider/plugin-host.js:91
- `isValidBrowserName` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:95
- `isLocalBrowser` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:103
- `resizeWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:126
- `canResizeWindowToDimensions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:130
- `takeScreenshot` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:134
- `maximizeWindow` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:138
- `getVideoFrameData` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:148
- `reportJobResult` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:154
- `getOSInfo` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/browser/provider/plugin-host.js:166
- Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×2) — src/client/automation/playback/click/select-child.js:49, src/client/core/select/index.ts:86
- `_getEndPoint` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/client/automation/playback/drag/base.js:41
- `ensureCropOptions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- `restoreChild` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/client/driver/driver-link/window/parent.js:42
- `reportTaskStart` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/reporter/plugin-host.ts:203
- `reportFixtureStart` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/reporter/plugin-host.ts:207
- `reportTestDone` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/reporter/plugin-host.ts:216
- `reportTaskDone` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — src/reporter/plugin-host.ts:220
- `killUnixProcessSoft` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:75
- `killUnixProcessHard` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:79
- `_findFreeTmpDir` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/utils/temp-directory/index.js:34
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×13) — test/functional/fixtures/api/es-next/hooks/testcafe-fixtures/fixture-hooks.js:61, test/functional/fixtures/api/es-next/request-hooks/testcafe-fixtures/api/8229.js:12, test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/skip-test.js:27, …
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.
M1 · Documentation (README)
- 39 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 1 of 6 project(s) that lack one — worth up to 0.3 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- 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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `src/utils/handle-errors.js` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/utils/handle-errors.js:9
- `src/client/browser/service-worker.js` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/client/browser/service-worker.js:30
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 37335 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:60
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `fs.copyFileSync` in `_saveFiles` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/video-recorder/recorder.js:200
- `fs.readFileSync` in `app.get("/transport-worker.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. — test/client/config-qunit-server-app.js:53
- `fs.writeFileSync` in `router.get("/data/file")` 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. — test/functional/site/api.js:47
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
- 321 typed · 378 plain JS — the untyped files are gulp/constants/client-test-settings.js, gulp/constants/functional-test-globs.js, gulp/docker/ensure-docker-environment.js, REDACTED, gulp/docker/get-publish-info.js, gulp/docker/get-publish-tags.js (+372 more). 0 production file(s) opt out entirely with @ts-nocheck · 125 @ts-ignore suppression(s).
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 6 duplicated blocks under src/client/ have copies in at least two of the sibling directories automation, core, driver, ui — 0 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 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. — src/client/automation/playback/click/browser-click-strategy.ts:7
- 5 duplicated blocks under src/client/ui/ have copies in at least two of the sibling directories cursor, progress-panel, status-bar — 1 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/client/ui/progress-panel/index.js:10
- src/client/driver/barriers/request.ts:43 · src/client/driver/barriers/script-execution.ts:29 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/driver/barriers/request.ts:43
- src/client/automation/playback/drag/base.js:131 · src/client/automation/playback/rclick.js:66 — the two spans are one implementation copied and then locally edited — 116 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/drag/base.js:131
- src/client/automation/playback/press/shortcuts.js:244 · src/client/automation/playback/press/shortcuts.js:286 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/automation/playback/press/shortcuts.js:244
- src/client/automation/playback/drag/base.js:45 · src/client/automation/playback/select/base.js:112 — the two spans are one implementation copied and then locally edited — 93 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/drag/base.js:45
- src/reporter/index.ts:632 · src/reporter/index.ts:651 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/reporter/index.ts:632
- src/client/automation/playback/press/shortcuts.js:340 · src/client/automation/playback/press/shortcuts.js:377 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/automation/playback/press/shortcuts.js:340
- REDACTED:361 · REDACTED:379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:361
- src/client/automation/playback/click/select-child.js:12 · src/client/automation/playback/dblclick.js:7 — the two spans are one implementation copied and then locally edited — 82 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/click/select-child.js:12
- REDACTED:587 · REDACTED:614 · REDACTED:646 · REDACTED:683 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:587
- src/client/core/utils/text-selection.js:161 · src/client/core/utils/text-selection.js:176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/core/utils/text-selection.js:161
- src/api/structure/fixture.ts:103 · src/api/structure/fixture.ts:117 · src/api/structure/test.ts:100 · src/api/structure/test.ts:114 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/api/structure/fixture.ts:103
- src/client/core/scroll/index.ts:111 · src/client/core/scroll/index.ts:127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/core/scroll/index.ts:111
- src/browser/connection/gateway/index.ts:139 · src/browser/connection/gateway/index.ts:176 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/browser/connection/gateway/index.ts:139
- REDACTED:663 · REDACTED:741 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:663
- src/client/automation/playback/press/shortcuts.js:178 · src/client/automation/playback/press/shortcuts.js:200 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/automation/playback/press/shortcuts.js:178
- src/client/automation/playback/press/shortcuts.js:367 · src/client/automation/playback/press/shortcuts.js:407 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/automation/playback/press/shortcuts.js:367
- src/client/automation/playback/select/utils.js:171 · src/client/automation/playback/select/utils.js:203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/automation/playback/select/utils.js:171
- REDACTED:319 · REDACTED:345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:319
- src/cli/argument-parser/index.ts:257 · src/cli/argument-parser/index.ts:273 · src/cli/argument-parser/index.ts:316 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/cli/argument-parser/index.ts:257
- src/client/automation/playback/click/select-child.js:96 · src/client/automation/playback/select/base.js:66 — the two spans are one implementation copied and then locally edited — 77 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/click/select-child.js:96
- src/client/automation/playback/move/event-sequence/drag-and-drop-first-move.js:3 · src/client/automation/playback/move/event-sequence/move-event-sequence.js:4 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/move/event-sequence/drag-and-drop-first-move.js:3
- src/browser/connection/gateway/index.ts:211 · src/browser/connection/gateway/index.ts:232 · src/browser/connection/gateway/index.ts:258 — 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. — src/browser/connection/gateway/index.ts:211
- src/browser/provider/built-in/locally-installed.js:1 · src/browser/provider/built-in/path.js:2 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/browser/provider/built-in/locally-installed.js:1
- REDACTED:642 · REDACTED:679 · REDACTED:720 · REDACTED:760 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:642
- src/client/automation/playback/dblclick.js:9 · src/client/automation/playback/rclick.js:10 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/client/automation/playback/dblclick.js:9
- src/client/automation/playback/press/shortcuts.js:227 · src/client/automation/playback/press/shortcuts.js:266 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/automation/playback/press/shortcuts.js:227
- src/client/ui/status-bar/progress-bar/indeterminate-indicator.js:95 · src/client/ui/status-bar/progress-bar/indeterminate-indicator.js:105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/ui/status-bar/progress-bar/indeterminate-indicator.js:95
- src/client/core/utils/text-selection.js:83 · src/client/core/utils/text-selection.js:92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/core/utils/text-selection.js:83
- src/client/driver/command-executors/action-executor/actions-initializer.ts:72 · src/client/driver/command-executors/action-executor/actions-initializer.ts:113 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/driver/command-executors/action-executor/actions-initializer.ts:72
- src/client/driver/driver.js:394 · src/client/driver/driver.js:817 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/driver/driver.js:394
- src/client/core/utils/content-editable.js:76 · src/client/core/utils/content-editable.js:107 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/client/core/utils/content-editable.js:76
- src/runner/fixture-hook-controller.ts:79 · src/runner/fixture-hook-controller.ts:93 — the two spans are one implementation copied and then locally edited — 52 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. — src/runner/fixture-hook-controller.ts:79
- src/cli/argument-parser/index.ts:289 · src/cli/argument-parser/index.ts:298 · src/cli/argument-parser/index.ts:307 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/cli/argument-parser/index.ts:289
- REDACTED:481 · REDACTED:552 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:481
- src/client/core/utils/position.ts:329 · src/client/core/utils/position.ts:377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/client/core/utils/position.ts:329
- src/client/driver/command-executors/execute-selector.js:4 · src/client/driver/command-executors/execute-selector.js:22 — the two spans are one implementation copied and then locally edited — 50 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. — src/client/driver/command-executors/execute-selector.js:4
- REDACTED:538 · REDACTED:555 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:538
- src/assertions/get-fn.ts:29 · src/assertions/get-fn.ts:38 · src/assertions/get-fn.ts:47 — 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. — src/assertions/get-fn.ts:29
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- REDACTED:17 imports test/functional/config.js, 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:17
- REDACTED:19 imports test/dependency-licenses-checker.js, 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:19
- gulp/constants/client-test-settings.js:23 imports test/client/config-qunit-server-app.js, 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. — gulp/constants/client-test-settings.js:23
- src/api/exportable-lib/index.js:64 imports src/api/test-controller/proxy.js, 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. — src/api/exportable-lib/index.js:64
- src/api/request-hooks/hook.ts:11 imports src/errors/test-run/index.js, 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. — src/api/request-hooks/hook.ts:11
- src/api/skip-js-errors/index.ts:5 imports src/test-run/commands/execute-client-function.js, 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. — src/api/skip-js-errors/index.ts:5
- REDACTED:3 imports src/test-run/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. — REDACTED:3
- src/api/wrap-test-function.ts:2 imports src/test-run/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. — src/api/wrap-test-function.ts:2
- src/api/wrap-test-function.ts:5 imports src/errors/test-run/index.js, 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. — src/api/wrap-test-function.ts:5
- src/assertions/executor.ts:4 imports src/errors/test-run/index.js, 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. — src/assertions/executor.ts:4
- src/assertions/executor.ts:7 imports src/test-run/commands/assertion.js, 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. — src/assertions/executor.ts:7
- src/assertions/get-fn.ts:3 imports src/test-run/commands/assertion.js, 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. — src/assertions/get-fn.ts:3
- src/browser/connection/gateway/index.ts:18 imports src/test-run/commands/validations/initializers.js, 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. — src/browser/connection/gateway/index.ts:18
- src/browser/connection/gateway/index.ts:19 imports src/test-run/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. — src/browser/connection/gateway/index.ts:19
- src/browser/connection/index.ts:32 imports src/test-run/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. — src/browser/connection/index.ts:32
- src/client-functions/client-function-builder.js:5 imports src/test-run/commands/execute-client-function.js, 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. — src/client-functions/client-function-builder.js:5
- src/client-functions/client-function-builder.js:12 imports src/test-run/marker-symbol.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. — src/client-functions/client-function-builder.js:12
- src/client-functions/client-function-builder.js:13 imports src/errors/test-run/templates.js, 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. — src/client-functions/client-function-builder.js:13
- src/client-functions/selectors/selector-builder.js:9 imports src/test-run/commands/execute-client-function.js, 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. — src/client-functions/selectors/selector-builder.js:9
- src/client/automation/index.js:17 imports src/test-run/commands/options.js, 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. — src/client/automation/index.js:17
- src/client/automation/move.ts:3 imports src/test-run/commands/options.js, 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. — src/client/automation/move.ts:3
- src/client/automation/playback/click/index.ts:3 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/click/index.ts:3
- src/client/automation/playback/click/select-child.js:5 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/click/select-child.js:5
- src/client/automation/playback/dblclick.js:3 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/dblclick.js:3
- src/client/automation/playback/drag/base.js:11 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/drag/base.js:11
- src/client/automation/playback/move/move.js:3 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/move/move.js:3
- src/client/automation/playback/scroll-into-view.ts:2 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/scroll-into-view.ts:2
- src/client/automation/playback/select/base.js:7 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/select/base.js:7
- src/client/automation/playback/set-scroll.ts:3 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/set-scroll.ts:3
- src/client/automation/playback/type/index.js:3 imports src/test-run/commands/options.js, 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. — src/client/automation/playback/type/index.js:3
- src/client/automation/visible-element-automation.ts:16 imports src/test-run/commands/options.js, 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. — src/client/automation/visible-element-automation.ts:16
- src/client/core/barriers/page-unload-barrier.ts:4 imports src/test-run/client-messages.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. — src/client/core/barriers/page-unload-barrier.ts:4
- src/client/core/scroll/index.ts:8 imports src/test-run/commands/options.js, 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. — src/client/core/scroll/index.ts:8
- src/client/driver/client-browser-console-messages.js:1 imports src/test-run/browser-console-messages.js, 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. — src/client/driver/client-browser-console-messages.js:1
- src/client/driver/command-executors/action-executor/actions-initializer.ts:39 imports src/test-run/commands/type.js, 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. — src/client/driver/command-executors/action-executor/actions-initializer.ts:39
- src/client/driver/command-executors/action-executor/actions-initializer.ts:40 imports src/test-run/commands/base.js, 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. — src/client/driver/command-executors/action-executor/actions-initializer.ts:40
- src/client/driver/command-executors/action-executor/elements-retriever.ts:1 imports src/test-run/commands/execute-client-function.js, 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. — src/client/driver/command-executors/action-executor/elements-retriever.ts:1
- src/client/driver/command-executors/action-executor/index.ts:5 imports src/test-run/commands/base.js, 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. — src/client/driver/command-executors/action-executor/index.ts:5
- src/client/driver/command-executors/browser-manipulation/index.js:26 imports src/test-run/client-messages.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. — src/client/driver/command-executors/browser-manipulation/index.js:26
- src/client/driver/command-executors/browser-manipulation/index.js:27 imports src/test-run/commands/type.js, 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. — src/client/driver/command-executors/browser-manipulation/index.js:27
What to do
- Fix the listed violations: move the shared test helper into a source directory production code may depend on (94 rows).
R2 · Cyclomatic Complexity
- _internalExecuteCommand has cyclomatic complexity 28 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/test-run/index.ts:1134
- _executeCommand has cyclomatic complexity 28 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/driver/driver.js:1701
- correctContentEditableSelectionBeforeDelete has cyclomatic complexity 26 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. — src/client/core/utils/text-selection.js:64
- getHiddenReason has cyclomatic complexity 21 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/core/utils/position.ts:308
- getEventPageCoordinates has cyclomatic complexity 21 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/core/utils/position.ts:154
- runTests has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — test/functional/setup.js:252
- isNodeAfterNodeBlockWithBreakLine has cyclomatic complexity 20 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. — src/client/core/utils/content-editable.js:91
- analyzeMemberExp has cyclomatic complexity 19 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. — src/compiler/test-file/formats/es-next/get-test-list.js:87
- checkChildNodes has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/core/utils/content-editable.js:431
- press has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/automation/playback/press/key-press-simulator.js:78
- (anonymous) has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/automation/utils/utils.js:57
- checkChildNodes has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/core/utils/content-editable.js:482
- checkScreenshotsCreated has cyclomatic complexity 18 and cognitive complexity 16; 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. — test/functional/assertion-helper.js:239
- selectContentEditable has cyclomatic complexity 17 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/core/utils/text-selection.js:18
- _typeChar has cyclomatic complexity 17 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/automation/playback/type/index.js:289
- ensureCropOptions has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- constructor has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/client-functions/selectors/selector-builder.js:18
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- src/client/driver/driver.js has 1558 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/driver/driver.js:1
- src/test-run/index.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. — src/test-run/index.ts:1
- src/test-run/commands/actions.js has 668 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/test-run/commands/actions.js:1
- src/runner/index.js has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/runner/index.js:1
- src/reporter/index.ts has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/reporter/index.ts:1
- REDACTED has 585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- src/browser/connection/index.ts has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/browser/connection/index.ts:1
- src/api/test-controller/index.js has 507 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/api/test-controller/index.js:1
- src/client/core/utils/content-editable.js has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/core/utils/content-editable.js:1
- src/client/automation/playback/press/shortcuts.js has 440 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/client/automation/playback/press/shortcuts.js:1
- REDACTED has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- src/native-automation/request-pipeline/index.ts has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/native-automation/request-pipeline/index.ts:1
- src/cli/argument-parser/index.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/cli/argument-parser/index.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- test/server/data/test-suites/live/test-external-unexisting-module.js:1 imports './non-existing-module', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/server/data/test-suites/live/test-external-unexisting-module.js:1
- test/server/data/test-suites/require-error-in-dep/dep.js:1 imports './yo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/server/data/test-suites/require-error-in-dep/dep.js:1
- test/server/data/test-suites/require-error-in-testfile/testfile.js:1 imports './yo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/server/data/test-suites/require-error-in-testfile/testfile.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. (×37) — src/client/driver/driver.js:1, src/client/core/utils/content-editable.js:1, src/client/automation/playback/press/shortcuts.js:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 96 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but test/server/data/test-suites/live/test-external-unexisting-module.js and 2 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — test/server/data/test-suites/live/test-external-unexisting-module.js:1
What to do
- Add eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
- 1 file(s) (~34 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — test/functional/esm-utils
- Unreachable from the 164 application, 55 tooling and 1287 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (164 application, 55 tooling, 1287 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) — REDACTED, src/utils/check-is-vm.ts, src/compiler/esm-loader.ts, …
- no import path from any entry point (164 application, 55 tooling, 1287 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/utils/diff/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/utils/diff/util.ts
- Nothing imports this binding — it is safe to review for removal. (×4) — src/client/driver/utils/ensure-elements.js:67, src/compiler/babel/preset-stage-2.ts:1, src/native-automation/request-pipeline/safe-api.ts:73, …
- Nothing in its class calls or references this private method — no member access, no string key, no decorator, and no test reaches it by name. A private member cannot be called from outside its class, so this is the whole search: remove it, or call it where it was meant to be used. (×21) — src/api/structure/fixture.ts:65, src/api/structure/fixture.ts:71, src/api/structure/fixture.ts:79, …
- This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — src/browser/connection/index.ts:118
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — eslint.config.js:5, eslint.config.js:4, test/server/browser-connection-test.js:2
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/api/request-hooks/hook.ts → src/notifications/warning-log.ts → src/test-run/index.ts → src/api/request-hooks/hook.ts (one verified cycle inside a mutually-dependent group of 85 files) — src/api/request-hooks/hook.ts:12
- src/errors/error-list.js → src/errors/process-test-fn-error.js → src/errors/error-list.js — src/errors/error-list.js:1
- src/live/controller.ts → src/live/keyboard-observer.ts → src/live/controller.ts (one verified cycle inside a mutually-dependent group of 3 files) — src/live/controller.ts:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
- 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. — src/client/automation/utils/utils.js:57
What to do
- `async` Promise executor
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/client/automation/playback/press/utils.js:80
- `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. — REDACTED:331
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~0.2 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 17616 source line(s) of the 262 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: src/client/core/scroll/index.ts (1), src/client/driver/barriers/request.ts (1), src/client/driver/barriers/script-execution.ts (1). 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 `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate | Strongest area. |
| Architecture | 52% | Adequate — gated by D26, R11, R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 27% | Weak — gated by D10, R5, R6, R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (21 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — docker build failed (exit 1) — 3 | 4 | COPY ${packageId} /opt/testcafe/${packageId} 5 | >>> COPY docker/testcafe-docker.sh /opt/testcafe/docker/testcafe-docker.sh 6 | 7 | ENV ALPINE_REPOS="\ -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 5ce6b7a7-ab88-443e-8e41-87c8e7b7baca::l8gyfbn5y8n5j8e7rzckgljyw: "/docker/testcafe-docker.sh": not found; 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not included — no browser-driven test runner (testcafe)
- 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 — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.html,.js,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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 (.js, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- 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`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: 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.
- S1 Web-Security Posture — Not assessed: 508 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — 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
- 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)
Critical — 224 finding(s)
- No assertions (empty test): (unnamed test) test/server/data/test-suites/typescript-parser-smoke/testfile1.ts:17
- No assertions (empty test): (unnamed test) test/server/data/test-suites/typescript-compile-errors/testfile.ts:9
- No assertions (empty test): TheAnswer test/server/data/test-suites/test-name-is-not-a-string/testfile.js:6
- No assertions (empty test): (unnamed test) test/server/data/test-suites/test-name-is-not-a-string/testfile.js:9
- No assertions (empty test): Dummy test/server/data/test-suites/syntax-error-in-testfile/testfile.js:5
- No assertions (empty test): Dummy test/server/data/test-suites/syntax-error-in-dep/testfile.js:5
- No assertions (empty test): test test/server/data/test-suites/skip-js-errors/fixture-function-with-options-object-argument.js:4
- No assertions (empty test): test test/server/data/test-suites/skip-js-errors/fixture-invalid-argument.js:4
- No assertions (empty test): test test/server/data/test-suites/skip-js-errors/fixture-options-object-argument.js:4
- No assertions (empty test): yo test/server/data/test-suites/selector-with-text-arg-is-not-regexp-or-string/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-with-attr-arg-is-not-regexp-or-string/attrName.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-with-attr-arg-is-not-regexp-or-string/attrValue.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-visibility-check-opt-not-bool/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-timeout-is-not-non-negative-value/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-sibling-incorrect-arg-type/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-prev-sibling-incorrect-arg-type/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-parent-incorrect-arg-type/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-nth-arg-is-nan-value/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-nth-arg-is-infinity-value/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-nth-arg-is-a-number-value/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-next-sibling-incorrect-arg-type/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-find-arg-is-not-a-string-or-function/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-filter-arg-is-not-a-function-or-string/testfile.js:7
- No assertions (empty test): yo test/server/data/test-suites/selector-custom-dom-property-incorrect-arg-type/testfile.js:6
- No assertions (empty test): yo test/server/data/test-suites/selector-custom-dom-method-incorrect-arg-type/testfile.js:6
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: REDACTED ↔ option-names.ts src/cli/argument-parser/index.ts:1
- Boundary-crossing change coupling: capturer.js ↔ browser-manipulation-queue.js src/screenshots/capturer.js:1
- Import cycle (2 files) src/errors/error-list.js:1
- Import cycle (2 files) src/live/controller.ts:4
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@eslint/eslintrc' eslint.config.js:5
- Unlisted import '@eslint/js' eslint.config.js:4
- Unlisted import 'node-fetch' test/server/browser-connection-test.js:2
- Import cycle (3 files) src/api/request-hooks/hook.ts:12
Serious — 1852 finding(s)
- No assertions: Should raise an error if fixture name is not a string test/server/api-test.js:25
- No assertions: Should raise an error if fixture page is not a string test/server/api-test.js:54
- No assertions: Should raise an error if beforeEach is not a function test/server/api-test.js:79
- No assertions: Should raise an error if afterEach is not a function test/server/api-test.js:104
- No assertions: Should raise an error if fixture.before is not a function test/server/api-test.js:129
- No assertions: Should raise an error if fixture.after is not a function test/server/api-test.js:154
- No assertions: Should raise an error if httpAuth takes a wrong argument test/server/api-test.js:179
- No assertions: Should raise an error if requestHooks takes a wrong argument test/server/api-test.js:248
- No assertions: Should raise an error if "fixture.requestHooks" method calls several times test/server/api-test.js:273
- No assertions: Should raise an error if fixture.meta is undefined test/server/api-test.js:310
- No assertions: Should raise an error if "fixture.clientScripts" method takes a wrong argument test/server/api-test.js:336
- No assertions: Should raise an error if "fixture.clientScripts" method calls several times test/server/api-test.js:358
- No assertions: Should raise an error if "fixture.skipJsErrors" method argument has invalid value type test/server/api-test.js:430
- No assertions: Should raise an error if "fixture.skipJsErrors" method argument has invalid SkipJsErrorsOptionsObject structure test/server/api-test.js:455
- No assertions: Should raise an error if "fixture.skipJsErrors" method argument has invalid SkipJsErrorsCallbackWithOptionsObject structure test/server/api-test.js:480
- No assertions: Should raise an error if test name is not a string test/server/api-test.js:507
- No assertions: Should raise an error if test body is not a function test/server/api-test.js:532
- No assertions: Should raise an error if test.before is not a function test/server/api-test.js:554
- No assertions: Should raise an error if test.after is not a function test/server/api-test.js:578
- No assertions: Should raise an error if requestHooks takes a wrong argument test/server/api-test.js:602
- No assertions: Should raise an error if "test.requestHooks" method calls several times test/server/api-test.js:653
- No assertions: Should raise an error if test.meta is null test/server/api-test.js:689
- No assertions: Should raise an error if fixture is missing test/server/api-test.js:715
- No assertions: Should raise an error if "test.clientScripts" method takes a wrong argument test/server/api-test.js:738
- No assertions: Should raise an error if "test.clientScripts" method calls several times test/server/api-test.js:761
- Boundary violation [package:test-suite-dependency] REDACTED:17
- Boundary violation [package:test-suite-dependency] REDACTED:19
- Boundary violation [package:test-suite-dependency] gulp/constants/client-test-settings.js:23
- Boundary violation [package:test-suite-dependency] src/api/exportable-lib/index.js:64
- Boundary violation [package:test-suite-dependency] src/api/request-hooks/hook.ts:11
- Boundary violation [package:test-suite-dependency] src/api/skip-js-errors/index.ts:5
- Boundary violation [package:test-suite-dependency] REDACTED:3
- Boundary violation [package:test-suite-dependency] src/api/wrap-test-function.ts:2
- Boundary violation [package:test-suite-dependency] src/api/wrap-test-function.ts:5
- Boundary violation [package:test-suite-dependency] src/assertions/executor.ts:4
- Boundary violation [package:test-suite-dependency] src/assertions/executor.ts:7
- Boundary violation [package:test-suite-dependency] src/assertions/get-fn.ts:3
- Boundary violation [package:test-suite-dependency] src/browser/connection/gateway/index.ts:18
- Boundary violation [package:test-suite-dependency] src/browser/connection/gateway/index.ts:19
- Boundary violation [package:test-suite-dependency] src/browser/connection/index.ts:32
- Boundary violation [package:test-suite-dependency] src/client-functions/client-function-builder.js:5
- Boundary violation [package:test-suite-dependency] src/client-functions/client-function-builder.js:12
- Boundary violation [package:test-suite-dependency] src/client-functions/client-function-builder.js:13
- Boundary violation [package:test-suite-dependency] src/client-functions/selectors/selector-builder.js:9
- Boundary violation [package:test-suite-dependency] src/client/automation/index.js:17
- Boundary violation [package:test-suite-dependency] src/client/automation/move.ts:3
- Boundary violation [package:test-suite-dependency] src/client/automation/playback/click/index.ts:3
- Boundary violation [package:test-suite-dependency] src/client/automation/playback/click/select-child.js:5
- Boundary violation [package:test-suite-dependency] src/client/automation/playback/dblclick.js:3
- Boundary violation [package:test-suite-dependency] src/client/automation/playback/drag/base.js:11
- No test reaches this file src/client/driver/driver.js:1
- No test reaches this file src/client/core/utils/content-editable.js:1
- No test reaches this file src/client/automation/playback/press/shortcuts.js:1
- No test reaches this file src/client/ui/status-bar/index.js:1
- No test reaches this file src/client/core/utils/dom.js:1
- No test reaches this file src/client/core/utils/position.ts:1
- No test reaches this file src/client/core/utils/text-selection.js:1
- No test reaches this file src/client/automation/visible-element-automation.ts:1
- No test reaches this file src/client/automation/playback/type/index.js:1
- No test reaches this file src/client/automation/move.ts:1
- No test reaches this file src/client/automation/playback/select/utils.js:1
- No test reaches this file src/client/automation/playback/type/type-text.js:1
- No test reaches this file src/client/core/scroll/index.ts:1
- No test reaches this file src/client/browser/idle-page/status-indicator.js:1
- No test reaches this file src/client/browser/index.js:1
- No test reaches this file src/client/driver/command-executors/browser-manipulation/index.js:1
- No test reaches this file src/client/automation/playback/press/index.js:1
- No test reaches this file src/client/driver/command-executors/action-executor/index.ts:1
- No test reaches this file src/client/ui/select-element.js:1
- No test reaches this file src/client/driver/native-dialog-tracker/index.js:1
- No test reaches this file src/client/automation/playback/click/browser-click-strategy.ts:1
- No test reaches this file src/client/driver/command-executors/action-executor/actions-initializer.ts:1
- No test reaches this file src/cli/cli.js:1
- No test reaches this file src/client/automation/playback/click/select-child.js:1
- No test reaches this file src/client/ui/progress-panel/index.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits REDACTED:286
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:81
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:85
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:95
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:103
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:126
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:130
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:134
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:138
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:148
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:154
- Fake-async — async method never awaits src/browser/provider/plugin-host.js:166
- Fake-async — async method never awaits src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- Fake-async — async method never awaits src/client/driver/driver-link/window/parent.js:42
- Fake-async — async method never awaits REDACTED:75
- Fake-async — async method never awaits REDACTED:79
- Fake-async — async method never awaits src/utils/temp-directory/index.js:34
- TodoComment src/utils/re-executable-promise.ts:1
- TodoComment src/client/driver/command-executors/action-executor/index.ts:54
- TodoComment src/client/driver/command-executors/action-executor/index.ts:66
- TodoComment src/client/driver/command-executors/action-executor/index.ts:70
- TodoComment src/client/driver/command-executors/action-executor/index.ts:91
- TodoComment src/client/driver/command-executors/action-executor/index.ts:99
- TodoComment src/client/driver/command-executors/action-executor/index.ts:122
- TodoComment src/client/driver/command-executors/action-executor/index.ts:126
- TodoComment src/client/driver/command-executors/action-executor/index.ts:128
- TodoComment src/client/driver/command-executors/action-executor/index.ts:130
- TodoComment src/client/driver/command-executors/action-executor/index.ts:201
- TodoComment src/api/structure/test-file.ts:24
- Skipped test: Should compile test defined in separate module if option is enabled test/server/compiler-test.js:649
- Skipped test: 2 test/server/data/test-suites/live/test-with-skipped.js:4
- Skipped test: fixture2test4 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:18
- Skipped test: Test report should contains correct duration time (GH-22) test/functional/legacy-fixtures/page-js-errors/test.js:69
- Skipped test: Skipped test 1 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:7
- Skipped test: Skipped test 2 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:11
- Skipped test: Skipped test 3 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:14
- Skipped test: Skipped test 4 test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:17
- Skipped test: Fixture5Test1 test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/skip-test.js:27
- Skipped test: Test4 test/functional/fixtures/api/es-next/hooks/testcafe-fixtures/fixture-hooks.js:61
- Unfinished stub — throws a "not implemented" error src/browser/provider/plugin-host.js:72
- Unfinished stub — throws a "not implemented" error src/browser/provider/plugin-host.js:76
- Unfinished stub — throws a "not implemented" error src/browser/provider/plugin-host.js:91
- Unfinished stub — throws a "not implemented" error src/client/automation/playback/drag/base.js:41
- Unfinished stub — throws a "not implemented" error src/reporter/plugin-host.ts:203
- Unfinished stub — throws a "not implemented" error src/reporter/plugin-host.ts:207
- Unfinished stub — throws a "not implemented" error src/reporter/plugin-host.ts:216
- Unfinished stub — throws a "not implemented" error src/reporter/plugin-host.ts:220
- Unfinished stub — throws a "not implemented" exception src/browser/provider/plugin-host.js:72
- Unfinished stub — throws a "not implemented" exception src/browser/provider/plugin-host.js:76
- Unfinished stub — throws a "not implemented" exception src/browser/provider/plugin-host.js:91
- Unfinished stub — throws a "not implemented" exception src/client/automation/playback/drag/base.js:41
- Unfinished stub — throws a "not implemented" exception src/reporter/plugin-host.ts:203
- Unfinished stub — throws a "not implemented" exception src/reporter/plugin-host.ts:207
- Unfinished stub — throws a "not implemented" exception src/reporter/plugin-host.ts:216
- Unfinished stub — throws a "not implemented" exception src/reporter/plugin-host.ts:220
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyMethods: Driver src/client/driver/driver.js:169
- TooManyMethods: Runner src/runner/index.js:53
- TooManyMethods: BrowserProvider src/browser/provider/index.ts:57
- TooManyMethods: BrowserConnection src/browser/connection/index.ts:100
- TooManyMethods: CLIArgumentParser src/cli/argument-parser/index.ts:95
- TooManyMethods: BrowserProviderPluginHost src/browser/provider/plugin-host.js:10
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2 locations) src/browser/connection/gateway/index.ts:139
- Duplicated block (11 lines × 2 locations) REDACTED:663
- Duplicated block (11 lines × 2 locations) src/client/automation/playback/press/shortcuts.js:178
- Duplicated block (11 lines × 2 locations) src/client/automation/playback/press/shortcuts.js:367
- Duplicated block (11 lines × 2 locations) src/client/automation/playback/select/utils.js:171
- HackComment src/test-run/marker-symbol.ts:1
- HackComment src/role/marker-symbol.ts:1
- HackComment src/client/driver/command-executors/client-functions/replicator/transforms/function-transform.ts:18
- HackComment src/browser/provider/index.ts:67
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: Fixture (LCOM4 8) src/api/structure/fixture.ts:22
- Low cohesion: Test (LCOM4 6) src/api/structure/test.ts:24
- Low cohesion: RunnerMock (LCOM4 5) test/server/live-test.js:87
- Sync-over-async blocking src/video-recorder/recorder.js:200
- Sync-over-async blocking test/client/config-qunit-server-app.js:53
- Sync-over-async blocking test/functional/site/api.js:47
- Duplicated block (8 lines × 2 locations) src/client/core/utils/text-selection.js:83
- Duplicated block (8 lines × 2 locations) src/client/driver/command-executors/action-executor/actions-initializer.ts:72
- Duplicated block (8 lines × 2 locations) src/client/driver/driver.js:394
- Duplicated block (6 lines × 2 locations) REDACTED:481
- Duplicated block (6 lines × 2 locations) src/client/core/utils/position.ts:329
- Duplicated block (6 lines × 2 locations) REDACTED:538
- This test file cannot be loaded test/server/data/test-suites/live/test-external-unexisting-module.js:1
- This test file cannot be loaded test/server/data/test-suites/require-error-in-dep/dep.js:1
- This test file cannot be loaded test/server/data/test-suites/require-error-in-testfile/testfile.js:1
- Deprecated: eslint package.json:194
- Deprecated: sinon package.json:222
- REDACTED
- REDACTED
- ClassTooLong: Driver src/client/driver/driver.js:169
- ClassTooLong: Runner src/runner/index.js:53
- FileTooLong: driver/driver.js src/client/driver/driver.js
- FileTooLong: runner/index.js src/runner/index.js
- Change coupling: base.js ↔ REDACTED src/browser/provider/built-in/dedicated/base.js:1
- Change coupling: REDACTED ↔ plugin-host.js src/browser/provider/built-in/dedicated/chrome/index.js:1
- REDACTED
- REDACTED
- Both branches are identical — the condition decides nothing src/client/automation/playback/click/select-child.js:49
- Both branches are identical — the condition decides nothing src/client/core/select/index.ts:86
- Duplicated block with local edits (10 matched lines × 2 locations) src/client/automation/playback/click/select-child.js:96
- Duplicated block with local edits (10 matched lines × 2 locations) src/client/automation/playback/move/event-sequence/drag-and-drop-first-move.js:3
- Duplicated block with local edits (9 matched lines × 2 locations) src/browser/provider/built-in/locally-installed.js:1
- Duplicated block with local edits (9 matched lines × 2 locations) src/client/automation/playback/dblclick.js:9
- Duplicated block (9 lines × 2 locations) src/client/automation/playback/press/shortcuts.js:227
- Duplicated block (9 lines × 2 locations) src/client/ui/status-bar/progress-bar/indeterminate-indicator.js:95
- addHierarchicalSelectors (cyclomatic 31) REDACTED:551
- Driver._executeCommand (cyclomatic 28) src/client/driver/driver.js:1701
- text-selection.correctContentEditableSelectionBeforeDelete (cyclomatic 26) src/client/core/utils/text-selection.js:64
- utils.focusAndSetSelection (cyclomatic 23) src/client/automation/utils/utils.js:56
- position.getEventPageCoordinates (cyclomatic 21) src/client/core/utils/position.ts:154
- position.getHiddenReason (cyclomatic 21) src/client/core/utils/position.ts:308
- content-editable.isNodeAfterNodeBlockWithBreakLine (cyclomatic 20) src/client/core/utils/content-editable.js:91
- KeyPressSimulator.press (cyclomatic 18) src/client/automation/playback/press/key-press-simulator.js:78
- content-editable.calculateNodeAndOffsetByPosition::checkChildNodes (cyclomatic 18) src/client/core/utils/content-editable.js:431
- content-editable.calculatePositionByNodeAndOffset::checkChildNodes (cyclomatic 18) src/client/core/utils/content-editable.js:482
- TypeAutomation._typeChar (cyclomatic 17) src/client/automation/playback/type/index.js:289
- text-selection.selectContentEditable (cyclomatic 17) src/client/core/utils/text-selection.js:18
- ensure-crop-options.ensureCropOptions (cyclomatic 17) src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- correctContentEditableSelectionBeforeDelete (cognitive 41) src/client/core/utils/text-selection.js:64
- addHierarchicalSelectors (cognitive 36) REDACTED:551
- Driver._executeCommand (cognitive 28) src/client/driver/driver.js:1701
- utils.focusAndSetSelection (cognitive 23) src/client/automation/utils/utils.js:56
- content-editable.calculateNodeAndOffsetByPosition::checkChildNodes (cognitive 23) src/client/core/utils/content-editable.js:431
- home (cognitive 21) src/client/automation/playback/press/shortcuts.js:343
- end (cognitive 21) src/client/automation/playback/press/shortcuts.js:380
- position.getHiddenReason (cognitive 20) src/client/core/utils/position.ts:308
- getSelectedPositionInParentByOffset (cognitive 20) src/client/core/utils/content-editable.js:287
- content-editable.isNodeAfterNodeBlockWithBreakLine (cognitive 19) src/client/core/utils/content-editable.js:91
- text-selection.selectByNodesAndOffsets (cognitive 19) src/client/core/utils/text-selection.js:231
- selectContentEditable (cognitive 19) src/client/core/utils/text-selection.js:18
- position.getEventPageCoordinates (cognitive 18) src/client/core/utils/position.ts:154
- KeyPressSimulator.press (cognitive 18) src/client/automation/playback/press/key-press-simulator.js:78
- shortcuts.submitFormOnEnterPressInInput (cognitive 18) src/client/automation/playback/press/shortcuts.js:142
- TypeAutomation._typeChar (cognitive 18) src/client/automation/playback/type/index.js:289
- position.getClientDimensions (cognitive 17) src/client/core/utils/position.ts:16
- content-editable.calculatePositionByNodeAndOffset::checkChildNodes (cognitive 17) src/client/core/utils/content-editable.js:482
- ensure-crop-options.ensureCropOptions (cognitive 17) src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- (anonymous) (cognitive 17) REDACTED:18
- shortcuts.right (cognitive 16) src/client/automation/playback/press/shortcuts.js:269
- select-element.clickOnOption (cognitive 16) src/client/ui/select-element.js:54
- switchOptionsByKeys (cognitive 16) src/client/ui/select-element.js:192
- REDACTED
- REDACTED
- REDACTED
- FunctionTooLong: add-api.addHierarchicalSelectors REDACTED:551
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- README may be stale
- Type Safety
- Duplication concentrated across 4 sibling directories (6 clone groups) src/client/automation/playback/click/browser-click-strategy.ts:7
- Duplication concentrated across 3 sibling directories (5 clone groups) src/client/ui/progress-panel/index.js:10
- Duplicated block with local edits (37 matched lines × 2 locations) src/client/driver/barriers/request.ts:43
- Duplicated block with local edits (20 matched lines × 2 locations) src/client/automation/playback/drag/base.js:131
- Duplicated block (19 lines × 2 locations) src/client/automation/playback/press/shortcuts.js:244
- Duplicated block with local edits (18 matched lines × 2 locations) src/client/automation/playback/drag/base.js:45
- Duplicated block (18 lines × 2 locations) src/reporter/index.ts:632
- Duplicated block (16 lines × 2 locations) src/client/automation/playback/press/shortcuts.js:340
- Duplicated block (15 lines × 2 locations) REDACTED:361
- Duplicated block with local edits (15 matched lines × 2 locations) src/client/automation/playback/click/select-child.js:12
- Duplicated block (14 lines × 5 locations) REDACTED:587
- Duplicated block (14 lines × 2 locations) src/client/core/utils/text-selection.js:161
- Duplicated block (13 lines × 4 locations) src/api/structure/fixture.ts:103
- Duplicated block (13 lines × 2 locations) src/client/core/scroll/index.ts:111
- Duplicated block (10 lines × 2 locations) REDACTED:319
- Duplicated block (10 lines × 3 locations) src/cli/argument-parser/index.ts:257
- Duplicated block (9 lines × 3 locations) src/browser/connection/gateway/index.ts:211
- Duplicated block (9 lines × 4 locations) REDACTED:642
- Duplicated block (7 lines × 2 locations) src/client/core/utils/content-editable.js:76
- Duplicated block with local edits (7 matched lines × 2 locations) src/runner/fixture-hook-controller.ts:79
- Duplicated block (6 lines × 3 locations) src/cli/argument-parser/index.ts:289
- Duplicated block with local edits (6 matched lines × 2 locations) src/client/driver/command-executors/execute-selector.js:4
- Duplicated block (5 lines × 3 locations) src/assertions/get-fn.ts:29
- Complex function _internalExecuteCommand (cyclomatic 28, cognitive 30) src/test-run/index.ts:1134
- Complex function _executeCommand (cyclomatic 28, cognitive 28) src/client/driver/driver.js:1701
- Complex function correctContentEditableSelectionBeforeDelete (cyclomatic 26, cognitive 41) src/client/core/utils/text-selection.js:64
- Complex function getHiddenReason (cyclomatic 21, cognitive 20) src/client/core/utils/position.ts:308
- Complex function getEventPageCoordinates (cyclomatic 21, cognitive 17) src/client/core/utils/position.ts:154
- Complex function runTests (cyclomatic 20, cognitive 20) test/functional/setup.js:252
- Complex function isNodeAfterNodeBlockWithBreakLine (cyclomatic 20, cognitive 19) src/client/core/utils/content-editable.js:91
- Complex function analyzeMemberExp (cyclomatic 19, cognitive 32) src/compiler/test-file/formats/es-next/get-test-list.js:87
- Complex function checkChildNodes (cyclomatic 18, cognitive 23) src/client/core/utils/content-editable.js:431
- Complex function press (cyclomatic 18, cognitive 18) src/client/automation/playback/press/key-press-simulator.js:78
- Complex function (anonymous) (cyclomatic 18, cognitive 18) src/client/automation/utils/utils.js:57
- Complex function checkChildNodes (cyclomatic 18, cognitive 17) src/client/core/utils/content-editable.js:482
- Complex function checkScreenshotsCreated (cyclomatic 18, cognitive 16) test/functional/assertion-helper.js:239
- Complex function selectContentEditable (cyclomatic 17, cognitive 19) src/client/core/utils/text-selection.js:18
- Complex function _typeChar (cyclomatic 17, cognitive 18) src/client/automation/playback/type/index.js:289
- Complex function ensureCropOptions (cyclomatic 17, cognitive 17) src/client/driver/command-executors/browser-manipulation/ensure-crop-options.js:38
- Complex function constructor (cyclomatic 15, cognitive 15) src/client-functions/selectors/selector-builder.js:18
- src/client/driver/driver.js: 1558 lines of code src/client/driver/driver.js:1
- src/test-run/index.ts: 1167 lines of code src/test-run/index.ts:1
- src/test-run/commands/actions.js: 668 lines of code src/test-run/commands/actions.js:1
- src/runner/index.js: 616 lines of code src/runner/index.js:1
- src/reporter/index.ts: 602 lines of code src/reporter/index.ts:1
- REDACTED: 585 lines of code REDACTED:1
- src/browser/connection/index.ts: 531 lines of code src/browser/connection/index.ts:1
- src/api/test-controller/index.js: 507 lines of code src/api/test-controller/index.js:1
- src/client/core/utils/content-editable.js: 453 lines of code src/client/core/utils/content-editable.js:1
- src/client/automation/playback/press/shortcuts.js: 440 lines of code src/client/automation/playback/press/shortcuts.js:1
- REDACTED: 438 lines of code REDACTED:1
- src/native-automation/request-pipeline/index.ts: 420 lines of code src/native-automation/request-pipeline/index.ts:1
- src/cli/argument-parser/index.ts: 408 lines of code src/cli/argument-parser/index.ts:1
- Dependency Freshness
- The declared test suite includes a file that cannot be loaded test/server/data/test-suites/live/test-external-unexisting-module.js:1
- Dead file (~68 LoC) REDACTED
- Dead file (~63 LoC) src/utils/check-is-vm.ts
- Dead file (~50 LoC) src/compiler/esm-loader.ts
- Dead file (~38 LoC) src/configuration/types.ts
- Dead file (~33 LoC) src/utils/diff/index.ts
- Dead file (~28 LoC) src/utils/diff/util.ts
- Dead file (~25 LoC) src/utils/prerender-callsite.ts
- Dead file (~21 LoC) src/client/driver/command-executors/execute-child-window-selector.js
- Dead file (~15 LoC) src/utils/get-options/dashboard.ts
- Dead file (~10 LoC) REDACTED
- Dead file (~9 LoC) src/browser/provider/built-in/dedicated/firefox/interfaces.ts
- Dead file (~7 LoC) src/api/request-hooks/hook-method-names.ts
- Unused dependency '@ffmpeg-installer/ffmpeg'
- Unused dependency 'basic-auth'
- Unused dependency 'body-parser'
- `async` Promise executor src/client/automation/utils/utils.js:57
- Swallowed exception (empty catch) src/client/automation/playback/press/utils.js:80
- Swallowed exception (caught, then discarded) REDACTED:331
Minor — 270 finding(s)
- Orphaned file src/browser/connection/index.ts:1
- Orphaned file src/cli/argument-parser/index.ts:1
- Orphaned file src/native-automation/request-pipeline/index.ts:1
- Orphaned file src/errors/test-run/templates.js:1
- Orphaned file src/client/core/utils/content-editable.js:1
- Orphaned file src/client/automation/playback/press/shortcuts.js:1
- Orphaned file REDACTED:1
- Orphaned file src/browser/provider/index.ts:1
- Orphaned file src/client/ui/status-bar/index.js:1
- Orphaned file src/errors/runtime/templates.js:1
- Orphaned file src/client/core/utils/dom.js:1
- Orphaned file REDACTED:1
- Orphaned file REDACTED:1
- Orphaned file src/browser/connection/gateway/index.ts:1
- Orphaned file src/shared/errors/index.js:1
- Orphaned file src/client/core/scroll/index.ts:1
- Orphaned file src/configuration/testcafe-configuration.ts:1
- Orphaned file src/client/automation/playback/type/index.js:1
- Orphaned file src/errors/types.js:1
- Orphaned file src/client/automation/move.ts:1
- Orphaned file src/runner/browser-job.ts:1
- Orphaned file src/client/core/utils/text-selection.js:1
- Orphaned file src/client/automation/playback/type/type-text.js:1
- Orphaned file src/runner/test-run-controller.ts:1
- Orphaned file src/client/automation/playback/select/utils.js:1
- Deprecated: @sinonjs/text-encoding REDACTED:3568
- Deprecated: core-js REDACTED:5727
- Deprecated: debuglog REDACTED:5835
- Deprecated: glob REDACTED:7569
- Deprecated: inflight REDACTED:8800
- Deprecated: mkdirp REDACTED:10159
- Deprecated: osenv REDACTED:10803
- Deprecated: read-installed REDACTED:11572
- Deprecated: read-package-json REDACTED:11601
- Deprecated: readdir-scoped-modules REDACTED:11636
- Deprecated: rimraf REDACTED:11952
- Deprecated: sourcemap-codec REDACTED:12418
- Deprecated: spdx REDACTED:12436
- Deprecated: rimraf REDACTED:13082
- Outdated (npm): @types/node package.json:80
- Outdated (npm): chalk package.json:88
- Outdated (npm): commander package.json:91
- Outdated (npm): del package.json:94
- Outdated (npm): execa package.json:102
- Outdated (npm): globby package.json:104
- Outdated (npm): indent-string package.json:110
- Outdated (npm): is-ci package.json:111
- Outdated (npm): nanoid package.json:124
- Outdated (npm): parse5 package.json:126
- Outdated (npm): pify package.json:127
- Outdated (npm): pngjs package.json:129
- Outdated (npm): strip-bom package.json:141
- Outdated (npm): typescript package.json:154
- Disabled test test/functional/fixtures/api/es-next/hooks/testcafe-fixtures/fixture-hooks.js:61
- Disabled test test/functional/fixtures/api/es-next/request-hooks/testcafe-fixtures/api/8229.js:12
- Disabled test test/functional/fixtures/api/es-next/skip-only/testcafe-fixtures/skip-test.js:27
- Disabled test test/functional/fixtures/regression/gh-1999/test.js:2
- Disabled test test/functional/fixtures/regression/gh-3456/test.js:10
- Disabled test test/functional/fixtures/regression/gh-3904/test.js:2
- Disabled test test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:7
- Disabled test test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:11
- Disabled test test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:14
- Disabled test test/functional/fixtures/reporter/testcafe-fixtures/skipped-tests.js:17
- Disabled test test/functional/legacy-fixtures/page-js-errors/test.js:69
- Disabled test test/server/compiler-test.js:649
- Disabled test test/server/data/test-suites/fixture-and-test-hooks/testfile.js:18
- Silent fallback default in catch REDACTED:25
- Silent fallback default in catch src/utils/render-callsite-sync.js:33
- Silent fallback default in catch REDACTED:134
- Silent fallback default in catch src/utils/detect-ffmpeg.js:15
- Silent fallback default in catch src/utils/detect-ffmpeg.js:26
- Silent fallback default in catch src/utils/detect-ffmpeg.js:35
- Silent fallback default in catch test/functional/utils/file-storage.js:29
- Duplicated predicate src/client/automation/playback/press/shortcuts.js:128
- Duplicated predicate src/assertions/executor.ts:94
- Duplicated predicate src/errors/is-internal-stack-frame.ts:37
- Duplicated predicate src/client/automation/playback/click/browser-click-strategy.ts:97
- Duplicated predicate src/client/automation/playback/select/select-editable-content.js:41
- Most significant orphaned file src/client/driver/driver.js:1
- Most significant orphaned file src/test-run/index.ts:1
- Most significant orphaned file REDACTED:1
- REDACTED
- REDACTED
- Console output used as the logging channel src/utils/handle-errors.js:9
- Console output used as the logging channel src/client/browser/service-worker.js:30
- Unused private method '_before$' src/api/structure/fixture.ts:71
- Unused private method '_before$' src/api/structure/test.ts:84
- Unused private method '_after$' src/api/structure/fixture.ts:79
- Unused private method '_after$' src/api/structure/test.ts:92
- Unused private method '_requestHooks$' src/api/structure/fixture.ts:103
- Unused private method '_requestHooks$' src/api/structure/test.ts:100
- Unused private method '_clientScripts$' src/api/structure/fixture.ts:117
- Unused private method '_clientScripts$' src/api/structure/test.ts:114
- Mock-dominated test: Should log the connection url test/server/cli-remote-wizard-test.js:11
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:6
- No dependency-update automation package.json:60
- Unused export 'createAdditionalElementDescriptor' src/client/driver/utils/ensure-elements.js:67
- Unused export 'default' src/compiler/babel/preset-stage-2.ts:1
- Unused export 'safeFailRequest' src/native-automation/request-pipeline/safe-api.ts:73
- Unused export 'fromBase64String' src/native-automation/utils/string.ts:27
- Unused private method '_disableConcurrency$getter' src/api/structure/fixture.ts:65
- Unused private method '_beforeEach$' src/api/structure/fixture.ts:87
- Unused private method '_afterEach$' src/api/structure/fixture.ts:95
- Unused private method '_timeouts$' src/api/structure/test.ts:128
- Unused private method '_only$getter' src/api/structure/testing-unit.ts:75
- Unused private method '_skip$getter' src/api/structure/testing-unit.ts:81
- Unused private method '_disablePageReloads$getter' src/api/structure/testing-unit.ts:87
- Unused private method '_enablePageReloads$getter' src/api/structure/testing-unit.ts:93
- Unused private method '_page$' src/api/structure/testing-unit.ts:99
- Unused private method '_skipJsErrors$' src/api/structure/testing-unit.ts:114
- Unused private method '_httpAuth$' src/api/structure/testing-unit.ts:124
- Unused private method '_meta$' src/api/structure/testing-unit.ts:139
- Unused private method '_disablePageCaching$getter' src/api/structure/testing-unit.ts:151
- Write-only private field 'forcedIdleUrl' src/browser/connection/index.ts:118
- Null assertions (`!`) reduce the strict null checking score
Minor — 58 finding(s)
- Outdated (npm): @babel/core
- Outdated (npm): @babel/plugin-proposal-decorators
- Outdated (npm): @babel/plugin-transform-async-generator-functions
- Outdated (npm): @babel/plugin-transform-async-to-generator
- Outdated (npm): @babel/plugin-transform-class-properties
- Outdated (npm): @babel/plugin-transform-class-static-block
- Outdated (npm): @babel/plugin-transform-exponentiation-operator
- Outdated (npm): @babel/plugin-transform-for-of
- Outdated (npm): @babel/plugin-transform-object-rest-spread
- Outdated (npm): @babel/plugin-transform-private-methods
- Outdated (npm): @babel/plugin-transform-runtime
- Outdated (npm): @babel/preset-env
- Outdated (npm): @babel/preset-flow
- Outdated (npm): @babel/preset-react
- Outdated (npm): @babel/runtime
- Outdated (npm): async-exit-hook
- Outdated (npm): babel-plugin-module-resolver
- Outdated (npm): bowser
- Outdated (npm): chai
- Outdated (npm): chrome-remote-interface
- Outdated (npm): coffeescript
- Outdated (npm): dedent
- Outdated (npm): devtools-protocol
- Outdated (npm): diff
- Outdated (npm): elegant-spinner
- Skipped (documented): (unnamed test) test/server/data/test-suites/typescript-testcafe-scripts-defs/test-controller.ts:794
- Skipped (documented): (unnamed test) test/server/data/test-suites/typescript-testcafe-scripts-defs/test-controller.ts:798
- Skipped (documented): (unnamed test) test/server/data/test-suites/typescript-defs/test-controller.ts:799
- Skipped (documented): (unnamed test) test/server/data/test-suites/typescript-defs/test-controller.ts:803
- Skipped (documented): fixture2test3 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:17
- Skipped (documented): fixture3test1 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:22
- Skipped (documented): fixture3test2 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:23
- Skipped (documented): fixture9test1 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:93
- Skipped (documented): fixture10test1 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:102
- Skipped (documented): fixture11test1 test/server/data/test-suites/fixture-and-test-hooks/testfile.js:106
- Skipped (documented): test 2 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:6
- Skipped (documented): test 3 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:14
- Skipped (documented): test 4 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:20
- Skipped (documented): test 5 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:26
- Skipped (documented): test 6 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:33
- Skipped (documented): test 1 test/server/data/test-suites/call-fixture-from-async-function/testfile.js:38
- Skipped (documented): Pending test/server/data/mocha-reporter-spec-with-retries/suite1.js:26
- Skipped (documented): Pending test/server/data/mocha-reporter-spec-with-retries/suite2.js:26
- Skipped (documented): (unnamed test) test/server/data/custom-client-scripts/utils.js:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-596f81dc2a8e47d3a3cc427afcdfbb35/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-596f81dc2a8e47d3a3cc427afcdfbb35/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 127 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 5 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 2 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `@types/indent-string/index.d.ts`, `@types/promisify-event/index.d.ts`, `@types/time-limit-promise/index.d.ts`, `@types/unquote/index.d.ts`, `src/configuration/types.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |