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

jestjs/jest

Measured 26 October 2026, 15:12 UTC, at code version 61050e9

Regression: 2 dimensions fell since the last survey Code coverage: not measured

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

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

CAI score 48out of 100 At risk Down 2 since the last survey

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

Architecture 87 Strong Performance 66 Adequate Code Health 62 Adequate Maturity 59 Adequate Security and Compliance 54 Adequate Production Readiness 36 Weak

A medium codebase: 62,246 lines of product code in 53 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Production Readiness, 36

Findings by how serious they are

98 critical 843 serious 352 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 15:12 UTC

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

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

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

74of 74 dimensions measured by tools.
1192of 1293 findings point to an exact file and line, so you can open each one in the code. The other 101 concern the repository as a whole, such as missing documentation.
74dimensions across 6 lenses, read from 62,246 lines of product code in 53 projects.
Chapters

Executive summary

jestjs/jest is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code, and it has uses of packages that aren't listed. It scores 48 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 36, is the weakest lens and counts most in the score. The best first steps are balancing fast unit tests against broader integration tests and pinning the dependencies taken from a moving source, each worth about 9 points. Raising Production Readiness to 70 would lift the score to about 59.

Eleven known security holes in the packages the code depends on can be used by attackers. One weakness in the code could be used by an attacker. Updating the vulnerable packages and fixing the weaknesses the scanner points to would close both risks. The 55 tests that check nothing need to check the result they produce.

The product code is 62,246 lines, about €150,000 to rebuild.

Code Health 62 Adequate, capped by Cognitive Complexity Architecture 87 Strong Maturity 59 Adequate, capped by Architecture documentation Production Readiness 36 Weak, capped by Dependency Hygiene, Observability and Security & performance tooling Security and Compliance 54 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Malicious Dependencies Performance 66 Adequate

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

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

If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 48 to about 59.

Code composition: what the lines of code are
Product code 37%Tests 63%
New since the last survey: 127 findings

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

  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts
  • Test Quality · Skipped test: (unnamed test) e2e/Utils.ts
  • Test Quality · Skipped test: (unnamed test) e2e/Utils.ts
  • Test Quality · Skipped test: (unnamed test) e2e/Utils.ts
  • Test Quality · Skipped test: skips e2e/test-todo/__tests__/statuses.test.js
  • Test Quality · Skipped test: does not run skipped tests e2e/test-retries/__tests__/entireDescribe.test.js
  • Test Quality · Skipped test: skips e2e/test-failing/__tests__/statuses.test.js
  • Test Quality · Skipped test: passing test e2e/test-failing/__tests__/worksWithSkipMode.test.js
  • Test Quality · Skipped test: failing test e2e/test-failing/__tests__/worksWithSkipMode.test.js
  • Test Quality · Skipped test: xit no ancestors e2e/location-in-results/__tests__/test.js
  • Test Quality · Skipped test: xit nested e2e/location-in-results/__tests__/test.js
  • Test Quality · Skipped test: skipped test e2e/json-reporter/__tests__/sum.test.js
  • Test Quality · Skipped test: should skip this test e2e/jasmine-async/__tests__/concurrent-each.test.js
  • Test Quality · Skipped test: two e2e/jasmine-async/__tests__/concurrent.test.js
  • Test Quality · Skipped test: fails with thrown error - async e2e/jasmine-async/__tests__/promiseIt.test.js
  • Test Quality · Skipped test: fails but will be skipped e2e/jasmine-async/__tests__/promiseXit.test.js
  • Test Quality · Skipped test: skipped test e2e/empty-describe-with-hooks/__tests__/hookInDescribeWithSkippedTest.test.js
  • Test Quality · Skipped test: Should not be ran: fails all rows expected %s == %s e2e/each/__tests__/eachSkip.test.js
  • Test Quality · Skipped test: sample e2e/custom-reporters/__tests__/skip.test.js
  • Test Quality · Skipped test: explicitly skipped e2e/collect-tests/__tests__/kitchenSink.test.js
  • Test Quality · Skipped test: skipped each %i e2e/collect-tests/__tests__/kitchenSink.test.js
  • Test Quality · Skipped test: should skip this test e2e/circus-concurrent/__tests__/concurrent-each.test.js
  • Test Quality · Skipped test: skipped three e2e/circus-concurrent/__tests__/concurrent-skip.test.js
  • Test Quality · Skipped test: five (skipped) e2e/circus-concurrent/__tests__/concurrent-skip.test.js
  • Test Quality · Skipped test: six (skipped) e2e/circus-concurrent/__tests__/concurrent-skip.test.js
  • Test Quality · Skipped test: nine (skipped) e2e/circus-concurrent/__tests__/concurrent-skip.test.js
  • Test Quality · Skipped test: it should be skipped e2e/before-all-skipped/__tests__/beforeAllFiltered.test.js
  • Test Quality · Skipped test: prints that no project was found e2e/__tests__/selectProjects.test.ts
  • Test Quality · Skipped test: prints that no project was found e2e/__tests__/selectProjects.test.ts
  • Test Quality · Test project verifies nothing: e2e/declaration-errors e2e/declaration-errors/__tests__/describeReturnPromise.test.js
  • Test Quality · Test project verifies nothing: e2e/empty-describe-with-hooks e2e/empty-describe-with-hooks/__tests__/hookInEmptyDescribe.test.js
  • Test Quality · Test project verifies nothing: e2e/multi-project-config-root e2e/multi-project-config-root/foo/__tests__/boggusFoo.test.js
  • Test Quality · Test project verifies nothing: e2e/node-url-manual-mocks e2e/node-url-manual-mocks/__tests__/importAndMock.test.js
  • Test Quality · Test project verifies nothing: e2e/run-programmatically-multiple-projects e2e/run-programmatically-multiple-projects/server/server.test.js
  • Test Quality · Test project verifies nothing: e2e/test-path-patterns-subprojects e2e/test-path-patterns-subprojects/src/__tests__/testA.js
  • Test Quality · Test project verifies nothing: e2e/transform/no-babel-jest e2e/transform/no-babel-jest/__tests__/failsWithSyntaxError.test.js
  • Test Quality · Test project verifies nothing: e2e/worker-restart-before-send e2e/worker-restart-before-send/__tests__/test1.js
  • Dependency Hygiene · Deprecated: discord.js e2e/native-esm/package.json
  • Dependency Hygiene · Deprecated: discord.js e2e/require-missing-ext/package.json
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → expect) packages/expect/src/jestMatchersObject.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → expect) packages/expect/src/jestMatchersObject.ts
  • Boundary Type-Coupling · Cross-context type Event (jest-types → jest-circus) packages/jest-circus/src/formatNodeAssertErrors.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/formatNodeAssertErrors.ts
  • Boundary Type-Coupling · Cross-context type BlockMode (jest-types → jest-circus) packages/jest-circus/src/utils.ts
  • Boundary Type-Coupling · Cross-context type TestFn (jest-types → jest-circus) packages/jest-circus/src/utils.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/state.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/state.ts
  • Boundary Type-Coupling · Cross-context type AsyncEvent (jest-types → jest-circus) packages/jest-circus/src/state.ts
  • Boundary Type-Coupling · Cross-context type SyncEvent (jest-types → jest-circus) packages/jest-circus/src/state.ts
  • Boundary Type-Coupling · Cross-context type Event (jest-types → jest-circus) packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapterInit.ts
  • Boundary Type-Coupling · Cross-context type ArrayTable (jest-types → jest-each) packages/jest-each/src/table/array.ts
  • Boundary Type-Coupling · Cross-context type EachTable (jest-types → jest-each) packages/jest-each/src/index.ts
  • Boundary Type-Coupling · Cross-context type TestNameLike (jest-types → jest-jasmine2) packages/jest-jasmine2/src/jasmine/Suite.ts
  • Boundary Type-Coupling · Cross-context type SnapshotUpdateState (jest-types → jest-snapshot-utils) packages/jest-snapshot-utils/src/utils.ts
  • Boundary Type-Coupling · Cross-context type SnapshotUpdateState (jest-types → jest-snapshot) packages/jest-snapshot/src/index.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-watcher) packages/jest-watcher/src/TestWatcher.ts
  • Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-watcher) packages/jest-watcher/src/TestWatcher.ts
  • Static Analysis (SAST) · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Knowledge Freshness · Orphaned knowledge REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Web-Security Posture · Weak hash algorithm packages/jest-config/src/normalize.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-create-cache-key-function/src/index.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-create-cache-key-function/src/index.ts
  • Web-Security Posture · Weak hash algorithm REDACTED
  • Web-Security Posture · Weak hash algorithm REDACTED
  • Web-Security Posture · Weak hash algorithm packages/jest-haste-map/src/worker.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts
  • Web-Security Posture · Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-util/src/createProcessObject.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-util/src/garbage-collection-utils.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-transform/src/ScriptTransformer.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-snapshot-utils/src/utils.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-snapshot-utils/src/utils.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-runtime/src/helpers.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve-dependencies/src/index.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve-dependencies/src/index.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve/src/resolver.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve/src/resolver.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve/src/utils.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-resolve/src/utils.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-reporters/src/CoverageReporter.ts
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmineAsyncInstall.ts
  • Exception handling · Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmine/Suite.ts

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

Fixed since the last survey: 77 findings

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

  • Test Quality · Test project verifies nothing: e2e/declaration-errors e2e/declaration-errors/__tests__/describeThrow.test.js
  • Test Quality · Test project verifies nothing: e2e/empty-describe-with-hooks e2e/empty-describe-with-hooks/__tests__/multipleHooksInEmptyDescribe.test.js
  • Test Quality · Test project verifies nothing: e2e/multi-project-config-root e2e/multi-project-config-root/bar/__tests__/boggusBar.test.js
  • Test Quality · Test project verifies nothing: e2e/node-url-manual-mocks e2e/node-url-manual-mocks/__tests__/mockOnly.test.js
  • Test Quality · Test project verifies nothing: e2e/run-programmatically-multiple-projects e2e/run-programmatically-multiple-projects/client/client.test.js
  • Test Quality · Test project verifies nothing: e2e/test-path-patterns-subprojects e2e/test-path-patterns-subprojects/src/__tests__/testC.js
  • Test Quality · Test project verifies nothing: e2e/transform/no-babel-jest e2e/transform/no-babel-jest/__tests__/passesWithNoBabelJest.js
  • Test Quality · Test project verifies nothing: e2e/worker-restart-before-send e2e/worker-restart-before-send/__tests__/test3.js
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/expect/src/spyMatchers.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/jest-matcher-utils/src/index.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/jest-mock/src/index.ts
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/jest-resolve/src/resolver.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/diff-sequences/src/index.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/expect/src/spyMatchers.ts
  • Code Duplication · Duplicated block (15 lines × 4 locations) packages/jest-mock/src/index.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/jest-reporters/src/GitHubActionsReporter.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/jest-resolve/src/resolver.ts
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/jest-snapshot/src/printSnapshot.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/jest-circus/src/run.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/jest-core/src/TestNamePatternPrompt.ts
  • Code Duplication · Duplicated block (14 lines × 3 locations) packages/jest-mock/src/index.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/jest-resolve/src/resolver.ts
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/jest-runtime/src/internals/EsmLoader.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/diff-sequences/src/index.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/expect/src/spyMatchers.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/jest-core/src/FailedTestsInteractiveMode.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/jest-core/src/getNoTestFound.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/jest-runtime/src/internals/EsmLoader.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/jest-transform/src/ScriptTransformer.ts
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/jest-validate/src/errors.ts
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/jest-worker/src/workers/messageParent.ts
  • Code Duplication · Duplicated block (13 lines × 3 locations) scripts/babel-plugin-jest-native-globals.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/jest-circus/src/run.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/jest-runtime/src/internals/TransformCache.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/jest-snapshot/src/index.ts
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/jest-source-map/src/SourceMapSupport.ts
  • Code Duplication · Duplicated block (11 lines × 5 locations) packages/expect/src/spyMatchers.ts
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/jest-reporters/src/GitHubActionsReporter.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/expect/src/toThrowMatchers.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/jest-config/src/utils.ts
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/jest-fake-timers/src/legacyFakeTimers.ts
  • Code Duplication · Duplicated block (9 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/jest-config/src/normalize.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/jest-mock/src/index.ts
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) scripts/babel-plugin-jest-native-globals.js
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) scripts/build.mjs
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/jest-circus/src/unhandledRejectionHandler.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/jest-each/src/index.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/expect-utils/src/jasmineUtils.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/jest-diff/src/diffLines.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/jest-diff/src/getAlignedDiffs.ts
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/jest-reporters/src/getSummary.ts
  • Code Duplication · Duplicated block (5 lines × 2 locations) eslint.config.mjs
  • Test Coverage · This test file cannot be loaded e2e/resolve-no-extensions/index.js
  • Test Coverage · This test file cannot be loaded packages/jest-diff/src/__tests__/joinAlignedDiffs.test.ts
  • Test Coverage · This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/dynamic-imports-automock-json.cjs
  • Test Coverage · This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-automock-json-extensionless.mjs
  • Async & latency hygiene · Sync-over-async blocking packages/create-jest/src/runCreate.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-config/src/index.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-core/src/runJest.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-core/src/runJest.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-haste-map/src/worker.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-haste-map/src/worker.ts
  • Async & latency hygiene · Sync-over-async blocking packages/jest-reporters/src/CoverageReporter.ts
Rebuild cost: about €150,000 · Estimate
Cost to rebuild€51,000 to €250,000, for 842 to 2,672 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 62,246 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Improve Test Distribution — currently 6.0/10.
Raises the score by about 9 points · Medium effort · Test Distribution
2
Resolve the 19 Floating npm dependency finding(s) in Dependency Hygiene.
Raises the score by about 9 points · Medium effort · Dependency Hygiene
3
Adopt pino (or winston) and log at meaningful points in the services you run.
Raises the score by about 6 points · Medium effort · Observability

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €150,000 to build again, about 1.0 person-years of work. Its weakest lens is Production Readiness, at 36 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Improve Test Distribution — currently 6.0/10. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.0 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 40,653 lines over the last 90 days, which is about 164,870 lines a year. At that pace, the extra work comes to an estimated 20.8 to 125.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch @jest/core core @jest/reporters reporters @jest/core->@jest/reporters @jest/test-result test-result @jest/core->@jest/test-result @jest/transform transform @jest/core->@jest/transform @jest/types types @jest/core->@jest/types jest-config jest-config @jest/core->jest-config jest-haste-map jest-haste-map @jest/core->jest-haste-map jest-message-util jest-message-util @jest/core->jest-message-util jest-runner jest-runner @jest/core->jest-runner jest-runtime jest-runtime @jest/core->jest-runtime jest-snapshot jest-snapshot @jest/core->jest-snapshot jest-util jest-util @jest/core->jest-util pretty-format pretty-format @jest/core->pretty-format @jest/environment environment @jest/fake-timers fake-timers @jest/environment->@jest/fake-timers @jest/environment->@jest/types jest-mock jest-mock @jest/environment->jest-mock @jest/fake-timers->@jest/types @jest/fake-timers->jest-message-util @jest/fake-timers->jest-mock @jest/fake-timers->jest-util @jest/get-type get-type @jest/reporters->@jest/test-result @jest/reporters->@jest/transform @jest/reporters->@jest/types @jest/reporters->jest-message-util @jest/reporters->jest-util @jest/test-result->@jest/types @jest/transform->@jest/types @jest/transform->jest-haste-map @jest/transform->jest-util expect expect expect->@jest/get-type expect->jest-message-util expect->jest-mock expect->jest-util jest-circus jest-circus jest-circus->@jest/environment jest-circus->@jest/test-result jest-circus->@jest/types jest-circus->jest-message-util jest-circus->jest-runtime jest-circus->jest-snapshot jest-circus->jest-util jest-circus->pretty-format jest-config->@jest/get-type jest-config->@jest/types jest-config->jest-circus jest-config->jest-runner jest-config->jest-util jest-config->pretty-format jest-haste-map->@jest/types jest-haste-map->jest-util jest-jasmine2 jest-jasmine2 jest-jasmine2->@jest/environment jest-jasmine2->@jest/test-result jest-jasmine2->@jest/types jest-jasmine2->jest-message-util jest-jasmine2->jest-runtime jest-jasmine2->jest-snapshot jest-jasmine2->jest-util jest-jasmine2->pretty-format jest-message-util->@jest/types jest-message-util->jest-util jest-message-util->pretty-format jest-mock->@jest/types jest-mock->jest-util jest-runner->@jest/environment jest-runner->@jest/test-result jest-runner->@jest/transform jest-runner->@jest/types jest-runner->jest-haste-map jest-runner->jest-message-util jest-runner->jest-runtime jest-runner->jest-util jest-runtime->@jest/environment jest-runtime->@jest/fake-timers jest-runtime->@jest/test-result jest-runtime->@jest/transform jest-runtime->@jest/types jest-runtime->jest-haste-map jest-runtime->jest-message-util jest-runtime->jest-mock jest-runtime->jest-snapshot jest-runtime->jest-util jest-snapshot->@jest/get-type jest-snapshot->@jest/transform jest-snapshot->@jest/types jest-snapshot->expect jest-snapshot->jest-message-util jest-snapshot->jest-util jest-snapshot->pretty-format jest-util->@jest/types __more__ +33 more projects

Architecture: which parts of the code depend on which

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

227 modules, with 244 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 jest-config.src2 jest-diff.src.cleanupSemantic3 jest-haste-map.src.types4 jest-jasmine2.src.types5 jest-matcher-utils.src6 jest-mock.src7 jest-reporters.src.types8 jest-resolve.src.defaultResolver9 jest-runtime.src.internals.FileCache10 jest-runtime.src.internals.ModuleRegistries11 jest-runtime.src.internals.TestState12 jest-snapshot.src.State13 jest-transform.src.types14 jest-types.src.Global15 jest-watcher.src.BaseWatchPlugin16 jest-watcher.src.lib.Prompt17 jest-worker.src.types18 pretty-format.src.types19 expect.src20 jest-core.src.TestScheduler21 jest-environment.src22 jest-haste-map.src23 jest-reporters.src.BaseReporter24 jest-runtime.src.internals.Resolution25 jest-transform.src.ScriptTransformer26 jest-core.src27 jest-jasmine2.src28 jest-reporters.src.DefaultReporter29 jest-runtime.src.internals.MockState30 jest-runtime.src.internals.TransformCache31 jest-runtime.src.internals.cjsRequire32 jest-runtime.src.internals.CjsExportsCache33 jest-runtime.src.internals.JestGlobals34 jest-runtime.src.internals.EsmLoader35 jest-runtime.src.internals.ModuleExecutor36 jest-runtime.src.internals37 jest-runtime.src.internals.CjsLoader38 jest-runtime.src39 jest-circus.src40 jest-circus.src.legacy-code-todo-rewrite
1 jest-config.src
2 jest-diff.src.cleanupSemantic
3 jest-haste-map.src.types
4 jest-jasmine2.src.types
5 jest-matcher-utils.src
6 jest-mock.src
7 jest-reporters.src.types
8 jest-resolve.src.defaultResolver
9 jest-runtime.src.internals.FileCache
10 jest-runtime.src.internals.ModuleRegistries
11 jest-runtime.src.internals.TestState
12 jest-snapshot.src.State
13 jest-transform.src.types
14 jest-types.src.Global
15 jest-watcher.src.BaseWatchPlugin
16 jest-watcher.src.lib.Prompt
17 jest-worker.src.types
18 pretty-format.src.types
19 expect.src1
20 jest-core.src.TestScheduler1
21 jest-environment.src1
22 jest-haste-map.src11
23 jest-reporters.src.BaseReporter1
24 jest-runtime.src.internals.Resolution1
25 jest-transform.src.ScriptTransformer21
26 jest-core.src11
27 jest-jasmine2.src211311
28 jest-reporters.src.DefaultReporter1
29 jest-runtime.src.internals.MockState112
30 jest-runtime.src.internals.TransformCache11
31 jest-runtime.src.internals.cjsRequire224
32 jest-runtime.src.internals.CjsExportsCache222
33 jest-runtime.src.internals.JestGlobals2232
34 jest-runtime.src.internals.EsmLoader2222222222
35 jest-runtime.src.internals.ModuleExecutor32222
36 jest-runtime.src.internals1111
37 jest-runtime.src.internals.CjsLoader22322323
38 jest-runtime.src211111111112211111
39 jest-circus.src1311
40 jest-circus.src.legacy-code-todo-rewrite211
Uses a module listed above itPart of a loopThe module itself
1 jest-config.src2 jest-diff.src.cleanupSemantic3 jest-haste-map.src.types4 jest-jasmine2.src.types5 jest-matcher-utils.src6 jest-mock.src7 jest-reporters.src.types8 jest-resolve.src.defaultResolver9 jest-runtime.src.internals.FileCache10 jest-runtime.src.internals.ModuleRegistries11 jest-runtime.src.internals.TestState12 jest-snapshot.src.State13 jest-transform.src.types14 jest-types.src.Global15 jest-watcher.src.BaseWatchPlugin16 jest-watcher.src.lib.Prompt17 jest-worker.src.types18 pretty-format.src.types19 expect.src20 jest-core.src.TestScheduler21 jest-environment.src22 jest-haste-map.src23 jest-reporters.src.BaseReporter24 jest-runtime.src.internals.Resolution25 jest-transform.src.ScriptTransformer26 jest-core.src27 jest-jasmine2.src28 jest-reporters.src.DefaultReporter29 jest-runtime.src.internals.MockState30 jest-runtime.src.internals.TransformCache31 jest-runtime.src.internals.cjsRequire32 jest-runtime.src.internals.CjsExportsCache33 jest-runtime.src.internals.JestGlobals34 jest-runtime.src.internals.EsmLoader35 jest-runtime.src.internals.ModuleExecutor36 jest-runtime.src.internals37 jest-runtime.src.internals.CjsLoader38 jest-runtime.src39 jest-circus.src40 jest-circus.src.legacy-code-todo-rewritejest-config.src1jest-diff.src.cleanupSemantic2jest-haste-map.src.types3jest-jasmine2.src.types4jest-matcher-utils.src5jest-mock.src6jest-reporters.src.types7jest-resolve.src.defaultResolver8jest-runtime.src.internals.FileCache9jest-runtime.src.internals.ModuleRegistries10jest-runtime.src.internals.TestState11jest-snapshot.src.State12jest-transform.src.types13jest-types.src.Global14jest-watcher.src.BaseWatchPlugin15jest-watcher.src.lib.Prompt16jest-worker.src.types17pretty-format.src.types18expect.src19jest-core.src.TestScheduler20jest-environment.src21jest-haste-map.src22jest-reporters.src.BaseReporter23jest-runtime.src.internals.Resolution24jest-transform.src.ScriptTransformer25jest-core.src26jest-jasmine2.src27jest-reporters.src.DefaultReporter28jest-runtime.src.internals.MockState29jest-runtime.src.internals.TransformCache30jest-runtime.src.internals.cjsRequire31jest-runtime.src.internals.CjsExportsCache32jest-runtime.src.internals.JestGlobals33jest-runtime.src.internals.EsmLoader34jest-runtime.src.internals.ModuleExecutor35jest-runtime.src.internals36jest-runtime.src.internals.CjsLoader37jest-runtime.src38jest-circus.src39jest-circus.src.legacy-code-todo-rewrite401111111211121131111121122422222322222222222322221111223223232111111111122111111311211+187 more modules (most-connected shown)

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

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

At a glance — Architecture · 87% · Strong ·

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

At a glance — Maturity · 59% · Adequate · gated by M2 ·

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

At a glance — Readiness · 36% · Weak · gated by R8, P2, P3 ·

The Good
D10 · TypeScript Test Quality 9.0 D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 9.5 R6 · React / TS Tooling 10.0
The Bad
D9 · TypeScript Test Distribution 6.0 D12 · TypeScript Dependency Hygiene 5.4
The Ugly
P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 3.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 54% · Adequate · gated by D29, D30, D43 ·

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

At a glance — Performance · 66% · Adequate ·

The Good
PF1 · Repo Benchmark discipline 7.5
The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures20High / Critical
A05:2025 — Injection16High / Critical
A08:2025 — Software or Data Integrity Failures2Medium

Roadmap

First, rebalance the test suite by significantly increasing integration and BDD coverage to complement the existing unit and e2e tests. Next, clean up the dependency landscape by removing unused packages, explicitly declaring imports, moving type and test dependencies to devDependencies, and updating outdated packages. Finally, implement structured logging using pino or winston at key service points to establish basic observability and health monitoring.

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

Do thisHelpsEffortDimension
Improve Test Distribution — currently 6.0/10.+8.8 ptsMediumTest Distribution
Resolve the 19 Floating npm dependency finding(s) in Dependency Hygiene.+8.7 ptsMediumDependency Hygiene
Adopt pino (or winston) and log at meaningful points in the services you run.+6.1 ptsMediumObservability
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+6.1 ptsMediumDependency Hygiene
Resolve the 11 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (11).+5.4 ptsMediumDependency Hygiene
Resolve the 55 No assertions (empty test) finding(s) in Test Quality — start with globals.test.ts (10), toThrowMatchers.test.ts (6), asymmetricMatchers.test.ts (4).+4.6 ptsMediumTest Quality
Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2).+2.3 ptsLowMalicious Dependencies
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.0 ptsLowADR Quality

File quality

Per-file score 0–10 — a quality signature. Of 280 files carrying findings, judged against the Production bar: 1% slop · 49% mixed · 50% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
packages/jest-types/__typetests__/globals.test.ts3.0SlopTest Quality: No assertions (empty test): (unnamed test)
packages/expect/src/__tests__/toThrowMatchers.test.ts3.1SlopTest Quality: No assertions (empty test): to throw or not to throw
packages/expect/src/__tests__/asymmetricMatchers.test.ts3.3SlopTest Quality: No assertions (empty test): Any.asymmetricMatch()
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
packages/jest-mock/__typetests__/utility-types.test.ts4.4MixedTest Quality: No assertions (empty test): ClassLike
e2e/test-retries/__tests__/entireDescribeFailureBoundaries.test.js5.0MixedTest Quality: No assertions (empty test): passes
e2e/circus-declaration-errors/__tests__/asyncDefinition.test.js5.0MixedTest Quality: No assertions (empty test): correct test def
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
packages/expect/src/__tests__/assertionCounts.test.ts5.2MixedTest Quality: No assertions (empty test): hasAssertions not leaking to global state
packages/jest-circus/src/utils.ts5.5MixedCyclomatic Complexity: utils.callAsyncCircusFn (cyclomatic 16)
e2e/lifecycles/__tests__/index.js5.5MixedTest Quality: No assertions (empty test): one
packages/jest-reporters/src/CoverageReporter.ts5.6MixedCyclomatic Complexity: CoverageReporter._checkThreshold (cyclomatic 31)
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
packages/jest-snapshot/src/index.ts5.9MixedCyclomatic Complexity: index._toMatchSnapshot (cyclomatic 18)
packages/jest-config/src/normalize.ts6.0MixedExplicit Debt: TodoComment
packages/jest-jasmine2/src/jasmine/Env.ts6.0MixedExplicit Debt: TodoComment
packages/jest-runtime/src/internals/EsmLoader.ts6.0MixedExplicit Debt: TodoComment
packages/jest-config/src/index.ts6.0MixedExplicit Debt: TodoComment

How the grades work

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

Critical — 98

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 843

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 352

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

Could not be resolved — 10

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 74 of 74 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 74 dimensions across the health lenses
D1D2D3D5D6D9D10D12D13D14D15D16D17D19D20D23D26D28D29D30D34D35D36D37D43AX10AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1192 of 1293 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a178c5-9af1-7681-88ea-60d7ae34a9b0.

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

Run transparency — what happened this run

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

  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the jest run in the repository root produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the jest run in the repository root produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/angular/ was NOT MEASURED: the jest run in examples/angular/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/async/ was NOT MEASURED: the jest run in examples/async/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/automatic-mocks/ was NOT MEASURED: the jest run in examples/automatic-mocks/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/expect-extend/ was NOT MEASURED: the jest run in examples/expect-extend/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/getting-started/ was NOT MEASURED: the jest run in examples/getting-started/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/jquery/ was NOT MEASURED: the jest run in examples/jquery/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/manual-mocks/ was NOT MEASURED: the jest run in examples/manual-mocks/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/module-mock/ was NOT MEASURED: the jest run in examples/module-mock/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/react/ was NOT MEASURED: the jest run in examples/react/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/react-native/ was NOT MEASURED: the jest run in examples/react-native/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/react-testing-library/ was NOT MEASURED: the jest run in examples/react-testing-library/ produced no per-test report (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/babel-jest/src/index.ts`, `packages/jest-runtime/src/internals/ModuleRegistries.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.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • 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. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
  • M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • 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. 56 further occurrence(s) are not listed individually; the score already reflects all 96.
  • 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.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity4.6 / 10Weak✓ Tool-verified

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

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

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

57 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was normalize.normalize at 213. A further 3 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 SpyRegistry.constructor at 25 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/jest-jasmine2/src/jasmine/spyRegistry.ts (SpyRegistry.constructor at 25), packages/jest-haste-map/src/watchers/ChangeQueue.ts (ChangeQueue.onChange at 21), packages/jest-config/src/setFromArgv.ts (setFromArgv.setFromArgv at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

normalize.normalize (cyclomatic 213)packages/jest-config/src/normalize.ts:536
eventHandler.eventHandler (cyclomatic 55)packages/jest-circus/src/eventHandler.ts:27
Env.constructor (cyclomatic 50)packages/jest-jasmine2/src/jasmine/Env.ts:122
Env.jasmineEnv (cyclomatic 50)packages/jest-jasmine2/src/jasmine/Env.ts:59
jasmineUtils.eq (cyclomatic 47)packages/expect-utils/src/jasmineUtils.ts:63

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with normalize.normalize (cyclomatic 213). — Refactoring it lifts Cyclomatic Complexity from 4.6 to about 6.2/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity3.3 / 10Weak✓ Tool-verified

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

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

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

102 method(s) exceeded the cognitive complexity threshold of 15; the worst was normalize.normalize at 115.

normalize.normalize (cognitive 115)packages/jest-config/src/normalize.ts:536
EsmLoader.walkGraphSync (cognitive 97)packages/jest-runtime/src/internals/EsmLoader.ts:681
joinAlignedDiffs.joinAlignedDiffsNoExpand (cognitive 87)packages/jest-diff/src/joinAlignedDiffs.ts:112
utils.iterableEquality (cognitive 79)packages/expect-utils/src/utils.ts:175
watchman.watchmanCrawl (cognitive 69)packages/jest-haste-map/src/crawlers/watchman.ts:93

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

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with normalize.normalize (cognitive 115), EsmLoader.walkGraphSync (cognitive 97), joinAlignedDiffs.joinAlignedDiffsNoExpand (cognitive 87). — 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 8 together lifts Cognitive Complexity from 3.3 to about 4.8/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

35 god class(es) detected.

FunctionTooLong: Env.jasmineEnv · ×12packages/jest-jasmine2/src/jasmine/Env.ts:59
FileTooLong: internals/EsmLoader.ts · ×10packages/jest-runtime/src/internals/EsmLoader.ts
MethodTooLong: Env.constructor · ×6packages/jest-jasmine2/src/jasmine/Env.ts:122
TooManyMethods: EsmLoader · ×4packages/jest-runtime/src/internals/EsmLoader.ts:291
ClassTooLong: matchers · ×3REDACTED:1

What to do

  1. Resolve the 12 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), Env.ts, watch.ts. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 10 FileTooLong finding(s) in God Classes — start with REDACTED (2), EsmLoader.ts, spyMatchers.ts. — One of this dimension's main actionable groups (10 warning-level).
  3. Resolve the 6 MethodTooLong finding(s) in God Classes — start with Env.ts, JestGlobals.ts, EsmLoader.ts. — One of this dimension's main actionable groups (6 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D5 · Coupling6.9 / 10Adequate✓ Tool-verified

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

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

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

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

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

Off the main sequence: @jest/diff-sequences · ×12
Unstable project @jest/core
Unstable project @jest/environment-jsdom-abstract
Unstable project @jest/reporters
Unstable project jest-circus

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

What to do

  1. Resolve the 12 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 1 Unstable project @jest/core finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project @jest/environment-jsdom-abstract finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 79 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution6.0 / 10Adequate✓ Tool-verified

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

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

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

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

What to do

  1. Improve Test Distribution — currently 6.0/10. — 5780 test methods: 3990 unit, 0 integration, 0 BDD, 1790 e2e. The JavaScript/TypeScript suite contributes 5780 `it`/`test` case(s) across 1056 test file(s) declaring at least one; its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.0 / 10Adequategated by 55 critical findings✓ Tool-verified

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

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

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

86 skipped (51 with a documented reason), 346 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5778 tests (5 harness-style project(s) excluded from the assertion penalty).

No assertions (empty test): does not throw when the child process returns a strange message · ×55packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:375
No assertions: skipping test on broken platform · ×239packages/jest-worker/src/workers/__tests__/WorkerEdgeCases.test.ts:45
Skipped test: (unnamed test) · ×35packages/jest-types/__typetests__/globals.test.ts:333
Test project verifies nothing: benchmarks/test-file-overhead · ×28benchmarks/test-file-overhead/0.test.js:8
No direct assertions: fails with error without proper message · ×52e2e/stack-trace/__tests__/stackTraceWithoutMessage.test.js:9

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

What to do

  1. Resolve the 55 No assertions (empty test) finding(s) in Test Quality — start with globals.test.ts (10), toThrowMatchers.test.ts (6), asymmetricMatchers.test.ts (4). — One of this dimension's main actionable groups (55 issue-level).
  2. Resolve the 239 No assertions finding(s) in Test Quality — start with asymmetricMatchers.test.ts (53), matchers.test.js (27), toThrowMatchers.test.ts (22). — One of this dimension's main actionable groups (239 warning-level).
  3. Resolve the 35 Skipped test finding(s) in Test Quality — start with globals.test.ts (7), concurrent-skip.test.js (4), Utils.ts (3). — One of this dimension's main actionable groups (35 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene5.5 5.4 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 5.4 / 10 · rule-coverage 98% · ceiling Verified

56 outdated direct production npm dependency(ies) of 116 graded, 19 pinning defect(s), across 106 package.json (89 of them the product) and 33 committed lockfile(s). 116 of 118 resolved direct production dependency(ies) were graded against registry.npmjs.org (2 not published there — private or renamed). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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.

Floating npm dependency: @types/node · ×19
Deprecated: discord.js · ×2e2e/native-esm/package.json:8
Outdated (npm): @types/jsdom · ×11packages/jest-environment-jsdom-abstract/package.json:31
Deprecated: glob · ×10e2e/coverage-transform-instrumented/REDACTED:1517
Outdated (npm): @angular/common · ×45

What to do

  1. Resolve the 19 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (19 warning-level).
  2. Resolve the 11 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (11). — One of this dimension's main actionable groups (11 recommendation-level).
  3. 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).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 116 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 118 production dependency(ies) this repository's committed lockfile resolves, across 89 product package.json manifest(s). Its 334 `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. A further 2 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: packages/jest-config/src/normalize.ts (3×213=639); packages/jest-runtime/src/internals/EsmLoader.ts (11×47=517); packages/jest-runtime/src/internals/CjsLoader.ts (9×25=225) Repeated repair below the complexity floor: packages/jest-resolve/src/resolver.ts (7 of 10 changes were fixes); packages/jest-runtime/src/internals/ModuleRegistries.ts (5 of 8 changes were fixes); REDACTED (4 of 7 changes were fixes)

Hotspot: packages/jest-config/src/normalize.ts · ×15packages/jest-config/src/normalize.ts:536
Repeated repair: packages/jest-resolve/src/resolver.ts · ×4packages/jest-resolve/src/resolver.ts:174

What to do

  1. Resolve the 15 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED (3), normalize.ts, EsmLoader.ts. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with resolver.ts, ModuleRegistries.ts, REDACTED. — One of this dimension's main actionable groups (4 warning-level).

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

D16 · Bus Factor9.0 / 10Exemplary✓ Tool-verified

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

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

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

20 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 206 of the 439 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

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

✓ On the Gold path — maintain.

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

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

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

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

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

35 deducted task-comment markers across 57236 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×35packages/jest-worker/src/workers/ChildProcessWorker.ts:263

What to do

  1. Resolve the 35 TodoComment finding(s) in Explicit Debt — start with REDACTED (7), raw-types.ts (3), ChildProcessWorker.ts (2). — One of this dimension's main actionable groups (35 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D23 · Boundary Type-Coupling9.4 / 10Stronggated by 18 serious findings✓ Tool-verified

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

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

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

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

18 domain type(s) cross context boundaries across 65 contexts.

Cross-context type State (jest-runtime → jest-circus) · ×3packages/jest-circus/src/formatNodeAssertErrors.ts:41
Cross-context type State (jest-runtime → expect) · ×2packages/expect/src/jestMatchersObject.ts:44
Cross-context type Event (jest-types → jest-circus) · ×2packages/jest-circus/src/formatNodeAssertErrors.ts:41
Cross-context type State (jest-runtime → jest-watcher) · ×2packages/jest-watcher/src/TestWatcher.ts:15
Cross-context type BlockMode (jest-types → jest-circus)packages/jest-circus/src/utils.ts:41

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

What to do

  1. Resolve the 3 Cross-context type State (jest-runtime → jest-circus) finding(s) in Boundary Type-Coupling — start with state.ts (2), formatNodeAssertErrors.ts. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Cross-context type State (jest-runtime → expect) finding(s) in Boundary Type-Coupling — start with jestMatchersObject.ts (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Cross-context type Event (jest-types → jest-circus) finding(s) in Boundary Type-Coupling — start with formatNodeAssertErrors.ts, jestAdapterInit.ts. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)3.9 / 10Weak✓ Tool-verified

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

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

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

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

16 finding(s): 0 critical, 1 high, 15 medium, 0 low. semgrep hit a parse error in 16 file(s) — `e2e/explicit-resource-management/__tests__/index.js` (line 12, line 27, line 42), `e2e/native-esm/__tests__/native-esm-import-assertions.test.js` (line 8), `e2e/native-esm/__tests__/native-esm-import-attributes.test.js` (line 8), `packages/babel-jest/src/index.ts` (line 186), `packages/jest-mock/__typetests__/mock-functions.test.ts` (line 233), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

17 finding(s): 3 critical, 8 high, 4 medium, 2 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness7.6 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

Orphaned knowledge · ×3packages/expect/src/spyMatchers.ts:1
Orphaned file · ×45packages/jest-worker/src/workers/ChildProcessWorker.ts:1
Further orphaned files (smaller)

What to do

  1. Resolve the 45 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (5), test.js (2), types.ts (2). — One of this dimension's main actionable groups (45 recommendation-level).
  2. Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with spyMatchers.ts, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: REDACTED↔config.ts 75%; normalize.ts↔config.ts 63%; ValidConfig.ts↔REDACTED 51%

Boundary-crossing change coupling: CoverageWorker.ts ↔ testWorker.tspackages/jest-reporters/src/CoverageWorker.ts:1
Change coupling: REDACTED ↔ config.ts · ×4packages/jest-config/src/index.ts:1

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with CoverageWorker.ts. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 4 Change coupling finding(s) in Change Coupling — start with REDACTED, normalize.ts, ValidConfig.ts. — One of this dimension's main actionable groups (4 warning-level).

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

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 2 Malicious package finding(s) in Malicious Dependencies — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.9 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

AX6 · Interface segregation9.7 / 10Exemplary✓ Tool-verified

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

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

  • `Matchers` declares 33 required operations: `_unusedT`, `toBe`, `toBeCloseTo`, `toBeDefined`, `toBeFalsy`, `toBeGreaterThan`, `toBeGreaterThanOrEqual`, `toBeInstanceOf`, `toBeLessThan`, `toBeLessThanOrEqual`, `toBeNaN`, `toBeNull`, `toBeTruthy`, `toBeUndefined`, `toContain`, `toContainEqual`, `toEqual`, `toHaveBeenCalled`, `toHaveBeenCalledTimes`, `toHaveBeenCalledWith`, `toHaveBeenNthCalledWith`, `toHaveBeenLastCalledWith`, `toHaveLastReturnedWith`, `toHaveLength`, `toHaveNthReturnedWith`, `toHaveProperty`, `toHaveReturned`, `toHaveReturnedTimes`, `toHaveReturnedWith`, `toMatch`, `toMatchObject`, `toStrictEqual`, `toThrow`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/expect/src/types.ts:146
  • `Jest` declares 45 required operations: `advanceTimersByTime`, `advanceTimersByTimeAsync`, `advanceTimersToNextFrame`, `advanceTimersToNextTimer`, `advanceTimersToNextTimerAsync`, `autoMockOff`, `autoMockOn`, `clearAllMocks`, `clearAllTimers`, `createMockFromModule`, `deepUnmock`, `disableAutomock`, `doMock`, `dontMock`, `enableAutomock`, `getRealSystemTime`, `getSeed`, `getTimerCount`, `isEnvironmentTornDown`, `isolateModules`, `isolateModulesAsync`, `mock`, `unstable_mockModule`, `now`, `onGenerateMock`, `requireActual`, `requireMock`, `resetAllMocks`, `resetModules`, `restoreAllMocks`, `retryTimes`, `runAllImmediates`, `runAllTicks`, `runAllTimers`, `runAllTimersAsync`, `runOnlyPendingTimers`, `runOnlyPendingTimersAsync`, `setMock`, `setSystemTime`, `setTimeout`, and 5 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/jest-environment/src/index.ts:69
  • `MockInstance` declares 18 required operations: `getMockImplementation`, `getMockName`, `mockClear`, `mockReset`, `mockRestore`, `mockImplementation`, `mockImplementationOnce`, `withImplementation`, `withImplementation`, `mockName`, `mockReturnThis`, `mockReturnValue`, `mockReturnValueOnce`, `mockResolvedValue`, `mockResolvedValueOnce`, `mockRejectedValue`, `mockRejectedValueOnce`, `whenCalledWith`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/jest-mock/src/index.ts:178

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs8.5 / 10Strong✓ Tool-verified

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

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

  • `eventHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapterInit.ts:354
  • `createSnapshotResolver` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/jest-snapshot/src/SnapshotResolver.ts:50
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×37) — e2e/Utils.ts:348, e2e/Utils.ts:363, e2e/Utils.ts:381, …
  • `start` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/jest-jasmine2/src/jasmine/JsApiReporter.ts:38

What to do

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

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

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

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

What to do

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

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy8.0 / 10Strong✓ Tool-verified

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

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

  • docs/ECMAScriptModules.md names Node.js 24, but the repository declares engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ECMAScriptModules.md:67

What to do

  • Reconcile the README with reality: docs/ECMAScriptModules.md names Node.js 24, but the repository declares engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

  • `yarn lint:prettier:ci` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted. — .github/workflows/nodejs.yml:87

What to do

  • Add `--check` to the prettier step in `.github/workflows/nodejs.yml` so a change that is not formatted fails CI, instead of being silently reformatted into a checkout that is thrown away — or, if reformatting the branch is the intent, commit the result back so the fix reaches the repository.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

  • No logging call was found in the 447 JavaScript/TypeScript production file(s) this check read across 63 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Adopt pino (or winston) and log at meaningful points in the services you run.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 23868 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF1 · Benchmark discipline7.5 / 10Strong✓ Tool-verified

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

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

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `fs.existsSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/create-jest/src/runCreate.ts:55
  • `fs.readFileSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/create-jest/src/runCreate.ts:65
  • `fs.existsSync` in `callback to JEST_CONFIG_EXT_ORDER.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/create-jest/src/runCreate.ts:76
  • `fs.writeFileSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/create-jest/src/runCreate.ts:143, packages/create-jest/src/runCreate.ts:155
  • `fs.existsSync` in `callback to projects.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-config/src/index.ts:442
  • `fs.lstatSync` in `callback to projects.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-config/src/index.ts:443
  • `fs.readFileSync` in `readConfigFileAndSetRootDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-config/src/readConfigFileAndSetRootDir.ts:90
  • `fs.rmSync` in `runCLI` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-core/src/cli/index.ts:73
  • `fs.writeFileSync` in `processResults` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-core/src/runJest.ts:203
  • `fs.writeFileSync` in `runJest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-core/src/runJest.ts:322
  • `fs.readFileSync` in `getContent` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-haste-map/src/worker.ts:43
  • `fs.readFileSync` in `worker` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-haste-map/src/worker.ts:95
  • `fs.readFileSync` in `getSha1` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-haste-map/src/worker.ts:103
  • `fs.existsSync` in `callback to result.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-reporters/src/CoverageReporter.ts:494
  • `fs.readFileSync` in `callback to result.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/jest-reporters/src/CoverageReporter.ts:497, packages/jest-reporters/src/CoverageReporter.ts:512
  • `fs.statSync` in `generateEmptyCoverage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-reporters/src/generateEmptyCoverage.ts:46
  • `fs.readFileSync` in `runTestInternal` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-runner/src/runTest.ts:90
  • `fs.readFileSync` in `_transformAndBuildScriptAsync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/jest-transform/src/ScriptTransformer.ts:636

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 Safety4.5 / 10Weak✓ Tool-verified

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

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

  • 922 typed · 1124 plain JS — the untyped files are e2e/MockStdinWatchPlugin.js, e2e/__tests__/nodeURLManualMocks.test.js, e2e/__tests__/testFailingSnapshot.test.js, e2e/async-regenerator/__tests__/test.js, e2e/auto-clear-mocks/with-auto-clear/__tests__/index.js, e2e/auto-clear-mocks/with-auto-clear/index.js (+1118 more).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.3 / 10Exemplary✓ Tool-verified

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

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

  • 12 duplicated blocks under packages/ have copies in at least two of the sibling directories expect, jest-circus, jest-config, jest-diff, jest-environment-jsdom-abstract, jest-environment-node (+9 more sibling(s) not listed) — 9 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/jest-circus/src/formatNodeAssertErrors.ts:77
  • packages/jest-worker/src/workers/ChildProcessWorker.ts:57 · packages/jest-worker/src/workers/NodeThreadsWorker.ts:31 — the two spans are one implementation copied and then locally edited — 1166 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-worker/src/workers/ChildProcessWorker.ts:57
  • packages/jest-worker/src/workers/processChild.ts:26 · packages/jest-worker/src/workers/threadChild.ts:28 — the two spans are one implementation copied and then locally edited — 664 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-worker/src/workers/processChild.ts:26
  • packages/expect/src/spyMatchers.ts:953 · packages/expect/src/spyMatchers.ts:1102 — the two spans are one implementation copied and then locally edited — 568 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/expect/src/spyMatchers.ts:953
  • packages/jest-circus/src/formatNodeAssertErrors.ts:77 · packages/jest-jasmine2/src/assertionErrorMessage.ts:35 — the two spans are one implementation copied and then locally edited — 528 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-circus/src/formatNodeAssertErrors.ts:77
  • packages/jest-console/src/BufferedConsole.ts:79 · packages/jest-console/src/CustomConsole.ts:81 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/jest-console/src/BufferedConsole.ts:79
  • packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:43 · REDACTED:234 — the two spans are one implementation copied and then locally edited — 401 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:43
  • packages/expect/src/index.ts:170 · packages/expect/src/index.ts:226 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/expect/src/index.ts:170
  • packages/jest-transform/src/ScriptTransformer.ts:627 · packages/jest-transform/src/ScriptTransformer.ts:675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/jest-transform/src/ScriptTransformer.ts:627
  • packages/jest-environment-jsdom-abstract/src/index.ts:140 · packages/jest-environment-node/src/index.ts:209 — the two spans are one implementation copied and then locally edited — 168 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-environment-jsdom-abstract/src/index.ts:140
  • packages/jest-config/src/ValidConfig.ts:39 · packages/jest-config/src/ValidConfig.ts:223 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-config/src/ValidConfig.ts:39
  • packages/expect/src/toThrowMatchers.ts:150 · packages/expect/src/toThrowMatchers.ts:346 — the two spans are one implementation copied and then locally edited — 248 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/expect/src/toThrowMatchers.ts:150
  • packages/jest-resolve/src/resolver.ts:241 · packages/jest-resolve/src/resolver.ts:316 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-resolve/src/resolver.ts:241
  • packages/jest-core/src/plugins/TestNamePattern.ts:20 · packages/jest-core/src/plugins/TestPathPattern.ts:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/jest-core/src/plugins/TestNamePattern.ts:20
  • packages/pretty-format/src/collections.ts:45 · packages/pretty-format/src/collections.ts:107 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/pretty-format/src/collections.ts:45
  • packages/jest-fake-timers/src/legacyFakeTimers.ts:351 · packages/jest-fake-timers/src/legacyFakeTimers.ts:386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/jest-fake-timers/src/legacyFakeTimers.ts:351
  • packages/jest-jasmine2/src/jasmineAsyncInstall.ts:48 · packages/jest-jasmine2/src/jasmineAsyncInstall.ts:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-jasmine2/src/jasmineAsyncInstall.ts:48
  • packages/expect/src/spyMatchers.ts:814 · packages/expect/src/spyMatchers.ts:905 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/expect/src/spyMatchers.ts:814
  • packages/jest-transform/src/ScriptTransformer.ts:727 · packages/jest-transform/src/ScriptTransformer.ts:755 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-transform/src/ScriptTransformer.ts:727
  • packages/pretty-format/src/plugins/AsymmetricMatcher.ts:17 · packages/pretty-format/src/plugins/Immutable.ts:62 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/pretty-format/src/plugins/AsymmetricMatcher.ts:17
  • packages/jest-changed-files/src/hg.ts:16 · packages/jest-changed-files/src/sl.ts:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/jest-changed-files/src/hg.ts:16
  • packages/jest-resolve/src/resolver.ts:885 · packages/jest-resolve/src/resolver.ts:947 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-resolve/src/resolver.ts:885
  • packages/expect/src/spyMatchers.ts:612 · packages/expect/src/spyMatchers.ts:689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/expect/src/spyMatchers.ts:612
  • packages/jest-reporters/src/AgentReporter.ts:41 · packages/jest-reporters/src/DefaultReporter.ts:167 — the two spans are one implementation copied and then locally edited — 89 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/jest-reporters/src/AgentReporter.ts:41
  • packages/jest-core/src/SnapshotInteractiveMode.ts:75 · packages/jest-core/src/SnapshotInteractiveMode.ts:109 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-core/src/SnapshotInteractiveMode.ts:75
  • packages/jest-transform/src/ScriptTransformer.ts:540 · packages/jest-transform/src/ScriptTransformer.ts:605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/jest-transform/src/ScriptTransformer.ts:540
  • packages/diff-sequences/src/index.ts:251 · packages/diff-sequences/src/index.ts:384 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/diff-sequences/src/index.ts:251
  • packages/jest-core/src/SnapshotInteractiveMode.ts:52 · packages/jest-core/src/SnapshotInteractiveMode.ts:94 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-core/src/SnapshotInteractiveMode.ts:52
  • packages/pretty-format/src/plugins/Immutable.ts:25 · packages/pretty-format/src/plugins/Immutable.ts:130 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/pretty-format/src/plugins/Immutable.ts:25
  • packages/jest-core/src/FailedTestsInteractiveMode.ts:118 · packages/jest-core/src/FailedTestsInteractiveMode.ts:146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/jest-core/src/FailedTestsInteractiveMode.ts:118
  • packages/jest-matcher-utils/src/index.ts:250 · packages/jest-snapshot/src/printSnapshot.ts:141 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/jest-matcher-utils/src/index.ts:250
  • packages/jest-mock/src/index.ts:1375 · packages/jest-mock/src/index.ts:1468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/jest-mock/src/index.ts:1375
  • REDACTED:215 · REDACTED:389 · REDACTED:408 · REDACTED:427 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — REDACTED:215
  • packages/expect/src/spyMatchers.ts:281 · packages/jest-matcher-utils/src/index.ts:293 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/expect/src/spyMatchers.ts:281
  • packages/expect/src/spyMatchers.ts:892 · packages/expect/src/spyMatchers.ts:1157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/expect/src/spyMatchers.ts:892
  • REDACTED:537 · REDACTED:590 — 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:537
  • packages/expect/src/spyMatchers.ts:646 · packages/expect/src/spyMatchers.ts:726 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/expect/src/spyMatchers.ts:646
  • packages/expect/src/spyMatchers.ts:705 · packages/expect/src/spyMatchers.ts:883 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/expect/src/spyMatchers.ts:705
  • packages/jest-circus/src/formatNodeAssertErrors.ts:23 · packages/jest-jasmine2/src/assertionErrorMessage.ts:17 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/jest-circus/src/formatNodeAssertErrors.ts:23
  • packages/jest-jasmine2/src/jasmine/Spec.ts:275 · packages/jest-jasmine2/src/jasmine/Suite.ts:135 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/jest-jasmine2/src/jasmine/Spec.ts:275

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

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

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

  • e2e/resolve/__tests__/resolve.test.js:68 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/jest-resolve) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — e2e/resolve/__tests__/resolve.test.js:68
  • packages/jest-config/src/normalize.ts:602 imports jest-jasmine2, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/jest-config/src/normalize.ts:602
  • packages/jest-config/src/readConfigFileAndSetRootDir.ts:212 imports esbuild-register/dist/node, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/jest-config/src/readConfigFileAndSetRootDir.ts:212
  • packages/jest/src/index.ts:19 imports jest-config, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/jest/src/index.ts:19

What to do

  • Fix the listed violations: declare the workspace packages these files import in the importing package's own package.json dependencies (2 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (2 rows).
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

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

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

  • (anonymous) has cyclomatic complexity 140 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-config/src/normalize.ts:643
  • normalize has cyclomatic complexity 64 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-config/src/normalize.ts:536
  • eventHandler has cyclomatic complexity 53 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-circus/src/eventHandler.ts:27
  • walkGraphSync has cyclomatic complexity 48 and cognitive complexity 99; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-runtime/src/internals/EsmLoader.ts:681
  • eq has cyclomatic complexity 47 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/expect-utils/src/jasmineUtils.ts:63
  • (anonymous) has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/expect-utils/src/utils.ts:182
  • (anonymous) has cyclomatic complexity 35 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-diff/src/joinAlignedDiffs.ts:115
  • runTestInternal has cyclomatic complexity 34 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-runner/src/runTest.ts:82
  • onRunComplete has cyclomatic complexity 31 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-reporters/src/NotifyReporter.ts:34
  • updateGlobalConfig has cyclomatic complexity 30 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-core/src/lib/updateGlobalConfig.ts:16
  • getSummary has cyclomatic complexity 29 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-reporters/src/getSummary.ts:82
  • watchmanCrawl has cyclomatic complexity 27 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-haste-map/src/crawlers/watchman.ts:93
  • (anonymous) has cyclomatic complexity 27 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:151
  • requireModule has cyclomatic complexity 27 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-runtime/src/internals/CjsLoader.ts:77
  • runJest has cyclomatic complexity 24 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-core/src/runJest.ts:220
  • printComplexValue has cyclomatic complexity 24 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. — packages/pretty-format/src/index.ts:204
  • shouldInstrument has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-transform/src/shouldInstrument.ts:32
  • stringToBytes has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/jest-config/src/stringToBytes.ts:24
  • mock has cyclomatic complexity 23 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/babel-plugin-jest-hoist/src/index.ts:118

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files6.8 / 10Adequate✓ Tool-verified

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

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

  • packages/jest-runtime/src/internals/EsmLoader.ts has 2239 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-runtime/src/internals/EsmLoader.ts:1
  • packages/jest-mock/src/index.ts has 1455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-mock/src/index.ts:1
  • packages/expect/src/spyMatchers.ts has 1162 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/expect/src/spyMatchers.ts:1
  • packages/jest-config/src/normalize.ts has 1159 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-config/src/normalize.ts:1
  • packages/jest-resolve/src/resolver.ts has 1029 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-resolve/src/resolver.ts:1
  • packages/jest-transform/src/ScriptTransformer.ts has 982 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-transform/src/ScriptTransformer.ts:1
  • REDACTED has 874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/jest-cli/src/args.ts has 785 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-cli/src/args.ts:1
  • packages/diff-sequences/src/index.ts has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/diff-sequences/src/index.ts:1
  • REDACTED has 711 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
  • REDACTED has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/jest-jasmine2/src/jasmine/Env.ts has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-jasmine2/src/jasmine/Env.ts:1
  • REDACTED has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/jest-fake-timers/src/legacyFakeTimers.ts has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-fake-timers/src/legacyFakeTimers.ts:1
  • packages/jest-core/src/watch.ts has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-core/src/watch.ts:1
  • packages/jest-matcher-utils/src/index.ts has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-matcher-utils/src/index.ts:1
  • packages/expect-utils/src/utils.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/expect-utils/src/utils.ts:1
  • packages/jest-snapshot/src/index.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-snapshot/src/index.ts:1
  • packages/pretty-format/src/index.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/pretty-format/src/index.ts:1
  • REDACTED has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/jest-circus/src/utils.ts has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-circus/src/utils.ts:1
  • packages/expect/src/toThrowMatchers.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/expect/src/toThrowMatchers.ts:1
  • packages/jest-config/src/index.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-config/src/index.ts:1
  • packages/jest-core/src/TestScheduler.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-core/src/TestScheduler.ts:1
  • packages/jest-reporters/src/CoverageReporter.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-reporters/src/CoverageReporter.ts:1
  • packages/jest-circus/src/run.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-circus/src/run.ts:1
  • packages/jest-worker/src/workers/ChildProcessWorker.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-worker/src/workers/ChildProcessWorker.ts:1
  • packages/jest-environment/src/index.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-environment/src/index.ts:1
  • packages/jest-snapshot/src/State.ts has 456 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-snapshot/src/State.ts:1
  • packages/jest-reporters/src/GitHubActionsReporter.ts has 431 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-reporters/src/GitHubActionsReporter.ts:1
  • packages/jest-runtime/src/internals/JestGlobals.ts has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-runtime/src/internals/JestGlobals.ts:1
  • packages/expect/src/index.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/expect/src/index.ts:1
  • packages/jest-core/src/runJest.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-core/src/runJest.ts:1
  • packages/jest-snapshot/src/utils.ts has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/jest-snapshot/src/utils.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage9.5 / 10Exemplary✓ Tool-verified

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

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

  • e2e/native-esm/__tests__/native-esm-mocks.test.js:18 imports '../mockedModule.mjs', 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. — e2e/native-esm/__tests__/native-esm-mocks.test.js:18
  • e2e/native-esm/virtualMockReexport.mjs:7 imports './mockedModule.mjs', 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. — e2e/native-esm/virtualMockReexport.mjs:7
  • e2e/presets/cjs/__tests__/index.js:10 imports './test.foo', 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. — e2e/presets/cjs/__tests__/index.js:10
  • e2e/presets/js-type-module/__tests__/index.js:10 imports './test.foo', 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. — e2e/presets/js-type-module/__tests__/index.js:10
  • e2e/presets/js/__tests__/index.js:10 imports './test.foo', 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. — e2e/presets/js/__tests__/index.js:10
  • e2e/presets/json/__tests__/index.js:10 imports './test.foo', 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. — e2e/presets/json/__tests__/index.js:10
  • e2e/presets/mjs/__tests__/index.js:10 imports './test.foo', 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. — e2e/presets/mjs/__tests__/index.js:10
  • e2e/resolve-async/__tests__/resolveAsync.test.js:8 imports '../some-file', 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. — e2e/resolve-async/__tests__/resolveAsync.test.js:8
  • packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-automock-then-missing.mjs:9 imports './does-not-exist.js', 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. — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-automock-then-missing.mjs:9
  • packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-cjs-then-missing.mjs:9 imports './does-not-exist.js', 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. — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-cjs-then-missing.mjs:9
  • packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-factory-then-missing.mjs:9 imports './does-not-exist.js', 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. — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-factory-then-missing.mjs:9
  • packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/unmarked-esm-missing-dep.js:8 imports './does-not-exist.js', 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. — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/unmarked-esm-missing-dep.js:8
  • 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. (×18) — packages/jest-schemas/src/raw-types.ts:1, scripts/buildUtils.mjs:1, scripts/buildTs.mjs:1, …

What to do

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

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

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

  • This repository declares test tooling, and the ✓ above records that declaration — but e2e/native-esm/__tests__/native-esm-mocks.test.js and 11 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. — e2e/native-esm/__tests__/native-esm-mocks.test.js:18
R7 · Dead Code8.9 / 10Strong✓ Tool-verified

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

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

  • 1 file(s) (~11 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. — e2e/bad-source-map
  • 1 file(s) (~42 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. — e2e/before-all-filtered
  • 1 file(s) (~65 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. — e2e/before-all-skipped
  • Unreachable from the 403 application, 92 tooling and 1765 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (403 application, 92 tooling, 1765 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 (×5) — packages/pretty-format/__benchmarks__/test.js, packages/jest-worker/__benchmarks__/test.js, packages/jest-runtime/__benchmarks__/test.js, …
  • no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/jest-worker/__benchmarks__/workers/jest_worker.js, packages/jest-worker/__benchmarks__/workers/worker_farm.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/jest-worker/__benchmarks__/workers/pi.js
  • no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/jest-worker/__benchmarks__/test.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/jest-worker/__benchmarks__/workers/worker_farm.js, packages/jest-worker/__benchmarks__/workers/jest_worker.js
  • Nothing imports this binding — it is safe to review for removal. (×12) — packages/jest-core/src/types.ts:33, packages/jest-haste-map/src/watchers/types.ts:19, packages/jest-worker/__typetests__/testWorker.ts:8, …
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×6) — e2e/stack-trace-source-maps-with-coverage/lib.ts:8, packages/jest-reporters/src/__tests__/getResultHeader.test.js:14, packages/jest-runner/__typetests__/jest-runner.test.ts:54, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×25) — e2e/__tests__/nativeEsm.test.ts:29, e2e/babel-plugin-jest-hoist/__tests__/integration.test.js:21, e2e/custom-haste-map/__tests__/hasteExample.test.js:11, …
  • 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. (×2)
  • Declared in packages/babel-plugin-jest-hoist/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.
  • Every import is type-only — move it to devDependencies. — packages/jest-reporters/src/CoverageReporter.ts:10

What to do

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

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

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

  • REDACTED → packages/expect/src/jestMatchersObject.ts → REDACTED — REDACTED:18
  • packages/jest-circus/src/eventHandler.ts → packages/jest-circus/src/globalErrorHandlers.ts → packages/jest-circus/src/state.ts → packages/jest-circus/src/eventHandler.ts (one verified cycle inside a mutually-dependent group of 4 files) — packages/jest-circus/src/eventHandler.ts:10

What to do

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

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.

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

  • MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×11) — packages/babel-jest/src/index.ts:93, packages/jest-config/src/normalize.ts:365, packages/jest-create-cache-key-function/src/index.ts:54, …
  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 11 sites, not one: `packages/babel-jest/src/index.ts:93` (createHash("sha1")), `packages/jest-config/src/normalize.ts:365` (createHash("sha1")), `packages/jest-create-cache-key-function/src/index.ts:54` (createHash("sha1")), `packages/jest-create-cache-key-function/src/index.ts:97` (createHash("sha1")), `REDACTED:299` (createHash("sha1")), `REDACTED:351` (createHash("sha1")), `packages/jest-haste-map/src/worker.ts:25` (createHash("sha1")), `packages/jest-transform/src/ScriptTransformer.ts:124` (createHash("sha1")), and 3 further site(s). Each is a separate decision — fixing only the line this row cites leaves the others in place.
  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X13 · Undrained process stream3.5 / 10Weak✓ Tool-verified

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

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

  • `spawn` pipes `stderr` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `child.stderr`, while `child.stdout` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stderr (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`child.stderr.on('data', …)`, or `child.stderr.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot. — packages/jest-haste-map/src/crawlers/node.ts:127

What to do

  • Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document1.8 / 10Critical✓ Tool-verified

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

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

  • `serialize` is exported, takes a document from its caller (line 97) and hands it to `getChildren`, which calls itself at line 37 (`getChildren`) with a piece of `arg` — and nowhere in `getChildren` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getChildren` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/pretty-format/src/plugins/ReactElement.ts:37
  • `deepMerge` is exported and takes `target: any` from its caller, and it calls itself at line 118 (`deepMerge`) with a piece of `target` — and nowhere in `deepMerge` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepMerge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/jest-snapshot/src/utils.ts:118
  • `replaceMatchedToAsymmetricMatcher` is exported, takes a document from its caller (line 412) and hands it to `_replaceMatchedToAsymmetricMatcher`, which calls itself at line 461 (`_replaceMatchedToAsymmetricMatcher`) with a piece of `replacedExpected` — and nowhere in `_replaceMatchedToAsymmetricMatcher` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `_replaceMatchedToAsymmetricMatcher` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/jest-matcher-utils/src/index.ts:461
  • `getPath` is exported and takes `object: Record<string, any>` from its caller, and it calls itself at line 83 (`getPath`) with a piece of `object` — and nowhere in `getPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/expect-utils/src/utils.ts:83
  • `getObjectSubset` is exported and takes `object: any` from its caller, and it calls itself at line 127 (`getObjectSubset`) with a piece of `object` (and at line 154) — and nowhere in `getObjectSubset` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getObjectSubset` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/expect-utils/src/utils.ts:127

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×27) — packages/jest-util/src/createProcessObject.ts:140, packages/jest-util/src/garbage-collection-utils.ts:124, packages/jest-transform/src/ScriptTransformer.ts:929, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/jest-jasmine2/src/jasmineAsyncInstall.ts:230

What to do

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

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

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

X5 · Nullable reference types9.0 / 10Strong✓ Tool-verified

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

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

  • 124/129 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~1.8 `!` null assertions per 1k TypeScript source lines — 111 assertion(s) across the 60175 source line(s) of the 349 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/jest-runtime/src/internals/EsmLoader.ts (11), packages/jest-worker/src/workers/threadChild.ts (9), packages/jest-fake-timers/src/legacyFakeTimers.ts (7). 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

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

LensScoreRatingImpact
Code Health62%Adequate — gated by D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture87%StrongStrongest area.
Maturity59%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness36%Weak — gated by R8, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security54%Adequate — gated by D29, D30, D43Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance66%AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

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

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • 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 measured — JavaScript/TypeScript suite did not run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.js,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • 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 — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 98 finding(s)
D10 · Test Quality · No assertions (empty test) · ×55
  • No assertions (empty test): does not throw when the child process returns a strange message packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:375 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): does not throw when the thread returns a strange message packages/jest-worker/src/workers/__tests__/NodeThreadsWorker.test.ts:372 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:214 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:215 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:241 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:242 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:256 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:258 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:298 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:299 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:322 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:323 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): ClassLike packages/jest-mock/__typetests__/utility-types.test.ts:110 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): FunctionLike packages/jest-mock/__typetests__/utility-types.test.ts:123 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): global.test packages/jest-jasmine2/src/__tests__/itToTestAlias.test.ts:9 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): hasAssertions not leaking to global state packages/expect/src/__tests__/assertionCounts.test.ts:45 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): Any.asymmetricMatch() packages/expect/src/__tests__/asymmetricMatchers.test.ts:28 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): Any.toAsymmetricMatcher() with function name packages/expect/src/__tests__/asymmetricMatchers.test.ts:68 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): Anything matches any type packages/expect/src/__tests__/asymmetricMatchers.test.ts:116 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): ObjectContaining matches prototype properties packages/expect/src/__tests__/asymmetricMatchers.test.ts:229 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): to throw or not to throw packages/expect/src/__tests__/toThrowMatchers.test.ts:29 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): passes packages/expect/src/__tests__/toThrowMatchers.test.ts:37 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): passes packages/expect/src/__tests__/toThrowMatchers.test.ts:95 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): passes packages/expect/src/__tests__/toThrowMatchers.test.ts:165 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): isNot true packages/expect/src/__tests__/toThrowMatchers.test.ts:448 — Test method has an empty body — it asserts nothing and exercises no code.
  • + 30 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×3
  • Orphaned knowledge packages/expect/src/spyMatchers.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge REDACTED:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge packages/diff-sequences/src/index.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
R8 · Dependency Hygiene · Unlisted import 'bar' · ×2
  • Unlisted import 'bar' e2e/custom-resolver/__mocks__/manualMock.js:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
  • Unlisted import 'bar' e2e/custom-resolver-esm/__tests__/customResolverEsm.test.js:10 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: CoverageWorker.ts ↔ testWorker.ts packages/jest-reporters/src/CoverageWorker.ts:1 — `packages/jest-reporters/src/CoverageWorker.ts` (context jest-reporters) and `packages/jest-runner/src/testWorker.ts` (context jest-runner) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `20765482` chore: replace exit with exit-x (#15399); `a30a52fb` fix: log unhandled error even if its stack is empty (#14619); `17ffcc95` fix: serialize changedFiles passed to workers (#8090) (at that commit the file was still `packages/jest-reporters/src/coverage_worker.ts`) — run `git show` on any of them.
R8 · Dependency Hygiene · Unlisted import 'isolated-vm' · ×1
  • Unlisted import 'isolated-vm' e2e/__tests__/nativeEsm.test.ts:29 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'virtual-module' · ×1
  • Unlisted import 'virtual-module' e2e/babel-plugin-jest-hoist/__tests__/integration.test.js:21 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'fakeModuleName' · ×1
  • Unlisted import 'fakeModuleName' e2e/custom-haste-map/__tests__/hasteExample.test.js:11 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@@storage/track' · ×1
  • Unlisted import '@@storage/track' e2e/module-name-mapper-mock/__tests__/storage/track/TrackExpected.test.js:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'unesitent_module__' · ×1
  • Unlisted import 'unesitent_module__' e2e/pnp/undeclared-dependency/index.js:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'Test5' · ×1
  • Unlisted import 'Test5' e2e/resolve/__tests__/resolve.test.js:78 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'Test6' · ×1
  • Unlisted import 'Test6' e2e/resolve/__tests__/resolve.test.js:83 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'Test7' · ×1
  • Unlisted import 'Test7' e2e/resolve/__tests__/resolve.test.js:105 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'Test8' · ×1
  • Unlisted import 'Test8' e2e/resolve/__tests__/resolve.test.js:121 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'nope' · ×1
  • Unlisted import 'nope' e2e/resolve/requiresUnexistingModule.js:10 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'mock-module-without-pkg' · ×1
  • Unlisted import 'mock-module-without-pkg' e2e/resolve-node-module/__tests__/resolve-node-module.test.js:31 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@foo/js' · ×1
  • Unlisted import '@foo/js' e2e/resolve-with-paths/__tests__/resolveWithPaths.test.js:45 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'mod' · ×1
  • Unlisted import 'mod' e2e/resolve-with-paths/__tests__/resolveWithPaths.test.js:23 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'mod.js' · ×1
  • Unlisted import 'mod.js' e2e/resolve-with-paths/__tests__/resolveWithPaths.test.js:17 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'library-that-is-not-installed' · ×1
  • Unlisted import 'library-that-is-not-installed' packages/jest-config/src/__tests__/normalize.test.ts:1240 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'createRuntime' · ×1
  • Unlisted import 'createRuntime' packages/jest-runtime/src/__tests__/Runtime-sourceMaps.test.js:14 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'disagreeing-alias' · ×1
  • Unlisted import 'disagreeing-alias' packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-disagreeing-alias.mjs:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'dual-alias-esm' · ×1
  • Unlisted import 'dual-alias-esm' packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-dual-alias.mjs:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'dual-alias-mockable' · ×1
  • Unlisted import 'dual-alias-mockable' packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/dynamic-imports-dual-alias.cjs:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'ghost-pkg' · ×1
  • Unlisted import 'ghost-pkg' packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/dynamic-imports-ghost.cjs:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'virtual-only-pkg' · ×1
  • Unlisted import 'virtual-only-pkg' packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-virtual-mock.mjs:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'ExclusivelyManualMock' · ×1
  • Unlisted import 'ExclusivelyManualMock' packages/jest-runtime/src/__tests__/test_root/root.js:11 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'Foo.react' · ×1
  • Unlisted import 'Foo.react' packages/jest-runtime/src/__tests__/test_root/haste-modules/FooContainer.react.js:11 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) REDACTED:18 — REDACTED → packages/expect/src/jestMatchersObject.ts → REDACTED
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) packages/jest-circus/src/eventHandler.ts:10 — packages/jest-circus/src/eventHandler.ts → packages/jest-circus/src/globalErrorHandlers.ts → packages/jest-circus/src/state.ts → packages/jest-circus/src/eventHandler.ts (one verified cycle inside a mutually-dependent group of 4 files)
Serious — 843 finding(s)
D10 · Test Quality · No assertions · ×239
  • No assertions: skipping test on broken platform packages/jest-worker/src/workers/__tests__/WorkerEdgeCases.test.ts:45 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:33 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:37 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:41 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:222 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:225 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:230 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ConstructorKeys packages/jest-mock/__typetests__/utility-types.test.ts:136 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: MethodKeys packages/jest-mock/__typetests__/utility-types.test.ts:143 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: PropertyKeys packages/jest-mock/__typetests__/utility-types.test.ts:157 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: json from Response packages/jest-matcher-utils/src/__tests__/deepCyclicCopyReplaceable.test.ts:178 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does not emit error when subscribe rejects after close() packages/jest-haste-map/src/watchers/__tests__/ParcelWatcher.test.ts:290 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does not emit error when an in-flight lstat fails after close() packages/jest-haste-map/src/watchers/__tests__/ParcelWatcher.test.ts:311 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/legacyFakeTimers.test.ts:527 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/legacyFakeTimers.test.ts:728 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/legacyFakeTimers.test.ts:908 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/modernFakeTimers.test.ts:311 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/modernFakeTimers.test.ts:494 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does nothing when no timers have been scheduled packages/jest-fake-timers/src/__tests__/modernFakeTimers.test.ts:624 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: should advance the clock to next timer with nextAsync packages/jest-fake-timers/src/__tests__/modernFakeTimers.test.ts:1444 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: dispatch event packages/jest-environment-node/src/__tests__/globals_cleanup_1.test.ts:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: dispatch event packages/jest-environment-node/src/__tests__/globals_cleanup_2.test.ts:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: assign Object prototype descriptors to a new empty object packages/jest-environment-node/src/__tests__/globals_cleanup_3.test.ts:9 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: does not crash when asyncError is undefined and a plain object is thrown packages/jest-circus/src/__tests__/asyncError.test.ts:9 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: inner test packages/jest-circus/src/__tests__/asyncError.test.ts:12 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 214 more in this group — see findings.md.
D10 · Test Quality · Skipped test · ×35
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:333 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:334 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:336 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:337 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:338 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:339 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) packages/jest-types/__typetests__/globals.test.ts:340 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) e2e/Utils.ts:348 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) e2e/Utils.ts:363 — Skipped — switched off by test.skip
  • Skipped test: (unnamed test) e2e/Utils.ts:381 — Skipped — switched off by test.skip
  • Skipped test: skips e2e/test-todo/__tests__/statuses.test.js:16 — Skipped — switched off by it.skip
  • Skipped test: does not run skipped tests e2e/test-retries/__tests__/entireDescribe.test.js:47 — Skipped — switched off by test.skip
  • Skipped test: skips e2e/test-failing/__tests__/statuses.test.js:16 — Skipped — switched off by it.skip
  • Skipped test: passing test e2e/test-failing/__tests__/worksWithSkipMode.test.js:25 — Skipped — switched off by it.skip
  • Skipped test: failing test e2e/test-failing/__tests__/worksWithSkipMode.test.js:39 — Skipped — switched off by it.skip
  • Skipped test: xit no ancestors e2e/location-in-results/__tests__/test.js:14 — Skipped — switched off by xit
  • Skipped test: xit nested e2e/location-in-results/__tests__/test.js:32 — Skipped — switched off by xit
  • Skipped test: skipped test e2e/json-reporter/__tests__/sum.test.js:26 — Skipped — switched off by it.skip
  • Skipped test: should skip this test e2e/jasmine-async/__tests__/concurrent-each.test.js:17 — Skipped — switched off by it.concurrent.skip.each
  • Skipped test: two e2e/jasmine-async/__tests__/concurrent.test.js:22 — Skipped — switched off by it.concurrent.skip
  • Skipped test: fails with thrown error - async e2e/jasmine-async/__tests__/promiseIt.test.js:80 — Skipped — switched off by it.skip
  • Skipped test: fails but will be skipped e2e/jasmine-async/__tests__/promiseXit.test.js:11 — Skipped — switched off by xit
  • Skipped test: skipped test e2e/empty-describe-with-hooks/__tests__/hookInDescribeWithSkippedTest.test.js:10 — Skipped — switched off by test.skip
  • Skipped test: Should not be ran: fails all rows expected %s == %s e2e/each/__tests__/eachSkip.test.js:15 — Skipped — switched off by it.skip.each
  • Skipped test: sample e2e/custom-reporters/__tests__/skip.test.js:12 — Skipped — switched off by it.skip
  • + 10 more in this group — see findings.md.
D17 · Explicit Debt · TodoComment · ×35
  • TodoComment packages/jest-worker/src/workers/ChildProcessWorker.ts:263 — // TODO: Add appropriate type check — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-worker/src/workers/ChildProcessWorker.ts:330 — // TODO: At some point it would make sense to make use of — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-worker/src/workers/NodeThreadsWorker.ts:339 — // TODO: At some point it would make sense to make use of — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-types/src/Config.ts:333 — // TODO: make non-optional in Jest 30 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-types/__typetests__/jest.test.ts:595 — // TODO: add these two once we are on TypeScript v6 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-source-map/src/SourceMapSupport.ts:9 — // TODO: replace with `util.getCallSites()`, whose `columnNumber` landed in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-source-map/src/getCallsite.ts:8 — // TODO: replace with `util.getCallSites()`, whose `columnNumber` landed in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-source-map/src/SourceMapSupport.ts:52 — // TODO: return `column + 1` in Jest 31, so this matches V8 and — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-snapshot/src/State.ts:238 — // TODO(jest next major): require `testIdentity` and drop this branch. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-schemas/src/raw-types.ts:61 — // TODO: add type test that these are all the colors available in chalk.ForegroundColor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-schemas/src/raw-types.ts:88 — // TODO: verify these are the names of istanbulReport.ReportOptions — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-schemas/src/raw-types.ts:297 — // TODO: Make sure to type these correctly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-runtime/src/internals/EsmLoader.ts:113 — // TODO(jest next major): drop `assert` once we require Node 22+. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-runtime/src/internals/EsmLoader.ts:1796 — // TODO: legacy async path - everything below is deletable when min-Node — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-runtime/src/internals/V8CoverageCollector.ts:81 — // TODO: will this work on windows? It might be better if `shouldInstrument` deals with it anyways — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-runtime/src/internals/importAttributes.ts:70 — // TODO(jest next major): match Node and throw — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-runner/src/index.ts:157 — // TODO: Get appropriate type for `onCustomMessage` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-reporters/src/generateEmptyCoverage.ts:83 — // TODO: consider passing AST — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:412 — // TODO: check & read HasteFS instead of reading the filesystem: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment REDACTED:175 — // TODO: Remove config option if V8 exposes some way of getting location of caller — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-jasmine2/src/jasmine/Env.ts:423 — // @ts-expect-error TODO Possible error: Suite does not have todo method — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-jasmine2/src/__tests__/collectSpecs.test.ts:123 — // todo deselected by focus is also pending, mirroring `Spec.status`. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-haste-map/src/crawlers/node.ts:204 — // TODO: consider making forceNodeFilesystemAPI the default. find(1) does — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-fake-timers/src/legacyFakeTimers.ts:510 — // TODO: Use performance.now() once it's mocked — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/jest-fake-timers/src/modernFakeTimers.ts:105 — // TODO: pass msToRun directly once https://github.com/sinonjs/fake-timers/pull/574 is published
  • + 10 more in this group — see findings.md.
D10 · Test Quality · Test project verifies nothing · ×28
  • Test project verifies nothing: benchmarks/test-file-overhead benchmarks/test-file-overhead/0.test.js:8 — No conventional assertion call was detected in 1 of 1 tests in `benchmarks/test-file-overhead` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/before-all-filtered e2e/before-all-filtered/__tests__/beforeAllFiltered.test.js:21 — No conventional assertion call was detected in 2 of 2 tests in `e2e/before-all-filtered` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/before-each-queue e2e/before-each-queue/__tests__/beforeEachQueue.test.js:13 — No conventional assertion call was detected in 2 of 2 tests in `e2e/before-each-queue` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/circus-declaration-errors e2e/circus-declaration-errors/__tests__/asyncDefinition.test.js:9 — No conventional assertion call was detected in 3 of 3 tests in `e2e/circus-declaration-errors` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/console e2e/console/__tests__/console.test.js:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/console` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/console-after-teardown e2e/console-after-teardown/__tests__/console.test.js:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/console-after-teardown` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/console-winston e2e/console-winston/__tests__/console.test.js:14 — No conventional assertion call was detected in 1 of 1 tests in `e2e/console-winston` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/declaration-errors e2e/declaration-errors/__tests__/describeReturnPromise.test.js:12 — No conventional assertion call was detected in 3 of 3 tests in `e2e/declaration-errors` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/empty-describe-with-hooks e2e/empty-describe-with-hooks/__tests__/hookInEmptyDescribe.test.js:13 — No conventional assertion call was detected in 3 of 3 tests in `e2e/empty-describe-with-hooks` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/environment-after-teardown e2e/environment-after-teardown/__tests__/afterTeardown.test.js:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/environment-after-teardown` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/environment-teardown-error e2e/environment-teardown-error/__tests__/environmentTeardownError.test.js:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/environment-teardown-error` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/expect-in-vm e2e/expect-in-vm/__tests__/expect-in-vm.test.js:12 — No conventional assertion call was detected in 1 of 1 tests in `e2e/expect-in-vm` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/fake-timers-legacy/use-real-timers e2e/fake-timers-legacy/use-real-timers/__tests__/useRealTimers.test.js:12 — No conventional assertion call was detected in 1 of 1 tests in `e2e/fake-timers-legacy/use-real-timers` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/fake-timers/clear-real-timers e2e/fake-timers/clear-real-timers/__tests__/clearRealTimers.test.js:10 — No conventional assertion call was detected in 1 of 1 tests in `e2e/fake-timers/clear-real-timers` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/fake-timers/use-real-timers e2e/fake-timers/use-real-timers/__tests__/useRealTimers.test.js:12 — No conventional assertion call was detected in 1 of 1 tests in `e2e/fake-timers/use-real-timers` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/lifecycles e2e/lifecycles/__tests__/index.js:11 — No conventional assertion call was detected in 2 of 2 tests in `e2e/lifecycles` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/multi-project-config-root e2e/multi-project-config-root/foo/__tests__/boggusFoo.test.js:9 — No conventional assertion call was detected in 2 of 2 tests in `e2e/multi-project-config-root` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/node-url-manual-mocks e2e/node-url-manual-mocks/__tests__/importAndMock.test.js:12 — No conventional assertion call was detected in 3 of 3 tests in `e2e/node-url-manual-mocks` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/promise-and-callback e2e/promise-and-callback/__tests__/promise-and-callback.test.js:10 — No conventional assertion call was detected in 3 of 3 tests in `e2e/promise-and-callback` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/reset-modules e2e/reset-modules/__tests__/resetModules.test.js:17 — No conventional assertion call was detected in 1 of 1 tests in `e2e/reset-modules` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/run-programmatically-multiple-projects e2e/run-programmatically-multiple-projects/server/server.test.js:9 — No conventional assertion call was detected in 2 of 2 tests in `e2e/run-programmatically-multiple-projects` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/source-map-not-transformed e2e/source-map-not-transformed/__tests__/precompiled.test.js:12 — No conventional assertion call was detected in 1 of 1 tests in `e2e/source-map-not-transformed` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/stack-trace-source-maps-with-coverage e2e/stack-trace-source-maps-with-coverage/__tests__/fails.ts:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/stack-trace-source-maps-with-coverage` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/test-environment-run-script e2e/test-environment-run-script/__tests__/envUsingRunScript.test.js:9 — No conventional assertion call was detected in 1 of 1 tests in `e2e/test-environment-run-script` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/test-path-patterns-subprojects e2e/test-path-patterns-subprojects/src/__tests__/testA.js:10 — No conventional assertion call was detected in 3 of 3 tests in `e2e/test-path-patterns-subprojects` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • + 3 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×28
  • Swallowed exception (empty catch) packages/jest-util/src/createProcessObject.ts:140 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-util/src/garbage-collection-utils.ts:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-transform/src/ScriptTransformer.ts:929 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-snapshot-utils/src/utils.ts:150 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-snapshot-utils/src/utils.ts:176 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-runtime/src/helpers.ts:68 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve-dependencies/src/index.ts:64 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve-dependencies/src/index.ts:83 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve/src/resolver.ts:307 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve/src/resolver.ts:386 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve/src/utils.ts:61 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-resolve/src/utils.ts:73 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-reporters/src/CoverageReporter.ts:230 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:30 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:416 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmineAsyncInstall.ts:230 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmine/Suite.ts:207 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmine/spyRegistry.ts:116 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-jasmine2/src/jasmine/spyRegistry.ts:169 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-haste-map/src/lib/watchmanSockname.ts:101 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-haste-map/src/lib/watchmanSockname.ts:173 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-haste-map/src/lib/watchmanSockname.ts:182 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-config/src/normalize.ts:195 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-config/src/normalize.ts:321 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/jest-config/src/normalize.ts:395 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 3 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×20
  • Sync-over-async blocking packages/create-jest/src/runCreate.ts:55 — `fs.existsSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-jest/src/runCreate.ts:65 — `fs.readFileSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-jest/src/runCreate.ts:76 — `fs.existsSync` in `callback to JEST_CONFIG_EXT_ORDER.find` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-jest/src/runCreate.ts:143 — `fs.writeFileSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-jest/src/runCreate.ts:155 — `fs.writeFileSync` in `runCreate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-config/src/index.ts:442 — `fs.existsSync` in `callback to projects.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-config/src/index.ts:443 — `fs.lstatSync` in `callback to projects.filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-config/src/readConfigFileAndSetRootDir.ts:90 — `fs.readFileSync` in `readConfigFileAndSetRootDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-core/src/cli/index.ts:73 — `fs.rmSync` in `runCLI` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-core/src/runJest.ts:203 — `fs.writeFileSync` in `processResults` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-core/src/runJest.ts:322 — `fs.writeFileSync` in `runJest` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-haste-map/src/worker.ts:43 — `fs.readFileSync` in `getContent` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-haste-map/src/worker.ts:95 — `fs.readFileSync` in `worker` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-haste-map/src/worker.ts:103 — `fs.readFileSync` in `getSha1` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-reporters/src/CoverageReporter.ts:494 — `fs.existsSync` in `callback to result.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-reporters/src/CoverageReporter.ts:497 — `fs.readFileSync` in `callback to result.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-reporters/src/CoverageReporter.ts:512 — `fs.readFileSync` in `callback to result.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-reporters/src/generateEmptyCoverage.ts:46 — `fs.statSync` in `generateEmptyCoverage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-runner/src/runTest.ts:90 — `fs.readFileSync` in `runTestInternal` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/jest-transform/src/ScriptTransformer.ts:636 — `fs.readFileSync` in `_transformAndBuildScriptAsync` 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.
D12 · Dependency Hygiene · Floating npm dependency · ×19
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-circus/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-console/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-core/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-environment-jsdom-abstract/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-environment-node/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-environment/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-fake-timers/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-haste-map/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-jasmine2/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-mock/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-pattern/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-reporters/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-runner/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-runtime/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-types/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-util/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-watcher/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/jest-worker/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: @types/node — `@types/node` is declared as `*` in packages/test-utils/package.json, which names no releasable version: any published version satisfies it. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
R4 · Test Coverage · No test reaches this file · ×18
  • No test reaches this file packages/jest-schemas/src/raw-types.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/buildUtils.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/buildTs.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/lintTs.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/bundleTs.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/checkCopyrightHeaders.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/babel-plugin-jest-native-globals.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/build.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/checkChangelog.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/requireChangelog.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/mapCoverage.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/watch.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/jest-phabricator/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/cleanE2e.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/jest-worker/__typetests__/testWorker.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/remove-examples.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/jest-schemas/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/create-jest/bin/create-jest.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.
D15 · Churn × Complexity Hotspots · Hotspot · ×15
  • Hotspot: packages/jest-config/src/normalize.ts packages/jest-config/src/normalize.ts:536 — packages/jest-config/src/normalize.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 213 in normalize.normalize at line 536. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-config/src/normalize.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-runtime/src/internals/EsmLoader.ts packages/jest-runtime/src/internals/EsmLoader.ts:681 — packages/jest-runtime/src/internals/EsmLoader.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in EsmLoader.walkGraphSync at line 681. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-runtime/src/internals/EsmLoader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-runtime/src/internals/CjsLoader.ts packages/jest-runtime/src/internals/CjsLoader.ts:77 — packages/jest-runtime/src/internals/CjsLoader.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in CjsLoader.requireModule at line 77. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-runtime/src/internals/CjsLoader.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-haste-map/src/lib/FileProcessor.ts packages/jest-haste-map/src/lib/FileProcessor.ts:72 — packages/jest-haste-map/src/lib/FileProcessor.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in FileProcessor.processFile at line 72. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-haste-map/src/lib/FileProcessor.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-circus/src/eventHandler.ts packages/jest-circus/src/eventHandler.ts:27 — packages/jest-circus/src/eventHandler.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in eventHandler.eventHandler at line 27. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-circus/src/eventHandler.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-jasmine2/src/jasmine/Env.ts packages/jest-jasmine2/src/jasmine/Env.ts:122 — packages/jest-jasmine2/src/jasmine/Env.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in Env.constructor at line 122. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-jasmine2/src/jasmine/Env.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-haste-map/src/crawlers/watchman.ts packages/jest-haste-map/src/crawlers/watchman.ts:93 — packages/jest-haste-map/src/crawlers/watchman.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in watchman.watchmanCrawl at line 93. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-haste-map/src/crawlers/watchman.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:152 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in index.jasmine2 at line 152. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-circus/src/utils.ts packages/jest-circus/src/utils.ts:196 — packages/jest-circus/src/utils.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in utils.callAsyncCircusFn at line 196. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-circus/src/utils.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:202 — REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in MockState.decideSync at line 202. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-haste-map/src/watchers/WatchmanWatcher.js packages/jest-haste-map/src/watchers/WatchmanWatcher.js:78 — packages/jest-haste-map/src/watchers/WatchmanWatcher.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in WatchmanWatcher.WatchmanWatcher.init at line 78. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-haste-map/src/watchers/WatchmanWatcher.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-config/src/index.ts packages/jest-config/src/index.ts:394 — packages/jest-config/src/index.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in index.readConfigs at line 394. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-config/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-haste-map/src/watchers/ChangeQueue.ts packages/jest-haste-map/src/watchers/ChangeQueue.ts:81 — packages/jest-haste-map/src/watchers/ChangeQueue.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ChangeQueue.onChange at line 81. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-haste-map/src/watchers/ChangeQueue.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-snapshot/src/index.ts packages/jest-snapshot/src/index.ts:277 — packages/jest-snapshot/src/index.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in index._toMatchSnapshot at line 277. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-snapshot/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/jest-runtime/src/internals/JestGlobals.ts packages/jest-runtime/src/internals/JestGlobals.ts:162 — packages/jest-runtime/src/internals/JestGlobals.ts changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in JestGlobals.buildJestObject at line 162. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-runtime/src/internals/JestGlobals.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×12
  • FunctionTooLong: Env.jasmineEnv packages/jest-jasmine2/src/jasmine/Env.ts:59 — FunctionTooLong — jasmineEnv runs 435 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 335 over it, 4.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: watch.watch packages/jest-core/src/watch.ts:91 — FunctionTooLong — watch runs 271 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 171 over it, 2.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: eventHandler.eventHandler packages/jest-circus/src/eventHandler.ts:27 — FunctionTooLong — eventHandler runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: runJest.runJest packages/jest-core/src/runJest.ts:220 — FunctionTooLong — runJest runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: watchman.watchmanCrawl packages/jest-haste-map/src/crawlers/watchman.ts:93 — FunctionTooLong — watchmanCrawl runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.groupOptions packages/jest-config/src/index.ts:122 — FunctionTooLong — groupOptions runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: _landingAnimation.setupLandingAnimation website/src/pages/animations/_landingAnimation.js:17 — FunctionTooLong — setupLandingAnimation runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.jasmine2 REDACTED:152 — FunctionTooLong — jasmine2 runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: utils.iterableEquality packages/expect-utils/src/utils.ts:175 — FunctionTooLong — iterableEquality runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: joinAlignedDiffs.joinAlignedDiffsNoExpand packages/jest-diff/src/joinAlignedDiffs.ts:112 — FunctionTooLong — joinAlignedDiffsNoExpand runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: buildUtils.createBuildConfigs scripts/buildUtils.mjs:154 — FunctionTooLong — createBuildConfigs runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: getSummary.getSummary packages/jest-reporters/src/getSummary.ts:82 — FunctionTooLong — getSummary runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D5 · Coupling · Off the main sequence · ×12
  • Off the main sequence: @jest/diff-sequences — @jest/diff-sequences: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: @jest/get-type — @jest/get-type: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: babel-plugin-jest-hoist — babel-plugin-jest-hoist: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: jest-docblock — jest-docblock: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
  • Off the main sequence: jest-regex-util — jest-regex-util: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
  • Off the main sequence: jest-util — jest-util: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
  • Off the main sequence: pretty-format — pretty-format: abstractness 0.00, instability 0.08, distance 0.92 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
  • Off the main sequence: @jest/source-map — @jest/source-map: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @jest/test-result — @jest/test-result: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: jest-message-util — jest-message-util: abstractness 0.00, instability 0.23, distance 0.77 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: @jest/expect-utils — @jest/expect-utils: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @jest/pattern — @jest/pattern: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
R4 · Test Coverage · This test file cannot be loaded · ×12
  • This test file cannot be loaded e2e/native-esm/__tests__/native-esm-mocks.test.js:18 — e2e/native-esm/__tests__/native-esm-mocks.test.js:18 imports '../mockedModule.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/native-esm/virtualMockReexport.mjs:7 — e2e/native-esm/virtualMockReexport.mjs:7 imports './mockedModule.mjs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/presets/cjs/__tests__/index.js:10 — e2e/presets/cjs/__tests__/index.js:10 imports './test.foo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/presets/js-type-module/__tests__/index.js:10 — e2e/presets/js-type-module/__tests__/index.js:10 imports './test.foo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/presets/js/__tests__/index.js:10 — e2e/presets/js/__tests__/index.js:10 imports './test.foo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/presets/json/__tests__/index.js:10 — e2e/presets/json/__tests__/index.js:10 imports './test.foo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/presets/mjs/__tests__/index.js:10 — e2e/presets/mjs/__tests__/index.js:10 imports './test.foo', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded e2e/resolve-async/__tests__/resolveAsync.test.js:8 — e2e/resolve-async/__tests__/resolveAsync.test.js:8 imports '../some-file', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-automock-then-missing.mjs:9 — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-automock-then-missing.mjs:9 imports './does-not-exist.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-cjs-then-missing.mjs:9 — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-cjs-then-missing.mjs:9 imports './does-not-exist.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-factory-then-missing.mjs:9 — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/import-factory-then-missing.mjs:9 imports './does-not-exist.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/unmarked-esm-missing-dep.js:8 — packages/jest-runtime/src/__tests__/test_esm_sync_graph_root/unmarked-esm-missing-dep.js:8 imports './does-not-exist.js', 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.
S1 · Web-Security Posture · Weak hash algorithm · ×11
  • Weak hash algorithm packages/babel-jest/src/index.ts:93 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-config/src/normalize.ts:365 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-create-cache-key-function/src/index.ts:54 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-create-cache-key-function/src/index.ts:97 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm REDACTED:299 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm REDACTED:351 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-haste-map/src/worker.ts:25 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts:124 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts:135 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts:950 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
  • Weak hash algorithm packages/jest-transform/src/ScriptTransformer.ts:966 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
D3 · God Classes · FileTooLong · ×10
  • FileTooLong: internals/EsmLoader.ts packages/jest-runtime/src/internals/EsmLoader.ts — FileTooLong — 1501 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: EsmLoader (291-2386). The bar is 500 significant lines; this is 1001 over it, 3.00× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: REDACTED packages/jest-mock/src/index.ts — FileTooLong — 1056 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 556 over it, 2.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/spyMatchers.ts packages/expect/src/spyMatchers.ts — FileTooLong — 937 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 437 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/normalize.ts packages/jest-config/src/normalize.ts — FileTooLong — 811 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 311 over it, 1.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/resolver.ts packages/jest-resolve/src/resolver.ts — FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: Resolver (59-1005). The bar is 500 significant lines; this is 262 over it, 1.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/ScriptTransformer.ts packages/jest-transform/src/ScriptTransformer.ts — FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded), about 75% of them inside a single declaration: ScriptTransformer (87-898). The bar is 500 significant lines; this is 226 over it, 1.45× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 700 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: matchers (74-992). The bar is 500 significant lines; this is 200 over it, 1.40× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/args.ts packages/jest-cli/src/args.ts — FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: usage (95-797). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: Runtime (103-780). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: pages/index.js website/src/pages/index.js — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · MethodTooLong · ×6
  • MethodTooLong: Env.constructor packages/jest-jasmine2/src/jasmine/Env.ts:122 — MethodTooLong — constructor runs 373 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 273 over it, 3.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: JestGlobals.buildJestObject packages/jest-runtime/src/internals/JestGlobals.ts:162 — MethodTooLong — buildJestObject runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EsmLoader.walkGraphSync packages/jest-runtime/src/internals/EsmLoader.ts:681 — MethodTooLong — walkGraphSync runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Runtime.constructor REDACTED:126 — MethodTooLong — constructor runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FileProcessor.processFile packages/jest-haste-map/src/lib/FileProcessor.ts:72 — MethodTooLong — processFile runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CoverageReporter._checkThreshold packages/jest-reporters/src/CoverageReporter.ts:243 — MethodTooLong — _checkThreshold runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×5
  • Duplicated block (17 lines × 2 locations) REDACTED:537 — REDACTED:537 · REDACTED:590 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) packages/expect/src/spyMatchers.ts:646 — packages/expect/src/spyMatchers.ts:646 · packages/expect/src/spyMatchers.ts:726 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) packages/expect/src/spyMatchers.ts:705 — packages/expect/src/spyMatchers.ts:705 · packages/expect/src/spyMatchers.ts:883 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) packages/jest-circus/src/formatNodeAssertErrors.ts:23 — packages/jest-circus/src/formatNodeAssertErrors.ts:23 · packages/jest-jasmine2/src/assertionErrorMessage.ts:17 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
  • Duplicated block (17 lines × 2 locations) packages/jest-jasmine2/src/jasmine/Spec.ts:275 — packages/jest-jasmine2/src/jasmine/Spec.ts:275 · packages/jest-jasmine2/src/jasmine/Suite.ts:135 — 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.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×5
  • Recursive walk over a caller-supplied document has no depth cap packages/pretty-format/src/plugins/ReactElement.ts:37 — `serialize` is exported, takes a document from its caller (line 97) and hands it to `getChildren`, which calls itself at line 37 (`getChildren`) with a piece of `arg` — and nowhere in `getChildren` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getChildren` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/jest-snapshot/src/utils.ts:118 — `deepMerge` is exported and takes `target: any` from its caller, and it calls itself at line 118 (`deepMerge`) with a piece of `target` — and nowhere in `deepMerge` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepMerge` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/jest-matcher-utils/src/index.ts:461 — `replaceMatchedToAsymmetricMatcher` is exported, takes a document from its caller (line 412) and hands it to `_replaceMatchedToAsymmetricMatcher`, which calls itself at line 461 (`_replaceMatchedToAsymmetricMatcher`) with a piece of `replacedExpected` — and nowhere in `_replaceMatchedToAsymmetricMatcher` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `_replaceMatchedToAsymmetricMatcher` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/expect-utils/src/utils.ts:83 — `getPath` is exported and takes `object: Record<string, any>` from its caller, and it calls itself at line 83 (`getPath`) with a piece of `object` — and nowhere in `getPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/expect-utils/src/utils.ts:127 — `getObjectSubset` is exported and takes `object: any` from its caller, and it calls itself at line 127 (`getObjectSubset`) with a piece of `object` (and at line 154) — and nowhere in `getObjectSubset` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `getObjectSubset` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
D15 · Churn × Complexity Hotspots · Repeated repair · ×4
  • Repeated repair: packages/jest-resolve/src/resolver.ts packages/jest-resolve/src/resolver.ts:174 — packages/jest-resolve/src/resolver.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is Resolver.findNodeModuleAsync at line 174), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “revert(jest-resolve): match `moduleNameMapper` against the specifier as written (#16417)”; “fix(jest-resolve): apply `moduleNameMapper` to both spellings of core modules (#16390)”; “fix(jest-resolve): keep the `node:` prefix through async resolution (#16388)”; “fix(jest-runtime): match Node for "type": "commonjs" packages, module.children and data: URIs (#16368)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-resolve/src/resolver.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/jest-runtime/src/internals/ModuleRegistries.ts packages/jest-runtime/src/internals/ModuleRegistries.ts:222 — packages/jest-runtime/src/internals/ModuleRegistries.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ModuleRegistries.getRequireCacheProxy at line 222), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(jest-runtime): close ESM mocking, require(esm) and JSON module parity gaps (#16389)”; “fix(jest-runtime): key ES modules by full URL and share modules between overlapping graphs (#16375)”; “fix(jest-runtime): match Node for "type": "commonjs" packages, module.children and data: URIs (#16368)”; “fix(jest-runtime): mirror Node's ESM/CJS interop and entry-point metadata (#16367)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-runtime/src/internals/ModuleRegistries.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:531 — REDACTED changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is Runtime._esmMockTarget at line 531), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(jest-runtime): close ESM mocking, require(esm) and JSON module parity gaps (#16389)”; “fix(jest-runtime): mirror Node's ESM/CJS interop and entry-point metadata (#16367)”; “fix(jest-runtime): throw ERR_REQUIRE_CYCLE_MODULE on require(esm) re-entry (#16366)”; “fix: keep source maps past teardown (#16330)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/jest-runtime/src/internals/syntheticBuilders.ts packages/jest-runtime/src/internals/syntheticBuilders.ts:106 — packages/jest-runtime/src/internals/syntheticBuilders.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is syntheticBuilders.buildCjsAsEsmSyntheticModule at line 106), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(jest-runtime): close ESM mocking, require(esm) and JSON module parity gaps (#16389)”; “fix(jest-runtime): mirror Node's ESM/CJS interop and entry-point metadata (#16367)”; “fix(jest-runtime): give `fs` and `node:fs` one ESM namespace (#16341)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-04..2026-10-02, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-04 12:49:20 +02:00' --until='2026-10-02 12:49:20 +02:00' --full-history --no-merges -- packages/jest-runtime/src/internals/syntheticBuilders.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: EsmLoader packages/jest-runtime/src/internals/EsmLoader.ts:291 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Resolver packages/jest-resolve/src/resolver.ts:59 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Runtime REDACTED:103 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MockState REDACTED:39 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium CVE · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: REDACTED ↔ config.ts packages/jest-config/src/index.ts:1 — `packages/jest-config/src/index.ts` and `packages/test-utils/src/config.ts` change together 75% of the time (49 of the 65 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 49 shared commits counted here, the most recent 3 are `ea7258e3` fix(jest-config): only warn about global-only options where they're a…; `69b7072e` feat: allow custom runner configuration options (tuple format) (#16141); `db7141a9` fix: allow `collectCoverage` and `coverageProvider` in project config… — run `git show` on any of them.
  • Change coupling: normalize.ts ↔ config.ts packages/jest-config/src/normalize.ts:1 — `packages/jest-config/src/normalize.ts` and `packages/test-utils/src/config.ts` change together 63% of the time (41 of the 65 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 41 shared commits counted here, the most recent 3 are `ea7258e3` fix(jest-config): only warn about global-only options where they're a…; `69b7072e` feat: allow custom runner configuration options (tuple format) (#16141); `db7141a9` fix: allow `collectCoverage` and `coverageProvider` in project config… — run `git show` on any of them.
  • Change coupling: ValidConfig.ts ↔ REDACTED packages/jest-config/src/ValidConfig.ts:1 — `packages/jest-config/src/ValidConfig.ts` and `packages/jest-config/src/index.ts` change together 51% of the time (50 of the 98 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 50 shared commits counted here, the most recent 3 are `ea7258e3` fix(jest-config): only warn about global-only options where they're a…; `69b7072e` feat: allow custom runner configuration options (tuple format) (#16141); `4f964516` fix: support `silent` and `verbose` as project config (#16133) — run `git show` on any of them.
  • Change coupling: CoverageReporter.ts ↔ generateEmptyCoverage.ts packages/jest-reporters/src/CoverageReporter.ts:1 — `packages/jest-reporters/src/CoverageReporter.ts` and `packages/jest-reporters/src/generateEmptyCoverage.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `11fd5fca` fix: make coverage work when using `projects` option (#16140); `3f107a33` Show coverage of sources related to tests in changed files (#9769) (at that commit the file was still `packages/jest-reporters/src/coverage_reporter.ts`); `2e454103` Improve source map handling when instrumenting transformed code (#9811) (at that commit the file was still `packages/jest-reporters/src/coverage_reporter.ts`) — run `git show` on any of them.
R11 · Import Boundaries · Boundary violation [package · ×4
  • Boundary violation [package:test-cross-package-internals] e2e/resolve/__tests__/resolve.test.js:68 — e2e/resolve/__tests__/resolve.test.js:68 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/jest-resolve) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:undeclared-workspace-dep] packages/jest-config/src/normalize.ts:602 — packages/jest-config/src/normalize.ts:602 imports jest-jasmine2, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
  • Boundary violation [package:third-party-deep-import] packages/jest-config/src/readConfigFileAndSetRootDir.ts:212 — packages/jest-config/src/readConfigFileAndSetRootDir.ts:212 imports esbuild-register/dist/node, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:undeclared-workspace-dep] packages/jest/src/index.ts:19 — packages/jest/src/index.ts:19 imports jest-config, a package this repository publishes, but this package's own package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
D23 · Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-circus) · ×3
  • Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/formatNodeAssertErrors.ts:41 — State (context jest-runtime) is exposed in jest-circus's public surface via formatNodeAssertErrors.formatNodeAssertErrors — couples the contexts.
  • Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/state.ts:54 — State (context jest-runtime) is exposed in jest-circus's public surface via state.getState — couples the contexts.
  • Cross-context type State (jest-runtime → jest-circus) packages/jest-circus/src/state.ts:56 — State (context jest-runtime) is exposed in jest-circus's public surface via state.setState — couples the contexts.
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: matchers REDACTED:1 — ClassTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 242 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Resolver packages/jest-resolve/src/resolver.ts:59 — ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 227 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Runtime REDACTED:103 — ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×3
  • Duplicated block (20 lines × 2 locations) packages/diff-sequences/src/index.ts:251 — packages/diff-sequences/src/index.ts:251 · packages/diff-sequences/src/index.ts:384 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (20 lines × 2 locations) packages/jest-core/src/SnapshotInteractiveMode.ts:52 — packages/jest-core/src/SnapshotInteractiveMode.ts:52 · packages/jest-core/src/SnapshotInteractiveMode.ts:94 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (20 lines × 2 locations) packages/pretty-format/src/plugins/Immutable.ts:25 — packages/pretty-format/src/plugins/Immutable.ts:25 · packages/pretty-format/src/plugins/Immutable.ts:130 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×3
  • Duplicated block (19 lines × 2 locations) packages/jest-core/src/FailedTestsInteractiveMode.ts:118 — packages/jest-core/src/FailedTestsInteractiveMode.ts:118 · packages/jest-core/src/FailedTestsInteractiveMode.ts:146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (19 lines × 2 locations) packages/jest-matcher-utils/src/index.ts:250 — packages/jest-matcher-utils/src/index.ts:250 · packages/jest-snapshot/src/printSnapshot.ts:141 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (19 lines × 2 locations) packages/jest-mock/src/index.ts:1375 — packages/jest-mock/src/index.ts:1375 · packages/jest-mock/src/index.ts:1468 — 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.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: discord.js e2e/native-esm/package.json:8 — discord.js 14.3.0, declared in e2e/native-esm/package.json, is marked deprecated by its publisher: "Hard crashes on interactions with a channel in the payload, use 14.8.0 and up". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: discord.js e2e/require-missing-ext/package.json:8 — discord.js 11.5.1, declared in e2e/require-missing-ext/package.json, is marked deprecated by its publisher: "no longer supported". Replace it with the package or version that message names, or record why this one must stay.
D23 · Boundary Type-Coupling · Cross-context type State (jest-runtime → expect) · ×2
  • Cross-context type State (jest-runtime → expect) packages/expect/src/jestMatchersObject.ts:44 — State (context jest-runtime) is exposed in expect's public surface via jestMatchersObject.getState — couples the contexts.
  • Cross-context type State (jest-runtime → expect) packages/expect/src/jestMatchersObject.ts:47 — State (context jest-runtime) is exposed in expect's public surface via jestMatchersObject.setState — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type Event (jest-types → jest-circus) · ×2
  • Cross-context type Event (jest-types → jest-circus) packages/jest-circus/src/formatNodeAssertErrors.ts:41 — Event (context jest-types) is exposed in jest-circus's public surface via formatNodeAssertErrors.formatNodeAssertErrors — couples the contexts.
  • Cross-context type Event (jest-types → jest-circus) packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapterInit.ts:354 — Event (context jest-types) is exposed in jest-circus's public surface via jestAdapterInit.eventHandler — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type State (jest-runtime → jest-watcher) · ×2
  • Cross-context type State (jest-runtime → jest-watcher) packages/jest-watcher/src/TestWatcher.ts:15 — State (context jest-runtime) is exposed in jest-watcher's public surface via TestWatcher.state — couples the contexts.
  • Cross-context type State (jest-runtime → jest-watcher) packages/jest-watcher/src/TestWatcher.ts:24 — State (context jest-runtime) is exposed in jest-watcher's public surface via TestWatcher.setState — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D43 · Malicious Dependencies · Malicious package · ×2
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Fake-async · ×2
  • Fake-async — async method never awaits packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapterInit.ts:354 — `eventHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits packages/jest-snapshot/src/SnapshotResolver.ts:50 — `createSnapshotResolver` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×2
  • Duplicated block (27 lines × 2 locations) packages/jest-fake-timers/src/legacyFakeTimers.ts:351 — packages/jest-fake-timers/src/legacyFakeTimers.ts:351 · packages/jest-fake-timers/src/legacyFakeTimers.ts:386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (27 lines × 2 locations) packages/jest-jasmine2/src/jasmineAsyncInstall.ts:48 — packages/jest-jasmine2/src/jasmineAsyncInstall.ts:48 · packages/jest-jasmine2/src/jasmineAsyncInstall.ts:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×2
  • Duplicated block (23 lines × 2 locations) packages/jest-changed-files/src/hg.ts:16 — packages/jest-changed-files/src/hg.ts:16 · packages/jest-changed-files/src/sl.ts:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (23 lines × 2 locations) packages/jest-resolve/src/resolver.ts:885 — packages/jest-resolve/src/resolver.ts:885 · packages/jest-resolve/src/resolver.ts:947 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×2
  • Duplicated block (21 lines × 2 locations) packages/jest-core/src/SnapshotInteractiveMode.ts:75 — packages/jest-core/src/SnapshotInteractiveMode.ts:75 · packages/jest-core/src/SnapshotInteractiveMode.ts:109 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (21 lines × 2 locations) packages/jest-transform/src/ScriptTransformer.ts:540 — packages/jest-transform/src/ScriptTransformer.ts:540 · packages/jest-transform/src/ScriptTransformer.ts:605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×2
  • Duplicated block (18 lines × 2 locations) packages/expect/src/spyMatchers.ts:281 — packages/expect/src/spyMatchers.ts:281 · packages/jest-matcher-utils/src/index.ts:293 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (18 lines × 2 locations) packages/expect/src/spyMatchers.ts:892 — packages/expect/src/spyMatchers.ts:892 · packages/expect/src/spyMatchers.ts:1157 — 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.
D1 · Cyclomatic Complexity · normalize.normalize (cyclomatic 213) · ×1
  • normalize.normalize (cyclomatic 213) packages/jest-config/src/normalize.ts:536 — normalize.normalize has cyclomatic complexity 213 (threshold 15). Of this number, 63 points are the body's own statements and 150 belong to 7 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/jest-config/src/normalize.ts holds 2 of the 57 methods over the threshold — including the worst — and 200 of the 786 points over it (25%), 2.9× the next-largest file (packages/jest-jasmine2/src/jasmine/Env.ts at 70). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · eventHandler.eventHandler (cyclomatic 55) · ×1
  • eventHandler.eventHandler (cyclomatic 55) packages/jest-circus/src/eventHandler.ts:27 — eventHandler.eventHandler has cyclomatic complexity 55 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Env.constructor (cyclomatic 50) · ×1
  • Env.constructor (cyclomatic 50) packages/jest-jasmine2/src/jasmine/Env.ts:122 — Env.constructor has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 9 of the 50 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 303, a function literal at line 401, addSpecsToSuite, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: one other method here (Env.jasmineEnv) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Env.jasmineEnv (cyclomatic 50) · ×1
  • Env.jasmineEnv (cyclomatic 50) packages/jest-jasmine2/src/jasmine/Env.ts:59 — Env.jasmineEnv has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 9 of the 50 points are its own statements and the rest belongs to 17 function items inside it that branch (a function literal at line 303, a function literal at line 401, addSpecsToSuite, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: one other method here (Env.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · jasmineUtils.eq (cyclomatic 47) · ×1
  • jasmineUtils.eq (cyclomatic 47) packages/expect-utils/src/jasmineUtils.ts:63 — jasmineUtils.eq has cyclomatic complexity 47 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D1 · Cyclomatic Complexity · EsmLoader.walkGraphSync (cyclomatic 47) · ×1
  • EsmLoader.walkGraphSync (cyclomatic 47) packages/jest-runtime/src/internals/EsmLoader.ts:681 — EsmLoader.walkGraphSync has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · utils.iterableEquality (cyclomatic 45) · ×1
  • utils.iterableEquality (cyclomatic 45) packages/expect-utils/src/utils.ts:175 — utils.iterableEquality has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · watchman.watchmanCrawl (cyclomatic 40) · ×1
  • watchman.watchmanCrawl (cyclomatic 40) packages/jest-haste-map/src/crawlers/watchman.ts:93 — watchman.watchmanCrawl has cyclomatic complexity 40 (threshold 15). Of this number, 26 points are the body's own statements and 14 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FileProcessor.processFile (cyclomatic 39) · ×1
  • FileProcessor.processFile (cyclomatic 39) packages/jest-haste-map/src/lib/FileProcessor.ts:72 — FileProcessor.processFile has cyclomatic complexity 39 (threshold 15). Of this number, 20 points are the body's own statements and 19 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · joinAlignedDiffs.joinAlignedDiffsNoExpand (cyclomatic 38) · ×1
  • joinAlignedDiffs.joinAlignedDiffsNoExpand (cyclomatic 38) packages/jest-diff/src/joinAlignedDiffs.ts:112 — joinAlignedDiffs.joinAlignedDiffsNoExpand has cyclomatic complexity 38 (threshold 15). Of this number, 35 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NotifyReporter.onRunComplete (cyclomatic 36) · ×1
  • NotifyReporter.onRunComplete (cyclomatic 36) packages/jest-reporters/src/NotifyReporter.ts:34 — NotifyReporter.onRunComplete has cyclomatic complexity 36 (threshold 15). Of this number, 31 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ModuleMocker._makeComponent (cyclomatic 32) · ×1
  • ModuleMocker._makeComponent (cyclomatic 32) packages/jest-mock/src/index.ts:731 — ModuleMocker._makeComponent has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 787, 753, 853, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · CoverageReporter._checkThreshold (cyclomatic 31) · ×1
  • CoverageReporter._checkThreshold (cyclomatic 31) packages/jest-reporters/src/CoverageReporter.ts:243 — CoverageReporter._checkThreshold has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 294, 256, 291, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · updateGlobalConfig.updateGlobalConfig (cyclomatic 30) · ×1
  • updateGlobalConfig.updateGlobalConfig (cyclomatic 30) packages/jest-core/src/lib/updateGlobalConfig.ts:16 — updateGlobalConfig.updateGlobalConfig has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · run._runTestsForDescribeBlockOnce (cyclomatic 29) · ×1
  • run._runTestsForDescribeBlockOnce (cyclomatic 29) packages/jest-circus/src/run.ts:243 — run._runTestsForDescribeBlockOnce has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · getSummary.getSummary (cyclomatic 29) · ×1
  • getSummary.getSummary (cyclomatic 29) packages/jest-reporters/src/getSummary.ts:82 — getSummary.getSummary has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.formatExecErrorWithSeen (cyclomatic 27) · ×1
  • index.formatExecErrorWithSeen (cyclomatic 27) REDACTED:143 — index.formatExecErrorWithSeen has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _landingAnimation.setupLandingAnimation (cyclomatic 26) · ×1
  • _landingAnimation.setupLandingAnimation (cyclomatic 26) website/src/pages/animations/_landingAnimation.js:17 — _landingAnimation.setupLandingAnimation has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 39, forceRun, runTest, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · runJest.runJest (cyclomatic 25) · ×1
  • runJest.runJest (cyclomatic 25) packages/jest-core/src/runJest.ts:220 — runJest.runJest has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CjsLoader.requireModule (cyclomatic 25) · ×1
  • CjsLoader.requireModule (cyclomatic 25) packages/jest-runtime/src/internals/CjsLoader.ts:77 — CjsLoader.requireModule has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · spyMatchers.createToHaveBeenNthCalledWithMatcher (cyclomatic 24) · ×1
  • spyMatchers.createToHaveBeenNthCalledWithMatcher (cyclomatic 24) packages/expect/src/spyMatchers.ts:950 — spyMatchers.createToHaveBeenNthCalledWithMatcher has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 1029, 953, 995). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · stringToBytes.stringToBytes (cyclomatic 24) · ×1
  • stringToBytes.stringToBytes (cyclomatic 24) packages/jest-config/src/stringToBytes.ts:24 — stringToBytes.stringToBytes has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.readConfigs (cyclomatic 24) · ×1
  • index.readConfigs (cyclomatic 24) packages/jest-config/src/index.ts:394 — index.readConfigs has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.printComplexValue (cyclomatic 24) · ×1
  • index.printComplexValue (cyclomatic 24) packages/pretty-format/src/index.ts:204 — index.printComplexValue has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.FUNCTIONS.mock (cyclomatic 23) · ×1
  • index.FUNCTIONS.mock (cyclomatic 23) packages/babel-plugin-jest-hoist/src/index.ts:118 — index.FUNCTIONS.mock has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · spyMatchers.createToHaveNthReturnedWithMatcher (cyclomatic 23) · ×1
  • spyMatchers.createToHaveNthReturnedWithMatcher (cyclomatic 23) packages/expect/src/spyMatchers.ts:1099 — spyMatchers.createToHaveNthReturnedWithMatcher has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 1172, 1135, 1102). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SnapshotState.match (cyclomatic 23) · ×1
  • SnapshotState.match (cyclomatic 23) packages/jest-snapshot/src/State.ts:352 — SnapshotState.match has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · shouldInstrument.shouldInstrument (cyclomatic 23) · ×1
  • shouldInstrument.shouldInstrument (cyclomatic 23) packages/jest-transform/src/shouldInstrument.ts:32 — shouldInstrument.shouldInstrument has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.printBasicValue (cyclomatic 23) · ×1
  • index.printBasicValue (cyclomatic 23) packages/pretty-format/src/index.ts:122 — index.printBasicValue has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · constraints (cyclomatic 23) · ×1
  • constraints (cyclomatic 23) yarn.config.cjs:20 — constraints has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · unhandledRejectionHandler.unhandledRejectionHandler (cyclomatic 22) · ×1
  • unhandledRejectionHandler.unhandledRejectionHandler (cyclomatic 22) packages/jest-circus/src/unhandledRejectionHandler.ts:94 — unhandledRejectionHandler.unhandledRejectionHandler has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 98). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · watch.watch · ×1
  • watch.watch::onKeypress (cyclomatic 21) packages/jest-core/src/watch.ts:349 — watch.watch::onKeypress has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CoverageReporter._addUntestedFiles (cyclomatic 21) · ×1
  • CoverageReporter._addUntestedFiles (cyclomatic 21) packages/jest-reporters/src/CoverageReporter.ts:129 — CoverageReporter._addUntestedFiles has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validate._validate (cyclomatic 21) · ×1
  • validate._validate (cyclomatic 21) packages/jest-validate/src/validate.ts:20 — validate._validate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ReactElement.getType (cyclomatic 21) · ×1
  • ReactElement.getType (cyclomatic 21) packages/pretty-format/src/plugins/ReactElement.ts:45 — ReactElement.getType has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · defaultResolver.baseResolver (cyclomatic 20) · ×1
  • defaultResolver.baseResolver (cyclomatic 20) packages/jest-resolve/src/defaultResolver.ts:131 — defaultResolver.baseResolver has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (getResolveOptions, resolveWithPathsFallback, attemptResolve). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · spyMatchers.printExpectedReceivedCallsPositive (cyclomatic 19) · ×1
  • spyMatchers.printExpectedReceivedCallsPositive (cyclomatic 19) packages/expect/src/spyMatchers.ts:139 — spyMatchers.printExpectedReceivedCallsPositive has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · args.check (cyclomatic 19) · ×1
  • args.check (cyclomatic 19) packages/jest-cli/src/args.ts:12 — args.check has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · readConfigFileAndSetRootDir.readConfigFileAndSetRootDir (cyclomatic 19) · ×1
  • readConfigFileAndSetRootDir.readConfigFileAndSetRootDir (cyclomatic 19) packages/jest-config/src/readConfigFileAndSetRootDir.ts:33 — readConfigFileAndSetRootDir.readConfigFileAndSetRootDir has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ModuleMocker.getMetadata (cyclomatic 19) · ×1
  • ModuleMocker.getMetadata (cyclomatic 19) packages/jest-mock/src/index.ts:1153 — ModuleMocker.getMetadata has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ScriptTransformer._buildTransformResult (cyclomatic 19) · ×1
  • ScriptTransformer._buildTransformResult (cyclomatic 19) packages/jest-transform/src/ScriptTransformer.ts:407 — ScriptTransformer._buildTransformResult has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.jasmine2 (cyclomatic 18) · ×1
  • index.jasmine2 (cyclomatic 18) REDACTED:152 — index.jasmine2 has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · index.getType (cyclomatic 18) · ×1
  • index.getType (cyclomatic 18) packages/jest-mock/src/index.ts:471 — index.getType has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · index._toMatchSnapshot (cyclomatic 18) · ×1
  • index._toMatchSnapshot (cyclomatic 18) packages/jest-snapshot/src/index.ts:277 — index._toMatchSnapshot has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · babel-plugin-jest-native-globals.default (cyclomatic 18) · ×1
  • babel-plugin-jest-native-globals.default (cyclomatic 18) scripts/babel-plugin-jest-native-globals.js:13 — babel-plugin-jest-native-globals.default has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · buildUtils.createBuildConfigs (cyclomatic 18) · ×1
  • buildUtils.createBuildConfigs (cyclomatic 18) scripts/buildUtils.mjs:154 — buildUtils.createBuildConfigs has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 157, 239, 272, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · index.makeThrowingMatcher (cyclomatic 17) · ×1
  • index.makeThrowingMatcher (cyclomatic 17) packages/expect/src/index.ts:275 — index.makeThrowingMatcher has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 310, 353, 282). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · normalize.setupPreset (cyclomatic 17) · ×1
  • normalize.setupPreset (cyclomatic 17) packages/jest-config/src/normalize.ts:171 — normalize.setupPreset has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/jest-config/src/normalize.ts holds 2 of the 57 methods over the threshold — including the worst — and 200 of the 786 points over it (25%), 2.9× the next-largest file (packages/jest-jasmine2/src/jasmine/Env.ts at 70). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · walk.walk (cyclomatic 17) · ×1
  • walk.walk (cyclomatic 17) packages/jest-haste-map/src/lib/walk.ts:35 — walk.walk has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 102, 111, 83). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SummaryReporter._printSnapshotSummary (cyclomatic 17) · ×1
  • SummaryReporter._printSnapshotSummary (cyclomatic 17) packages/jest-reporters/src/SummaryReporter.ts:142 — SummaryReporter._printSnapshotSummary has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JestGlobals.buildJestObject (cyclomatic 17) · ×1
  • JestGlobals.buildJestObject (cyclomatic 17) packages/jest-runtime/src/internals/JestGlobals.ts:162 — JestGlobals.buildJestObject has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 14 function items inside it that branch (_getFakeTimers, mock, mockModule, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · EsmLoader.resolveSpecifierForSyncGraph (cyclomatic 17) · ×1
  • EsmLoader.resolveSpecifierForSyncGraph (cyclomatic 17) packages/jest-runtime/src/internals/EsmLoader.ts:1127 — EsmLoader.resolveSpecifierForSyncGraph has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.extendOverlappablePathsR (cyclomatic 16) · ×1
  • index.extendOverlappablePathsR (cyclomatic 16) packages/diff-sequences/src/index.ts:389 — index.extendOverlappablePathsR has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · toThrowMatchers.createMatcher (cyclomatic 16) · ×1
  • toThrowMatchers.createMatcher (cyclomatic 16) packages/expect/src/toThrowMatchers.ts:78 — toThrowMatchers.createMatcher has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · utils.callAsyncCircusFn (cyclomatic 16) · ×1
  • utils.callAsyncCircusFn (cyclomatic 16) packages/jest-circus/src/utils.ts:196 — utils.callAsyncCircusFn has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 207, 238, 218). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ModuleMocker.spyOn (cyclomatic 16) · ×1
  • ModuleMocker.spyOn (cyclomatic 16) packages/jest-mock/src/index.ts:1269 — ModuleMocker.spyOn has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · init (cyclomatic 16) · ×1
  • init (cyclomatic 16) packages/jest-haste-map/src/watchers/WatchmanWatcher.js:78 — init has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (onClock, onCapability, onWatchProject, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · normalize.normalize (cognitive 115) · ×1
  • normalize.normalize (cognitive 115) packages/jest-config/src/normalize.ts:536 — normalize.normalize has cognitive complexity 115 (threshold 15). Drivers by points: if/else 50 (66 pts), boolean chains 38, ternaries 4 (6 pts), error handling 2 (3 pts), loops 1, match/switch 1 (nesting depth added 19). Of this number, 60 points are the body's own statements and 55 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EsmLoader.walkGraphSync (cognitive 97) · ×1
  • EsmLoader.walkGraphSync (cognitive 97) packages/jest-runtime/src/internals/EsmLoader.ts:681 — EsmLoader.walkGraphSync has cognitive complexity 97 (threshold 15). Drivers by points: if/else 32 (77 pts), loops 4 (7 pts), boolean chains 6, ternaries 1 (4 pts), error handling 1 (3 pts) (nesting depth added 53). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · joinAlignedDiffs.joinAlignedDiffsNoExpand (cognitive 87) · ×1
  • joinAlignedDiffs.joinAlignedDiffsNoExpand (cognitive 87) packages/jest-diff/src/joinAlignedDiffs.ts:112 — joinAlignedDiffs.joinAlignedDiffsNoExpand has cognitive complexity 87 (threshold 15). Drivers by points: if/else 18 (39 pts), loops 12 (35 pts), boolean chains 9, ternaries 1 (4 pts) (nesting depth added 47). Of this number, 84 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.iterableEquality (cognitive 79) · ×1
  • utils.iterableEquality (cognitive 79) packages/expect-utils/src/utils.ts:175 — utils.iterableEquality has cognitive complexity 79 (threshold 15). Drivers by points: if/else 19 (53 pts), loops 6 (18 pts), boolean chains 7, error handling 1 (nesting depth added 46). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · watchman.watchmanCrawl (cognitive 69) · ×1
  • watchman.watchmanCrawl (cognitive 69) packages/jest-haste-map/src/crawlers/watchman.ts:93 — watchman.watchmanCrawl has cognitive complexity 69 (threshold 15). Drivers by points: if/else 23 (42 pts), loops 5 (10 pts), ternaries 5 (9 pts), boolean chains 8 (nesting depth added 28). Of this number, 48 points are the body's own statements and 21 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · eventHandler.eventHandler (cognitive 64) · ×1
  • eventHandler.eventHandler (cognitive 64) packages/jest-circus/src/eventHandler.ts:27 — eventHandler.eventHandler has cognitive complexity 64 (threshold 15). Drivers by points: if/else 25 (48 pts), boolean chains 9, loops 2 (6 pts), match/switch 1 (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · FileProcessor.processFile (cognitive 61) · ×1
  • FileProcessor.processFile (cognitive 61) packages/jest-haste-map/src/lib/FileProcessor.ts:72 — FileProcessor.processFile has cognitive complexity 61 (threshold 15). Drivers by points: if/else 25 (46 pts), boolean chains 9, ternaries 2 (6 pts) (nesting depth added 25). Of this number, 39 points are the body's own statements and 22 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CoverageReporter._checkThreshold (cognitive 61) · ×1
  • CoverageReporter._checkThreshold (cognitive 61) packages/jest-reporters/src/CoverageReporter.ts:243 — CoverageReporter._checkThreshold has cognitive complexity 61 (threshold 15). Drivers by points: if/else 17 (41 pts), loops 2 (6 pts), ternaries 2 (6 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 34). Of this number, 31 points are the body's own statements and 30 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · jasmineUtils.eq (cognitive 52) · ×1
  • jasmineUtils.eq (cognitive 52) packages/expect-utils/src/jasmineUtils.ts:63 — jasmineUtils.eq has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 14, loops 5 (7 pts), match/switch 1 (nesting depth added 11). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · index.FUNCTIONS.mock (cognitive 48) · ×1
  • index.FUNCTIONS.mock (cognitive 48) packages/babel-plugin-jest-hoist/src/index.ts:118 — index.FUNCTIONS.mock has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (37 pts), boolean chains 6, loops 2 (5 pts) (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · spyMatchers.createToHaveBeenNthCalledWithMatcher (cognitive 45) · ×1
  • spyMatchers.createToHaveBeenNthCalledWithMatcher (cognitive 45) packages/expect/src/spyMatchers.ts:950 — spyMatchers.createToHaveBeenNthCalledWithMatcher has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (11 pts), boolean chains 6, ternaries 3 (nesting depth added 23). None of this is in the body itself: all 45 points belong to 3 function literals inside it that branch (lines 1029, 953, 995). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · spyMatchers.createToHaveNthReturnedWithMatcher (cognitive 43) · ×1
  • spyMatchers.createToHaveNthReturnedWithMatcher (cognitive 43) packages/expect/src/spyMatchers.ts:1099 — spyMatchers.createToHaveNthReturnedWithMatcher has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 3 (11 pts), boolean chains 6, ternaries 1 (nesting depth added 23). None of this is in the body itself: all 43 points belong to 3 function literals inside it that branch (lines 1172, 1102, 1135). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · run._runTestsForDescribeBlockOnce (cognitive 43) · ×1
  • run._runTestsForDescribeBlockOnce (cognitive 43) packages/jest-circus/src/run.ts:243 — run._runTestsForDescribeBlockOnce has cognitive complexity 43 (threshold 15). Drivers by points: loops 7 (15 pts), if/else 8 (13 pts), boolean chains 7, ternaries 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 18). Of this number, 36 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · spyMatchers.printExpectedReceivedCallsPositive (cognitive 41) · ×1
  • spyMatchers.printExpectedReceivedCallsPositive (cognitive 41) packages/expect/src/spyMatchers.ts:139 — spyMatchers.printExpectedReceivedCallsPositive has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (32 pts), boolean chains 6, loops 1 (3 pts) (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · constraints (cognitive 41) · ×1
  • constraints (cognitive 41) yarn.config.cjs:20 — constraints has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (25 pts), loops 10 (14 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.extendOverlappablePathsR (cognitive 39) · ×1
  • index.extendOverlappablePathsR (cognitive 39) packages/diff-sequences/src/index.ts:389 — index.extendOverlappablePathsR has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (30 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · readConfigFileAndSetRootDir.readConfigFileAndSetRootDir (cognitive 38) · ×1
  • readConfigFileAndSetRootDir.readConfigFileAndSetRootDir (cognitive 38) packages/jest-config/src/readConfigFileAndSetRootDir.ts:33 — readConfigFileAndSetRootDir.readConfigFileAndSetRootDir has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (27 pts), error handling 3 (8 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SnapshotState.match (cognitive 38) · ×1
  • SnapshotState.match (cognitive 38) packages/jest-snapshot/src/State.ts:352 — SnapshotState.match has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 9, ternaries 3 (6 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · buildUtils.createBuildConfigs (cognitive 38) · ×1
  • buildUtils.createBuildConfigs (cognitive 38) scripts/buildUtils.mjs:154 — buildUtils.createBuildConfigs has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 9 (30 pts), if/else 4 (5 pts), boolean chains 3 (nesting depth added 22). None of this is in the body itself: all 38 points belong to 4 function literals inside it that branch (lines 157, 239, 272, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · unhandledRejectionHandler.unhandledRejectionHandler (cognitive 36) · ×1
  • unhandledRejectionHandler.unhandledRejectionHandler (cognitive 36) packages/jest-circus/src/unhandledRejectionHandler.ts:94 — unhandledRejectionHandler.unhandledRejectionHandler has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (18 pts), loops 6 (15 pts), boolean chains 3 (nesting depth added 14). None of this is in the body itself: all 36 points belong to one function literal inside it that branches (line 98). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · runJest.runJest (cognitive 36) · ×1
  • runJest.runJest (cognitive 36) packages/jest-core/src/runJest.ts:220 — runJest.runJest has cognitive complexity 36 (threshold 15). Drivers by points: if/else 24 (33 pts), boolean chains 3 (nesting depth added 9). Of this number, 35 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NotifyReporter.onRunComplete (cognitive 36) · ×1
  • NotifyReporter.onRunComplete (cognitive 36) packages/jest-reporters/src/NotifyReporter.ts:34 — NotifyReporter.onRunComplete has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 14, ternaries 3 (6 pts) (nesting depth added 10). Of this number, 25 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.formatExecErrorWithSeen (cognitive 35) · ×1
  • index.formatExecErrorWithSeen (cognitive 35) REDACTED:143 — index.formatExecErrorWithSeen has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 9, ternaries 4 (7 pts), loops 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.printComplexValue (cognitive 34) · ×1
  • index.printComplexValue (cognitive 34) packages/pretty-format/src/index.ts:204 — index.printComplexValue has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (24 pts), if/else 6, boolean chains 4 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.extendOverlappablePathsF (cognitive 32) · ×1
  • index.extendOverlappablePathsF (cognitive 32) packages/diff-sequences/src/index.ts:256 — index.extendOverlappablePathsF has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (23 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Env.constructor (cognitive 30) · ×1
  • Env.constructor (cognitive 30) packages/jest-jasmine2/src/jasmine/Env.ts:122 — Env.constructor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, loops 5 (6 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 17 function items inside it that branch (unfocusAncestor, addSpecsToSuite, findFocusedAncestor, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: one other method here (Env.jasmineEnv) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Env.jasmineEnv (cognitive 30) · ×1
  • Env.jasmineEnv (cognitive 30) packages/jest-jasmine2/src/jasmine/Env.ts:59 — Env.jasmineEnv has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 9, loops 5 (6 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 30 points are its own statements and the rest belongs to 17 function items inside it that branch (unfocusAncestor, addSpecsToSuite, findFocusedAncestor, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest. This shape REPEATS in the file: one other method here (Env.constructor) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · _landingAnimation.setupLandingAnimation (cognitive 30) · ×1
  • _landingAnimation.setupLandingAnimation (cognitive 30) website/src/pages/animations/_landingAnimation.js:17 — _landingAnimation.setupLandingAnimation has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 7 (10 pts), boolean chains 3, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 39, runTest, forceRun, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CjsExportsCache.getExportsOf (cognitive 29) · ×1
  • CjsExportsCache.getExportsOf (cognitive 29) packages/jest-runtime/src/internals/CjsExportsCache.ts:56 — CjsExportsCache.getExportsOf has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (8 pts), error handling 3 (5 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubActionsReporter.recursivePrintResultTree (cognitive 28) · ×1
  • GitHubActionsReporter.recursivePrintResultTree (cognitive 28) packages/jest-reporters/src/GitHubActionsReporter.ts:355 — GitHubActionsReporter.recursivePrintResultTree has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (11 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · updateGlobalConfig.updateGlobalConfig (cognitive 27) · ×1
  • updateGlobalConfig.updateGlobalConfig (cognitive 27) packages/jest-core/src/lib/updateGlobalConfig.ts:16 — updateGlobalConfig.updateGlobalConfig has cognitive complexity 27 (threshold 15). Drivers by points: if/else 21, boolean chains 6. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · index.jasmine2 (cognitive 27) · ×1
  • index.jasmine2 (cognitive 27) REDACTED:152 — index.jasmine2 has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · CoverageReporter._addUntestedFiles (cognitive 27) · ×1
  • CoverageReporter._addUntestedFiles (cognitive 27) packages/jest-reporters/src/CoverageReporter.ts:129 — CoverageReporter._addUntestedFiles has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, loops 2 (4 pts), error handling 2 (3 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 12 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate._validate (cognitive 27) · ×1
  • validate._validate (cognitive 27) packages/jest-validate/src/validate.ts:20 — validate._validate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 5, loops 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · toThrowMatchers.createMatcher (cognitive 26) · ×1
  • toThrowMatchers.createMatcher (cognitive 26) packages/expect/src/toThrowMatchers.ts:78 — toThrowMatchers.createMatcher has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, ternaries 1 (4 pts), error handling 1 (3 pts) (nesting depth added 8). None of this is in the body itself: all 26 points belong to one function literal inside it that branches (line 82). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · stringToBytes.stringToBytes (cognitive 26) · ×1
  • stringToBytes.stringToBytes (cognitive 26) packages/jest-config/src/stringToBytes.ts:24 — stringToBytes.stringToBytes has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, match/switch 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · normalize.setupBabelJest (cognitive 26) · ×1
  • normalize.setupBabelJest (cognitive 26) packages/jest-config/src/normalize.ts:262 — normalize.setupBabelJest has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). Of this number, 24 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · index.readConfigs (cognitive 26) · ×1
  • index.readConfigs (cognitive 26) packages/jest-config/src/index.ts:394 — index.readConfigs has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 10, ternaries 2 (4 pts) (nesting depth added 6). Of this number, 15 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getSnapshotSummary.getSnapshotSummary (cognitive 26) · ×1
  • getSnapshotSummary.getSnapshotSummary (cognitive 26) packages/jest-reporters/src/getSnapshotSummary.ts:25 — getSnapshotSummary.getSnapshotSummary has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 3 (7 pts), ternaries 2 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JestGlobals.buildJestObject (cognitive 26) · ×1
  • JestGlobals.buildJestObject (cognitive 26) packages/jest-runtime/src/internals/JestGlobals.ts:162 — JestGlobals.buildJestObject has cognitive complexity 26 (threshold 15). Drivers by points: if/else 24, boolean chains 2. None of this is in the body itself: all 26 points belong to 14 function items inside it that branch (_getFakeTimers, useFakeTimers, retryTimes, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ReactElement.getType (cognitive 26) · ×1
  • ReactElement.getType (cognitive 26) packages/pretty-format/src/plugins/ReactElement.ts:45 — ReactElement.getType has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.callAsyncCircusFn (cognitive 25) · ×1
  • utils.callAsyncCircusFn (cognitive 25) packages/jest-circus/src/utils.ts:196 — utils.callAsyncCircusFn has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 8). None of this is in the body itself: all 25 points belong to 3 function literals inside it that branch (lines 207, 238, 218). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ModuleMocker.getMetadata (cognitive 25) · ×1
  • ModuleMocker.getMetadata (cognitive 25) packages/jest-mock/src/index.ts:1153 — ModuleMocker.getMetadata has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · shouldInstrument.shouldInstrument (cognitive 25) · ×1
  • shouldInstrument.shouldInstrument (cognitive 25) packages/jest-transform/src/shouldInstrument.ts:32 — shouldInstrument.shouldInstrument has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · index.printBasicValue (cognitive 25) · ×1
  • index.printBasicValue (cognitive 25) packages/pretty-format/src/index.ts:122 — index.printBasicValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (21 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · walk.walk (cognitive 24) · ×1
  • walk.walk (cognitive 24) packages/jest-haste-map/src/lib/walk.ts:35 — walk.walk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 6 (10 pts), boolean chains 3, loops 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 102, 111, 83). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · normalize.setupPreset (cognitive 23) · ×1
  • normalize.setupPreset (cognitive 23) packages/jest-config/src/normalize.ts:171 — normalize.setupPreset has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 5, error handling 2, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubActionsReporter.getResultChildren (cognitive 23) · ×1
  • GitHubActionsReporter.getResultChildren (cognitive 23) packages/jest-reporters/src/GitHubActionsReporter.ts:259 — GitHubActionsReporter.getResultChildren has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CjsLoader.requireModule (cognitive 23) · ×1
  • CjsLoader.requireModule (cognitive 23) packages/jest-runtime/src/internals/CjsLoader.ts:77 — CjsLoader.requireModule has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 5, error handling 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index._toMatchSnapshot (cognitive 23) · ×1
  • index._toMatchSnapshot (cognitive 23) packages/jest-snapshot/src/index.ts:277 — index._toMatchSnapshot has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 5 (9 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScriptTransformer._buildTransformResult (cognitive 23) · ×1
  • ScriptTransformer._buildTransformResult (cognitive 23) packages/jest-transform/src/ScriptTransformer.ts:407 — ScriptTransformer._buildTransformResult has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · index.makeThrowingMatcher (cognitive 22) · ×1
  • index.makeThrowingMatcher (cognitive 22) packages/expect/src/index.ts:275 — index.makeThrowingMatcher has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, error handling 1 (nesting depth added 5). None of this is in the body itself: all 22 points belong to 3 function literals inside it that branch (lines 310, 282, 353). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · runGlobalHook.runGlobalHook (cognitive 22) · ×1
  • runGlobalHook.runGlobalHook (cognitive 22) packages/jest-core/src/runGlobalHook.ts:14 — runGlobalHook.runGlobalHook has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (3 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). Of this number, 19 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · watch.watch (cognitive 22) · ×1
  • watch.watch (cognitive 22) packages/jest-core/src/watch.ts:91 — watch.watch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 25 (39 pts), boolean chains 6, loops 4 (6 pts), error handling 2 (4 pts), match/switch 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (watch.watch::onKeypress) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ModuleMocker._makeComponent (cognitive 22) · ×1
  • ModuleMocker._makeComponent (cognitive 22) packages/jest-mock/src/index.ts:731 — ModuleMocker._makeComponent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 6 belong to 8 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EsmLoader.resolveSpecifierForSyncGraph (cognitive 22) · ×1
  • EsmLoader.resolveSpecifierForSyncGraph (cognitive 22) packages/jest-runtime/src/internals/EsmLoader.ts:1127 — EsmLoader.resolveSpecifierForSyncGraph has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EsmLoader.loadEsmModule (cognitive 22) · ×1
  • EsmLoader.loadEsmModule (cognitive 22) packages/jest-runtime/src/internals/EsmLoader.ts:1841 — EsmLoader.loadEsmModule has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (6 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dedentLines.dedentMarkup (cognitive 22) · ×1
  • dedentLines.dedentMarkup (cognitive 22) packages/jest-snapshot/src/dedentLines.ts:80 — dedentLines.dedentMarkup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · printSnapshot.printSnapshotAndReceived (cognitive 22) · ×1
  • printSnapshot.printSnapshotAndReceived (cognitive 22) packages/jest-snapshot/src/printSnapshot.ts:238 — printSnapshot.printSnapshotAndReceived has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · createProcessObject.createProcessEnv (cognitive 22) · ×1
  • createProcessObject.createProcessEnv (cognitive 22) packages/jest-util/src/createProcessObject.ts:20 — createProcessObject.createProcessEnv has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 3 (4 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (deletePropertyWin32, getPropertyWin32). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · init (cognitive 22) · ×1
  • init (cognitive 22) packages/jest-haste-map/src/watchers/WatchmanWatcher.js:78 — init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), loops 1 (3 pts), other 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 8 function items inside it that branch (onClock, onCapability, onWatchProject, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · spyMatchers.createToHaveBeenLastCalledWithMatcher (cognitive 21) · ×1
  • spyMatchers.createToHaveBeenLastCalledWithMatcher (cognitive 21) packages/expect/src/spyMatchers.ts:760 — spyMatchers.createToHaveBeenLastCalledWithMatcher has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (4 pts), boolean chains 3, ternaries 3 (nesting depth added 10). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 816, 763, 787). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · jestAdapter.jestAdapter (cognitive 21) · ×1
  • jestAdapter.jestAdapter (cognitive 21) packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:17 — jestAdapter.jestAdapter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 1, loops 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubActionsReporter.getResultTree (cognitive 21) · ×1
  • GitHubActionsReporter.getResultTree (cognitive 21) packages/jest-reporters/src/GitHubActionsReporter.ts:212 — GitHubActionsReporter.getResultTree has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InlineSnapshots.saveInlineSnapshots (cognitive 21) · ×1
  • InlineSnapshots.saveInlineSnapshots (cognitive 21) packages/jest-snapshot/src/InlineSnapshots.ts:45 — InlineSnapshots.saveInlineSnapshots has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, error handling 1 (2 pts), ternaries 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveConfigPath.resolveConfigPathByTraversing (cognitive 20) · ×1
  • resolveConfigPath.resolveConfigPathByTraversing (cognitive 20) packages/jest-config/src/resolveConfigPath.ts:67 — resolveConfigPath.resolveConfigPathByTraversing has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · node.findNative (cognitive 20) · ×1
  • node.findNative (cognitive 20) packages/jest-haste-map/src/crawlers/node.ts:100 — node.findNative has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 137, 147, 142). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · printSnapshot.matcherHintFromConfig (cognitive 20) · ×1
  • printSnapshot.matcherHintFromConfig (cognitive 20) packages/jest-snapshot/src/printSnapshot.ts:94 — printSnapshot.matcherHintFromConfig has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · spyMatchers.createToHaveLastReturnedWithMatcher (cognitive 19) · ×1
  • spyMatchers.createToHaveLastReturnedWithMatcher (cognitive 19) packages/expect/src/spyMatchers.ts:858 — spyMatchers.createToHaveLastReturnedWithMatcher has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 1 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 10). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 907, 859, 875). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · worker.worker (cognitive 19) · ×1
  • worker.worker (cognitive 19) packages/jest-haste-map/src/worker.ts:28 — worker.worker has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (4 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ModuleMocker.spyOn (cognitive 19) · ×1
  • ModuleMocker.spyOn (cognitive 19) packages/jest-mock/src/index.ts:1269 — ModuleMocker.spyOn has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CoverageReporter._getCoverageResult (cognitive 19) · ×1
  • CoverageReporter._getCoverageResult (cognitive 19) packages/jest-reporters/src/CoverageReporter.ts:468 — CoverageReporter._getCoverageResult has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 3 (7 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 9). Of this number, 13 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Resolver.resolveStubModuleName (cognitive 19) · ×1
  • Resolver.resolveStubModuleName (cognitive 19) packages/jest-resolve/src/resolver.ts:881 — Resolver.resolveStubModuleName has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Resolver.resolveStubModuleNameAsync) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Resolver.resolveStubModuleNameAsync (cognitive 19) · ×1
  • Resolver.resolveStubModuleNameAsync (cognitive 19) packages/jest-resolve/src/resolver.ts:943 — Resolver.resolveStubModuleNameAsync has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Resolver.resolveStubModuleName) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · EsmLoader.linkAndEvaluateModule (cognitive 19) · ×1
  • EsmLoader.linkAndEvaluateModule (cognitive 19) packages/jest-runtime/src/internals/EsmLoader.ts:2114 — EsmLoader.linkAndEvaluateModule has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · babel-plugin-jest-native-globals.default (cognitive 19) · ×1
  • babel-plugin-jest-native-globals.default (cognitive 19) scripts/babel-plugin-jest-native-globals.js:13 — babel-plugin-jest-native-globals.default has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 7 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · args.check (cognitive 18) · ×1
  • args.check (cognitive 18) packages/jest-cli/src/args.ts:12 — args.check has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · watch.watch · ×1
  • watch.watch::onKeypress (cognitive 18) packages/jest-core/src/watch.ts:349 — watch.watch::onKeypress has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (watch.watch) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · NodeEnvironment.constructor (cognitive 18) · ×1
  • NodeEnvironment.constructor (cognitive 18) packages/jest-environment-node/src/index.ts:100 — NodeEnvironment.constructor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ParcelWatcher._handleEvents (cognitive 18) · ×1
  • ParcelWatcher._handleEvents (cognitive 18) packages/jest-haste-map/src/watchers/ParcelWatcher.ts:200 — ParcelWatcher._handleEvents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 9). Of this number, 11 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VerboseReporter._logTests (cognitive 18) · ×1
  • VerboseReporter._logTests (cognitive 18) packages/jest-reporters/src/VerboseReporter.ts:137 — VerboseReporter._logTests has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (8 pts) (nesting depth added 8). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · defaultResolver.baseResolver (cognitive 18) · ×1
  • defaultResolver.baseResolver (cognitive 18) packages/jest-resolve/src/defaultResolver.ts:131 — defaultResolver.baseResolver has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (7 pts), boolean chains 6, if/else 5 (nesting depth added 2). Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · WatchmanWatcher.WatchmanWatcher.handleFileChange (cognitive 17) · ×1
  • WatchmanWatcher.WatchmanWatcher.handleFileChange (cognitive 17) packages/jest-haste-map/src/watchers/WatchmanWatcher.js:244 — WatchmanWatcher.WatchmanWatcher.handleFileChange has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 4). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 269). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · wrapAnsiString.wrapAnsiString (cognitive 17) · ×1
  • wrapAnsiString.wrapAnsiString (cognitive 17) packages/jest-reporters/src/wrapAnsiString.ts:10 — wrapAnsiString.wrapAnsiString has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 42). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · SummaryReporter._printSnapshotSummary (cognitive 17) · ×1
  • SummaryReporter._printSnapshotSummary (cognitive 17) packages/jest-reporters/src/SummaryReporter.ts:142 — SummaryReporter._printSnapshotSummary has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (5 pts), ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.deepMerge (cognitive 17) · ×1
  • utils.deepMerge (cognitive 17) packages/jest-snapshot/src/utils.ts:111 — utils.deepMerge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index._toThrowErrorMatchingSnapshot (cognitive 17) · ×1
  • index._toThrowErrorMatchingSnapshot (cognitive 17) packages/jest-snapshot/src/index.ts:493 — index._toThrowErrorMatchingSnapshot has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createProcessObject.createProcessObject (cognitive 17) · ×1
  • createProcessObject.createProcessObject (cognitive 17) packages/jest-util/src/createProcessObject.ts:83 — createProcessObject.createProcessObject has cognitive complexity 17 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 4 (7 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · messageParent.messageParent (cognitive 17) · ×1
  • messageParent.messageParent (cognitive 17) packages/jest-worker/src/workers/messageParent.ts:14 — messageParent.messageParent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AsymmetricMatcher.serialize (cognitive 17) · ×1
  • AsymmetricMatcher.serialize (cognitive 17) packages/pretty-format/src/plugins/AsymmetricMatcher.ts:17 — AsymmetricMatcher.serialize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build.buildNodePackages (cognitive 17) · ×1
  • build.buildNodePackages (cognitive 17) scripts/build.mjs:26 — build.buildNodePackages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (7 pts), boolean chains 1, error handling 1 (nesting depth added 8). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runCreate.runCreate (cognitive 16) · ×1
  • runCreate.runCreate (cognitive 16) packages/create-jest/src/runCreate.ts:50 — runCreate.runCreate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · index.divide (cognitive 16) · ×1
  • index.divide (cognitive 16) packages/diff-sequences/src/index.ts:530 — index.divide has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · utils.getObjectSubset (cognitive 16) · ×1
  • utils.getObjectSubset (cognitive 16) packages/expect-utils/src/utils.ts:116 — utils.getObjectSubset has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · collectHandles.collectHandles (cognitive 16) · ×1
  • collectHandles.collectHandles (cognitive 16) packages/jest-core/src/collectHandles.ts:64 — collectHandles.collectHandles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 73, 145). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.runCLI (cognitive 16) · ×1
  • index.runCLI (cognitive 16) packages/jest-core/src/cli/index.ts:38 — index.runCLI has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · jasmineAsyncInstall.promisifyIt (cognitive 16) · ×1
  • jasmineAsyncInstall.promisifyIt (cognitive 16) packages/jest-jasmine2/src/jasmineAsyncInstall.ts:105 — jasmineAsyncInstall.promisifyIt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 4). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 161, 156, 114). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · index.collectSpecs (cognitive 16) · ×1
  • index.collectSpecs (cognitive 16) REDACTED:56 — index.collectSpecs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, loops 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ImportAttributeValidator.validate (cognitive 16) · ×1
  • ImportAttributeValidator.validate (cognitive 16) packages/jest-runtime/src/internals/importAttributes.ts:51 — ImportAttributeValidator.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · EsmLoader.resolveModule (cognitive 16) · ×1
  • EsmLoader.resolveModule (cognitive 16) packages/jest-runtime/src/internals/EsmLoader.ts:1994 — EsmLoader.resolveModule has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D23 · Boundary Type-Coupling · Cross-context type BlockMode (jest-types → jest-circus) · ×1
  • Cross-context type BlockMode (jest-types → jest-circus) packages/jest-circus/src/utils.ts:41 — BlockMode (context jest-types) is exposed in jest-circus's public surface via utils.makeDescribe — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type TestFn (jest-types → jest-circus) · ×1
  • Cross-context type TestFn (jest-types → jest-circus) packages/jest-circus/src/utils.ts:63 — TestFn (context jest-types) is exposed in jest-circus's public surface via utils.makeTest — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type AsyncEvent (jest-types → jest-circus) · ×1
  • Cross-context type AsyncEvent (jest-types → jest-circus) packages/jest-circus/src/state.ts:82 — AsyncEvent (context jest-types) is exposed in jest-circus's public surface via state.dispatch — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type SyncEvent (jest-types → jest-circus) · ×1
  • Cross-context type SyncEvent (jest-types → jest-circus) packages/jest-circus/src/state.ts:88 — SyncEvent (context jest-types) is exposed in jest-circus's public surface via state.dispatchSync — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type ArrayTable (jest-types → jest-each) · ×1
  • Cross-context type ArrayTable (jest-types → jest-each) packages/jest-each/src/table/array.ts:24 — ArrayTable (context jest-types) is exposed in jest-each's public surface via array.array — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type EachTable (jest-types → jest-each) · ×1
  • Cross-context type EachTable (jest-types → jest-each) packages/jest-each/src/index.ts:69 — EachTable (context jest-types) is exposed in jest-each's public surface via index.each — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type TestNameLike (jest-types → jest-jasmine2) · ×1
  • Cross-context type TestNameLike (jest-types → jest-jasmine2) packages/jest-jasmine2/src/jasmine/Suite.ts:61 — TestNameLike (context jest-types) is exposed in jest-jasmine2's public surface via Suite.description — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type SnapshotUpdateState (jest-types → jest-snapshot-utils) · ×1
  • Cross-context type SnapshotUpdateState (jest-types → jest-snapshot-utils) packages/jest-snapshot-utils/src/utils.ts:133 — SnapshotUpdateState (context jest-types) is exposed in jest-snapshot-utils's public surface via utils.getSnapshotData — couples the contexts.
D23 · Boundary Type-Coupling · Cross-context type SnapshotUpdateState (jest-types → jest-snapshot) · ×1
  • Cross-context type SnapshotUpdateState (jest-types → jest-snapshot) packages/jest-snapshot/src/index.ts:117 — SnapshotUpdateState (context jest-types) is exposed in jest-snapshot's public surface via index.cleanup — couples the contexts.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D5 · Coupling · Unstable project @jest/core · ×1
  • Unstable project @jest/core — @jest/core has instability 0.91 with 2 dependents.
D5 · Coupling · Unstable project @jest/environment-jsdom-abstract · ×1
  • Unstable project @jest/environment-jsdom-abstract — @jest/environment-jsdom-abstract has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project @jest/reporters · ×1
  • Unstable project @jest/reporters — @jest/reporters has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project jest-circus · ×1
  • Unstable project jest-circus — jest-circus has instability 0.92 with 1 dependents.
D5 · Coupling · Unstable project jest-cli · ×1
  • Unstable project jest-cli — jest-cli has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project jest-config · ×1
  • Unstable project jest-config — jest-config has instability 0.82 with 3 dependents.
D5 · Coupling · Unstable project jest-runner · ×1
  • Unstable project jest-runner — jest-runner has instability 0.89 with 2 dependents.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (Error: Cannot find module 'packages/jest-cli/build/index.js'. Please verify that the package.json has a valid "main" entry), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 231 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P1 · CI/CD gates · CI formatting step cannot fail · ×1
  • CI formatting step cannot fail .github/workflows/nodejs.yml:87 — `yarn lint:prettier:ci` invokes prettier in the mode that REWRITES the files it reformats and exits 0 whatever it changed. The rewrite happens inside the runner's throwaway checkout and is then discarded, so the step passes on a badly-formatted change exactly as it passes on a clean one — it enforces nothing, and no other step in this file reads the result. `--check` is the flag that turns the same invocation into a gate: it leaves the files alone and exits non-zero when anything would have been reformatted.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 447 JavaScript/TypeScript production file(s) this check read across 63 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 922 typed · 1124 plain JS — the untyped files are e2e/MockStdinWatchPlugin.js, e2e/__tests__/nodeURLManualMocks.test.js, e2e/__tests__/testFailingSnapshot.test.js, e2e/async-regenerator/__tests__/test.js, e2e/auto-clear-mocks/with-auto-clear/__tests__/index.js, e2e/auto-clear-mocks/with-auto-clear/index.js (+1118 more).
R10 · Code Duplication · Duplication concentrated across 15 sibling directories (12 clone groups) · ×1
  • Duplication concentrated across 15 sibling directories (12 clone groups) packages/jest-circus/src/formatNodeAssertErrors.ts:77 — 12 duplicated blocks under packages/ have copies in at least two of the sibling directories expect, jest-circus, jest-config, jest-diff, jest-environment-jsdom-abstract, jest-environment-node (+9 more sibling(s) not listed) — 9 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 12 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 12 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (204 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (204 matched lines × 2 locations) packages/jest-worker/src/workers/ChildProcessWorker.ts:57 — packages/jest-worker/src/workers/ChildProcessWorker.ts:57 · packages/jest-worker/src/workers/NodeThreadsWorker.ts:31 — the two spans are one implementation copied and then locally edited — 1166 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (126 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (126 matched lines × 2 locations) packages/jest-worker/src/workers/processChild.ts:26 — packages/jest-worker/src/workers/processChild.ts:26 · packages/jest-worker/src/workers/threadChild.ts:28 — the two spans are one implementation copied and then locally edited — 664 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (103 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (103 matched lines × 2 locations) packages/expect/src/spyMatchers.ts:953 — packages/expect/src/spyMatchers.ts:953 · packages/expect/src/spyMatchers.ts:1102 — the two spans are one implementation copied and then locally edited — 568 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (93 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (93 matched lines × 2 locations) packages/jest-circus/src/formatNodeAssertErrors.ts:77 — packages/jest-circus/src/formatNodeAssertErrors.ts:77 · packages/jest-jasmine2/src/assertionErrorMessage.ts:35 — the two spans are one implementation copied and then locally edited — 528 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (85 lines × 2 locations) · ×1
  • Duplicated block (85 lines × 2 locations) packages/jest-console/src/BufferedConsole.ts:79 — packages/jest-console/src/BufferedConsole.ts:79 · packages/jest-console/src/CustomConsole.ts:81 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (66 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (66 matched lines × 2 locations) packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:43 — packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:43 · REDACTED:234 — the two spans are one implementation copied and then locally edited — 401 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (48 lines × 2 locations) · ×1
  • Duplicated block (48 lines × 2 locations) packages/expect/src/index.ts:170 — packages/expect/src/index.ts:170 · packages/expect/src/index.ts:226 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (47 lines × 2 locations) · ×1
  • Duplicated block (47 lines × 2 locations) packages/jest-transform/src/ScriptTransformer.ts:627 — packages/jest-transform/src/ScriptTransformer.ts:627 · packages/jest-transform/src/ScriptTransformer.ts:675 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) packages/jest-environment-jsdom-abstract/src/index.ts:140 — packages/jest-environment-jsdom-abstract/src/index.ts:140 · packages/jest-environment-node/src/index.ts:209 — the two spans are one implementation copied and then locally edited — 168 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (35 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (35 matched lines × 2 locations) packages/jest-config/src/ValidConfig.ts:39 — packages/jest-config/src/ValidConfig.ts:39 · packages/jest-config/src/ValidConfig.ts:223 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (31 matched lines × 2 locations) packages/expect/src/toThrowMatchers.ts:150 — packages/expect/src/toThrowMatchers.ts:150 · packages/expect/src/toThrowMatchers.ts:346 — the two spans are one implementation copied and then locally edited — 248 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) packages/jest-resolve/src/resolver.ts:241 — packages/jest-resolve/src/resolver.ts:241 · packages/jest-resolve/src/resolver.ts:316 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) packages/jest-core/src/plugins/TestNamePattern.ts:20 — packages/jest-core/src/plugins/TestNamePattern.ts:20 · packages/jest-core/src/plugins/TestPathPattern.ts:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (28 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (28 matched lines × 2 locations) packages/pretty-format/src/collections.ts:45 — packages/pretty-format/src/collections.ts:45 · packages/pretty-format/src/collections.ts:107 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) packages/expect/src/spyMatchers.ts:814 — packages/expect/src/spyMatchers.ts:814 · packages/expect/src/spyMatchers.ts:905 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) packages/jest-transform/src/ScriptTransformer.ts:727 — packages/jest-transform/src/ScriptTransformer.ts:727 · packages/jest-transform/src/ScriptTransformer.ts:755 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (24 matched lines × 2 locations) packages/pretty-format/src/plugins/AsymmetricMatcher.ts:17 — packages/pretty-format/src/plugins/AsymmetricMatcher.ts:17 · packages/pretty-format/src/plugins/Immutable.ts:62 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) packages/expect/src/spyMatchers.ts:612 — packages/expect/src/spyMatchers.ts:612 · packages/expect/src/spyMatchers.ts:689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block with local edits (22 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (22 matched lines × 2 locations) packages/jest-reporters/src/AgentReporter.ts:41 — packages/jest-reporters/src/AgentReporter.ts:41 · packages/jest-reporters/src/DefaultReporter.ts:167 — the two spans are one implementation copied and then locally edited — 89 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (18 lines × 4 locations) · ×1
  • Duplicated block (18 lines × 4 locations) REDACTED:215 — REDACTED:215 · REDACTED:389 · REDACTED:408 · REDACTED:427 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 140, cognitive 66) · ×1
  • Complex function (anonymous) (cyclomatic 140, cognitive 66) packages/jest-config/src/normalize.ts:643 — (anonymous) has cyclomatic complexity 140 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function normalize (cyclomatic 64, cognitive 63) · ×1
  • Complex function normalize (cyclomatic 64, cognitive 63) packages/jest-config/src/normalize.ts:536 — normalize has cyclomatic complexity 64 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function eventHandler (cyclomatic 53, cognitive 62) · ×1
  • Complex function eventHandler (cyclomatic 53, cognitive 62) packages/jest-circus/src/eventHandler.ts:27 — eventHandler has cyclomatic complexity 53 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function walkGraphSync (cyclomatic 48, cognitive 99) · ×1
  • Complex function walkGraphSync (cyclomatic 48, cognitive 99) packages/jest-runtime/src/internals/EsmLoader.ts:681 — walkGraphSync has cyclomatic complexity 48 and cognitive complexity 99; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function eq (cyclomatic 47, cognitive 52) · ×1
  • Complex function eq (cyclomatic 47, cognitive 52) packages/expect-utils/src/jasmineUtils.ts:63 — eq has cyclomatic complexity 47 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 45, cognitive 81) · ×1
  • Complex function (anonymous) (cyclomatic 45, cognitive 81) packages/expect-utils/src/utils.ts:182 — (anonymous) has cyclomatic complexity 45 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 35, cognitive 84) · ×1
  • Complex function (anonymous) (cyclomatic 35, cognitive 84) packages/jest-diff/src/joinAlignedDiffs.ts:115 — (anonymous) has cyclomatic complexity 35 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runTestInternal (cyclomatic 34, cognitive 40) · ×1
  • Complex function runTestInternal (cyclomatic 34, cognitive 40) packages/jest-runner/src/runTest.ts:82 — runTestInternal has cyclomatic complexity 34 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onRunComplete (cyclomatic 31, cognitive 30) · ×1
  • Complex function onRunComplete (cyclomatic 31, cognitive 30) packages/jest-reporters/src/NotifyReporter.ts:34 — onRunComplete has cyclomatic complexity 31 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function updateGlobalConfig (cyclomatic 30, cognitive 29) · ×1
  • Complex function updateGlobalConfig (cyclomatic 30, cognitive 29) packages/jest-core/src/lib/updateGlobalConfig.ts:16 — updateGlobalConfig has cyclomatic complexity 30 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getSummary (cyclomatic 29, cognitive 29) · ×1
  • Complex function getSummary (cyclomatic 29, cognitive 29) packages/jest-reporters/src/getSummary.ts:82 — getSummary has cyclomatic complexity 29 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function watchmanCrawl (cyclomatic 27, cognitive 49) · ×1
  • Complex function watchmanCrawl (cyclomatic 27, cognitive 49) packages/jest-haste-map/src/crawlers/watchman.ts:93 — watchmanCrawl has cyclomatic complexity 27 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 27, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 27, cognitive 38) REDACTED:151 — (anonymous) has cyclomatic complexity 27 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function requireModule (cyclomatic 27, cognitive 27) · ×1
  • Complex function requireModule (cyclomatic 27, cognitive 27) packages/jest-runtime/src/internals/CjsLoader.ts:77 — requireModule has cyclomatic complexity 27 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runJest (cyclomatic 24, cognitive 36) · ×1
  • Complex function runJest (cyclomatic 24, cognitive 36) packages/jest-core/src/runJest.ts:220 — runJest has cyclomatic complexity 24 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function printComplexValue (cyclomatic 24, cognitive 28) · ×1
  • Complex function printComplexValue (cyclomatic 24, cognitive 28) packages/pretty-format/src/index.ts:204 — printComplexValue has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function shouldInstrument (cyclomatic 24, cognitive 27) · ×1
  • Complex function shouldInstrument (cyclomatic 24, cognitive 27) packages/jest-transform/src/shouldInstrument.ts:32 — shouldInstrument has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function stringToBytes (cyclomatic 24, cognitive 26) · ×1
  • Complex function stringToBytes (cyclomatic 24, cognitive 26) packages/jest-config/src/stringToBytes.ts:24 — stringToBytes has cyclomatic complexity 24 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function mock (cyclomatic 23, cognitive 55) · ×1
  • Complex function mock (cyclomatic 23, cognitive 55) packages/babel-plugin-jest-hoist/src/index.ts:118 — mock has cyclomatic complexity 23 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/jest-runtime/src/internals/EsmLoader.ts · ×1
  • packages/jest-runtime/src/internals/EsmLoader.ts: 2239 lines of code packages/jest-runtime/src/internals/EsmLoader.ts:1 — packages/jest-runtime/src/internals/EsmLoader.ts has 2239 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-mock/src/index.ts · ×1
  • packages/jest-mock/src/index.ts: 1455 lines of code packages/jest-mock/src/index.ts:1 — packages/jest-mock/src/index.ts has 1455 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/expect/src/spyMatchers.ts · ×1
  • packages/expect/src/spyMatchers.ts: 1162 lines of code packages/expect/src/spyMatchers.ts:1 — packages/expect/src/spyMatchers.ts has 1162 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-config/src/normalize.ts · ×1
  • packages/jest-config/src/normalize.ts: 1159 lines of code packages/jest-config/src/normalize.ts:1 — packages/jest-config/src/normalize.ts has 1159 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-resolve/src/resolver.ts · ×1
  • packages/jest-resolve/src/resolver.ts: 1029 lines of code packages/jest-resolve/src/resolver.ts:1 — packages/jest-resolve/src/resolver.ts has 1029 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-transform/src/ScriptTransformer.ts · ×1
  • packages/jest-transform/src/ScriptTransformer.ts: 982 lines of code packages/jest-transform/src/ScriptTransformer.ts:1 — packages/jest-transform/src/ScriptTransformer.ts has 982 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 874 lines of code REDACTED:1 — REDACTED has 874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-cli/src/args.ts · ×1
  • packages/jest-cli/src/args.ts: 785 lines of code packages/jest-cli/src/args.ts:1 — packages/jest-cli/src/args.ts has 785 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/diff-sequences/src/index.ts · ×1
  • packages/diff-sequences/src/index.ts: 778 lines of code packages/diff-sequences/src/index.ts:1 — packages/diff-sequences/src/index.ts has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 711 lines of code REDACTED:1 — REDACTED has 711 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 645 lines of code REDACTED:1 — REDACTED has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-jasmine2/src/jasmine/Env.ts · ×1
  • packages/jest-jasmine2/src/jasmine/Env.ts: 629 lines of code packages/jest-jasmine2/src/jasmine/Env.ts:1 — packages/jest-jasmine2/src/jasmine/Env.ts has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 595 lines of code REDACTED:1 — REDACTED has 595 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-fake-timers/src/legacyFakeTimers.ts · ×1
  • packages/jest-fake-timers/src/legacyFakeTimers.ts: 541 lines of code packages/jest-fake-timers/src/legacyFakeTimers.ts:1 — packages/jest-fake-timers/src/legacyFakeTimers.ts has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-core/src/watch.ts · ×1
  • packages/jest-core/src/watch.ts: 536 lines of code packages/jest-core/src/watch.ts:1 — packages/jest-core/src/watch.ts has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-matcher-utils/src/index.ts · ×1
  • packages/jest-matcher-utils/src/index.ts: 522 lines of code packages/jest-matcher-utils/src/index.ts:1 — packages/jest-matcher-utils/src/index.ts has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/expect-utils/src/utils.ts · ×1
  • packages/expect-utils/src/utils.ts: 509 lines of code packages/expect-utils/src/utils.ts:1 — packages/expect-utils/src/utils.ts has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-snapshot/src/index.ts · ×1
  • packages/jest-snapshot/src/index.ts: 497 lines of code packages/jest-snapshot/src/index.ts:1 — packages/jest-snapshot/src/index.ts has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/pretty-format/src/index.ts · ×1
  • packages/pretty-format/src/index.ts: 496 lines of code packages/pretty-format/src/index.ts:1 — packages/pretty-format/src/index.ts has 496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 493 lines of code REDACTED:1 — REDACTED has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-circus/src/utils.ts · ×1
  • packages/jest-circus/src/utils.ts: 482 lines of code packages/jest-circus/src/utils.ts:1 — packages/jest-circus/src/utils.ts has 482 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/expect/src/toThrowMatchers.ts · ×1
  • packages/expect/src/toThrowMatchers.ts: 479 lines of code packages/expect/src/toThrowMatchers.ts:1 — packages/expect/src/toThrowMatchers.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-config/src/index.ts · ×1
  • packages/jest-config/src/index.ts: 477 lines of code packages/jest-config/src/index.ts:1 — packages/jest-config/src/index.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-core/src/TestScheduler.ts · ×1
  • packages/jest-core/src/TestScheduler.ts: 477 lines of code packages/jest-core/src/TestScheduler.ts:1 — packages/jest-core/src/TestScheduler.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-reporters/src/CoverageReporter.ts · ×1
  • packages/jest-reporters/src/CoverageReporter.ts: 477 lines of code packages/jest-reporters/src/CoverageReporter.ts:1 — packages/jest-reporters/src/CoverageReporter.ts has 477 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-circus/src/run.ts · ×1
  • packages/jest-circus/src/run.ts: 467 lines of code packages/jest-circus/src/run.ts:1 — packages/jest-circus/src/run.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-worker/src/workers/ChildProcessWorker.ts · ×1
  • packages/jest-worker/src/workers/ChildProcessWorker.ts: 467 lines of code packages/jest-worker/src/workers/ChildProcessWorker.ts:1 — packages/jest-worker/src/workers/ChildProcessWorker.ts has 467 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-environment/src/index.ts · ×1
  • packages/jest-environment/src/index.ts: 459 lines of code packages/jest-environment/src/index.ts:1 — packages/jest-environment/src/index.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-snapshot/src/State.ts · ×1
  • packages/jest-snapshot/src/State.ts: 456 lines of code packages/jest-snapshot/src/State.ts:1 — packages/jest-snapshot/src/State.ts has 456 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-reporters/src/GitHubActionsReporter.ts · ×1
  • packages/jest-reporters/src/GitHubActionsReporter.ts: 431 lines of code packages/jest-reporters/src/GitHubActionsReporter.ts:1 — packages/jest-reporters/src/GitHubActionsReporter.ts has 431 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-runtime/src/internals/JestGlobals.ts · ×1
  • packages/jest-runtime/src/internals/JestGlobals.ts: 428 lines of code packages/jest-runtime/src/internals/JestGlobals.ts:1 — packages/jest-runtime/src/internals/JestGlobals.ts has 428 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/expect/src/index.ts · ×1
  • packages/expect/src/index.ts: 418 lines of code packages/expect/src/index.ts:1 — packages/expect/src/index.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-core/src/runJest.ts · ×1
  • packages/jest-core/src/runJest.ts: 404 lines of code packages/jest-core/src/runJest.ts:1 — packages/jest-core/src/runJest.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/jest-snapshot/src/utils.ts · ×1
  • packages/jest-snapshot/src/utils.ts: 401 lines of code packages/jest-snapshot/src/utils.ts:1 — packages/jest-snapshot/src/utils.ts has 401 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded e2e/native-esm/__tests__/native-esm-mocks.test.js:18 — This repository declares test tooling, and the ✓ above records that declaration — but e2e/native-esm/__tests__/native-esm-mocks.test.js and 11 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.
R7 · Dead Code · Dead file (~219 LoC) · ×1
  • Dead file (~219 LoC) packages/pretty-format/__benchmarks__/test.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~191 LoC) · ×1
  • Dead file (~191 LoC) packages/jest-worker/__benchmarks__/test.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~190 LoC) · ×1
  • Dead file (~190 LoC) packages/jest-runtime/__benchmarks__/test.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~164 LoC) · ×1
  • Dead file (~164 LoC) packages/jest-haste-map/__benchmarks__/test.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~58 LoC) · ×1
  • Dead file (~58 LoC) scripts/requireChangelog.mjs — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~21 LoC) · ×1
  • Dead file (~21 LoC) packages/jest-worker/__benchmarks__/workers/pi.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/jest-worker/__benchmarks__/workers/jest_worker.js, packages/jest-worker/__benchmarks__/workers/worker_farm.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~19 LoC) · ×1
  • Dead file (~19 LoC) packages/jest-worker/__benchmarks__/workers/worker_farm.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/jest-worker/__benchmarks__/test.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R7 · Dead Code · Dead file (~18 LoC) · ×1
  • Dead file (~18 LoC) packages/jest-worker/__benchmarks__/workers/jest_worker.js — no import path from any entry point (403 application, 92 tooling, 1765 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/jest-worker/__benchmarks__/test.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
R8 · Dependency Hygiene · Unused dependency '@lerna-lite/exec' · ×1
  • Unused dependency '@lerna-lite/exec' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'resolve' · ×1
  • Unused dependency 'resolve' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@babel-8/core' · ×1
  • Unused dependency '@babel-8/core' — Declared in packages/babel-plugin-jest-hoist/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.
X13 · Undrained process stream · Redirected process stream is never drained (deadlock) · ×1
  • Redirected process stream is never drained (deadlock) packages/jest-haste-map/src/crawlers/node.ts:127 — `spawn` pipes `stderr` here — it is given no `stdio` option, or `'pipe'` — but nothing in this scope ever reads `child.stderr`, while `child.stdout` is read and the child's end is awaited. Node holds an unread pipe's output only up to its buffer: once the child writes more than that to stderr (measured on Linux: about 128 KB — the 64 KB pipe plus Node's 64 KB read-ahead — and less elsewhere), the child blocks on the write, never exits, and the `close`/`exit` this code waits for never fires. Nothing fails loudly: the promise never settles, the request never returns, and the stuck child holds its resources until something kills it. Consume both streams (`child.stderr.on('data', …)`, or `child.stderr.resume()` to discard it), or stop piping the one you do not want — `stdio: ['pipe', 'pipe', 'inherit']` or `'ignore'` in that slot.
Minor — 256 finding(s)
D10 · Test Quality · No direct assertions · ×52
  • No direct assertions: fails with error without proper message e2e/stack-trace/__tests__/stackTraceWithoutMessage.test.js:9 — No conventional assertion call was detected, and 4 of 5 tests in `e2e/stack-trace` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: fails e2e/stack-trace/__tests__/testError.test.js:10 — No conventional assertion call was detected, and 4 of 5 tests in `e2e/stack-trace` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: fails strings e2e/stack-trace/__tests__/testError.test.js:14 — No conventional assertion call was detected, and 4 of 5 tests in `e2e/stack-trace` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: tests e2e/stack-trace/__tests__/testError.test.js:19 — No conventional assertion call was detected, and 4 of 5 tests in `e2e/stack-trace` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo e2e/promise-async-handling/__tests__/unhandledRejectionAfterAll.test.js:18 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo #1 e2e/promise-async-handling/__tests__/unhandledRejectionAfterEach.test.js:18 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo #2 e2e/promise-async-handling/__tests__/unhandledRejectionAfterEach.test.js:20 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo e2e/promise-async-handling/__tests__/unhandledRejectionAggregate.test.js:26 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo e2e/promise-async-handling/__tests__/unhandledRejectionBeforeAll.test.js:18 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo #1 e2e/promise-async-handling/__tests__/unhandledRejectionBeforeEach.test.js:18 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo #2 e2e/promise-async-handling/__tests__/unhandledRejectionBeforeEach.test.js:20 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: w/o event loop turn after rejection e2e/promise-async-handling/__tests__/unhandledRejectionTest.test.js:12 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: w/ event loop turn after rejection in async function e2e/promise-async-handling/__tests__/unhandledRejectionTest.test.js:16 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: w/ event loop turn after rejection in sync function e2e/promise-async-handling/__tests__/unhandledRejectionTest.test.js:22 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: foo e2e/promise-async-handling/__tests__/unhandledRejectionWithCause.test.js:36 — No conventional assertion call was detected, and 11 of 15 tests in `e2e/promise-async-handling` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: #${t} e2e/jasmine-async/__tests__/concurrent-many.test.js:14 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: Good Test e2e/jasmine-async/__tests__/concurrent-parallel-failure.test.js:10 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: one e2e/jasmine-async/__tests__/concurrent.test.js:18 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: three e2e/jasmine-async/__tests__/concurrent.test.js:26 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: concurrent test fails e2e/jasmine-async/__tests__/concurrent.test.js:30 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: concurrent test gets skipped e2e/jasmine-async/__tests__/concurrentWithinDescribe.test.js:11 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: concurrent test fails e2e/jasmine-async/__tests__/concurrentWithinDescribe.test.js:15 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: skips a test inside a promise e2e/jasmine-async/__tests__/pendingInPromise.test.js:10 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: fails e2e/jasmine-async/__tests__/promiseBeforeAll.test.js:32 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: fails e2e/jasmine-async/__tests__/promiseBeforeAll.test.js:41 — No conventional assertion call was detected, and 27 of 45 tests in `e2e/jasmine-async` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • + 27 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×45
  • Orphaned file packages/jest-worker/src/workers/ChildProcessWorker.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-matcher-utils/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/expect/src/toThrowMatchers.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-snapshot/src/printSnapshot.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-jasmine2/src/jasmine/Spec.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-diff/src/joinAlignedDiffs.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-circus/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-reporters/src/SummaryReporter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-diff/src/getAlignedDiffs.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/expect-utils/src/jasmineUtils.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-jasmine2/src/jasmine/spyRegistry.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-snapshot-utils/src/utils.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-jasmine2/src/jasmine/Suite.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-diff/src/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-diff/src/diffLines.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/pretty-format/src/plugins/Immutable.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-config/src/Descriptions.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/pretty-format/src/collections.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-jasmine2/src/jasmine/jasmineLight.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-core/src/FailedTestsInteractiveMode.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-matcher-utils/src/deepCyclicCopyReplaceable.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/diff-sequences/__benchmarks__/test.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-worker/src/PriorityQueue.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/jest-worker/__benchmarks__/test.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/expect/src/print.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 20 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×37
  • Disabled test e2e/Utils.ts:348 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/Utils.ts:363 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/Utils.ts:381 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/__tests__/selectProjects.test.ts:190 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/__tests__/selectProjects.test.ts:233 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/before-all-skipped/__tests__/beforeAllFiltered.test.js:11 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/before-all-skipped/__tests__/beforeAllFiltered.test.js:54 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/collect-tests/__tests__/kitchenSink.test.js:42 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/collect-tests/__tests__/kitchenSink.test.js:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/collect-tests/__tests__/kitchenSink.test.js:51 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/custom-reporters/__tests__/skip.test.js:12 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/each/__tests__/eachSkip.test.js:15 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/each/__tests__/eachSkip.test.js:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/each/__tests__/eachSkip.test.js:41 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/empty-describe-with-hooks/__tests__/hookInDescribeWithSkippedTest.test.js:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/jasmine-async/__tests__/promiseIt.test.js:80 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/jasmine-async/__tests__/promiseXit.test.js:11 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/json-reporter/__tests__/sum.test.js:26 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/location-in-results/__tests__/test.js:14 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/location-in-results/__tests__/test.js:32 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/test-failing/__tests__/statuses.test.js:16 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/test-failing/__tests__/statuses.test.js:38 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/test-failing/__tests__/statuses.test.js:42 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/test-failing/__tests__/worksWithSkipMode.test.js:9 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test e2e/test-failing/__tests__/worksWithSkipMode.test.js:13 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 12 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×36
  • Mock-dominated test: can send multiple messages to parent packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:261 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: creates error instances for known errors packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:298 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: when out of memory occurs the worker is killed and exits packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:436 — This test sets up 3 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 7 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should check for memory limits and not restart if under percentage limit packages/jest-worker/src/workers/__tests__/ChildProcessWorker.test.ts:535 — This test sets up 4 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 9 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: can send multiple messages to parent packages/jest-worker/src/workers/__tests__/NodeThreadsWorker.test.ts:254 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: creates error instances for known errors packages/jest-worker/src/workers/__tests__/NodeThreadsWorker.test.ts:292 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calls handler on change value packages/jest-watcher/src/lib/__tests__/prompt.test.ts:12 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calls handler on success prompt packages/jest-watcher/src/lib/__tests__/prompt.test.ts:36 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calls handler on cancel prompt packages/jest-watcher/src/lib/__tests__/prompt.test.ts:51 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: clears the line when CONTROL_U is pressed packages/jest-watcher/src/lib/__tests__/prompt.test.ts:66 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: clear() drops the cache so subsequent calls re-parse packages/jest-runtime/src/internals/__tests__/CjsExportsCache.test.ts:238 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: uses manual mock path when not currently executing it packages/jest-runtime/src/internals/__tests__/CjsLoader.test.ts:125 — This test sets up 12 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: skips manual mock when currently executing it (recursion guard) packages/jest-runtime/src/internals/__tests__/CjsLoader.test.ts:157 — This test sets up 10 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: shares cache between core specifier and its `node:`-prefixed form packages/jest-runtime/src/internals/__tests__/Resolution.test.ts:419 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: should mock constructor packages/jest-mock/src/__tests__/index.test.ts:1069 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: sets an implementation which is available within the callback packages/jest-mock/src/__tests__/index.test.ts:1115 — This test sets up 3 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: runs every function in the queue. packages/jest-jasmine2/src/__tests__/queueRunner.test.ts:12 — This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: exposes `fail` to `next`. packages/jest-jasmine2/src/__tests__/queueRunner.test.ts:29 — This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: passes errors to `onException`. packages/jest-jasmine2/src/__tests__/queueRunner.test.ts:49 — This test sets up 4 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calls `fail` with arguments packages/jest-jasmine2/src/__tests__/queueRunner.test.ts:103 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: calls `fail` when done(error) is invoked packages/jest-jasmine2/src/__tests__/queueRunner.test.ts:119 — This test sets up 4 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: re-subscribes when the subscribe callback receives an error packages/jest-haste-map/src/watchers/__tests__/ParcelWatcher.test.ts:187 — This test sets up 4 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: close() awaits every watcher packages/jest-haste-map/src/watchers/__tests__/index.test.ts:108 — This test sets up 4 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: reports errors emitted after ready via onError instead of crashing packages/jest-haste-map/src/watchers/__tests__/index.test.ts:178 — This test sets up 3 test doubles (for example `jest.fn`) against 2 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: executes callback with native timers packages/jest-fake-timers/src/__tests__/legacyFakeTimers.test.ts:1126 — This test sets up 4 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • + 11 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×20
  • Duplicated predicate packages/jest-environment-jsdom-abstract/src/index.ts:145 — `Array.isArray(customExportConditions) && customExportConditions.every(isString)` appears character-identically in 2 files — packages/jest-environment-jsdom-abstract/src/index.ts, packages/jest-environment-node/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-circus/src/formatNodeAssertErrors.ts:79 — `assertOperatorsMap[operator] || operator` appears character-identically in 2 files — packages/jest-circus/src/formatNodeAssertErrors.ts, packages/jest-jasmine2/src/assertionErrorMessage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts:67 — `config.fakeTimers.enableGlobally && config.fakeTimers.legacyFakeTimers` appears character-identically in 2 files — packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapter.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-reporters/src/CoverageWorker.ts:55 — `context.changedFiles && new Set(context.changedFiles)` appears character-identically in 2 files — packages/jest-reporters/src/CoverageWorker.ts, packages/jest-runner/src/testWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-reporters/src/CoverageWorker.ts:56 — `context.sourcesRelatedToTestsInChangedFiles && new Set(context.sourcesRelatedToTestsInChangedFiles)` appears character-identically in 2 files — packages/jest-reporters/src/CoverageWorker.ts, packages/jest-runner/src/testWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/ChildProcessWorker.ts:274 — `error != null && typeof error === 'object'` appears character-identically in 2 files — packages/jest-worker/src/workers/ChildProcessWorker.ts, packages/jest-worker/src/workers/NodeThreadsWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-resolve/src/resolver.ts:1160 — `error.code === 'ERR_REQUIRE_ESM' || error.code === 'ERR_REQUIRE_ASYNC_MODULE'` appears character-identically in 2 files — packages/jest-resolve/src/resolver.ts, packages/jest-util/src/requireOrImportModule.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/processChild.ts:150 — `error.constructor && error.constructor.name` appears character-identically in 2 files — packages/jest-worker/src/workers/processChild.ts, packages/jest-worker/src/workers/threadChild.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/ChildProcessWorker.ts:361 — `exitCode !== 0 && this.state === WorkerStates.OUT_OF_MEMORY` appears character-identically in 2 files — packages/jest-worker/src/workers/ChildProcessWorker.ts, packages/jest-worker/src/workers/NodeThreadsWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/expect/src/spyMatchers.ts:292 — `expected instanceof Error && received instanceof Error` appears character-identically in 2 files — packages/expect/src/spyMatchers.ts, packages/jest-matcher-utils/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/expect/src/spyMatchers.ts:285 — `expectedType === 'date' || expectedType === 'function' || expectedType === 'regexp'` appears character-identically in 2 files — packages/expect/src/spyMatchers.ts, packages/jest-matcher-utils/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-core/src/cli/index.ts:161 — `globalConfig.watch || globalConfig.watchAll` appears character-identically in 2 files — packages/jest-core/src/cli/index.ts, packages/jest-reporters/src/SummaryReporter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/messageParent.ts:35 — `isError(error) && !error.message.includes('.send is not a function')` appears character-identically in 2 files — packages/jest-worker/src/workers/messageParent.ts, packages/jest-worker/src/workers/processChild.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:453 — `isError(error) || error instanceof Error` appears character-identically in 2 files — REDACTED, packages/jest-snapshot/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/ChildProcessWorker.ts:341 — `limit && this._childIdleMemoryUsage && this._childIdleMemoryUsage > limit` appears character-identically in 2 files — packages/jest-worker/src/workers/ChildProcessWorker.ts, packages/jest-worker/src/workers/NodeThreadsWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-changed-files/src/hg.ts:23 — `options.changedSince != null && options.changedSince.length > 0` appears character-identically in 2 files — packages/jest-changed-files/src/hg.ts, packages/jest-changed-files/src/sl.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/expect/src/spyMatchers.ts:304 — `receivedType === 'object' && typeof (received as any).asymmetricMatch === 'function'` appears character-identically in 3 files — packages/expect/src/spyMatchers.ts, packages/jest-matcher-utils/src/index.ts, packages/jest-snapshot/src/printSnapshot.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/jest-worker/src/workers/ChildProcessWorker.ts:104 — `this.state === WorkerStates.OUT_OF_MEMORY || this.state === WorkerStates.SHUTTING_DOWN || this.state === WorkerStates.SHUT_DOWN` appears character-identically in 2 files — packages/jest-worker/src/workers/ChildProcessWorker.ts, packages/jest-worker/src/workers/NodeThreadsWorker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/pretty-format/src/plugins/AsymmetricMatcher.ts:12 — `typeof Symbol === 'function' && Symbol.for` appears character-identically in 2 files — packages/pretty-format/src/plugins/AsymmetricMatcher.ts, packages/pretty-format/src/plugins/ReactTestComponent.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:901 — `typeof received !== 'object' || received === null` appears character-identically in 2 files — REDACTED, packages/jest-snapshot/src/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated (npm) · ×11
  • Outdated (npm): @types/jsdom packages/jest-environment-jsdom-abstract/package.json:31 — @types/jsdom is pinned at 21.1.7; registry.npmjs.org publishes 30.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ansi-escapes packages/jest-core/package.json:24 — ansi-escapes is pinned at 4.3.2; registry.npmjs.org publishes 7.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): camelcase package.json:33 — camelcase is pinned at 6.3.0; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): discord.js e2e/native-esm/package.json:8 — discord.js is pinned at 11.5.1; registry.npmjs.org publishes 14.27.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): execa package.json:45 — execa is pinned at 5.1.1; registry.npmjs.org publishes 10.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): jsdom e2e/browser-resolver/package.json:4 — jsdom is pinned at 26.1.0; registry.npmjs.org publishes 30.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): p-limit package.json:66 — p-limit is pinned at 3.1.0; registry.npmjs.org publishes 7.3.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): parse-json packages/jest-config/package.json:57 — parse-json is pinned at 5.2.0; registry.npmjs.org publishes 8.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): string-length packages/jest-reporters/package.json:38 — string-length is pinned at 4.0.2; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): supports-color packages/jest-worker/package.json:26 — supports-color is pinned at 8.1.1; registry.npmjs.org publishes 11.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): write-file-atomic packages/jest-transform/package.json:35 — write-file-atomic is pinned at 5.0.1; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D12 · Dependency Hygiene · Deprecated · ×10
  • Deprecated: glob e2e/coverage-transform-instrumented/REDACTED:1517 — glob 10.5.0 is resolved in e2e/coverage-transform-instrumented/REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @angular/platform-browser-dynamic REDACTED:307 — @angular/platform-browser-dynamic 21.2.23 is resolved in REDACTED and is marked deprecated by its publisher: "@angular/platform-browser-dynamic is deprecated. Use `@angular/platform-browser` instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:13068 — glob 11.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:13095 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:14004 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:20726 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: uuid REDACTED:23094 — uuid 8.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: whatwg-encoding REDACTED:23459 — whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: prebuild-install e2e/native-esm/REDACTED:599 — prebuild-install 7.1.3 is resolved in e2e/native-esm/REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: snekfetch e2e/require-missing-ext/REDACTED:73 — snekfetch 3.6.4 is resolved in e2e/require-missing-ext/REDACTED and is marked deprecated by its publisher: "use node-fetch instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
AX6 · Interface segregation · Fat interface · ×3
  • Fat interface: Matchers (33 required operations) packages/expect/src/types.ts:146 — `Matchers` declares 33 required operations: `_unusedT`, `toBe`, `toBeCloseTo`, `toBeDefined`, `toBeFalsy`, `toBeGreaterThan`, `toBeGreaterThanOrEqual`, `toBeInstanceOf`, `toBeLessThan`, `toBeLessThanOrEqual`, `toBeNaN`, `toBeNull`, `toBeTruthy`, `toBeUndefined`, `toContain`, `toContainEqual`, `toEqual`, `toHaveBeenCalled`, `toHaveBeenCalledTimes`, `toHaveBeenCalledWith`, `toHaveBeenNthCalledWith`, `toHaveBeenLastCalledWith`, `toHaveLastReturnedWith`, `toHaveLength`, `toHaveNthReturnedWith`, `toHaveProperty`, `toHaveReturned`, `toHaveReturnedTimes`, `toHaveReturnedWith`, `toMatch`, `toMatchObject`, `toStrictEqual`, `toThrow`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Jest (45 required operations) packages/jest-environment/src/index.ts:69 — `Jest` declares 45 required operations: `advanceTimersByTime`, `advanceTimersByTimeAsync`, `advanceTimersToNextFrame`, `advanceTimersToNextTimer`, `advanceTimersToNextTimerAsync`, `autoMockOff`, `autoMockOn`, `clearAllMocks`, `clearAllTimers`, `createMockFromModule`, `deepUnmock`, `disableAutomock`, `doMock`, `dontMock`, `enableAutomock`, `getRealSystemTime`, `getSeed`, `getTimerCount`, `isEnvironmentTornDown`, `isolateModules`, `isolateModulesAsync`, `mock`, `unstable_mockModule`, `now`, `onGenerateMock`, `requireActual`, `requireMock`, `resetAllMocks`, `resetModules`, `restoreAllMocks`, `retryTimes`, `runAllImmediates`, `runAllTicks`, `runAllTimers`, `runAllTimersAsync`, `runOnlyPendingTimers`, `runOnlyPendingTimersAsync`, `setMock`, `setSystemTime`, `setTimeout`, and 5 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MockInstance (18 required operations) packages/jest-mock/src/index.ts:178 — `MockInstance` declares 18 required operations: `getMockImplementation`, `getMockName`, `mockClear`, `mockReset`, `mockRestore`, `mockImplementation`, `mockImplementationOnce`, `withImplementation`, `withImplementation`, `mockName`, `mockReturnThis`, `mockReturnValue`, `mockReturnValueOnce`, `mockResolvedValue`, `mockResolvedValueOnce`, `mockRejectedValue`, `mockRejectedValueOnce`, `whenCalledWith`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 18 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×3
  • Hand-rolled JSON/XML parsing via regex REDACTED:61 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:62 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex REDACTED:63 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: e2e/custom-esm-test-sequencer e2e/custom-esm-test-sequencer/a.test.js:7 — No conventional assertion call was detected in 5 of 5 tests in `e2e/custom-esm-test-sequencer` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: e2e/custom-test-sequencer e2e/custom-test-sequencer/a.test.js:7 — No conventional assertion call was detected in 5 of 5 tests in `e2e/custom-test-sequencer` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch packages/jest-haste-map/src/lib/watchmanSockname.ts:142 — `currentUserKey` swallows every exception into `return 'default'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/pretty-format/src/plugins/DOMElement.ts:28 — `testHasAttribute` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 19 significant file(s) lose their only recent owner: REDACTED, packages/jest-fake-timers/src/legacyFakeTimers.ts, REDACTED, packages/jest-haste-map/src/lib/FileProcessor.ts, packages/jest-haste-map/src/crawlers/watchman.ts, packages/jest-source-map/src/SourceMapCache.ts, packages/jest-runtime/src/internals/ModuleRegistries.ts, packages/jest-runtime/src/internals/Resolution.ts (+11 more). Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (20 single-owned of 206 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 206 of the 439 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/jest-circus/src/eventHandler.ts.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 45 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: packages/jest-worker/src/workers/ChildProcessWorker.ts, packages/jest-matcher-utils/src/index.ts, packages/expect/src/toThrowMatchers.ts, packages/jest-snapshot/src/printSnapshot.ts, packages/jest-jasmine2/src/jasmine/Spec.ts, packages/jest-diff/src/joinAlignedDiffs.ts, packages/jest-circus/src/index.ts, packages/jest-reporters/src/SummaryReporter.ts (and 37 more) (48 orphaned of 206 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 206 of the 439 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body packages/jest-jasmine2/src/jasmine/JsApiReporter.ts:38 — `start` has an empty body — confirm it's an intentional no-op and not an unfinished method.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift docs/ECMAScriptModules.md:67 — docs/ECMAScriptModules.md names Node.js 24, but the repository declares engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`, engines `^18.14.0 || ^20.0.0 || ^22.0.0 || >=24.0.0`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 23868 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code · Unused export 'TestPathCasesWithPathPattern' · ×1
  • Unused export 'TestPathCasesWithPathPattern' packages/jest-core/src/types.ts:33 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'WatcherEventType' · ×1
  • Unused export 'WatcherEventType' packages/jest-haste-map/src/watchers/types.ts:19 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'runTest' · ×1
  • Unused export 'runTest' packages/jest-worker/__typetests__/testWorker.ts:8 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'runTestAsync' · ×1
  • Unused export 'runTestAsync' packages/jest-worker/__typetests__/testWorker.ts:9 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'doSomething' · ×1
  • Unused export 'doSomething' packages/jest-worker/__typetests__/testWorker.ts:11 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'doSomethingAsync' · ×1
  • Unused export 'doSomethingAsync' packages/jest-worker/__typetests__/testWorker.ts:12 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'isResult' · ×1
  • Unused export 'isResult' packages/jest-worker/__typetests__/testWorker.ts:17 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'end' · ×1
  • Unused export 'end' packages/jest-worker/__typetests__/testWorker.ts:21 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'getStderr' · ×1
  • Unused export 'getStderr' packages/jest-worker/__typetests__/testWorker.ts:22 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'getStdout' · ×1
  • Unused export 'getStdout' packages/jest-worker/__typetests__/testWorker.ts:25 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'setup' · ×1
  • Unused export 'setup' packages/jest-worker/__typetests__/testWorker.ts:28 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'teardown' · ×1
  • Unused export 'teardown' packages/jest-worker/__typetests__/testWorker.ts:29 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'NotUsedButTakesUpLines' · ×1
  • Unused module-local declaration 'NotUsedButTakesUpLines' e2e/stack-trace-source-maps-with-coverage/lib.ts:8 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'testResult' · ×1
  • Unused module-local declaration 'testResult' packages/jest-reporters/src/__tests__/getResultHeader.test.js:14 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'CustomCallbackRunner' · ×1
  • Unused module-local declaration 'CustomCallbackRunner' packages/jest-runner/__typetests__/jest-runner.test.ts:54 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'CustomEmittingRunner' · ×1
  • Unused module-local declaration 'CustomEmittingRunner' packages/jest-runner/__typetests__/jest-runner.test.ts:107 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'snapshotResolver' · ×1
  • Unused module-local declaration 'snapshotResolver' packages/jest-snapshot/__typetests__/SnapshotResolver.test.ts:13 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'getResult' · ×1
  • Unused module-local declaration 'getResult' packages/jest-worker/__typetests__/testWorker.ts:14 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene · Type-only dependency '@jridgewell/trace-mapping' in production deps · ×1
  • Type-only dependency '@jridgewell/trace-mapping' in production deps packages/jest-reporters/src/CoverageReporter.ts:10 — Every import is type-only — move it to devDependencies.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected netlify.toml:1 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 124/129 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~1.8 `!` null assertions per 1k TypeScript source lines — 111 assertion(s) across the 60175 source line(s) of the 349 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/jest-runtime/src/internals/EsmLoader.ts (11), packages/jest-worker/src/workers/threadChild.ts (9), packages/jest-fake-timers/src/legacyFakeTimers.ts (7). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 96 finding(s)
D10 · Test Quality · Skipped (documented) · ×51
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:693 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:712 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:730 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:749 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:817 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/pretty-format/src/__tests__/prettyFormat.test.ts:835 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:219 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:220 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:348 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:350 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:351 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:352 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:353 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:354 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:356 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-types/__typetests__/globals.test.ts:357 — Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
  • Skipped (documented): (unnamed test) packages/jest-snapshot/src/__tests__/InlineSnapshots.test.ts:128 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): a: b packages/jest-snapshot/src/__tests__/State.test.ts:273 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): a packages/jest-snapshot/src/__tests__/State.test.ts:274 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-snapshot/src/__tests__/printSnapshot.test.ts:138 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): test1 packages/jest-jasmine2/src/__tests__/itTestError.test.ts:13 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-jasmine2/src/__tests__/itTestError.test.ts:21 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): test4 packages/jest-jasmine2/src/__tests__/itTestError.test.ts:37 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-jasmine2/src/__tests__/itTestError.test.ts:45 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/jest-jasmine2/src/__tests__/todoError.test.ts:13 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
  • + 26 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated (npm) · ×45
  • Outdated (npm): @angular/common — @angular/common is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @angular/compiler — @angular/compiler is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @angular/compiler-cli — @angular/compiler-cli is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @angular/core — @angular/core is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @angular/platform-browser — @angular/platform-browser is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @angular/platform-browser-dynamic — @angular/platform-browser-dynamic is pinned at 21.2.23; registry.npmjs.org publishes 22.2.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/code-frame — @babel/code-frame is pinned at 7.29.7; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/core — @babel/core is pinned at 7.29.7; registry.npmjs.org publishes 8.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/generator — @babel/generator is pinned at 7.29.8; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-syntax-jsx — @babel/plugin-syntax-jsx is pinned at 7.29.7; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-syntax-typescript — @babel/plugin-syntax-typescript is pinned at 7.29.7; registry.npmjs.org publishes 8.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-transform-explicit-resource-management — @babel/plugin-transform-explicit-resource-management is pinned at 7.29.7; registry.npmjs.org publishes 8.0.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-transform-regenerator — @babel/plugin-transform-regenerator is pinned at 7.29.8; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-transform-runtime — @babel/plugin-transform-runtime is pinned at 7.29.7; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/preset-env — @babel/preset-env is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/preset-flow — @babel/preset-flow is pinned at 7.29.7; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/preset-react — @babel/preset-react is pinned at 7.29.7; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/preset-typescript — @babel/preset-typescript is pinned at 7.29.7; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/types — @babel/types is pinned at 7.29.8; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @bcoe/v8-coverage — @bcoe/v8-coverage is pinned at 0.2.3; registry.npmjs.org publishes 1.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @react-native/babel-preset — @react-native/babel-preset is pinned at 0.86.3; registry.npmjs.org publishes 0.88.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @types/node — @types/node is pinned at 26.5.1; registry.npmjs.org publishes 26.6.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ansi-regex — ansi-regex is pinned at 5.0.1; registry.npmjs.org publishes 6.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): ansi-styles — ansi-styles is pinned at 5.2.0; registry.npmjs.org publishes 7.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): callsites — callsites is pinned at 3.1.0; registry.npmjs.org publishes 4.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • + 20 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-561f321cd8834131a21553244cdca39c/history.json --exit-code 0 --source .79artifacts/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-561f321cd8834131a21553244cdca39c/tree.json --exit-code 0 --source .4artifacts/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 --exclude .yarn/releases .16artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update17artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `packages/babel-jest/src/index.ts`, `packages/jest-runtime/src/internals/ModuleRegistries.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update2artifacts/raw/trivy-fs.json

Run 01a178c5-9af1-7681-88ea-60d7ae34a9b0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 98 · Warnings: 843 · Recommendations: 256 · Info: 96 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 15:12 UTC.

Downloadable artifacts

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

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