Public report of parcel-bundler/parcel, published 24 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, 24 October 2026, 16:08 UTC · Survey ID cd_bb9cd77dd9e24b3eae22340bc7f916ba

parcel-bundler/parcel

Measured 24 October 2026, 15:41 UTC, at code version 5948485

Regression: 1 dimension fell since the last survey Code coverage: not measuredTest reliability: 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 (CouldNotMeasureNoCollector).

Test reliability is not measured: A declared JavaScript/TypeScript suite contains no test files.

CAI score 44out of 100 At risk Down 4 since the last survey

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

Performance 73 Strong Architecture 68 Adequate Accessibility 64 Adequate Maturity 62 Adequate Production Readiness 50 Adequate Code Health 42 Weak Security and Compliance 37 Weak

A large codebase: 100,474 lines of product code in 153 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Security and Compliance, 37

Findings by how serious they are

175 critical 1103 serious 451 minor

4 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
24 October 2026, 15:41 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 ▸

80of 84 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
1672of 1729 findings point to an exact file and line, so you can open each one in the code. The other 57 concern the repository as a whole, such as missing documentation.
84dimensions across 7 lenses, read from 100,474 lines of product code in 153 projects.
Chapters

Executive summary

parcel-bundler/parcel scores 44 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Security and Compliance, which scores 37 and is rated Weak. Its Static Analysis (SAST) dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life and to resolve the 1 Yanked release finding(s) in Dependency Hygiene, and if Security and Compliance rose to 70, the score would rise from 44 to about 51.

175 findings are critical: 78 in Static Analysis (SAST), 67 in Dependency Vulnerabilities, 12 in Dependency Hygiene, five in Circular Imports, five in Test Quality, four in Test Reliability, two in Page structure, one in Coupling and one in Project dependency cycles.

Watchdog couldn't measure Navigability, Structured logging and Runtime accessibility in this code, so those dimensions are left out of the score. The product code is 100,474 lines, which would take an estimated 1.0 person-years, around €140,000, to rebuild.

Code Health 42 Weak, capped by Cyclomatic Complexity, Cognitive Complexity and Type Safety Architecture 68 Adequate, capped by Circular Imports Maturity 62 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 50 Adequate, capped by Dependency Hygiene Security and Compliance 37 Weak, capped by Static Analysis (SAST), Dependency Vulnerabilities, Supply-chain Provenance & Signing and Platform End-of-Life Accessibility 64 Adequate Performance 73 Strong

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

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

If Security and Compliance rose from 37 to 70, the lowest score rated Strong, the score would rise from 44 to about 51.

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

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

  • Coupling · Circular dependency packages/core/cache/package.json
  • Test Quality · Skipped test: bundles in workers with other loaders packages/core/integration-tests/test/workers.js
  • Test Quality · Skipped test: should re-generate bundle tree when files change packages/core/integration-tests/test/watcher.js
  • Test Quality · Skipped test: should only re-package bundles that changed packages/core/integration-tests/test/watcher.js
  • Test Quality · Skipped test: should unload assets that are orphaned packages/core/integration-tests/test/watcher.js
  • Test Quality · Skipped test: should recompile all assets when a config file changes packages/core/integration-tests/test/watcher.js
  • Test Quality · Skipped test: should rebuild if the file behind a symlink changes packages/core/integration-tests/test/watcher.js
  • Test Quality · Skipped test: should detect the version of SVGO to use packages/core/integration-tests/test/svg.js
  • Test Quality · Skipped test: should detect the version of SVGO to use packages/core/integration-tests/test/svg-react.js
  • Test Quality · Skipped test: should load existing sourcemaps for CSS files packages/core/integration-tests/test/sourcemaps.js
  • Test Quality · Skipped test: throws a meaningful error on undefined exports packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: supports tree shaking statically analyzable dynamic import: destructued await assignment packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: throws an error for missing exports for dynamic import: destructured await assignment packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: doesn't support require.resolve calls for included assets packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: supports require.resolve calls for excluded modules packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: does not include prelude if child bundles are isolated packages/core/integration-tests/test/scope-hoisting.js
  • Test Quality · Skipped test: Should be able to process an html file with plugins without any params for plugin packages/core/integration-tests/test/posthtml.js
  • Test Quality · Skipped test: should add dependencies referenced by posthtml-include packages/core/integration-tests/test/posthtml.js
  • Test Quality · Skipped test: should add dependencies referenced by plugins packages/core/integration-tests/test/posthtml.js
  • Test Quality · Skipped test: updates config for custom namespace packages/core/integration-tests/test/parcel-link.js
  • Test Quality · Skipped test: updates config for custom namespace packages/core/integration-tests/test/parcel-link.js
  • Test Quality · Skipped test: should support commonjs output from esmodule input (re-export namespace as) packages/core/integration-tests/test/output-formats.js
  • Test Quality · Skipped test: should support esmodule output (re-export namespace as) packages/core/integration-tests/test/output-formats.js
  • Test Quality · Skipped test: should support dynamic imports with chained reexports packages/core/integration-tests/test/output-formats.js
  • Test Quality · Skipped test: doesn't support require.resolve calls for excluded assets without commonjs packages/core/integration-tests/test/output-formats.js
  • Test Quality · Skipped test: should support split bundles between main script and workers packages/core/integration-tests/test/output-formats.js
  • Test Quality · Skipped test: should not bundle node_modules on --target=electron packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should bundle node_modules on --target=electron and --bundle-node-modules packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should load dynamic bundle when entry is in a subdirectory packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: Should not run parcel over external modules packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should support adding implicit dependencies packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not resolve the browser field for --target=node packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should resolve advanced browser resolution packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not resolve advanced browser resolution with --target=node packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should resolve the module field before main if scope-hoisting is enabled packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should resolve the module field before main if scope-hoisting is enabled packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should minify YAML for production packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not autoinstall if resolve failed on installed module packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not autoinstall if resolve failed on aliased module packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should expose variable with --browser-global packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should set `define` to undefined so AMD checks in UMD modules do not pass packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not dedupe imports with different contents packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not dedupe imports with same content but different absolute dependency paths packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should dedupe imports with same content and same dependency paths packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should not dedupe assets that exist in more than one bundle packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should support importing HTML from JS async packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should support importing HTML from JS async with --target=node packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should support importing HTML from JS sync packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should stub require.cache packages/core/integration-tests/test/javascript.js
  • Test Quality · Skipped test: should insert sibling JS bundles for CSS files in the HEAD packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should detect the version of SVGO to use packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should not minify default values inside HTML in production mode packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should support circular dependencies packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should support webmanifest packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should treat webmanifest as an entry module so it doesn't get content hashed packages/core/integration-tests/test/html.js
  • Test Quality · Skipped test: should inline a file with fs require assignment packages/core/integration-tests/test/fs.js
  • Test Quality · Skipped test: should inline a file with fs require assignment alias packages/core/integration-tests/test/fs.js
  • Test Quality · Skipped test: should inline a file with fs require destructure assignment packages/core/integration-tests/test/fs.js
  • Test Quality · Skipped test: create a new css bundle to maintain one css bundle per bundlegroup constraint packages/core/integration-tests/test/css.js
  • Test Quality · Skipped test: should not invalidate when package.json config keys don't change packages/core/integration-tests/test/cache.js
  • Test Quality · Skipped test: should auto install @babel/core v7 packages/core/integration-tests/test/babel.js
  • Test Quality · Skipped test: should auto install babel plugins packages/core/integration-tests/test/babel.js
  • Test Quality · Skipped test: should support compiling with babel using browserslist for different environments packages/core/integration-tests/test/babel.js
  • Test Quality · Skipped test: should compile node_modules with browserslist to app target packages/core/integration-tests/test/babel.js
  • Test Quality · Skipped test: Bi-directional call should return masters pid packages/core/workers/test/workerfarm.js
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Platform End-of-Life · End-of-life runtime: Node.js 10 packages/optimizers/esbuild/package.json
  • Platform End-of-Life · End-of-life runtime: Node.js 12 packages/runtimes/rsc/package.json
  • Platform End-of-Life · End-of-life runtime: Node.js 14 packages/optimizers/inline-requires/package.json
  • Exception handling · Swallowed exception (empty catch) packages/core/codeframe/src/codeframe.js
  • Exception handling · Swallowed exception (empty catch) packages/core/core/src/resolveOptions.js
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) packages/core/core/src/requests/WriteBundlesRequest.js
  • Exception handling · Swallowed exception (empty catch) packages/core/core/src/requests/DevDepRequest.js
  • Exception handling · Swallowed exception (empty catch) packages/core/core/src/requests/BundleGraphRequest.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/find.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/find.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/find.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/OverlayFS.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/OverlayFS.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/OverlayFS.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/NodeFS.js
  • Exception handling · Swallowed exception (caught, then discarded) packages/core/fs/src/NodeFS.js
  • Exception handling · Swallowed exception (empty catch) packages/core/fs/src/NodeFS.js
  • Exception handling · Swallowed exception (empty catch) packages/core/graph/src/shared-buffer.js
  • Exception handling · Swallowed exception (empty catch) packages/core/package-manager/src/installPackage.js
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) packages/core/utils/src/shared-buffer.js
  • Exception handling · Swallowed exception (empty catch) REDACTED

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

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

  • Coupling · Circular dependency
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (18 lines × 2 locations) packages/optimizers/html/src/HTMLOptimizer.js
  • Code Duplication · Duplicated block (18 lines × 2 locations) packages/transformers/html/src/HTMLTransformer.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/core/core/src/SymbolPropagation.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/core/fs/src/MemoryFS.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/core/utils/src/DefaultMap.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/core/utils/src/schema.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/core/core/src/public/Symbols.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/core/graph/src/shared-buffer.js
  • Code Duplication · Duplicated block (16 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/optimizers/html/src/HTMLOptimizer.js
  • Code Duplication · Duplicated block (16 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (16 lines × 3 locations) packages/packagers/js/src/dev-prelude.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/core/cache/src/LMDBCache.js
  • Code Duplication · Duplicated block (15 lines × 3 locations) packages/core/core/src/public/Bundle.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/core/fs/src/NodeFS.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/optimizers/css/src/CSSOptimizer.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/runtimes/js/src/helpers/browser/wasm-loader.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/transformers/typescript-types/src/wrappers.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/core/src/public/Symbols.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/core/src/requests/TargetRequest.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/fs/src/MemoryFS.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/fs/src/MemoryFS.js
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/core/fs/src/find.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/package-manager/src/getCurrentPackageManager.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/core/package-manager/src/promiseFromProcess.js
  • Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/core/utils/src/import-map.js
  • Code Duplication · Duplicated block (14 lines × 3 locations) packages/core/workers/src/process/ProcessWorker.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/dev/repl/src/index.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/packagers/svg/src/SVGPackager.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/reporters/cli/src/emoji.js
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/core/core/src/ParcelConfig.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/core/src/public/MutableBundleGraph.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/core/src/requests/AssetGraphRequest.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/core/src/requests/EntryRequest.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/core/workers/src/process/ProcessChild.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/packagers/react-static/src/ReactStaticPackager.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/packagers/react-static/src/ReactStaticPackager.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/transformers/toml/src/TOMLTransformer.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/core/core/src/SymbolPropagation.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/core/fs/src/MemoryFS.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/packagers/js/src/DevPackager.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/runtimes/js/src/helpers/node/html-loader.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/runtimes/rsc/src/RSCRuntime.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/transformers/react-refresh-wrap/src/helpers/helpers.js
  • Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/utils/create-parcel/templates/react-static/src/components/MDXLayout.tsx
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/utils/parcel-watcher-watchman-js/src/wrapper.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/core/core/src/requests/EntryRequest.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/core/fs/src/MemoryFS.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/core/package-manager/src/Yarn.js
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/core/workers/src/web/WebChild.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/optimizers/swc/src/SwcOptimizer.js
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/packagers/js/src/index.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/runtimes/js/src/helpers/browser/css-loader.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/core/graph/src/AdjacencyList.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/core/logger/src/Logger.js
  • Code Duplication · Duplicated block (10 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/dev/repl/src/parcel/ExtendedMemoryFS.js
  • Code Duplication · Duplicated block (10 lines × 3 locations) packages/dev/repl/src/parcel/ExtendedMemoryFS.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/dev/repl/src/utils/assets.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/reporters/dev-server-sw/src/HMRServer.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/reporters/dev-server/src/NodeRunner.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 3 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/packagers/js/src/DevPackager.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/utils/babel-plugin-transform-runtime/src/index.js
Rebuild cost: about €140,000 · Estimate
Cost to rebuild€46,000 to €230,000, for 768 to 2,437 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 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 100,474 lines of product code

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

Top priorities

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

1
Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4).
Raises the score by about 4 points · Low effort · Platform End-of-Life
2
Resolve the 1 Yanked release finding(s) in Dependency Hygiene.
Raises the score by about 2 points · Low effort · Dependency Hygiene
3
Resolve the 52 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (52).
Raises the score by about 3 points · Medium effort · Dependency Vulnerabilities

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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Security and Compliance, at 37 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 4 Platform End-of-Life findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.3 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 10% on every change. The history of the code shows how much it changes: about 4,730 lines over the last 90 days, which is about 19,183 lines a year. At that pace, the extra work comes to an estimated 2.1 to 12.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch @parcel/bundler-default bundler-default @parcel/diagnostic diagnostic @parcel/bundler-default->@parcel/diagnostic @parcel/plugin plugin @parcel/bundler-default->@parcel/plugin @parcel/rust rust @parcel/bundler-default->@parcel/rust @parcel/utils utils @parcel/bundler-default->@parcel/utils @parcel/cache cache @parcel/core core @parcel/fs fs @parcel/cache->@parcel/fs @parcel/logger logger @parcel/cache->@parcel/logger @parcel/cache->@parcel/utils @parcel/config-default config-default @parcel/config-default->@parcel/bundler-default @parcel/config-default->@parcel/core @parcel/optimizer-image optimizer-image @parcel/config-default->@parcel/optimizer-image @parcel/packager-js packager-js @parcel/config-default->@parcel/packager-js @parcel/transformer-js transformer-js @parcel/config-default->@parcel/transformer-js @parcel/config-repl config-repl @parcel/config-repl->@parcel/bundler-default @parcel/config-repl->@parcel/packager-js @parcel/config-repl->@parcel/transformer-js @parcel/config-webextension config-webextension @parcel/config-webextension->@parcel/config-default @parcel/config-webextension->@parcel/core @parcel/core->@parcel/cache @parcel/core->@parcel/diagnostic @parcel/core->@parcel/fs @parcel/core->@parcel/logger @parcel/package-manager package-manager @parcel/core->@parcel/package-manager @parcel/core->@parcel/plugin @parcel/core->@parcel/rust @parcel/types types @parcel/core->@parcel/types @parcel/core->@parcel/utils @parcel/workers workers @parcel/fs->@parcel/rust @parcel/fs->@parcel/utils @parcel/fs->@parcel/workers @parcel/logger->@parcel/diagnostic @parcel/node-resolver-core node-resolver-core @parcel/node-resolver-core->@parcel/diagnostic @parcel/node-resolver-core->@parcel/fs @parcel/node-resolver-core->@parcel/rust @parcel/node-resolver-core->@parcel/utils @parcel/optimizer-image->@parcel/core @parcel/optimizer-image->@parcel/diagnostic @parcel/optimizer-image->@parcel/plugin @parcel/optimizer-image->@parcel/rust @parcel/optimizer-image->@parcel/utils @parcel/optimizer-image->@parcel/workers @parcel/package-manager->@parcel/diagnostic @parcel/package-manager->@parcel/fs @parcel/package-manager->@parcel/logger @parcel/package-manager->@parcel/node-resolver-core @parcel/package-manager->@parcel/types @parcel/package-manager->@parcel/utils @parcel/package-manager->@parcel/workers @parcel/packager-js->@parcel/diagnostic @parcel/packager-js->@parcel/plugin @parcel/packager-js->@parcel/rust @parcel/packager-js->@parcel/types @parcel/packager-js->@parcel/utils @parcel/plugin->@parcel/types @parcel/transformer-js->@parcel/core @parcel/transformer-js->@parcel/diagnostic @parcel/transformer-js->@parcel/plugin @parcel/transformer-js->@parcel/rust @parcel/transformer-js->@parcel/utils @parcel/transformer-js->@parcel/workers @parcel/types->@parcel/workers @parcel/utils->@parcel/diagnostic @parcel/utils->@parcel/logger @parcel/utils->@parcel/rust @parcel/workers->@parcel/core @parcel/workers->@parcel/diagnostic @parcel/workers->@parcel/logger @parcel/workers->@parcel/utils parcel parcel parcel->@parcel/config-default parcel->@parcel/core parcel->@parcel/diagnostic parcel->@parcel/fs parcel->@parcel/logger parcel->@parcel/package-manager parcel->@parcel/utils __more__ +133 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.

683 modules, with 548 dependencies between them. 3 loops run through 14 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 643 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 packages.core.core.src.types2 packages.core.diagnostic.src.diagnostic3 packages.core.integration-tests.test.integration.formats.esm-bundle-import-reexport.i18n4 packages.core.types-internal.src.FileSystem5 packages.core.types-internal.src.PackageManager6 packages.core.workers.src.types7 parcel_core8 flow-typed.npm.@swc.core_v1_x_x9 flow-typed.npm.typescript_v3_3_x10 packages.core.types-internal.src11 parcel_core.diagnostic12 parcel_resolver.cache13 packages.core.core.src.BundleGraph14 packages.core.core.src.ParcelConfig15 packages.core.core.src.public.Asset16 packages.core.core.src.public.PluginOptions17 packages.core.logger.src.Logger18 packages.core.workers.src.WorkerFarm19 parcel_html20 parcel_js_swc_core.dependency_collector21 parcel_resolver22 packages.bundlers.default.src23 packages.core.core.src.PackagerRunner24 packages.core.core.src.RequestTracker25 packages.core.core.src.public.Bundle26 packages.core.core.src.requests.PathRequest27 packages.core.fs.src.MemoryFS28 parcel_js_swc_core29 parcel_resolver.specifier30 packages.core.core.src.Transformation31 packages.core.core.src.requests.AssetGraphRequest32 packages.core.core.src.requests.BundleGraphRequest33 packages.core.test-utils.src34 packages.core.utils.src35 packages.packagers.js.src.ScopeHoistingPackager36 packages.reporters.cli.src37 packages.reporters.dev-server.src.HMRServer38 parcel_dev_dep_resolver39 packages.core.core.src40 packages.core.core.src.requests
1 packages.core.core.src.types
2 packages.core.diagnostic.src.diagnostic
3 packages.core.integration-tests.test.integration.formats.esm-bundle-import-reexport.i18n
4 packages.core.types-internal.src.FileSystem
5 packages.core.types-internal.src.PackageManager
6 packages.core.workers.src.types
7 parcel_core
8 flow-typed.npm.@swc.core_v1_x_x1
9 flow-typed.npm.typescript_v3_3_x2
10 packages.core.types-internal.src4
11 parcel_core.diagnostic2
12 parcel_resolver.cache2
13 packages.core.core.src.BundleGraph11
14 packages.core.core.src.ParcelConfig41
15 packages.core.core.src.public.Asset23
16 packages.core.core.src.public.PluginOptions1111
17 packages.core.logger.src.Logger11
18 packages.core.workers.src.WorkerFarm1
19 parcel_html1
20 parcel_js_swc_core.dependency_collector122
21 parcel_resolver211
22 packages.bundlers.default.src321111
23 packages.core.core.src.PackagerRunner21111
24 packages.core.core.src.RequestTracker4211
25 packages.core.core.src.public.Bundle3123
26 packages.core.core.src.requests.PathRequest2111121
27 packages.core.fs.src.MemoryFS35111
28 parcel_js_swc_core22
29 parcel_resolver.specifier1
30 packages.core.core.src.Transformation5111111
31 packages.core.core.src.requests.AssetGraphRequest3111
32 packages.core.core.src.requests.BundleGraphRequest2111211
33 packages.core.test-utils.src122211
34 packages.core.utils.src11813214
35 packages.packagers.js.src.ScopeHoistingPackager11111
36 packages.reporters.cli.src111111
37 packages.reporters.dev-server.src.HMRServer11111
38 parcel_dev_dep_resolver1
39 packages.core.core.src241231244114131
40 packages.core.core.src.requests1213122514322
Uses a module listed above itPart of a loopThe module itself
1 packages.core.core.src.types2 packages.core.diagnostic.src.diagnostic3 packages.core.integration-tests.test.integration.formats.esm-bundle-import-reexport.i18n4 packages.core.types-internal.src.FileSystem5 packages.core.types-internal.src.PackageManager6 packages.core.workers.src.types7 parcel_core8 flow-typed.npm.@swc.core_v1_x_x9 flow-typed.npm.typescript_v3_3_x10 packages.core.types-internal.src11 parcel_core.diagnostic12 parcel_resolver.cache13 packages.core.core.src.BundleGraph14 packages.core.core.src.ParcelConfig15 packages.core.core.src.public.Asset16 packages.core.core.src.public.PluginOptions17 packages.core.logger.src.Logger18 packages.core.workers.src.WorkerFarm19 parcel_html20 parcel_js_swc_core.dependency_collector21 parcel_resolver22 packages.bundlers.default.src23 packages.core.core.src.PackagerRunner24 packages.core.core.src.RequestTracker25 packages.core.core.src.public.Bundle26 packages.core.core.src.requests.PathRequest27 packages.core.fs.src.MemoryFS28 parcel_js_swc_core29 parcel_resolver.specifier30 packages.core.core.src.Transformation31 packages.core.core.src.requests.AssetGraphRequest32 packages.core.core.src.requests.BundleGraphRequest33 packages.core.test-utils.src34 packages.core.utils.src35 packages.packagers.js.src.ScopeHoistingPackager36 packages.reporters.cli.src37 packages.reporters.dev-server.src.HMRServer38 parcel_dev_dep_resolver39 packages.core.core.src40 packages.core.core.src.requestspackages.core.core.src.types1packages.core.diagnostic.src.diagnostic2packages.core.integration-tests.test.integration.formats.esm-bundle-import-reexport.i18n3packages.core.types-internal.src.FileSystem4packages.core.types-internal.src.PackageManager5packages.core.workers.src.types6parcel_core7flow-typed.npm.@swc.core_v1_x_x8flow-typed.npm.typescript_v3_3_x9packages.core.types-internal.src10parcel_core.diagnostic11parcel_resolver.cache12packages.core.core.src.BundleGraph13packages.core.core.src.ParcelConfig14packages.core.core.src.public.Asset15packages.core.core.src.public.PluginOptions16packages.core.logger.src.Logger17packages.core.workers.src.WorkerFarm18parcel_html19parcel_js_swc_core.dependency_collector20parcel_resolver21packages.bundlers.default.src22packages.core.core.src.PackagerRunner23packages.core.core.src.RequestTracker24packages.core.core.src.public.Bundle25packages.core.core.src.requests.PathRequest26packages.core.fs.src.MemoryFS27parcel_js_swc_core28parcel_resolver.specifier29packages.core.core.src.Transformation30packages.core.core.src.requests.AssetGraphRequest31packages.core.core.src.requests.BundleGraphRequest32packages.core.test-utils.src33packages.core.utils.src34packages.packagers.js.src.ScopeHoistingPackager35packages.reporters.cli.src36packages.reporters.dev-server.src.HMRServer37parcel_dev_dep_resolver38packages.core.core.src39packages.core.core.src.requests401242211412311111111122211321111211114211312321111213511122151111113111211121112221111813214111111111111111112412312441141311213122514322+643 more modules (most-connected shown)

At a glance — Code Health · 42% · Weak · gated by D1, D2, R1 ·

The Good
D3 · JavaScript God Classes 7.7 D4 · JavaScript Code Duplication 9.8 D17 · JavaScript Explicit Debt 9.9 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 9.0 R10 · React / TS Code Duplication 9.1 R2 · React / TS Cyclomatic Complexity 7.0 R7 · React / TS Dead Code 9.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 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 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
R3 · React / TS Large Files 6.3
The Ugly
D1 · JavaScript Cyclomatic Complexity 3.2 D2 · JavaScript Cognitive Complexity 2.0 R1 · React / TS Type Safety 0.4 X2 · Repo Cancellation propagation 4.0 X3 · Repo Exception handling 5.0 X5 · Repo Nullable reference types 4.3

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

The Good
D5 · JavaScript Coupling 8.7 D6 · JavaScript Cohesion (LCOM4) 10.0 D22 · JavaScript Internal API Consistency 7.0 D26 · JavaScript Project Cohesion 9.9 D35 · JavaScript Change Coupling 9.9 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 7.7 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0 R11 · React / TS Import Boundaries 8.4
The Ugly
R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 62% · Adequate · gated by D34, M2 ·

The Good
D15 · JavaScript Churn × Complexity Hotspots 10.0 D16 · JavaScript Bus Factor 9.8 D19 · JavaScript Documentation Quality 9.0 D21 · JavaScript Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 9.6
The Bad
M1 · Repo Documentation (README) 6.8
The Ugly
D20 · JavaScript ADR Quality 0.0 D34 · JavaScript Knowledge Freshness 0.0 M2 · Repo Architecture documentation 3.0

At a glance — Readiness · 50% · Adequate · gated by R8 ·

The Good
D9 · JavaScript Test Distribution 10.0 D10 · JavaScript Test Quality 8.6 D12 · JavaScript Dependency Hygiene 8.5 D13 · JavaScript Secret Scanning 10.0 D14 · JavaScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R6 · React / TS Tooling 10.0
The Bad
P2 · Repo Observability 6.2 R4 · React / TS Test Coverage 5.5
The Ugly
P3 · Repo Security & performance tooling 4.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 37% · Weak · gated by D29, D30, D36, D44 ·

The Good
D28 · JavaScript Secrets (history) 10.0 D43 · JavaScript Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0
The Ugly
D29 · JavaScript Static Analysis (SAST) 0.0 D30 · JavaScript Dependency Vulnerabilities 0.0 D36 · JavaScript Supply-chain Provenance & Signing 0.0 D44 · JavaScript Platform End-of-Life 2.0 X17 · Repo Uncapped recursion over a caller-supplied document 2.7 X24 · Repo Document value interpolated into markup unescaped 4.2

At a glance — Accessibility · 64% · Adequate ·

The Good
AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 7.8
The Bad
AC3 · Repo Page structure 5.0
The Ugly
AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 73% · Strong ·

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

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection176High / Critical
A03:2025 — Software Supply Chain Failures115High / Critical

Roadmap

First, address the four End-of-life runtime issues by updating package.json to ensure platform stability. Next, immediately remediate the fifty-two high-severity dependency vulnerabilities by auditing REDACTED to protect the system from security risks. Then, begin migrating the remaining plain JavaScript files to TypeScript to improve code reliability and maintainability. Finally, clean up the dependency tree by removing unused packages, explicitly declaring imports, and resolving the single yanked release to ensure a lean and consistent environment.

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

Do thisHelpsEffortDimension
Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4).+4.4 ptsLowPlatform End-of-Life
Resolve the 1 Yanked release finding(s) in Dependency Hygiene.+1.9 ptsLowDependency Hygiene
Resolve the 52 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (52).+3.1 ptsMediumDependency Vulnerabilities
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+1.5 ptsLowStatic Analysis (SAST)
Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3).+1.5 ptsLowDependency Vulnerabilities
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED.+1.5 ptsLowSupply-chain Provenance & Signing
Migrate the remaining .js/.jsx files to TypeScript.+2.9 ptsMediumType Safety
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with image.js.+1.4 ptsLowTest Quality

File quality

Per-file score 0–10 — a quality signature. Of 210 files carrying findings, judged against the Production bar: 2% slop · 74% mixed · 24% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
packages/core/integration-tests/test/cache.js3.3SlopTest Quality: No assertions (empty test): should support adding a deeper node_modules folder
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 175

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

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

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

Could not be resolved — 4

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. 80 of 84 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. 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 — 84 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D16D17D19D20D21D22D26D28D29D30D34D35D36D43D44AC2AC3AC5AC6AC7AX10AX3AX4AX6AX8AX9GD1IC1M1M2M3M4P1P10P2P3P4P6PF1PF3R1R10R11R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X27X28X29X3X30X5

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, 1672 of 1729 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 measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16e92-cca3-7e81-badc-6afe30d4bc45.

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

Run transparency — what happened this run

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

  • D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2,266 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 8 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • 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 scored — the JavaScript/TypeScript suite (mocha via `yarn install --immutable --mode=skip-build` in the repository root; mocha via `yarn install --immutable --mode=skip-build` in packages/configs/default/ (0 tests); mocha via `yarn install --immutable --mode=skip-build` in packages/configs/repl/ (0 tests); mocha via `yarn install --immutable --mode=skip-build` in packages/core/core/ (0 tests); mocha via `yarn install --immutable --mode=skip-build` in packages/core/integration-tests/; mocha via `yarn install --immutable --mode=skip-build` in packages/core/package-manager/; mocha via `yarn install --immutable --mode=skip-build` in packages/transformers/js/ (0 tests); mocha via `yarn install --immutable --mode=skip-build` in packages/utils/node-resolver-core/) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
  • 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 mocha suite in the repository root was NOT MEASURED: the mocha run in the repository root produced no per-test report (Error: Cannot find module '@parcel/rust-linux-x64-gnu' from 'packages/core/rust'). 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 mocha suite in packages/core/integration-tests/ was NOT MEASURED: the mocha run in packages/core/integration-tests/ produced no per-test report (Error: Cannot find module '@parcel/rust-linux-x64-gnu' from 'packages/core/rust'). 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 mocha suite in packages/core/package-manager/ was NOT MEASURED: the mocha run in packages/core/package-manager/ produced no per-test report (Error: Cannot find module '@parcel/rust-linux-x64-gnu' from 'packages/core/rust'). 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 mocha suite in packages/utils/node-resolver-core/ was NOT MEASURED: the mocha run in packages/utils/node-resolver-core/ produced no per-test report (Error: Cannot find module '@parcel/rust-linux-x64-gnu' from 'packages/core/rust'). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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. `flow-libs/deasync.js`, `flow-typed/npm/@swc/core_v1.x.x.js`, `flow-typed/npm/chalk_v4.x.x.js`, `flow-typed/npm/express_v4.x.x.js`, `flow-typed/npm/mime_v2.x.x.js`, … (+106 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
  • 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.
  • PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
  • 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. 112 further occurrence(s) are not listed individually; the score already reflects all 152.
  • R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
  • R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 170 further occurrence(s) are not listed individually; the score already reflects all 210.
  • X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 61 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.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • 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.

The LLM boundary

LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity3.2 / 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 3.2 / 10 · rule-coverage 100% · ceiling Prevented

180 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DefaultBundler.createIdealGraph at 199. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being parcel_html::jsx::jsx_attr_name at 366 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: crates/core/src/asset.rs (AssetType::from_mime at 24), packages/utils/error-overlay/src/listenToRuntimeErrors.js (listenToRuntimeErrors.patchConsole at 23). 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.

parcel_html::optimize::optimize (cyclomatic 70) · ×6crates/html/src/optimize.rs:68
DependencyCollector::visit_element (cyclomatic 71) · ×5crates/html/src/dependencies.rs:170
Evaluator::eval (cyclomatic 96) · ×3crates/macros/src/lib.rs:393
ResolveRequest::resolve (cyclomatic 20) · ×3crates/parcel-resolver/src/lib.rs:541
parcel_js_swc_core::transform (cyclomatic 50) · ×2packages/transformers/js/core/src/lib.rs:253

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

What to do

  1. Bring the 4 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with DefaultBundler.createIdealGraph (cyclomatic 199), transform (cyclomatic 174), OxvgConfig::into_jobs (cyclomatic 160). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 3.2 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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

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

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

296 method(s) exceeded the cognitive complexity threshold of 15; the worst was DefaultBundler.createIdealGraph at 418.

parcel_html::package::insert_bundle_references (cognitive 108) · ×9crates/html/src/package.rs:32
DependencyCollector::fold_call_expr (cognitive 228) · ×7packages/transformers/js/core/src/dependency_collector.rs:518
parcel_js_swc_core::transform (cognitive 80) · ×7packages/transformers/js/core/src/lib.rs:253
Collect::visit_member_expr (cognitive 39) · ×6packages/transformers/js/core/src/collect.rs:631
ResolveRequest::load_file (cognitive 30) · ×6crates/parcel-resolver/src/lib.rs:976

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

What to do

  1. Bring the 40 bodies over 60 down to 60 or less in Cognitive Complexity — start with DefaultBundler.createIdealGraph (cognitive 418), transform (cognitive 323), resolvePackageTargets (cognitive 247). — 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 40 together lifts Cognitive Complexity from 2.0 to about 3.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 Classes7.7 / 10Strong✓ Tool-verified

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

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

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

72 god class(es) detected.

FunctionTooLong: DefaultBundler.createIdealGraph · ×25REDACTED:364
FileTooLong: REDACTED · ×23REDACTED
MethodTooLong: TargetResolver.resolvePackageTargets · ×14packages/core/core/src/requests/TargetRequest.js:440
ClassTooLong: DependencyCollector · ×8packages/transformers/js/core/src/dependency_collector.rs:214
TooManyFields: OxvgConfigcrates/html/src/oxvg.rs:1241

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

What to do

  1. Resolve the 25 FunctionTooLong finding(s) in God Classes — start with SymbolPropagation.js (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (25 warning-level).
  2. Resolve the 23 FileTooLong finding(s) in God Classes — start with lib.rs (3), REDACTED, TargetRequest.js. — One of this dimension's main actionable groups (23 warning-level).
  3. Resolve the 14 MethodTooLong finding(s) in God Classes — start with TargetRequest.js (2), hoist.rs (2), dependencies.rs. — One of this dimension's main actionable groups (14 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

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

Duplicated block (13 lines × 2) · ×5crates/html/src/dependencies.rs:350
Duplicated block (11 lines × 2) · ×5crates/parcel-resolver/src/package_json.rs:160
Duplicated block (9 lines × 2) · ×5packages/transformers/js/core/src/dependency_collector.rs:424
Duplicated block (10 lines × 2) · ×4crates/html/src/dependencies.rs:299
Duplicated block (7 lines × 2) · ×4crates/macros/src/lib.rs:209

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

What to do

  1. Resolve the 5 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with dependencies.rs, tsconfig.rs, collect.rs. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with package_json.rs, dependency_collector.rs, global_replacer.rs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with dependency_collector.rs, modules.rs, tsconfig.rs. — One of this dimension's main actionable groups (5 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D5 · Coupling8.7 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

153 production modules (Cargo+npm), 1 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 14 of the 153 (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).

Circular dependencypackages/core/cache/package.json:34
Off the main sequence: parcel-core · ×3
Unstable project @parcel/config-default
Unstable project @parcel/optimizer-image

What to do

  1. Resolve the 1 Circular dependency finding(s) in Coupling — start with package.json. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 Unstable project @parcel/config-default 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 58 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

2428 test methods: 722 unit, 1706 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 2266 `it`/`test` case(s) across 175 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 162 `#[test]` function(s) across 21 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.

Inverted test pyramid

✓ On the Gold path — maintain.

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

D10 · Test Quality8.6 / 10Adequategated by 5 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 8.6 / 10 · rule-coverage 100% · ceiling Prevented

131 skipped (67 with a documented reason), 119 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2266 tests. Measured on the JavaScript/TypeScript suite only — at least 8 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.

No assertions (empty test): should support adding a deeper node_modules folder · ×4packages/core/integration-tests/test/cache.js:4262
Assertions commented out: should lossless optimise progressive JPEGspackages/core/integration-tests/test/image.js:112
No assertions: is safe to add a bundle to a bundleGroup multiple times · ×114packages/core/core/test/PublicMutableBundleGraph.test.js:64
Skipped test: bundles in workers with other loaders · ×64packages/core/integration-tests/test/workers.js:1084
Skipped (documented): should compile node_modules when symlinked with a source field in package.json · ×66packages/core/integration-tests/test/transpilation.js:471

What to do

  1. Resolve the 4 No assertions (empty test) finding(s) in Test Quality — start with cache.js (4). — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 1 Assertions commented out finding(s) in Test Quality — start with image.js. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 114 No assertions finding(s) in Test Quality — start with html.js (18), bundler.js (17), output-formats.js (16). — One of this dimension's main actionable groups (114 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 Hygiene8.5 / 10Strong✓ 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 8.5 / 10 · rule-coverage 100% · ceiling Verified

20 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Yanked release: crossbeam-channel
Outdated: anyhow · ×20

What to do

  1. Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
  2. 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 377 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 9 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor9.8 / 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.8 / 10 · rule-coverage 100% · ceiling Documented

4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 240 of the 529 production source files in this repository: 278 are under the ~2,400-byte size floor this dimension measures over, and the remaining 11 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

✓ 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 23 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

23 deducted task-comment markers across 29523 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 · ×21crates/dev-dep-resolver/src/lib.rs:181
FixmeComment · ×2crates/html/src/serialize_html.rs:63

What to do

  1. Resolve the 21 TodoComment finding(s) in Explicit Debt — start with lib.rs (7), env_replacer.rs (7), srcset.rs. — One of this dimension's main actionable groups (21 warning-level).
  2. Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with serialize_html.rs (2). — One of this dimension's main actionable groups (2 warning-level).
  3. 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 QualityExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The parcel-resolver README is a directory README describing the resolver's purpose and an example. The bundled architecture/Docs markdown files (AdjacencyList, DefaultBundler) are comprehensive design documents covering data structures, algorithms, and bundling behavior. All visible documents are per-directory READMEs for their own directories; the root README is judged separately. This is a comprehensive parcel documentation set covering the core bundler concepts (deferring/scopehoisting, manual bundling, symbol propagation) as well as CI/native binary builds. The READMEs are each focused on one topic and describe what they contain; the Scopehoisting series gives an overview of the project in its own file before diving into the details, which is standard for a deep architecture document. All documents are clipped by the scanner at or past the body boundary, so any unshown sections cannot be flagged as missing.

✓ 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.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D22 · Internal API ConsistencyStrong◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

4 API inconsistencies across 228 exposed types.

The Cache API exposes multiple distinct methods for retrieving data based on content type or size (get, getStream, getBlob, getLargeBlob). This forces consumers to know the internal storage format or size constraints of the cached item before calling the correct method, rather than providing a unified retrieval interface.
The FileSystem API mixes synchronous and asynchronous methods (`readFile` vs `readFileSync`) in the same interface. While common in Node.js, this creates inconsistency in usage patterns (Promise vs direct return) and error handling within the same class, increasing cognitive load for developers using the API.
The Resolver class has three distinct methods for performing resolution that differ only by the additional parameters they accept (`options` vs `invalidations`). This creates a fragmented API where the caller must choose the correct method based on whether they need to pass extra options or track invalidations, rather than using a single method with an optional options object.
The MutableBundleGraph API exposes multiple 'add' methods that seem to perform similar graph mutation operations but with different scopes (asset graph vs single asset vs entry). This lacks a unified 'add' interface, forcing developers to understand the specific graph topology implications of each method.

What to do

  1. Resolve the 1 The Cache API exposes multiple distinct methods for retrieving data… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 The FileSystem API mixes synchronous and asynchronous methods… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 The Resolver class has three distinct methods for performing resolution… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

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

1 of 141 build units (Cargo, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

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

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

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

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

176 finding(s): 0 critical, 78 high, 97 medium, 1 low. 49 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 114 file(s) — `flow-libs/deasync.js` (line 6, line 9), `flow-typed/npm/@swc/core_v1.x.x.js`, `flow-typed/npm/chalk_v4.x.x.js` (line 67, line 101, line 102, …), `flow-typed/npm/express_v4.x.x.js` (line 8, line 16, line 45, …), `flow-typed/npm/mime_v2.x.x.js` (line 4), … (+109 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 13 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (5), REDACTED. — One of this dimension's main actionable groups (13 issue-level).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  3. No action in Static Analysis (SAST) — all 49 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (49 issue-level, 0 of them charged here).

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

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

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

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

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

105 finding(s): 12 critical, 55 high, 31 medium, 7 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

251 of 251 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/transformers/js/core/src/hoist.rs. Counted over 251 of the 529 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×248REDACTED:1
Most significant orphaned file · ×3packages/transformers/js/core/src/hoist.rs:1
Dormant codebase

What to do

  1. Resolve the 248 Orphaned file finding(s) in Knowledge Freshness — start with index.js (11), REDACTED (7), lib.rs (4). — One of this dimension's main actionable groups (248 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with hoist.rs, lib.rs, dependency_collector.rs. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: PluginOptions.js↔resolveOptions.js 85%; FSCache.js↔LMDBCache.js 73%; Parcel.js↔worker.js 70%

Change coupling: PluginOptions.js ↔ resolveOptions.js · ×4packages/core/core/src/public/PluginOptions.js:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with PluginOptions.js, FSCache.js, Parcel.js. — One of this dimension's main actionable groups (4 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life2.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

4 end-of-life runtime(s) and 0 end-of-life framework(s), read from 121 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life runtime: Node.js 10 · ×4packages/optimizers/esbuild/package.json:19

What to do

  1. Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4). — One of this dimension's main actionable groups (4 warning-level).

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

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC3 · Page structure5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×6) — packages/reporters/dev-server/src/templates/404.html:2, packages/reporters/dev-server/src/templates/500.html:2, packages/utils/create-parcel/templates/react-server/src/Page.tsx:10, …
  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/utils/create-react-app/templates/default/src/index.html:1
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — packages/utils/create-react-app/templates/default/src/index.html:1

What to do

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

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety7.8 / 10Strong✓ Tool-verified

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

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

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

  • `.resize-handle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/dev/repl/src/styles/app.css:34

What to do

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

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

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

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

  • No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 21 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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 cycles7.7 / 10Strong✓ 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.

  • The projects @parcel/cache → @parcel/core → @parcel/cache (one cycle inside a mutually-dependent group of 8 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/core/cache/package.json:34

What to do

  • Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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 segregation10.0 / 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.

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.

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

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 & stubs9.0 / 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.

  • The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — packages/core/core/src/Environment.js:40
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×39) — packages/core/integration-tests/test/babel.js:42, packages/core/integration-tests/test/babel.js:65, packages/core/integration-tests/test/babel.js:119, …

What to do

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

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

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

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 160 of 170 project(s) that lack one — worth up to 1.9 pts.
M2 · Architecture documentation3.0 / 10Weak✓ 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 accuracy9.6 / 10Exemplary◐ Sampled · advisory

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

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

  • CONTRIBUTING.md runs `yarn flow check`, but no package.json declares a `flow` script. 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. — CONTRIBUTING.md:44
  • CONTRIBUTING.md names the package `@parcel/*`, but no package.json of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:86
  • README.md names Parcel 1, but the manifest declares `parcel` ^2.14.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. — README.md:30
  • packages/core/parcel/README.md names Parcel 1, but the manifest declares `parcel` ^2.14.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. — packages/core/parcel/README.md:30
  • packages/core/parcel/README.md links to `CONTRIBUTING.md`, but `packages/core/parcel/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/parcel/README.md:44

What to do

  • Reconcile the README with reality: CONTRIBUTING.md runs `yarn flow check`, but no package.json declares a `flow` script; CONTRIBUTING.md names the package `@parcel/*`, but no package.json of the workspace declares or depends on it; README.md names Parcel 1, but the manifest declares `parcel` ^2.14.0; packages/core/parcel/README.md names Parcel 1, but the manifest declares `parcel` ^2.14.0; packages/core/parcel/README.md links to `CONTRIBUTING.md`, but `packages/core/parcel/CONTRIBUTING.md` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · Observability6.2 / 10Adequate✓ Tool-verified

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

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

  • Only 28/38 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/dev-dep-resolver`, `packages/core/parcel`, `packages/dev/bundle-stats-cli`, `packages/dev/parcel-link`, `packages/dev/query` and 5 more.
  • `packages/core/core/src/dumpGraphToGraphViz.js` reports through `console.*` at line 222 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/core/src/dumpGraphToGraphViz.js:222
  • `packages/optimizers/inline-requires/src/RequireInliningVisitor.js` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/optimizers/inline-requires/src/RequireInliningVisitor.js:185
  • `packages/optimizers/inline-requires/src/RequireInliningVisitor.js` reports through `console.*` at line 190 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/optimizers/inline-requires/src/RequireInliningVisitor.js:190

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling4.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 cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 16482 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: cargo-audit / cargo-deny (or clippy) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `github-actions`, `npm`, `cargo` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

PF1 · Benchmark discipline9.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

  • `readFileSync` in `readFile` 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/core/fs/src/MemoryFS.js:213, packages/core/fs/src/OverlayFS.js:138
  • `statSync` in `stat` 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/core/fs/src/MemoryFS.js:254, packages/core/fs/src/OverlayFS.js:172
  • `lstatSync` in `lstat` 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/core/fs/src/MemoryFS.js:281, packages/core/fs/src/OverlayFS.js:177
  • `readdirSync` in `readdir` 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/core/fs/src/MemoryFS.js:342, packages/core/fs/src/OverlayFS.js:368
  • `realpathSync` in `realpath` 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/core/fs/src/MemoryFS.js:544, packages/core/fs/src/OverlayFS.js:283
  • `readlinkSync` in `readlink` 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/core/fs/src/MemoryFS.js:557, packages/core/fs/src/OverlayFS.js:341
  • `existsSync` in `exists` 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/core/fs/src/MemoryFS.js:578, packages/core/fs/src/OverlayFS.js:346
  • `existsSync` in `_copyPathForWrite` 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/core/fs/src/OverlayFS.js:126
  • `writable.existsSync` in `_copyPathForWrite` 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/core/fs/src/OverlayFS.js:126
  • `statSync` in `unlink` 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/core/fs/src/OverlayFS.js:194, packages/core/fs/src/OverlayFS.js:204
  • `readdirSync` in `unlink` 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/core/fs/src/OverlayFS.js:200
  • `readable.existsSync` in `unlink` 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/core/fs/src/OverlayFS.js:221
  • `fs.existsSync` in `install` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:99
  • `deasync.loopWhile` in `module scope` 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/core/register/src/syncPromise.js:24
  • `overlayFS.readFileSync` in `callback to walk.call` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:469
  • `overlayFS.readFileSync` in `runBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:500
  • `fs.readFileSync` in `load` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1127
  • `fs.mkdirSync` in `run` 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/dev/bundle-stats-cli/src/cli.js:38
  • `fs.writeFileSync` in `run` 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/dev/bundle-stats-cli/src/cli.js:63
  • `fs.existsSync` in `link` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:92, REDACTED:109
  • `fs.readFileSync` in `link` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:93, REDACTED:110
  • `fs.existsSync` in `unlink` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:80, REDACTED:96
  • `fs.readFileSync` in `unlink` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:81, REDACTED:97
  • `execSync` in `unlink` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:126
  • `fs.readdirSync` in `cleanupNodeModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:119
  • `fs.statSync` in `cleanupNodeModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:146
  • `fs.accessSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:35
  • `fs.readdirSync` in `getMostRecentCacheBlobs` 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/dev/query/src/index.js:31

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 Safety0.4 / 10Critical✓ 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.

  • 23 typed · 608 plain JS — the untyped files are flow-libs/deasync.js, REDACTED, packages/bundlers/library/src/LibraryBundler.js, packages/compressors/brotli/src/BrotliCompressor.js, packages/compressors/gzip/src/GzipCompressor.js, packages/compressors/raw/src/RawCompressor.js (+602 more). 0 production file(s) opt out entirely with @ts-nocheck · 1 @ts-ignore suppression(s).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.1 / 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.

  • 20 duplicated blocks under packages/ have copies in at least two of the sibling directories core, dev, optimizers, packagers, reporters, runtimes (+3 more sibling(s) not listed) — 17 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/transformers/typescript-types/src/TSTypesTransformer.js:102
  • 7 duplicated blocks under packages/core/ have copies in at least two of the sibling directories cache, core, fs, graph, logger, types-internal (+1 more sibling(s) not listed) — 4 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/core/logger/src/Logger.js:110
  • 6 duplicated blocks under packages/reporters/ have copies in at least two of the sibling directories bundle-analyzer, bundle-stats, dev-server, dev-server-sw — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/reporters/dev-server-sw/src/HMRServer.js:84
  • 5 of the duplicated blocks reported below have copies in at least two of the sibling directories css, cssnano, html, htmlnano, svg, svgo (+2 more sibling(s) not listed) under packages/optimizers/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/optimizers/css/src/CSSOptimizer.js:170
  • packages/packagers/html/src/HTMLPackager.js:26 · packages/packagers/svg/src/SVGPackager.js:25 — the two spans are one implementation copied and then locally edited — 463 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/packagers/html/src/HTMLPackager.js:26
  • REDACTED:22 · REDACTED:22 — the two spans are one implementation copied and then locally edited — 485 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:22
  • packages/core/core/src/requests/TargetRequest.js:860 · packages/core/core/src/requests/TargetRequest.js:1065 — the two spans are one implementation copied and then locally edited — 332 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/core/core/src/requests/TargetRequest.js:860
  • REDACTED:51 · packages/transformers/sass/src/modern.js:57 — the two spans are one implementation copied and then locally edited — 325 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:51
  • packages/packagers/js/src/dev-prelude.js:97 · packages/packagers/react-static/src/ReactStaticPackager.js:433 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/packagers/js/src/dev-prelude.js:97
  • packages/core/core/src/public/Symbols.js:29 · packages/core/core/src/public/Symbols.js:98 — 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/core/core/src/public/Symbols.js:29
  • packages/reporters/dev-server-sw/src/HMRServer.js:84 · REDACTED:250 — 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/reporters/dev-server-sw/src/HMRServer.js:84
  • packages/transformers/postcss/src/loadPlugins.js:6 · packages/transformers/posthtml/src/loadPlugins.js:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/transformers/postcss/src/loadPlugins.js:6
  • packages/transformers/vue/src/VueTransformer.js:218 · packages/transformers/vue/src/VueTransformer.js:290 — the two spans are one implementation copied and then locally edited — 188 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/transformers/vue/src/VueTransformer.js:218
  • packages/core/core/src/public/Bundle.js:214 · packages/core/core/src/public/Bundle.js:269 — 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/core/core/src/public/Bundle.js:214
  • packages/core/core/src/requests/AssetRequest.js:81 · packages/core/core/src/requests/DevDepRequest.js:119 — the two spans are one implementation copied and then locally edited — 245 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/core/core/src/requests/AssetRequest.js:81
  • packages/core/cache/src/FSCache.js:46 · packages/core/cache/src/LMDBCache.js:65 — the two spans are one implementation copied and then locally edited — 222 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/core/cache/src/FSCache.js:46
  • packages/core/graph/src/AdjacencyList.js:556 · packages/core/graph/src/AdjacencyList.js:614 — 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/core/graph/src/AdjacencyList.js:556
  • packages/reporters/dev-server-sw/src/HMRServer.js:51 · REDACTED:214 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/reporters/dev-server-sw/src/HMRServer.js:51
  • packages/transformers/typescript-types/src/TSTypesTransformer.js:102 · packages/validators/typescript/src/TypeScriptValidator.js:159 — 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/transformers/typescript-types/src/TSTypesTransformer.js:102
  • packages/reporters/lsp-reporter/src/LspReporter.js:298 · packages/reporters/lsp-reporter/src/LspReporter.js:336 — the two spans are one implementation copied and then locally edited — 148 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/reporters/lsp-reporter/src/LspReporter.js:298
  • packages/core/graph/src/AdjacencyList.js:1410 · packages/core/graph/src/AdjacencyList.js:1453 — 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/core/graph/src/AdjacencyList.js:1410
  • packages/core/cache/src/IDBCache.browser.js:81 · packages/core/cache/src/LMDBCache.js:72 — the two spans are one implementation copied and then locally edited — 153 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/core/cache/src/IDBCache.browser.js:81
  • REDACTED:373 · REDACTED:506 — 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:373
  • REDACTED:86 · packages/dev/repl/src/parcel/BrowserPackageManager.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:86
  • packages/core/core/src/loadParcelPlugin.js:46 · packages/core/core/src/loadParcelPlugin.js:146 — the two spans are one implementation copied and then locally edited — 82 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/core/core/src/loadParcelPlugin.js:46
  • packages/core/package-manager/src/Npm.js:49 · REDACTED:149 — the two spans are one implementation copied and then locally edited — 85 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/core/package-manager/src/Npm.js:49
  • packages/core/graph/src/AdjacencyList.js:1174 · packages/core/graph/src/AdjacencyList.js:1212 — 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/core/graph/src/AdjacencyList.js:1174
  • packages/optimizers/css/src/CSSOptimizer.js:108 · REDACTED:289 — 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/optimizers/css/src/CSSOptimizer.js:108
  • packages/core/core/src/SymbolPropagation.js:59 · packages/core/core/src/SymbolPropagation.js:254 — 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/core/core/src/SymbolPropagation.js:59
  • REDACTED:382 · packages/core/package-manager/src/installPackage.js:115 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — REDACTED:382
  • REDACTED:858 · REDACTED:931 — the two spans are one implementation copied and then locally edited — 93 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. — REDACTED:858
  • packages/utils/create-parcel/templates/react-server/src/client.tsx:39 · packages/utils/create-parcel/templates/react-static/src/client.tsx:26 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/utils/create-parcel/templates/react-server/src/client.tsx:39
  • packages/core/core/src/CommittedAsset.js:63 · REDACTED:170 — the two spans are one implementation copied and then locally edited — 124 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/core/core/src/CommittedAsset.js:63
  • REDACTED:238 · REDACTED:210 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:238
  • packages/core/core/src/requests/BundleGraphRequest.js:221 · REDACTED:216 — the two spans are one implementation copied and then locally edited — 124 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/core/core/src/requests/BundleGraphRequest.js:221
  • packages/core/core/src/requests/TargetRequest.js:1339 · packages/core/core/src/requests/TargetRequest.js:1361 · packages/core/core/src/requests/TargetRequest.js:1382 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/core/src/requests/TargetRequest.js:1339
  • packages/optimizers/css/src/CSSOptimizer.js:170 · packages/optimizers/cssnano/src/CSSNanoOptimizer.js:56 — the two spans are one implementation copied and then locally edited — 83 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/optimizers/css/src/CSSOptimizer.js:170
  • packages/transformers/svg-jsx/src/SvgJsxTransformer.js:15 · packages/transformers/svg-react/src/SvgReactTransformer.js:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/transformers/svg-jsx/src/SvgJsxTransformer.js:15
  • packages/transformers/typescript-types/src/wrappers.js:109 · packages/transformers/typescript-types/src/wrappers.js:146 — 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/transformers/typescript-types/src/wrappers.js:109
  • packages/core/logger/src/Logger.js:110 · packages/core/types-internal/src/index.js:1052 — the two spans are one implementation copied and then locally edited — 73 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/core/logger/src/Logger.js:110

What to do

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

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

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

  • packages/core/core/src/dumpGraphToGraphViz.js:69 imports graphviz/lib/deps/graph, 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/core/core/src/dumpGraphToGraphViz.js:69
  • packages/core/integration-tests/test/api.js:13 reaches past another workspace package's public entry into its internals with a relative path (../../core/src/constants) — 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. — packages/core/integration-tests/test/api.js:13
  • packages/core/workers/test/workerfarm.js:75 reaches past another workspace package's public entry into its internals with a relative path (./integration/workerfarm/ipc.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/core/workers/test/workerfarm.js:75
  • packages/core/workers/test/workerfarm.js:87 reaches past another workspace package's public entry into its internals with a relative path (./integration/workerfarm/ipc.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/core/workers/test/workerfarm.js:87
  • packages/transformers/stylus/src/StylusTransformer.js:8 imports stylus/lib/parser, 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/transformers/stylus/src/StylusTransformer.js:8
  • packages/transformers/stylus/src/StylusTransformer.js:9 imports stylus/lib/visitor/deps-resolver, 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/transformers/stylus/src/StylusTransformer.js:9
  • packages/transformers/stylus/src/StylusTransformer.js:10 imports stylus/lib/nodes, 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/transformers/stylus/src/StylusTransformer.js:10
  • packages/transformers/stylus/src/StylusTransformer.js:11 imports stylus/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/transformers/stylus/src/StylusTransformer.js:11
  • packages/transformers/stylus/src/StylusTransformer.js:12 imports stylus/lib/visitor/evaluator, 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/transformers/stylus/src/StylusTransformer.js:12

What to do

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

  • transform has cyclomatic complexity 140 and cognitive complexity 265; 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:336
  • resolvePackageTargets has cyclomatic complexity 133 and cognitive complexity 237; 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/core/core/src/requests/TargetRequest.js:440
  • createIdealGraph has cyclomatic complexity 96 and cognitive complexity 236; 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:364
  • (anonymous) has cyclomatic complexity 57 and cognitive complexity 192; 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/runtimes/rsc/src/RSCRuntime.js:40
  • collectDependencies has cyclomatic complexity 57 and cognitive complexity 116; 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:39
  • dumpGraphToGraphViz has cyclomatic complexity 52 and cognitive complexity 137; 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/core/core/src/dumpGraphToGraphViz.js:38
  • enter has cyclomatic complexity 48 and cognitive complexity 98; 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:529
  • (anonymous) has cyclomatic complexity 47 and cognitive complexity 77; 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/transformers/typescript-types/src/shake.js:38
  • getSymbolResolution has cyclomatic complexity 47 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:983
  • _report has cyclomatic complexity 44 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/reporters/cli/src/CLIReporter.js:43
  • resolveOptions has cyclomatic complexity 44 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/core/src/resolveOptions.js:47
  • walk has cyclomatic complexity 43 and cognitive complexity 141; 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/core/utils/src/schema.js:116
  • transform has cyclomatic complexity 41 and cognitive complexity 76; 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:44
  • buildAssetPrelude has cyclomatic complexity 40 and cognitive complexity 73; 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:1151
  • (anonymous) has cyclomatic complexity 40 and cognitive complexity 67; 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/core/core/src/SymbolPropagation.js:257
  • package has cyclomatic complexity 40 and cognitive complexity 65; 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/packagers/js/src/DevPackager.js:46
  • loadConfig has cyclomatic complexity 40 and cognitive complexity 53; 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:181
  • (anonymous) has cyclomatic complexity 38 and cognitive complexity 87; 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/core/core/src/SymbolPropagation.js:62
  • codeFrame has cyclomatic complexity 37 and cognitive complexity 72; 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/core/codeframe/src/codeframe.js:42
  • addExternal has cyclomatic complexity 35 and cognitive complexity 101; 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:812

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files6.3 / 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/core/types-internal/src/index.js has 1995 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/core/types-internal/src/index.js:1
  • REDACTED has 1944 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 1699 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/core/core/src/requests/TargetRequest.js has 1578 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/core/core/src/requests/TargetRequest.js:1
  • packages/core/graph/src/AdjacencyList.js has 1509 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/core/graph/src/AdjacencyList.js:1
  • REDACTED has 1365 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 1359 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 1300 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 1129 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 1046 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/core/fs/src/MemoryFS.js has 923 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/core/fs/src/MemoryFS.js:1
  • REDACTED has 801 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 769 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/core/core/src/SymbolPropagation.js has 730 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/core/core/src/SymbolPropagation.js:1
  • REDACTED has 686 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/dev/repl/src/utils/assets.js has 665 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/dev/repl/src/utils/assets.js:1
  • packages/runtimes/hmr/src/loaders/hmr-runtime.js has 660 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/runtimes/hmr/src/loaders/hmr-runtime.js:1
  • packages/core/core/src/requests/ParcelConfigRequest.js has 648 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/core/core/src/requests/ParcelConfigRequest.js:1
  • packages/packagers/react-static/src/ReactStaticPackager.js has 642 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/packagers/react-static/src/ReactStaticPackager.js:1
  • REDACTED has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 620 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 617 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 603 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 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/transformers/webextension/src/schema.js has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/transformers/webextension/src/schema.js:1
  • packages/core/core/src/types.js has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/core/src/types.js:1
  • packages/dev/esm-fuzzer/generateExample.js has 526 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/dev/esm-fuzzer/generateExample.js:1
  • packages/core/core/src/requests/AssetGraphRequest.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/core/src/requests/AssetGraphRequest.js:1
  • packages/core/parcel/src/cli.js has 515 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/core/parcel/src/cli.js:1
  • packages/core/utils/src/schema.js has 490 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/core/utils/src/schema.js:1
  • packages/core/core/src/Parcel.js has 489 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/core/core/src/Parcel.js:1
  • packages/transformers/vue/src/VueTransformer.js has 488 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/transformers/vue/src/VueTransformer.js:1
  • packages/core/core/src/requests/BundleGraphRequest.js has 487 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/core/core/src/requests/BundleGraphRequest.js:1
  • packages/reporters/dev-server/src/Server.js has 481 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/reporters/dev-server/src/Server.js:1
  • packages/core/core/src/ParcelConfig.js has 451 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/core/core/src/ParcelConfig.js:1
  • REDACTED has 446 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/runtimes/rsc/src/RSCRuntime.js has 439 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/runtimes/rsc/src/RSCRuntime.js:1
  • packages/dev/repl/src/index.js has 426 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/dev/repl/src/index.js:1
  • REDACTED has 425 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

What to do

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

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

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

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — REDACTED:1, scripts/to-fs-fixture.js:1, packages/runtimes/hmr/src/loaders/hmr-runtime.js: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.

R7 · Dead Code9.0 / 10Exemplary✓ Tool-verified

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

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

  • 1 file(s) (~77 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/configs/default
  • 1 file(s) (~190 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. — packages/resolvers/repl-runtimes
  • 5 file(s) (~135 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. — packages/utils/create-parcel/templates/react-server
  • Unreachable from the 289 application, 23 tooling and 187 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 (289 application, 23 tooling, 187 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 (×10) — packages/dev/repl/SimplePackageInstaller/index.js, packages/core/utils/src/bundle-url.js, REDACTED, …
  • no import path from any entry point (289 application, 23 tooling, 187 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/dev/repl/SimplePackageInstaller/index.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/dev/repl/SimplePackageInstaller/untar.js
  • Nothing imports this binding — it is safe to review for removal. (×15) — packages/core/core/src/requests/ParcelConfigRequest.js:205, packages/core/core/src/serializer.js:243, packages/core/core/src/serializer.js:247, …
  • Nothing ultimately consumes this binding: its only referrer is the re-export in packages/dev/repl/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/dev/repl/src/components/index.js in the same commit, or the barrel will import a name that no longer exists. — packages/dev/repl/src/components/helper.js:319
  • This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments. — REDACTED:32

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. (×12) — scripts/to-fs-fixture.js:13, scripts/tag-release.mjs:7, scripts/to-fs-fixture.js:14, …
  • Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. (×5) — REDACTED:22, packages/core/types-internal/src/FileSystem.js:4, packages/core/utils/src/schema.js:7, …
  • Declared in packages/core/core/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.
  • Declared in packages/core/fs/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.
  • Declared in packages/core/integration-tests/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/core/types-internal/src/index.js:4

What to do

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

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

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

  • packages/core/core/src/index.js → packages/core/core/src/Parcel.js → packages/core/core/src/ReporterRunner.js → packages/core/workers/src/index.js → REDACTED → packages/core/core/src/index.js (one verified cycle inside a mutually-dependent group of 40 files) — packages/core/core/src/index.js:13
  • packages/core/core/src/CommittedAsset.js → REDACTED → packages/core/core/src/CommittedAsset.js (one verified cycle inside a mutually-dependent group of 4 files) — packages/core/core/src/CommittedAsset.js:9
  • REDACTED → REDACTED → REDACTED — REDACTED:44
  • packages/core/graph/src/AdjacencyList.js → REDACTED → packages/core/graph/src/AdjacencyList.js — packages/core/graph/src/AdjacencyList.js:6
  • packages/core/utils/src/blob.js → packages/core/utils/src/index.js → packages/core/utils/src/blob.js (one verified cycle inside a mutually-dependent group of 5 files) — packages/core/utils/src/blob.js:6

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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

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

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document2.7 / 10Weak✓ Tool-verified

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

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

  • `shake` is exported, takes a document from its caller (line 15) and hands it to `visit`, which calls itself at line 40 (`visit`) with a piece of `node` (and at line 63, line 75, line 171, line 246) — and nowhere in `visit` 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 `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/transformers/typescript-types/src/shake.js:40
  • `collect` is exported, takes a document from its caller (line 9) and hands it to `visit`, which calls itself at line 23 (`visit`) with a piece of `node` (and at line 33, line 86) — and nowhere in `visit` 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 `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/transformers/typescript-types/src/collect.js:23

What to do

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

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

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

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

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

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

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

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

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

  • Only 0/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/core/rust/src/browser.js:5
  • `_npmResolve` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/dev/repl/SimplePackageInstaller/index.js:55
  • `_npmFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/dev/repl/SimplePackageInstaller/index.js:102
  • `getStackFrames` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/utils/error-overlay/src/utils/getStackFrames.js:17

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). 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 unescaped4.2 / 10Weak✓ Tool-verified

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

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

  • `error` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/dev/repl/src/components/helper.js:18
  • `content` is text this program did not author, and it is written into the text of an element through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/dev/repl/src/components/helper.js:77
  • `e.group.label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/reporters/bundle-analyzer/client/index.js:51
  • `formatSize(e.group.weight)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/reporters/bundle-analyzer/client/index.js:56
  • `codeHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/utils/error-overlay/src/components/CodeBlock.js:43

What to do

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

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

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

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

Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.

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

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

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

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

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

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

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

X3 · Exception handling5.0 / 10Weak✓ 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. (×32) — packages/core/codeframe/src/codeframe.js:34, packages/core/core/src/resolveOptions.js:72, REDACTED:336, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×3) — packages/core/core/src/requests/WriteBundlesRequest.js:149, REDACTED:205, packages/runtimes/webextension/src/autoreload-bg.js:30
  • `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — packages/core/fs/src/NodeFS.js:226, REDACTED:500, packages/transformers/sass/src/modern.js:172, …
  • `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/core/package-manager/src/installPackage.js:240

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 types4.3 / 10Weak✓ 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.

  • 7/23 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.
  • ~0.9 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 1101 source line(s) of the 20 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/utils/create-parcel/templates/react-client/src/index.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

WCAG coverage — what static analysis assessed

Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health42%Weak — gated by D1, D2, R1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture68%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity62%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness50%Adequate — gated by R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security37%Weak — gated by D29, D30, D36, D44Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility64%AdequateAcceptable, with room to improve.
Performance73%StrongStrongest area.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 23 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 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 — 45 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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
  • 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — No tests discovered
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js), 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) — 111 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. 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 (12 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, Rust source (service entry point: packages/core/utils/src/http-server.js:47 (http.createServer())
  • 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 — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) 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. Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
  • 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
  • S1 Web-Security Posture — No web surface: 52 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. 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.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 175 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×52
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 27 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 24 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×4
  • No assertions (empty test): should support adding a deeper node_modules folder packages/core/integration-tests/test/cache.js:4262 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): should support adding sideEffects config packages/core/integration-tests/test/cache.js:6529 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): should support updating sideEffects config packages/core/integration-tests/test/cache.js:6531 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): should support removing sideEffects config packages/core/integration-tests/test/cache.js:6533 — Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability · Test suite declares a test script but contains no test files · ×4
  • Test suite declares a test script but contains no test files: packages/configs/default/ — The mocha suite in packages/configs/default/ was installed and launched successfully, and the runner then found no test files to run — Error: No test files found: "packages/*/!(integration-tests)/test/{*.js,**/*.{test,spec}.js}". The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: packages/configs/repl/ — The mocha suite in packages/configs/repl/ was installed and launched successfully, and the runner then found no test files to run — Error: No test files found: "packages/*/!(integration-tests)/test/{*.js,**/*.{test,spec}.js}". The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: packages/core/core/ — The mocha suite in packages/core/core/ was installed and launched successfully, and the runner then found no test files to run — Error: No test files found: "packages/*/!(integration-tests)/test/{*.js,**/*.{test,spec}.js}". The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: packages/transformers/js/ — The mocha suite in packages/transformers/js/ was installed and launched successfully, and the runner then found no test files to run — Error: No test files found: "packages/*/!(integration-tests)/test/{*.js,**/*.{test,spec}.js}". The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
R9 · Circular Imports · Import cycle (2 files) · ×4
  • Import cycle (2 files) packages/core/core/src/CommittedAsset.js:9 — packages/core/core/src/CommittedAsset.js → REDACTED → packages/core/core/src/CommittedAsset.js (one verified cycle inside a mutually-dependent group of 4 files)
  • Import cycle (2 files) REDACTED:44 — REDACTED → REDACTED → REDACTED
  • Import cycle (2 files) packages/core/graph/src/AdjacencyList.js:6 — packages/core/graph/src/AdjacencyList.js → REDACTED → packages/core/graph/src/AdjacencyList.js
  • Import cycle (2 files) packages/core/utils/src/blob.js:6 — packages/core/utils/src/blob.js → packages/core/utils/src/index.js → packages/core/utils/src/blob.js (one verified cycle inside a mutually-dependent group of 5 files)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'nullthrows' · ×2
  • Unlisted import 'nullthrows' scripts/to-fs-fixture.js:15 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
  • Unlisted import 'nullthrows' packages/core/integration-tests/test/cache.js:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang packages/utils/create-react-app/templates/default/src/index.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> packages/utils/create-react-app/templates/default/src/index.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AX3 · Project dependency cycles · Project dependency cycle · ×1
  • Project dependency cycle packages/core/cache/package.json:34 — The projects @parcel/cache → @parcel/core → @parcel/cache (one cycle inside a mutually-dependent group of 8 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
D10 · Test Quality · Assertions commented out · ×1
  • Assertions commented out: should lossless optimise progressive JPEGs packages/core/integration-tests/test/image.js:112 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D5 · Coupling · Circular dependency · ×1
  • Circular dependency packages/core/cache/package.json:34 — @parcel/cache → @parcel/core → @parcel/cache (one cycle inside a mutually-dependent group of 8 modules)
R8 · Dependency Hygiene · Unlisted import 'chalk' · ×1
  • Unlisted import 'chalk' scripts/to-fs-fixture.js:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'commander' · ×1
  • Unlisted import 'commander' scripts/tag-release.mjs:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'diff' · ×1
  • Unlisted import 'diff' scripts/to-fs-fixture.js:14 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'inquirer' · ×1
  • Unlisted import 'inquirer' scripts/to-fs-fixture.js:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'json5' · ×1
  • Unlisted import 'json5' packages/configs/default/test/config.test.js:6 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import '@parcel/source-map' · ×1
  • Unlisted import '@parcel/source-map' packages/core/integration-tests/test/hmr.js:24 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'graphql' · ×1
  • Unlisted import 'graphql' packages/core/integration-tests/test/graphql.js:4 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'sharp' · ×1
  • Unlisted import 'sharp' packages/core/integration-tests/test/image.js:5 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'deasync' · ×1
  • Unlisted import 'deasync' packages/core/register/src/syncPromise.js:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'strip-ansi' · ×1
  • Unlisted import 'strip-ansi' packages/reporters/cli/test/CLIReporter.test.js:11 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (5 files) · ×1
  • Import cycle (5 files) packages/core/core/src/index.js:13 — packages/core/core/src/index.js → packages/core/core/src/Parcel.js → packages/core/core/src/ReporterRunner.js → packages/core/workers/src/index.js → REDACTED → packages/core/core/src/index.js (one verified cycle inside a mutually-dependent group of 40 files)
Serious — 1103 finding(s)
D10 · Test Quality · No assertions · ×114
  • No assertions: is safe to add a bundle to a bundleGroup multiple times packages/core/core/test/PublicMutableBundleGraph.test.js:64 — 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 succeed with an array of valid package names packages/core/core/test/ParcelConfigRequest.test.js:148 — 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 support spread elements packages/core/core/test/ParcelConfigRequest.test.js:158 — 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 support relative paths packages/core/core/test/ParcelConfigRequest.test.js:220 — 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 succeed on valid config packages/core/core/test/ParcelConfigRequest.test.js:300 — 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 time out on glob-like entry packages/core/core/test/EntryRequest.test.js:211 — 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: can execute a config request packages/core/core/test/requests/ConfigRequest.test.js:72 — 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: bundles workers and service workers packages/core/integration-tests/test/workers.js:18 — 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 support workers pointing to themselves packages/core/integration-tests/test/workers.js:173 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: bundles workers pointing to themselves with import.meta.url packages/core/integration-tests/test/workers.js:200 — 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: bundles workers with different order packages/core/integration-tests/test/workers.js:491 — 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: bundles service workers packages/core/integration-tests/test/workers.js:661 — 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: bundles workers with circular dependencies packages/core/integration-tests/test/workers.js:973 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: supports workers with shared assets between page and worker with async imports packages/core/integration-tests/test/workers.js:1219 — 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: async dependency internalization successfully removes unneeded bundlegroups and their bundles packages/core/integration-tests/test/workers.js:1264 — 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 work when there is a target in package.json packages/core/integration-tests/test/webmanifest.js:254 — 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 handle legacy cast in .ts file packages/core/integration-tests/test/typescript.js:199 — 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 resolve @swc/helpers and regenerator-runtime relative to parcel packages/core/integration-tests/test/transpilation.js:344 — 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 be in separate bundles packages/core/integration-tests/test/svg.js:313 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: supports requiring a CSS asset packages/core/integration-tests/test/scope-hoisting.js:4574 — 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: replaces properties of require with undefined packages/core/integration-tests/test/scope-hoisting.js:4776 — 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 support non-object module.exports packages/core/integration-tests/test/scope-hoisting.js:5126 — 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 unmark dependency as deferred when dependency becomes used packages/core/integration-tests/test/scope-hoisting.js:5820 — 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 support scss imports in html for >1 target packages/core/integration-tests/test/sass.js:84 — 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 import from packages with a string key of `sass` in package.json packages/core/integration-tests/test/sass.js:329 — 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.
  • + 89 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×85
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 60 more in this group — see findings.md.
D10 · Test Quality · Skipped test · ×64
  • Skipped test: bundles in workers with other loaders packages/core/integration-tests/test/workers.js:1084 — Skipped — switched off by it.skip
  • Skipped test: should re-generate bundle tree when files change packages/core/integration-tests/test/watcher.js:140 — Skipped — switched off by it.skip
  • Skipped test: should only re-package bundles that changed packages/core/integration-tests/test/watcher.js:217 — Skipped — switched off by it.skip
  • Skipped test: should unload assets that are orphaned packages/core/integration-tests/test/watcher.js:246 — Skipped — switched off by it.skip
  • Skipped test: should recompile all assets when a config file changes packages/core/integration-tests/test/watcher.js:325 — Skipped — switched off by it.skip
  • Skipped test: should rebuild if the file behind a symlink changes packages/core/integration-tests/test/watcher.js:352 — Skipped — switched off by it.skip
  • Skipped test: should detect the version of SVGO to use packages/core/integration-tests/test/svg.js:141 — Skipped — switched off by it.skip
  • Skipped test: should detect the version of SVGO to use packages/core/integration-tests/test/svg-react.js:68 — Skipped — switched off by it.skip
  • Skipped test: should load existing sourcemaps for CSS files packages/core/integration-tests/test/sourcemaps.js:1153 — Skipped — switched off by it.skip
  • Skipped test: throws a meaningful error on undefined exports packages/core/integration-tests/test/scope-hoisting.js:970 — Skipped — switched off by it.skip
  • Skipped test: supports tree shaking statically analyzable dynamic import: destructued await assignment packages/core/integration-tests/test/scope-hoisting.js:1577 — Skipped — switched off by it.skip
  • Skipped test: throws an error for missing exports for dynamic import: destructured await assignment packages/core/integration-tests/test/scope-hoisting.js:1851 — Skipped — switched off by it.skip
  • Skipped test: doesn't support require.resolve calls for included assets packages/core/integration-tests/test/scope-hoisting.js:4342 — Skipped — switched off by it.skip
  • Skipped test: supports require.resolve calls for excluded modules packages/core/integration-tests/test/scope-hoisting.js:4439 — Skipped — switched off by it.skip
  • Skipped test: does not include prelude if child bundles are isolated packages/core/integration-tests/test/scope-hoisting.js:5439 — Skipped — switched off by it.skip
  • Skipped test: Should be able to process an html file with plugins without any params for plugin packages/core/integration-tests/test/posthtml.js:56 — Skipped — switched off by it.skip
  • Skipped test: should add dependencies referenced by posthtml-include packages/core/integration-tests/test/posthtml.js:80 — Skipped — switched off by it.skip
  • Skipped test: should add dependencies referenced by plugins packages/core/integration-tests/test/posthtml.js:93 — Skipped — switched off by it.skip
  • Skipped test: updates config for custom namespace packages/core/integration-tests/test/parcel-link.js:195 — Skipped — switched off by it.skip
  • Skipped test: updates config for custom namespace packages/core/integration-tests/test/parcel-link.js:432 — Skipped — switched off by it.skip
  • Skipped test: should support commonjs output from esmodule input (re-export namespace as) packages/core/integration-tests/test/output-formats.js:71 — Skipped — switched off by it.skip
  • Skipped test: should support esmodule output (re-export namespace as) packages/core/integration-tests/test/output-formats.js:639 — Skipped — switched off by it.skip
  • Skipped test: should support dynamic imports with chained reexports packages/core/integration-tests/test/output-formats.js:848 — Skipped — switched off by it.skip
  • Skipped test: doesn't support require.resolve calls for excluded assets without commonjs packages/core/integration-tests/test/output-formats.js:1203 — Skipped — switched off by it.skip
  • Skipped test: should support split bundles between main script and workers packages/core/integration-tests/test/output-formats.js:1503 — Skipped — switched off by it.skip
  • + 39 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking packages/core/fs/src/MemoryFS.js:213 — `readFileSync` in `readFile` 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/core/fs/src/MemoryFS.js:254 — `statSync` in `stat` 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/core/fs/src/MemoryFS.js:281 — `lstatSync` in `lstat` 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/core/fs/src/MemoryFS.js:342 — `readdirSync` in `readdir` 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/core/fs/src/MemoryFS.js:544 — `realpathSync` in `realpath` 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/core/fs/src/MemoryFS.js:557 — `readlinkSync` in `readlink` 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/core/fs/src/MemoryFS.js:578 — `existsSync` in `exists` 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/core/fs/src/OverlayFS.js:126 — `existsSync` in `_copyPathForWrite` 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/core/fs/src/OverlayFS.js:126 — `writable.existsSync` in `_copyPathForWrite` 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/core/fs/src/OverlayFS.js:138 — `readFileSync` in `readFile` 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/core/fs/src/OverlayFS.js:172 — `statSync` in `stat` 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/core/fs/src/OverlayFS.js:177 — `lstatSync` in `lstat` 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/core/fs/src/OverlayFS.js:194 — `statSync` in `unlink` 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/core/fs/src/OverlayFS.js:200 — `readdirSync` in `unlink` 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/core/fs/src/OverlayFS.js:204 — `statSync` in `unlink` 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/core/fs/src/OverlayFS.js:221 — `readable.existsSync` in `unlink` 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/core/fs/src/OverlayFS.js:283 — `realpathSync` in `realpath` 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/core/fs/src/OverlayFS.js:341 — `readlinkSync` in `readlink` 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/core/fs/src/OverlayFS.js:346 — `existsSync` in `exists` 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/core/fs/src/OverlayFS.js:368 — `readdirSync` in `readdir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:99 — `fs.existsSync` in `install` 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/core/register/src/syncPromise.js:24 — `deasync.loopWhile` in `module scope` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:469 — `overlayFS.readFileSync` in `callback to walk.call` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:500 — `overlayFS.readFileSync` in `runBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:1127 — `fs.readFileSync` in `load` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/to-fs-fixture.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/runtimes/hmr/src/loaders/hmr-runtime.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/packagers/react-static/src/ReactStaticPackager.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/utils/assets.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/transformers/webextension/src/schema.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/reporters/dev-server/src/Server.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/transformers/vue/src/VueTransformer.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/esm-fuzzer/generateExample.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/runtimes/rsc/src/RSCRuntime.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/reporters/lsp-reporter/src/LspReporter.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/transformers/stylus/src/StylusTransformer.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/components/helper.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/components/state.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/utils/parcel-lsp/src/LspServer.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/SimplePackageInstaller/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/transformers/image/src/validateConfig.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/sw.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/components/Options.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/dev/repl/src/components/FileBrowser.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.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×36
  • Swallowed exception (empty catch) packages/core/codeframe/src/codeframe.js:34 — 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/core/core/src/resolveOptions.js:72 — 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:336 — 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:1201 — 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:1400 — 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/core/core/src/requests/WriteBundlesRequest.js:149 — `.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/core/core/src/requests/DevDepRequest.js:60 — 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/core/core/src/requests/BundleGraphRequest.js:271 — 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/core/fs/src/find.js:23 — 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/core/fs/src/find.js:53 — 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/core/fs/src/find.js:77 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core/fs/src/OverlayFS.js:247 — 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/core/fs/src/OverlayFS.js:382 — 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/core/fs/src/OverlayFS.js:393 — 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/core/fs/src/NodeFS.js:167 — 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/core/fs/src/NodeFS.js:246 — 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/core/graph/src/shared-buffer.js:15 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core/package-manager/src/installPackage.js:240 — `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
  • Swallowed exception (empty catch) REDACTED:102 — 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/core/utils/src/shared-buffer.js:15 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:49 — 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:205 — `.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) REDACTED:108 — 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:147 — 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:151 — 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.
  • + 11 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×25
  • FunctionTooLong: DefaultBundler.createIdealGraph REDACTED:364 — FunctionTooLong — createIdealGraph runs 777 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 677 over it, 7.77× 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: cli.run REDACTED:25 — FunctionTooLong — run runs 691 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 591 over it, 6.91× 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: parcel_html::optimize::optimize crates/html/src/optimize.rs:68 — FunctionTooLong — parcel_html::optimize::optimize runs 303 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 203 over it, 3.03× 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: SymbolPropagation.propagateSymbols packages/core/core/src/SymbolPropagation.js:22 — FunctionTooLong — propagateSymbols runs 289 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 189 over it, 2.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: parcel_js_swc_core::transform packages/transformers/js/core/src/lib.rs:253 — FunctionTooLong — parcel_js_swc_core::transform runs 285 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: Options.Options packages/dev/repl/src/components/Options.js:14 — FunctionTooLong — Options runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: schema.validateSchema packages/core/utils/src/schema.js:115 — FunctionTooLong — validateSchema runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: applyRuntimes.applyRuntimes packages/core/core/src/applyRuntimes.js:45 — FunctionTooLong — applyRuntimes runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: parcel_html::jsx::to_component crates/html/src/jsx.rs:709 — FunctionTooLong — parcel_html::jsx::to_component runs 173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 73 over it, 1.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.
  • FunctionTooLong: SymbolPropagation.errors packages/core/core/src/SymbolPropagation.js:257 — FunctionTooLong — errors runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: loadParcelPlugin.loadPlugin packages/core/core/src/loadParcelPlugin.js:24 — FunctionTooLong — loadPlugin runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× 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: DefaultBundler.decorateLegacyGraph REDACTED:157 — FunctionTooLong — decorateLegacyGraph runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: resolveOptions.resolveOptions packages/core/core/src/resolveOptions.js:47 — FunctionTooLong — resolveOptions 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: state.reducer packages/dev/repl/src/components/state.js:81 — FunctionTooLong — reducer runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.Output packages/dev/repl/src/index.js:90 — FunctionTooLong — Output runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: shake.shake packages/transformers/typescript-types/src/shake.js:15 — FunctionTooLong — shake runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: CLIReporter._report packages/reporters/cli/src/CLIReporter.js:43 — FunctionTooLong — _report runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: parcel_html::srcset::parse_srcset crates/html/src/srcset.rs:50 — FunctionTooLong — parcel_html::srcset::parse_srcset runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: parcel_html::package::insert_bundle_references crates/html/src/package.rs:32 — FunctionTooLong — parcel_html::package::insert_bundle_references runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: parcel_html::serialize_html::can_omit_end_tag crates/html/src/serialize_html.rs:395 — FunctionTooLong — parcel_html::serialize_html::can_omit_end_tag runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: SymbolPropagation.propagateSymbolsUp packages/core/core/src/SymbolPropagation.js:595 — FunctionTooLong — propagateSymbolsUp runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: JSRuntime.getLoaderRuntime REDACTED:321 — FunctionTooLong — getLoaderRuntime 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: config.load REDACTED:40 — FunctionTooLong — load 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: cli.normalizeOptions packages/core/parcel/src/cli.js:431 — FunctionTooLong — normalizeOptions runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: schema.validateSchema.diagnostic packages/core/utils/src/schema.js:380 — FunctionTooLong — validateSchema.diagnostic 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.
D3 · God Classes · FileTooLong · ×23
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1358 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: BundleGraph (116-2160). The bar is 500 significant lines; this is 858 over it, 2.72× 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: requests/TargetRequest.js packages/core/core/src/requests/TargetRequest.js — FileTooLong — 1208 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 68% of them inside a single declaration: TargetResolver (187-1318). The bar is 500 significant lines; this is 708 over it, 2.42× 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 — 1197 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 65% of them inside a single declaration: createIdealGraph (364-1627). The bar is 500 significant lines; this is 697 over it, 2.39× 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/index.js packages/core/types-internal/src/index.js — FileTooLong — 1140 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 640 over it, 2.28× 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/dependency_collector.rs packages/transformers/js/core/src/dependency_collector.rs — FileTooLong — 1135 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: DependencyCollector (5 blocks, 214-1738). The bar is 500 significant lines; this is 635 over it, 2.27× 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/oxvg.rs crates/html/src/oxvg.rs — FileTooLong — 1119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 619 over it, 2.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1049 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 549 over it, 2.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 966 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ScopeHoistingPackager (78-1516). The bar is 500 significant lines; this is 466 over it, 1.93× 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 — 847 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 347 over it, 1.69× 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/lib.rs crates/parcel-resolver/src/lib.rs — FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: ResolveRequest (2 blocks, 415-1390). The bar is 500 significant lines; this is 341 over it, 1.68× 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/collect.rs packages/transformers/js/core/src/collect.rs — FileTooLong — 768 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: Collect (4 blocks, 59-1128). The bar is 500 significant lines; this is 268 over it, 1.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/hoist.rs packages/transformers/js/core/src/hoist.rs — FileTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: Hoist (4 blocks, 103-1352). The bar is 500 significant lines; this is 260 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/AdjacencyList.js packages/core/graph/src/AdjacencyList.js — FileTooLong — 756 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 256 over it, 1.51× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 708 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: run (25-1130). The bar is 500 significant lines; this is 208 over it, 1.42× 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/MemoryFS.js packages/core/fs/src/MemoryFS.js — FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 193 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/package_json.rs crates/parcel-resolver/src/package_json.rs — FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 185 over it, 1.37× 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/lib.rs crates/macros/src/lib.rs — FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: PackagerRunner (109-839). The bar is 500 significant lines; this is 126 over it, 1.25× 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/lib.rs packages/transformers/js/core/src/lib.rs — FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 84 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: NodeResolver (71-774). The bar is 500 significant lines; this is 76 over it, 1.15× 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 — 532 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: Transformation (96-726). The bar is 500 significant lines; this is 32 over it, 1.06× 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/dependencies.rs crates/html/src/dependencies.rs — FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: DependencyCollector (2 blocks, 97-657). The bar is 500 significant lines; this is 17 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/optimize.rs crates/html/src/optimize.rs — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D30 · Dependency Vulnerabilities · Medium CVE · ×23
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · TodoComment · ×21
  • TodoComment crates/dev-dep-resolver/src/lib.rs:181 — // TODO: how should we handle package exports? — 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 crates/html/src/srcset.rs:256 — // TODO: Do what Gecko does and first validate the number passed to the Rust float parser. — 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 crates/html/src/oxvg.rs:315 — // TODO: deprecate — 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 crates/parcel-resolver/src/lib.rs:609 — // TODO: should this follow aliases?? — 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 crates/parcel-resolver/src/lib.rs:912 — // TODO: track location of resolved field — 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 crates/parcel-resolver/src/lib.rs:1001 — // TODO: would be nice if there was a way to do this without cloning — 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 crates/parcel-resolver/src/lib.rs:1037 — // TODO: Revert this in the next major version. — 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 crates/parcel-resolver/src/lib.rs:1125 — // TODO: TypeScript only removes certain extensions here... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment crates/parcel-resolver/src/lib.rs:1264 — // TODO: should aliases apply to tsconfig paths?? — 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/transformers/js/core/src/node_replacer.rs:219 — // TODO: use import.meta.dirname if available? — 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/transformers/js/core/src/hoist.rs:282 — /// TODO: add example — 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/transformers/js/core/src/global_replacer.rs:22 — /// (TODO: why is this needed?). — 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/transformers/js/core/src/fs.rs:150 — // TODO: this should probably happen in JS so we use Parcel's file system — 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/transformers/js/core/src/env_replacer.rs:32 — // TODO: this seems questionable but we did it in the JS version?? — 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/transformers/js/core/src/env_replacer.rs:162 — // TODO: This can be written to run in-place to make it more efficient — 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/transformers/js/core/src/env_replacer.rs:282 — // TODO: This can be written to run in-place to make it more efficient — 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/transformers/js/core/src/env_replacer.rs:304 — // TODO: This can be written to run in-place to make it more efficient — 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/transformers/js/core/src/env_replacer.rs:403 — // TODO: This behaviour is wrong, nothing should be changed on this case — 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/transformers/js/core/src/env_replacer.rs:414 — // TODO: This behaviour should be removed and will be disabled for canary builds. — 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/transformers/js/core/src/env_replacer.rs:533 — // TODO: This seems wrong as there's an extra trailing object — 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/transformers/js/core/src/collect.rs:318 — // TODO: optimize `require('foo').bar` / `require('foo').bar()` as well — 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.
D3 · God Classes · MethodTooLong · ×14
  • MethodTooLong: TargetResolver.resolvePackageTargets packages/core/core/src/requests/TargetRequest.js:440 — MethodTooLong — resolvePackageTargets runs 581 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 481 over it, 5.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DependencyCollector.visit_element crates/html/src/dependencies.rs:170 — MethodTooLong — visit_element runs 275 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DependencyCollector.fold_call_expr packages/transformers/js/core/src/dependency_collector.rs:518 — MethodTooLong — fold_call_expr runs 275 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Hoist.fold_module packages/transformers/js/core/src/hoist.rs:376 — MethodTooLong — fold_module runs 273 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 173 over it, 2.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: DevPackager.package packages/packagers/js/src/DevPackager.js:46 — MethodTooLong — package runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× 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: ESMFold.fold_module packages/transformers/js/core/src/modules.rs:280 — MethodTooLong — fold_module runs 207 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: Evaluator.eval crates/macros/src/lib.rs:393 — MethodTooLong — eval runs 196 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: TargetResolver.resolve packages/core/core/src/requests/TargetRequest.js:200 — MethodTooLong — resolve runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: BundlerRunner.bundle packages/core/core/src/requests/BundleGraphRequest.js:247 — MethodTooLong — bundle runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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: EntryResolver.resolveEntry packages/core/core/src/requests/EntryRequest.js:160 — MethodTooLong — resolveEntry runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Hoist.fold_expr packages/transformers/js/core/src/hoist.rs:781 — MethodTooLong — fold_expr runs 131 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: NodeResolver.resolve REDACTED:80 — MethodTooLong — resolve runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RequestGraph.respondToFSEvents REDACTED:851 — MethodTooLong — respondToFSEvents runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OxvgConfig.into_jobs crates/html/src/oxvg.rs:1403 — MethodTooLong — into_jobs runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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.
D2 · Cognitive Complexity · parcel_html · ×9
  • parcel_html::package::insert_bundle_references (cognitive 108) crates/html/src/package.rs:32 — parcel_html::package::insert_bundle_references has cognitive complexity 108 (threshold 15). Drivers by points: if/else 28 (85 pts), loops 5 (14 pts), match/switch 3 (8 pts), boolean chains 1 (nesting depth added 71). 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.
  • parcel_html::jsx::to_component (cognitive 73) crates/html/src/jsx.rs:709 — parcel_html::jsx::to_component has cognitive complexity 73 (threshold 15). Drivers by points: if/else 26 (55 pts), match/switch 4 (9 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parcel_html::optimize::optimize (cognitive 66) crates/html/src/optimize.rs:68 — parcel_html::optimize::optimize has cognitive complexity 66 (threshold 15). Drivers by points: if/else 15 (49 pts), boolean chains 10, match/switch 3 (7 pts) (nesting depth added 38). 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.
  • parcel_html::srcset::parse_srcset (cognitive 64) crates/html/src/srcset.rs:50 — parcel_html::srcset::parse_srcset has cognitive complexity 64 (threshold 15). Drivers by points: if/else 13 (35 pts), match/switch 5 (18 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parcel_html::serialize_html::can_omit_start_tag (cognitive 31) crates/html/src/serialize_html.rs:331 — parcel_html::serialize_html::can_omit_start_tag has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 5 (11 pts), boolean chains 4 (nesting depth added 14). 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.
  • parcel_html::serialize_html::can_omit_end_tag (cognitive 29) crates/html/src/serialize_html.rs:395 — parcel_html::serialize_html::can_omit_end_tag has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (13 pts), match/switch 2 (3 pts) (nesting depth added 8). 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.
  • parcel_html::jsx::jsx_attr_value (cognitive 22) crates/html/src/jsx.rs:494 — parcel_html::jsx::jsx_attr_value has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3 (7 pts), boolean chains 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • parcel_html::dependencies::collect_dependencies (cognitive 20) crates/html/src/dependencies.rs:18 — parcel_html::dependencies::collect_dependencies has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (5 pts), boolean chains 1, match/switch 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.
  • parcel_html::optimize::remove_whitespace (cognitive 17) crates/html/src/optimize.rs:688 — parcel_html::optimize::remove_whitespace has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (5 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.
R11 · Import Boundaries · Boundary violation [package · ×9
  • Boundary violation [package:third-party-deep-import] packages/core/core/src/dumpGraphToGraphViz.js:69 — packages/core/core/src/dumpGraphToGraphViz.js:69 imports graphviz/lib/deps/graph, 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:test-cross-package-internals] packages/core/integration-tests/test/api.js:13 — packages/core/integration-tests/test/api.js:13 reaches past another workspace package's public entry into its internals with a relative path (../../core/src/constants) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] packages/core/workers/test/workerfarm.js:75 — packages/core/workers/test/workerfarm.js:75 reaches past another workspace package's public entry into its internals with a relative path (./integration/workerfarm/ipc.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:test-cross-package-internals] packages/core/workers/test/workerfarm.js:87 — packages/core/workers/test/workerfarm.js:87 reaches past another workspace package's public entry into its internals with a relative path (./integration/workerfarm/ipc.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
  • Boundary violation [package:third-party-deep-import] packages/transformers/stylus/src/StylusTransformer.js:8 — packages/transformers/stylus/src/StylusTransformer.js:8 imports stylus/lib/parser, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/transformers/stylus/src/StylusTransformer.js:9 — packages/transformers/stylus/src/StylusTransformer.js:9 imports stylus/lib/visitor/deps-resolver, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/transformers/stylus/src/StylusTransformer.js:10 — packages/transformers/stylus/src/StylusTransformer.js:10 imports stylus/lib/nodes, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/transformers/stylus/src/StylusTransformer.js:11 — packages/transformers/stylus/src/StylusTransformer.js:11 imports stylus/lib/utils, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] packages/transformers/stylus/src/StylusTransformer.js:12 — packages/transformers/stylus/src/StylusTransformer.js:12 imports stylus/lib/visitor/evaluator, 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.
D3 · God Classes · ClassTooLong · ×8
  • ClassTooLong: DependencyCollector packages/transformers/js/core/src/dependency_collector.rs:214 — ClassTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 5 blocks, lines 214-1738. The bar is 400 significant lines; this is 472 over it, 2.18× 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: TargetResolver packages/core/core/src/requests/TargetRequest.js:187 — ClassTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 417 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Hoist packages/transformers/js/core/src/hoist.rs:103 — ClassTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 4 blocks, lines 103-1352. The bar is 400 significant lines; this is 290 over it, 1.73× 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: Collect packages/transformers/js/core/src/collect.rs:59 — ClassTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 4 blocks, lines 59-1128. The bar is 400 significant lines; this is 224 over it, 1.56× 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: ResolveRequest crates/parcel-resolver/src/lib.rs:415 — ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 2 blocks, lines 415-1390. The bar is 400 significant lines; this is 204 over it, 1.51× 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: PackagerRunner REDACTED:109 — ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 132 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.
  • ClassTooLong: RequestGraph REDACTED:290 — ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 76 over it, 1.19× 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: NodeResolver REDACTED:71 — ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. The bar is 400 significant lines; this is 60 over it, 1.15× 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.
D2 · Cognitive Complexity · DependencyCollector · ×7
  • DependencyCollector::fold_call_expr (cognitive 228) packages/transformers/js/core/src/dependency_collector.rs:518 — DependencyCollector::fold_call_expr has cognitive complexity 228 (threshold 15). Drivers by points: if/else 60 (190 pts), match/switch 7 (30 pts), boolean chains 8 (nesting depth added 153). 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.
  • DependencyCollector::visit_element (cognitive 151) crates/html/src/dependencies.rs:170 — DependencyCollector::visit_element has cognitive complexity 151 (threshold 15). Drivers by points: if/else 52 (133 pts), boolean chains 12, loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 84). 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.
  • DependencyCollector::match_import_meta_prop (cognitive 54) packages/transformers/js/core/src/dependency_collector.rs:1535 — DependencyCollector::match_import_meta_prop has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (50 pts), match/switch 2 (4 pts) (nesting depth added 34). 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.
  • DependencyCollector::fold_new_promise (cognitive 51) packages/transformers/js/core/src/dependency_collector.rs:1133 — DependencyCollector::fold_new_promise has cognitive complexity 51 (threshold 15). Drivers by points: if/else 10 (41 pts), match/switch 3 (10 pts) (nesting depth added 38). 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.
  • DependencyCollector::fold_new_expr (cognitive 44) packages/transformers/js/core/src/dependency_collector.rs:952 — DependencyCollector::fold_new_expr has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (32 pts), match/switch 3 (10 pts), boolean chains 2 (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.
  • DependencyCollector::match_new_url (cognitive 38) packages/transformers/js/core/src/dependency_collector.rs:1400 — DependencyCollector::match_new_url has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (33 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • DependencyCollector::fold_expr (cognitive 16) packages/transformers/js/core/src/dependency_collector.rs:1062 — DependencyCollector::fold_expr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parcel_js_swc_core · ×7
  • parcel_js_swc_core::transform (cognitive 80) packages/transformers/js/core/src/lib.rs:253 — parcel_js_swc_core::transform has cognitive complexity 80 (threshold 15). Drivers by points: if/else 32 (50 pts), boolean chains 11, match/switch 7 (10 pts), loops 4 (9 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parcel_js_swc_core::targets_to_versions (cognitive 51) packages/transformers/js/core/src/lib.rs:223 — parcel_js_swc_core::targets_to_versions has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (51 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parcel_js_swc_core::dependency_collector::match_worker_type (cognitive 28) packages/transformers/js/core/src/dependency_collector.rs:1741 — parcel_js_swc_core::dependency_collector::match_worker_type has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 3 (9 pts) (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • parcel_js_swc_core::mdx::constant_exports (cognitive 28) packages/transformers/js/core/src/mdx.rs:229 — parcel_js_swc_core::mdx::constant_exports has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (20 pts), loops 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 21). 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.
  • parcel_js_swc_core::utils::match_require (cognitive 25) packages/transformers/js/core/src/utils.rs:123 — parcel_js_swc_core::utils::match_require has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (18 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • parcel_js_swc_core::mdx::parse_code_block (cognitive 24) packages/transformers/js/core/src/mdx.rs:279 — parcel_js_swc_core::mdx::parse_code_block has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (24 pts) (nesting depth added 15). 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.
  • parcel_js_swc_core::mdx::transform_js_code_block (cognitive 21) packages/transformers/js/core/src/mdx.rs:340 — parcel_js_swc_core::mdx::transform_js_code_block has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 3 (10 pts), if/else 4 (7 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 12). 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.
AC3 · Page structure · Page without a main landmark · ×6
  • Page without a main landmark packages/reporters/dev-server/src/templates/404.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark packages/reporters/dev-server/src/templates/500.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark packages/utils/create-parcel/templates/react-server/src/Page.tsx:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark packages/utils/create-parcel/templates/react-static/src/components/MDXLayout.tsx:13 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark packages/utils/create-parcel/templates/react-static/src/pages/index.tsx:9 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark packages/utils/create-parcel/templates/vanilla/src/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D1 · Cyclomatic Complexity · parcel_html · ×6
  • parcel_html::optimize::optimize (cyclomatic 70) crates/html/src/optimize.rs:68 — parcel_html::optimize::optimize has cyclomatic complexity 70 (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.
  • parcel_html::srcset::parse_srcset (cyclomatic 39) crates/html/src/srcset.rs:50 — parcel_html::srcset::parse_srcset has cyclomatic complexity 39 (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.
  • parcel_html::jsx::to_component (cyclomatic 37) crates/html/src/jsx.rs:709 — parcel_html::jsx::to_component has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: parcel_html::jsx::jsx_attr_name (cyclomatic 366) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
  • parcel_html::package::insert_bundle_references (cyclomatic 37) crates/html/src/package.rs:32 — parcel_html::package::insert_bundle_references has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • parcel_html::serialize_html::can_omit_end_tag (cyclomatic 37) crates/html/src/serialize_html.rs:395 — parcel_html::serialize_html::can_omit_end_tag has cyclomatic complexity 37 (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.
  • parcel_html::serialize_html::can_omit_start_tag (cyclomatic 18) crates/html/src/serialize_html.rs:331 — parcel_html::serialize_html::can_omit_start_tag has cyclomatic complexity 18 (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.
D2 · Cognitive Complexity · Collect · ×6
  • Collect::visit_member_expr (cognitive 39) packages/transformers/js/core/src/collect.rs:631 — Collect::visit_member_expr has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (36 pts), boolean chains 2, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Collect::visit_call_expr (cognitive 32) packages/transformers/js/core/src/collect.rs:912 — Collect::visit_call_expr has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 2 (8 pts), boolean chains 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.
  • Collect::visit_module (cognitive 24) packages/transformers/js/core/src/collect.rs:246 — Collect::visit_module has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (10 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Collect::add_pat_imports (cognitive 23) packages/transformers/js/core/src/collect.rs:959 — Collect::add_pat_imports has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 7 (18 pts), if/else 2 (3 pts), loops 1 (2 pts) (nesting depth added 13). 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.
  • Collect::visit_named_export (cognitive 20) packages/transformers/js/core/src/collect.rs:374 — Collect::visit_named_export has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • Collect::visit_expr (cognitive 16) packages/transformers/js/core/src/collect.rs:732 — Collect::visit_expr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (4 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResolveRequest · ×6
  • ResolveRequest::load_file (cognitive 30) crates/parcel-resolver/src/lib.rs:976 — ResolveRequest::load_file has cognitive complexity 30 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 3 (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.
  • ResolveRequest::resolve (cognitive 29) crates/parcel-resolver/src/lib.rs:541 — ResolveRequest::resolve has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 14). 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.
  • ResolveRequest::read_tsconfig (cognitive 27) crates/parcel-resolver/src/lib.rs:1293 — ResolveRequest::read_tsconfig has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 3 (8 pts), boolean chains 1, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ResolveRequest::resolve_package (cognitive 26) crates/parcel-resolver/src/lib.rs:798 — ResolveRequest::resolve_package has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 2, match/switch 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.
  • ResolveRequest::try_file (cognitive 24) crates/parcel-resolver/src/lib.rs:1162 — ResolveRequest::try_file has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (24 pts) (nesting depth added 15). 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.
  • ResolveRequest::try_suffixes (cognitive 23) crates/parcel-resolver/src/lib.rs:1101 — ResolveRequest::try_suffixes has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 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.
D29 · Static Analysis (SAST) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D1 · Cyclomatic Complexity · DependencyCollector · ×5
  • DependencyCollector::visit_element (cyclomatic 71) crates/html/src/dependencies.rs:170 — DependencyCollector::visit_element has cyclomatic complexity 71 (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.
  • DependencyCollector::fold_call_expr (cyclomatic 68) packages/transformers/js/core/src/dependency_collector.rs:518 — DependencyCollector::fold_call_expr has cyclomatic complexity 68 (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.
  • DependencyCollector::fold_new_expr (cyclomatic 18) packages/transformers/js/core/src/dependency_collector.rs:952 — DependencyCollector::fold_new_expr 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.
  • DependencyCollector::match_new_url (cyclomatic 16) packages/transformers/js/core/src/dependency_collector.rs:1400 — DependencyCollector::match_new_url 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.
  • DependencyCollector::match_import_meta_prop (cyclomatic 16) packages/transformers/js/core/src/dependency_collector.rs:1535 — DependencyCollector::match_import_meta_prop 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×5
  • Duplicated block (13 lines × 2) crates/html/src/dependencies.rs:350 — crates/html/src/dependencies.rs:350-362 | crates/html/src/dependencies.rs:379-391 — 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 (13 lines × 2) crates/parcel-resolver/src/tsconfig.rs:114 — crates/parcel-resolver/src/tsconfig.rs:114-126 | packages/utils/node-resolver-rs/src/tsconfig.rs:114-126 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) packages/transformers/js/core/src/collect.rs:449 — packages/transformers/js/core/src/collect.rs:449-461 | packages/transformers/js/core/src/collect.rs:463-475 — 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 (13 lines × 2) packages/transformers/js/core/src/hoist.rs:383 — packages/transformers/js/core/src/hoist.rs:383-395 | packages/transformers/js/core/src/hoist.rs:527-539 — 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 (13 lines × 2) packages/transformers/js/core/src/node_replacer.rs:101 — packages/transformers/js/core/src/node_replacer.rs:101-113 | packages/transformers/js/core/src/node_replacer.rs:149-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • Duplicated block (11 lines × 2) crates/parcel-resolver/src/package_json.rs:160 — crates/parcel-resolver/src/package_json.rs:160-170 | crates/parcel-resolver/src/package_json.rs:574-584 — 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 (11 lines × 2) packages/transformers/js/core/src/dependency_collector.rs:420 — packages/transformers/js/core/src/dependency_collector.rs:420-430 | packages/transformers/js/core/src/dependency_collector.rs:449-459 — 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 (11 lines × 2) packages/transformers/js/core/src/global_replacer.rs:83 — packages/transformers/js/core/src/global_replacer.rs:83-93 | packages/transformers/js/core/src/global_replacer.rs:103-113 — 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 (11 lines × 2) packages/transformers/js/core/src/hoist.rs:840 — packages/transformers/js/core/src/hoist.rs:840-850 | packages/transformers/js/core/src/hoist.rs:1032-1042 — 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 (11 lines × 2) crates/html/src/jsx.rs:795 — crates/html/src/jsx.rs:795-805 | crates/html/src/jsx.rs:807-817 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • Duplicated block (9 lines × 2) packages/transformers/js/core/src/dependency_collector.rs:424 — packages/transformers/js/core/src/dependency_collector.rs:424-432 | packages/transformers/js/core/src/dependency_collector.rs:478-486 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) packages/transformers/js/core/src/modules.rs:499 — packages/transformers/js/core/src/modules.rs:499-507 | packages/transformers/js/core/src/modules.rs:509-517 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) crates/parcel-resolver/src/tsconfig.rs:218 — crates/parcel-resolver/src/tsconfig.rs:218-226 | packages/utils/node-resolver-rs/src/tsconfig.rs:218-226 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) packages/transformers/js/core/src/lib.rs:797 — packages/transformers/js/core/src/lib.rs:797-805 | packages/transformers/js/core/src/lib.rs:808-816 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) packages/transformers/js/core/src/collect.rs:350 — packages/transformers/js/core/src/collect.rs:350-358 | packages/transformers/js/core/src/collect.rs:361-369 — 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.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×5
  • Untrusted text written into markup unescaped packages/dev/repl/src/components/helper.js:18 — `error` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/dev/repl/src/components/helper.js:77 — `content` is text this program did not author, and it is written into the text of an element through `document.write` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/reporters/bundle-analyzer/client/index.js:51 — `e.group.label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/reporters/bundle-analyzer/client/index.js:56 — `formatSize(e.group.weight)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped packages/utils/error-overlay/src/components/CodeBlock.js:43 — `codeHTML` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
D2 · Cognitive Complexity · Hoist · ×4
  • Hoist::fold_module (cognitive 183) packages/transformers/js/core/src/hoist.rs:376 — Hoist::fold_module has cognitive complexity 183 (threshold 15). Drivers by points: if/else 24 (125 pts), match/switch 9 (35 pts), loops 5 (20 pts), boolean chains 3 (nesting depth added 142). 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.
  • Hoist::fold_expr (cognitive 68) packages/transformers/js/core/src/hoist.rs:781 — Hoist::fold_expr has cognitive complexity 68 (threshold 15). Drivers by points: if/else 21 (55 pts), match/switch 4 (7 pts), boolean chains 6 (nesting depth added 37). 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.
  • Hoist::fold_ident (cognitive 26) packages/transformers/js/core/src/hoist.rs:1013 — Hoist::fold_ident has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 3 (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.
  • Hoist::fold_assign_expr (cognitive 26) packages/transformers/js/core/src/hoist.rs:1111 — Hoist::fold_assign_expr has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Evaluator · ×4
  • Evaluator::eval (cognitive 62) crates/macros/src/lib.rs:393 — Evaluator::eval has cognitive complexity 62 (threshold 15). Drivers by points: if/else 18 (34 pts), match/switch 8 (21 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 32). 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.
  • Evaluator::fold_expr (cognitive 39) packages/transformers/js/core/src/fs.rs:230 — Evaluator::fold_expr has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 8 (21 pts), if/else 4 (14 pts), loops 1 (4 pts) (nesting depth added 26). 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.
  • Evaluator::eval_pat (cognitive 29) crates/macros/src/lib.rs:783 — Evaluator::eval_pat has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 3 (8 pts), loops 2 (4 pts) (nesting depth added 19). 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.
  • Evaluator::eval_object (cognitive 23) crates/macros/src/lib.rs:650 — Evaluator::eval_object has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 2 (5 pts), loops 1 (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · PackageJson · ×4
  • PackageJson::resolve_package_target (cognitive 37) crates/parcel-resolver/src/package_json.rs:541 — PackageJson::resolve_package_target has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 5 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 20). 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.
  • PackageJson::resolve_alias (cognitive 37) crates/parcel-resolver/src/package_json.rs:730 — PackageJson::resolve_alias has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (29 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PackageJson::resolve_package_exports (cognitive 24) crates/parcel-resolver/src/package_json.rs:442 — PackageJson::resolve_package_exports has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (7 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.
  • PackageJson::resolve_package_imports_exports (cognitive 17) crates/parcel-resolver/src/package_json.rs:642 — PackageJson::resolve_package_imports_exports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parcel_dev_dep_resolver · ×4
  • parcel_dev_dep_resolver::skip_comments_and_whitespace (cognitive 35) crates/dev-dep-resolver/src/lib.rs:382 — parcel_dev_dep_resolver::skip_comments_and_whitespace has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 3 (11 pts), boolean chains 1 (nesting depth added 24). 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.
  • parcel_dev_dep_resolver::read_template_string (cognitive 34) crates/dev-dep-resolver/src/lib.rs:305 — parcel_dev_dep_resolver::read_template_string has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parcel_dev_dep_resolver::specifier_to_glob (cognitive 30) crates/dev-dep-resolver/src/lib.rs:222 — parcel_dev_dep_resolver::specifier_to_glob has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 2 (4 pts), boolean chains 3 (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.
  • parcel_dev_dep_resolver::skip_expression (cognitive 21) crates/dev-dep-resolver/src/lib.rs:418 — parcel_dev_dep_resolver::skip_expression has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: PluginOptions.js ↔ resolveOptions.js packages/core/core/src/public/PluginOptions.js:1 — `packages/core/core/src/public/PluginOptions.js` and `packages/core/core/src/resolveOptions.js` change together 85% of the time (11 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 11 shared commits counted here, the most recent 3 are `b8f7f90f` Add parcel version to PluginOptions (#9671); `56e5f40b` Add feature flags to ParcelOptions (#9551); `f9ea5b71` Replace options.entryRoot with bundleGraph.getEntryRoot(target) (#6608) — run `git show` on any of them.
  • Change coupling: FSCache.js ↔ LMDBCache.js packages/core/cache/src/FSCache.js:1 — `packages/core/cache/src/FSCache.js` and `packages/core/cache/src/LMDBCache.js` change together 73% of the time (11 of the 15 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 11 shared commits counted here, the most recent 3 are `d1f3ffee` Revert chunked cache blobs (#9965); `725eba8d` Revert transactional large blob entries (#9836); `d988abeb` Implement transactional large blob cache writes (#9726) — run `git show` on any of them.
  • Change coupling: Parcel.js ↔ worker.js packages/core/core/src/Parcel.js:1 — `packages/core/core/src/Parcel.js` and `packages/core/core/src/worker.js` change together 70% of the time (23 of the 33 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 23 shared commits counted here, the most recent 3 are `a24a30d2` Implements a `getFeatureFlag` to avoid option drilling (#9618); `d741b10c` Move registerCoreWithSerializer to its own file (#9396); `10620104` Browser version of xxhash (#6377) — run `git show` on any of them.
  • Change coupling: REDACTED ↔ Validation.js REDACTED:1 — `REDACTED` and `packages/core/core/src/Validation.js` change together 56% of the time (9 of the 16 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 9 shared commits counted here, the most recent 3 are `2d40ce5f` Drop per-pipeline transformation cache (#9459); `0a3b4372` Update Flow to v0.146.0 (#5971); `d5aece28` Add fallback for filePath to errorToDiagnostic (#5811) — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) crates/html/src/dependencies.rs:299 — crates/html/src/dependencies.rs:299-308 | crates/html/src/dependencies.rs:317-326 — 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 (10 lines × 2) crates/html/src/oxvg.rs:1069 — crates/html/src/oxvg.rs:1069-1078 | crates/html/src/oxvg.rs:1097-1106 — 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 (10 lines × 2) packages/transformers/js/core/src/collect.rs:970 — packages/transformers/js/core/src/collect.rs:970-979 | packages/transformers/js/core/src/collect.rs:1072-1081 — 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 (10 lines × 2) packages/transformers/js/core/src/global_replacer.rs:160 — packages/transformers/js/core/src/global_replacer.rs:160-169 | packages/transformers/js/core/src/node_replacer.rs:181-191 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) crates/macros/src/lib.rs:209 — crates/macros/src/lib.rs:209-215 | crates/macros/src/lib.rs:237-243 — 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 (7 lines × 2) crates/parcel-resolver/src/tsconfig.rs:85 — crates/parcel-resolver/src/tsconfig.rs:85-91 | packages/utils/node-resolver-rs/src/tsconfig.rs:85-91 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) crates/parcel-resolver/src/tsconfig.rs:206 — crates/parcel-resolver/src/tsconfig.rs:206-212 | packages/utils/node-resolver-rs/src/tsconfig.rs:206-212 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) packages/transformers/js/core/src/dependency_collector.rs:611 — packages/transformers/js/core/src/dependency_collector.rs:611-617 | packages/transformers/js/core/src/dependency_collector.rs:620-626 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) crates/parcel-resolver/src/tsconfig.rs:74 — crates/parcel-resolver/src/tsconfig.rs:74-78 | packages/utils/node-resolver-rs/src/tsconfig.rs:74-78 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/parcel-resolver/src/tsconfig.rs:201 — crates/parcel-resolver/src/tsconfig.rs:201-205 | packages/utils/node-resolver-rs/src/tsconfig.rs:201-205 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/html/src/serialize_html.rs:309 — crates/html/src/serialize_html.rs:309-313 | crates/html/src/serialize_xml.rs:210-214 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) crates/html/src/serialize_html.rs:315 — crates/html/src/serialize_html.rs:315-319 | crates/html/src/serialize_xml.rs:217-221 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D44 · Platform End-of-Life · End-of-life runtime · ×4
  • End-of-life runtime: Node.js 10 packages/optimizers/esbuild/package.json:19 — packages/optimizers/esbuild/package.json declares Node.js 10 as this project's engines.node, and Node.js 10, support ended 2021-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 12 packages/runtimes/rsc/package.json:27 — packages/runtimes/rsc/package.json declares Node.js 12 as this project's engines.node, and Node.js 12, support ended 2022-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 14 packages/optimizers/inline-requires/package.json:19 — packages/optimizers/inline-requires/package.json declares Node.js 14 as this project's engines.node, and Node.js 14, support ended 2023-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 16 package.json:70 — package.json declares Node.js 16 as this project's engines.node, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
R10 · Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) · ×4
  • Duplicated block with local edits (19 matched lines × 2 locations) packages/core/core/src/CommittedAsset.js:63 — packages/core/core/src/CommittedAsset.js:63 · REDACTED:170 — the two spans are one implementation copied and then locally edited — 124 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (19 matched lines × 2 locations) REDACTED:238 — REDACTED:238 · REDACTED:210 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (19 matched lines × 2 locations) packages/core/core/src/requests/BundleGraphRequest.js:221 — packages/core/core/src/requests/BundleGraphRequest.js:221 · REDACTED:216 — the two spans are one implementation copied and then locally edited — 124 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (19 matched lines × 2 locations) packages/optimizers/css/src/CSSOptimizer.js:170 — packages/optimizers/css/src/CSSOptimizer.js:170 · packages/optimizers/cssnano/src/CSSNanoOptimizer.js:56 — the two spans are one implementation copied and then locally edited — 83 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×4
  • Async function without AbortSignal: init packages/core/rust/src/browser.js:5 — `init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: _npmResolve packages/dev/repl/SimplePackageInstaller/index.js:55 — `_npmResolve` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: _npmFetch packages/dev/repl/SimplePackageInstaller/index.js:102 — `_npmFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: getStackFrames packages/utils/error-overlay/src/utils/getStackFrames.js:17 — `getStackFrames` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) packages/core/fs/src/NodeFS.js:226 — `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:500 — `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) packages/transformers/sass/src/modern.js:172 — `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:138 — `catch (err)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D1 · Cyclomatic Complexity · Evaluator · ×3
  • Evaluator::eval (cyclomatic 96) crates/macros/src/lib.rs:393 — Evaluator::eval has cyclomatic complexity 96 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • Evaluator::eval_pat (cyclomatic 19) crates/macros/src/lib.rs:783 — Evaluator::eval_pat has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • Evaluator::fold_expr (cyclomatic 16) packages/transformers/js/core/src/fs.rs:230 — Evaluator::fold_expr has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ResolveRequest · ×3
  • ResolveRequest::resolve (cyclomatic 20) crates/parcel-resolver/src/lib.rs:541 — ResolveRequest::resolve has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • ResolveRequest::load_file (cyclomatic 19) crates/parcel-resolver/src/lib.rs:976 — ResolveRequest::load_file 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.
  • ResolveRequest::resolve_package (cyclomatic 16) crates/parcel-resolver/src/lib.rs:798 — ResolveRequest::resolve_package 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.
D2 · Cognitive Complexity · InlineFS · ×3
  • InlineFS::evaluate_fs_arg (cognitive 27) packages/transformers/js/core/src/fs.rs:122 — InlineFS::evaluate_fs_arg has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 5 (10 pts) (nesting depth added 13). 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.
  • InlineFS::fold_expr (cognitive 22) packages/transformers/js/core/src/fs.rs:58 — InlineFS::fold_expr has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (21 pts), boolean chains 1 (nesting depth added 15). 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.
  • InlineFS::match_module_reference (cognitive 21) packages/transformers/js/core/src/fs.rs:78 — InlineFS::match_module_reference has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). 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.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D5 · Coupling · Off the main sequence · ×3
  • Off the main sequence: parcel-core — parcel-core: 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: parcel-macros — parcel-macros: 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: parcel-resolver — parcel-resolver: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
D1 · Cyclomatic Complexity · parcel_js_swc_core · ×2
  • parcel_js_swc_core::transform (cyclomatic 50) packages/transformers/js/core/src/lib.rs:253 — parcel_js_swc_core::transform has cyclomatic complexity 50 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • parcel_js_swc_core::targets_to_versions (cyclomatic 22) packages/transformers/js/core/src/lib.rs:223 — parcel_js_swc_core::targets_to_versions has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Hoist · ×2
  • Hoist::fold_module (cyclomatic 45) packages/transformers/js/core/src/hoist.rs:376 — Hoist::fold_module 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.
  • Hoist::fold_expr (cyclomatic 37) packages/transformers/js/core/src/hoist.rs:781 — Hoist::fold_expr has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Collect · ×2
  • Collect::add_pat_imports (cyclomatic 24) packages/transformers/js/core/src/collect.rs:959 — Collect::add_pat_imports has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • Collect::visit_member_expr (cyclomatic 22) packages/transformers/js/core/src/collect.rs:631 — Collect::visit_member_expr has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · cli.run · ×2
  • cli.run::findAssetWithSymbol (cyclomatic 21) REDACTED:203 — cli.run::findAssetWithSymbol 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. This shape REPEATS in the file: one other method here (cli.run::stats) 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.
  • cli.run::stats (cyclomatic 21) REDACTED:806 — cli.run::stats 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. This shape REPEATS in the file: one other method here (cli.run::findAssetWithSymbol) 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.
D17 · Explicit Debt · FixmeComment · ×2
  • FixmeComment crates/html/src/serialize_html.rs:63 — // FIXME(#122)
  • FixmeComment crates/html/src/serialize_html.rs:197 — // FIXME(#122)
D2 · Cognitive Complexity · EnvReplacer · ×2
  • EnvReplacer::visit_mut_expr (cognitive 80) packages/transformers/js/core/src/env_replacer.rs:30 — EnvReplacer::visit_mut_expr has cognitive complexity 80 (threshold 15). Drivers by points: if/else 24 (65 pts), match/switch 4 (13 pts), boolean chains 2 (nesting depth added 50). 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.
  • EnvReplacer::collect_pat_bindings (cognitive 24) packages/transformers/js/core/src/env_replacer.rs:266 — EnvReplacer::collect_pat_bindings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 15). 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 · cli.run · ×2
  • cli.run::findAssetWithSymbol (cognitive 48) REDACTED:203 — cli.run::findAssetWithSymbol has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (28 pts), loops 4 (9 pts), error handling 2 (7 pts), boolean chains 4 (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (cli.run::stats) 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.
  • cli.run::stats (cognitive 33) REDACTED:806 — cli.run::stats has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (cli.run::findAssetWithSymbol) 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 · ConstantModule · ×2
  • ConstantModule::is_constant_declarator (cognitive 21) packages/transformers/js/core/src/constant_module.rs:52 — ConstantModule::is_constant_declarator has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 2 (6 pts), loops 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ConstantModule::visit_module (cognitive 18) packages/transformers/js/core/src/constant_module.rs:110 — ConstantModule::visit_module has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 3 (8 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TsConfig · ×2
  • TsConfig::paths (cognitive 20) crates/parcel-resolver/src/tsconfig.rs:128 — TsConfig::paths has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • TsConfig::paths (cognitive 20) packages/utils/node-resolver-rs/src/tsconfig.rs:128 — TsConfig::paths has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×2
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) crates/core/src/environment.rs:350 — crates/core/src/environment.rs:350-355 | crates/core/src/environment.rs:364-369 — 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 (6 lines × 2) packages/transformers/js/core/src/dependency_collector.rs:657 — packages/transformers/js/core/src/dependency_collector.rs:657-662 | packages/transformers/js/core/src/dependency_collector.rs:675-680 — 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 (28 lines × 2 locations) · ×2
  • Duplicated block (28 lines × 2 locations) packages/reporters/dev-server-sw/src/HMRServer.js:51 — packages/reporters/dev-server-sw/src/HMRServer.js:51 · REDACTED:214 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (28 lines × 2 locations) packages/transformers/typescript-types/src/TSTypesTransformer.js:102 — packages/transformers/typescript-types/src/TSTypesTransformer.js:102 · packages/validators/typescript/src/TypeScriptValidator.js:159 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (23 matched lines × 2 locations) packages/core/core/src/loadParcelPlugin.js:46 — packages/core/core/src/loadParcelPlugin.js:46 · packages/core/core/src/loadParcelPlugin.js:146 — the two spans are one implementation copied and then locally edited — 82 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (23 matched lines × 2 locations) packages/core/package-manager/src/Npm.js:49 — packages/core/package-manager/src/Npm.js:49 · REDACTED:149 — the two spans are one implementation copied and then locally edited — 85 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) · ×2
  • Duplicated block (22 lines × 2 locations) packages/core/graph/src/AdjacencyList.js:1174 — packages/core/graph/src/AdjacencyList.js:1174 · packages/core/graph/src/AdjacencyList.js:1212 — 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 (22 lines × 2 locations) packages/optimizers/css/src/CSSOptimizer.js:108 — packages/optimizers/css/src/CSSOptimizer.js:108 · REDACTED:289 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×2
  • Duplicated block (20 lines × 2 locations) REDACTED:382 — REDACTED:382 · packages/core/package-manager/src/installPackage.js:115 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
  • Duplicated block (20 lines × 2 locations) packages/utils/create-parcel/templates/react-server/src/client.tsx:39 — packages/utils/create-parcel/templates/react-server/src/client.tsx:39 · packages/utils/create-parcel/templates/react-static/src/client.tsx:26 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) packages/transformers/svg-jsx/src/SvgJsxTransformer.js:15 — packages/transformers/svg-jsx/src/SvgJsxTransformer.js:15 · packages/transformers/svg-react/src/SvgReactTransformer.js:13 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (19 lines × 2 locations) packages/transformers/typescript-types/src/wrappers.js:109 — packages/transformers/typescript-types/src/wrappers.js:109 · packages/transformers/typescript-types/src/wrappers.js:146 — 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.
R7 · Dead Code · Dead file (~11 LoC) · ×2
  • Dead file (~11 LoC) flow-libs/deasync.js — no import path from any entry point (289 application, 23 tooling, 187 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~11 LoC) packages/core/utils/src/parseCSSImport.js — no import path from any entry point (289 application, 23 tooling, 187 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
R8 · Dependency Hygiene · Unlisted import '@parcel/watcher' · ×2
  • Unlisted import '@parcel/watcher' REDACTED:22 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
  • Unlisted import '@parcel/watcher' packages/core/types-internal/src/FileSystem.js:4 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
R8 · Dependency Hygiene · Unlisted import 'vscode-languageserver' · ×2
  • Unlisted import 'vscode-languageserver' packages/reporters/lsp-reporter/src/LspReporter.js:6 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
  • Unlisted import 'vscode-languageserver' packages/utils/parcel-lsp-protocol/src/index.js:12 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×2
  • Recursive walk over a caller-supplied document has no depth cap packages/transformers/typescript-types/src/shake.js:40 — `shake` is exported, takes a document from its caller (line 15) and hands it to `visit`, which calls itself at line 40 (`visit`) with a piece of `node` (and at line 63, line 75, line 171, line 246) — and nowhere in `visit` 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 `visit` 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/transformers/typescript-types/src/collect.js:23 — `collect` is exported, takes a document from its caller (line 9) and hands it to `visit`, which calls itself at line 23 (`visit`) with a piece of `node` (and at line 33, line 86) — and nowhere in `visit` 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 `visit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement packages/dev/repl/src/styles/app.css:34 — `.resize-handle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 21 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · DefaultBundler.createIdealGraph (cyclomatic 199) · ×1
  • DefaultBundler.createIdealGraph (cyclomatic 199) REDACTED:364 — DefaultBundler.createIdealGraph has cyclomatic complexity 199 (threshold 15). Of this number, 142 points are the body's own statements and 57 belong to 13 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 · transform (cyclomatic 174) · ×1
  • transform (cyclomatic 174) REDACTED:336 — transform has cyclomatic complexity 174 (threshold 15). Of this number, 140 points are the body's own statements and 34 belong to 14 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 · OxvgConfig · ×1
  • OxvgConfig::into_jobs (cyclomatic 160) crates/html/src/oxvg.rs:1403 — OxvgConfig::into_jobs has cyclomatic complexity 160 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · resolvePackageTargets (cyclomatic 144) · ×1
  • resolvePackageTargets (cyclomatic 144) packages/core/core/src/requests/TargetRequest.js:440 — resolvePackageTargets has cyclomatic complexity 144 (threshold 15). Of this number, 133 points are the body's own statements and 11 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 · propagateSymbols (cyclomatic 88) · ×1
  • propagateSymbols (cyclomatic 88) packages/core/core/src/SymbolPropagation.js:22 — propagateSymbols has cyclomatic complexity 88 (threshold 15). Most of this is not in the body itself: 2 of the 88 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 257, a function literal at line 62, (anonymous)::usedSymbolsUpAmbiguous, …). 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 · package (cyclomatic 73) · ×1
  • package (cyclomatic 73) packages/packagers/js/src/DevPackager.js:46 — package has cyclomatic complexity 73 (threshold 15). Of this number, 40 points are the body's own statements and 33 belong to 6 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 · apply (cyclomatic 67) · ×1
  • apply (cyclomatic 67) packages/runtimes/rsc/src/RSCRuntime.js:30 — apply has cyclomatic complexity 67 (threshold 15). Most of this is not in the body itself: 8 of the 67 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 40, 281, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · collectDependencies (cyclomatic 58) · ×1
  • collectDependencies (cyclomatic 58) REDACTED:39 — collectDependencies has cyclomatic complexity 58 (threshold 15). Of this number, 57 points are the body's own statements and 1 belongs 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 · dumpGraphToGraphViz (cyclomatic 55) · ×1
  • dumpGraphToGraphViz (cyclomatic 55) packages/core/core/src/dumpGraphToGraphViz.js:38 — dumpGraphToGraphViz has cyclomatic complexity 55 (threshold 15). Of this number, 52 points are the body's own statements and 3 belong to 8 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 · shake (cyclomatic 51) · ×1
  • shake (cyclomatic 51) packages/transformers/typescript-types/src/shake.js:15 — shake has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 3 of the 51 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 38, a function literal at line 138, a function literal at line 180, …). 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 · VueTransformer.processPipeline (cyclomatic 50) · ×1
  • VueTransformer.processPipeline (cyclomatic 50) packages/transformers/vue/src/VueTransformer.js:202 — VueTransformer.processPipeline has cyclomatic complexity 50 (threshold 15). Of this number, 34 points are the body's own statements and 16 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 · shake.shake · ×1
  • shake.shake::visit (cyclomatic 48) packages/transformers/typescript-types/src/shake.js:38 — shake.shake::visit has cyclomatic complexity 48 (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 · createIdealGraph · ×1
  • createIdealGraph::enter (cyclomatic 48) REDACTED:529 — createIdealGraph::enter has cyclomatic complexity 48 (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 · buildAsset (cyclomatic 48) · ×1
  • buildAsset (cyclomatic 48) REDACTED:466 — buildAsset has cyclomatic complexity 48 (threshold 15). Of this number, 33 points are the body's own statements and 15 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 · transform (cyclomatic 48) · ×1
  • transform (cyclomatic 48) REDACTED:44 — transform has cyclomatic complexity 48 (threshold 15). Of this number, 41 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · getSymbolResolution (cyclomatic 47) · ×1
  • getSymbolResolution (cyclomatic 47) REDACTED:983 — getSymbolResolution has cyclomatic complexity 47 (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 · buildAssetPrelude (cyclomatic 47) · ×1
  • buildAssetPrelude (cyclomatic 47) REDACTED:1151 — buildAssetPrelude has cyclomatic complexity 47 (threshold 15). Of this number, 40 points are the body's own statements and 7 belong to 5 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 · codeFrame (cyclomatic 45) · ×1
  • codeFrame (cyclomatic 45) packages/core/codeframe/src/codeframe.js:42 — codeFrame has cyclomatic complexity 45 (threshold 15). Of this number, 37 points are the body's own statements and 8 belong to 11 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 · _report (cyclomatic 45) · ×1
  • _report (cyclomatic 45) packages/reporters/cli/src/CLIReporter.js:43 — _report has cyclomatic complexity 45 (threshold 15). Of this number, 44 points are the body's own statements and 1 belongs 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 · resolveOptions (cyclomatic 44) · ×1
  • resolveOptions (cyclomatic 44) packages/core/core/src/resolveOptions.js:47 — resolveOptions has cyclomatic complexity 44 (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 · schema.validateSchema · ×1
  • schema.validateSchema::walk (cyclomatic 43) packages/core/utils/src/schema.js:116 — schema.validateSchema::walk has cyclomatic complexity 43 (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 · loadConfig (cyclomatic 42) · ×1
  • loadConfig (cyclomatic 42) REDACTED:181 — loadConfig has cyclomatic complexity 42 (threshold 15). Of this number, 40 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ESMFold · ×1
  • ESMFold::fold_module (cyclomatic 39) packages/transformers/js/core/src/modules.rs:280 — ESMFold::fold_module has cyclomatic complexity 39 (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 · reducer (cyclomatic 38) · ×1
  • reducer (cyclomatic 38) packages/dev/repl/src/components/state.js:81 — reducer has cyclomatic complexity 38 (threshold 15). Of this number, 34 points are the body's own statements and 4 belong to 9 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 · RequestGraph.respondToFSEvents (cyclomatic 37) · ×1
  • RequestGraph.respondToFSEvents (cyclomatic 37) REDACTED:851 — RequestGraph.respondToFSEvents has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NodeResolver.resolve (cyclomatic 37) · ×1
  • NodeResolver.resolve (cyclomatic 37) REDACTED:80 — NodeResolver.resolve has cyclomatic complexity 37 (threshold 15). Of this number, 33 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 36) · ×1
  • (anonymous) (cyclomatic 36) packages/packagers/js/src/dev-prelude.js:9 — (anonymous) has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 12 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 · addExternal (cyclomatic 35) · ×1
  • addExternal (cyclomatic 35) REDACTED:812 — addExternal has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · report (cyclomatic 34) · ×1
  • report (cyclomatic 34) packages/reporters/dev-server/src/ServerReporter.js:13 — report has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs 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 · DevPackager.this.bundle.traverse() (cyclomatic 33) · ×1
  • DevPackager.this.bundle.traverse() (cyclomatic 33) packages/packagers/js/src/DevPackager.js:72 — DevPackager.this.bundle.traverse() has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · package (cyclomatic 33) · ×1
  • package (cyclomatic 33) REDACTED:21 — package has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 9 of the 33 points are its own statements and the rest belongs to 8 function items inside it that branch (exit, a function literal at line 108, a function literal at line 91, …). 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 · collect (cyclomatic 33) · ×1
  • collect (cyclomatic 33) packages/transformers/typescript-types/src/collect.js:9 — collect has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 21, 118). 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 · EnvReplacer · ×1
  • EnvReplacer::visit_mut_expr (cyclomatic 32) packages/transformers/js/core/src/env_replacer.rs:30 — EnvReplacer::visit_mut_expr has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resolve (cyclomatic 32) · ×1
  • resolve (cyclomatic 32) packages/core/core/src/requests/TargetRequest.js:200 — resolve has cyclomatic complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 7 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 · apply (cyclomatic 32) · ×1
  • apply (cyclomatic 32) REDACTED:69 — apply has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DefaultBundler.decorateLegacyGraph (cyclomatic 31) · ×1
  • DefaultBundler.decorateLegacyGraph (cyclomatic 31) REDACTED:157 — DefaultBundler.decorateLegacyGraph has cyclomatic complexity 31 (threshold 15). Of this number, 25 points are the body's own statements and 6 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 · debugResolvedTargets (cyclomatic 31) · ×1
  • debugResolvedTargets (cyclomatic 31) packages/core/core/src/requests/TargetRequest.js:1539 — debugResolvedTargets has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · loadPlugin (cyclomatic 30) · ×1
  • loadPlugin (cyclomatic 30) packages/core/core/src/loadParcelPlugin.js:24 — loadPlugin has cyclomatic complexity 30 (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 · getSymbolResolution (cyclomatic 29) · ×1
  • getSymbolResolution (cyclomatic 29) REDACTED:1658 — getSymbolResolution has cyclomatic complexity 29 (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 · handleError (cyclomatic 29) · ×1
  • handleError (cyclomatic 29) REDACTED:404 — handleError has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · normalizeOptions (cyclomatic 29) · ×1
  • normalizeOptions (cyclomatic 29) packages/core/parcel/src/cli.js:431 — normalizeOptions has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · transform (cyclomatic 29) · ×1
  • transform (cyclomatic 29) packages/transformers/postcss/src/PostCSSTransformer.js:53 — transform has cyclomatic complexity 29 (threshold 15). Of this number, 25 points are the body's own statements and 4 belong to 7 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 · collect.collect · ×1
  • collect.collect::visit (cyclomatic 28) packages/transformers/typescript-types/src/collect.js:21 — collect.collect::visit has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Engines · ×1
  • Engines::supports (cyclomatic 28) crates/core/src/environment.rs:396 — Engines::supports has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · resolve (cyclomatic 28) · ×1
  • resolve (cyclomatic 28) REDACTED:247 — resolve has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EntryResolver.resolveEntry (cyclomatic 27) · ×1
  • EntryResolver.resolveEntry (cyclomatic 27) packages/core/core/src/requests/EntryRequest.js:160 — EntryResolver.resolveEntry 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 · package (cyclomatic 27) · ×1
  • package (cyclomatic 27) REDACTED:130 — package has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 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 · propagateSymbolsUp (cyclomatic 27) · ×1
  • propagateSymbolsUp (cyclomatic 27) packages/core/core/src/SymbolPropagation.js:595 — propagateSymbolsUp has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 7 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 · StackFrame.StackFrame (cyclomatic 26) · ×1
  • StackFrame.StackFrame (cyclomatic 26) REDACTED:55 — StackFrame.StackFrame has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · resolve (cyclomatic 26) · ×1
  • resolve (cyclomatic 26) packages/resolvers/glob/src/GlobResolver.js:36 — resolve has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs 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 · Environment.createEnvironment (cyclomatic 25) · ×1
  • Environment.createEnvironment (cyclomatic 25) packages/core/core/src/Environment.js:23 — Environment.createEnvironment has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · buildReplacements (cyclomatic 25) · ×1
  • buildReplacements (cyclomatic 25) REDACTED:705 — buildReplacements 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 · prettyDiagnostic (cyclomatic 25) · ×1
  • prettyDiagnostic (cyclomatic 25) packages/core/utils/src/prettyDiagnostic.js:33 — prettyDiagnostic 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 · cli.run (cyclomatic 24) · ×1
  • cli.run (cyclomatic 24) packages/core/parcel/src/cli.js:277 — cli.run has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 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 · Specifier · ×1
  • Specifier::parse (cyclomatic 24) crates/parcel-resolver/src/specifier.rs:73 — Specifier::parse 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 · buildBundlePrelude (cyclomatic 24) · ×1
  • buildBundlePrelude (cyclomatic 24) REDACTED:1365 — buildBundlePrelude has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs 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 · loadBundleUncached.loadAsset (cyclomatic 24) · ×1
  • loadBundleUncached.loadAsset (cyclomatic 24) packages/packagers/react-static/src/ReactStaticPackager.js:376 — loadBundleUncached.loadAsset has cyclomatic complexity 24 (threshold 15). Of this number, 12 points are the body's own statements and 12 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · load (cyclomatic 24) · ×1
  • load (cyclomatic 24) REDACTED:40 — load has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · applyRuntimes.applyRuntimes (cyclomatic 23) · ×1
  • applyRuntimes.applyRuntimes (cyclomatic 23) packages/core/core/src/applyRuntimes.js:45 — applyRuntimes.applyRuntimes has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 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 · JSRuntime.getLoaderRuntime (cyclomatic 23) · ×1
  • JSRuntime.getLoaderRuntime (cyclomatic 23) REDACTED:321 — JSRuntime.getLoaderRuntime 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 · PackageJson · ×1
  • PackageJson::resolve_package_target (cyclomatic 23) crates/parcel-resolver/src/package_json.rs:541 — PackageJson::resolve_package_target 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 · diagnostic (cyclomatic 23) · ×1
  • diagnostic (cyclomatic 23) packages/core/utils/src/schema.js:380 — diagnostic has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 417, 487, 429, …). 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 · startDevServer (cyclomatic 23) · ×1
  • startDevServer (cyclomatic 23) packages/reporters/dev-server/src/ServerReporter.js:111 — startDevServer 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 · patchConsole (cyclomatic 23) · ×1
  • patchConsole (cyclomatic 23) packages/utils/error-overlay/src/listenToRuntimeErrors.js:57 — patchConsole 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 5 function literals inside it that branch (lines 60, 79, 66, …). 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 · ReactLazy · ×1
  • ReactLazy::visit_call_expr (cyclomatic 22) packages/transformers/js/core/src/react_lazy.rs:29 — ReactLazy::visit_call_expr has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Options (cyclomatic 22) · ×1
  • Options (cyclomatic 22) packages/dev/repl/src/components/Options.js:14 — Options has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 21 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · optimize (cyclomatic 22) · ×1
  • optimize (cyclomatic 22) packages/optimizers/css/src/CSSOptimizer.js:71 — optimize has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 90, 106). 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 · Transformation.runPipeline (cyclomatic 21) · ×1
  • Transformation.runPipeline (cyclomatic 21) REDACTED:348 — Transformation.runPipeline has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 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 · fromAssetGraph · ×1
  • fromAssetGraph::walk (cyclomatic 21) REDACTED:194 — fromAssetGraph::walk 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 · isAssetReachableFromBundle (cyclomatic 21) · ×1
  • isAssetReachableFromBundle (cyclomatic 21) REDACTED:1222 — isAssetReachableFromBundle has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 1272, 1242, 1259, …). 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 · transform (cyclomatic 21) · ×1
  • transform (cyclomatic 21) packages/transformers/typescript-types/src/TSTypesTransformer.js:23 — transform has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 6 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 · CLIReporter.writeDiagnostic (cyclomatic 20) · ×1
  • CLIReporter.writeDiagnostic (cyclomatic 20) packages/reporters/cli/src/CLIReporter.js:215 — CLIReporter.writeDiagnostic has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · hmr-runtime.handleMessage (cyclomatic 20) · ×1
  • hmr-runtime.handleMessage (cyclomatic 20) packages/runtimes/hmr/src/loaders/hmr-runtime.js:204 — hmr-runtime.handleMessage has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HtmlSerializer · ×1
  • HtmlSerializer::start_elem (cyclomatic 20) crates/html/src/serialize_html.rs:154 — HtmlSerializer::start_elem has cyclomatic complexity 20 (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 · handleRequest (cyclomatic 20) · ×1
  • handleRequest (cyclomatic 20) packages/core/workers/src/child.js:122 — handleRequest has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · install (cyclomatic 20) · ×1
  • install (cyclomatic 20) REDACTED:84 — install has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · convertSVGOConfig (cyclomatic 20) · ×1
  • convertSVGOConfig (cyclomatic 20) packages/core/utils/src/svgo.js:58 — convertSVGOConfig has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · transform (cyclomatic 20) · ×1
  • transform (cyclomatic 20) packages/transformers/image/src/ImageTransformer.js:38 — transform has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.Output (cyclomatic 19) · ×1
  • index.Output (cyclomatic 19) packages/dev/repl/src/index.js:90 — index.Output has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 175, build, a function literal at line 146, …). 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 · RequireInliningVisitor.visitVariableDeclaration (cyclomatic 19) · ×1
  • RequireInliningVisitor.visitVariableDeclaration (cyclomatic 19) packages/optimizers/inline-requires/src/RequireInliningVisitor.js:75 — RequireInliningVisitor.visitVariableDeclaration 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 · modern.resolvePathImporter.canonicalize (cyclomatic 19) · ×1
  • modern.resolvePathImporter.canonicalize (cyclomatic 19) packages/transformers/sass/src/modern.js:85 — modern.resolvePathImporter.canonicalize 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 · Browsers · ×1
  • Browsers::fmt (cyclomatic 19) crates/core/src/environment.rs:166 — Browsers::fmt 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 · resolveBuiltin (cyclomatic 19) · ×1
  • resolveBuiltin (cyclomatic 19) REDACTED:254 — resolveBuiltin 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 · runTransformer (cyclomatic 19) · ×1
  • runTransformer (cyclomatic 19) REDACTED:564 — runTransformer has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · resolve (cyclomatic 19) · ×1
  • resolve (cyclomatic 19) REDACTED:278 — resolve 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 · sendIndex (cyclomatic 19) · ×1
  • sendIndex (cyclomatic 19) packages/reporters/dev-server/src/Server.js:173 — sendIndex 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 · resolvePathImporter.canonicalize (cyclomatic 19) · ×1
  • resolvePathImporter.canonicalize (cyclomatic 19) packages/transformers/sass/src/modern.js:85 — resolvePathImporter.canonicalize 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 · StylusTransformer.getDependencies (cyclomatic 18) · ×1
  • StylusTransformer.getDependencies (cyclomatic 18) packages/transformers/stylus/src/StylusTransformer.js:117 — StylusTransformer.getDependencies has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 154). 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 · build-native.build (cyclomatic 18) · ×1
  • build-native.build (cyclomatic 18) scripts/build-native.js:13 — build-native.build has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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 · parcel_dev_dep_resolver · ×1
  • parcel_dev_dep_resolver::read_template_string (cyclomatic 18) crates/dev-dep-resolver/src/lib.rs:305 — parcel_dev_dep_resolver::read_template_string 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 · report (cyclomatic 18) · ×1
  • report (cyclomatic 18) packages/reporters/lsp-reporter/src/LspReporter.js:154 — report has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · serializer.mapObject · ×1
  • serializer.mapObject::walk::processKey (cyclomatic 17) packages/core/core/src/serializer.js:90 — serializer.mapObject::walk::processKey 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 · SymbolPropagation.propagateSymbolsDown (cyclomatic 17) · ×1
  • SymbolPropagation.propagateSymbolsDown (cyclomatic 17) packages/core/core/src/SymbolPropagation.js:498 — SymbolPropagation.propagateSymbolsDown has cyclomatic complexity 17 (threshold 15). 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, 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 · HTMLNanoOptimizer.mapSVG (cyclomatic 17) · ×1
  • HTMLNanoOptimizer.mapSVG (cyclomatic 17) REDACTED:160 — HTMLNanoOptimizer.mapSVG 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 · HMRServer.serveCodeFrame (cyclomatic 17) · ×1
  • HMRServer.serveCodeFrame (cyclomatic 17) REDACTED:384 — HMRServer.serveCodeFrame 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 · bundle (cyclomatic 17) · ×1
  • bundle (cyclomatic 17) packages/core/core/src/requests/BundleGraphRequest.js:247 — bundle 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 · getConfigFrom (cyclomatic 17) · ×1
  • getConfigFrom (cyclomatic 17) REDACTED:132 — getConfigFrom has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · name (cyclomatic 17) · ×1
  • name (cyclomatic 17) packages/namers/default/src/DefaultNamer.js:20 — name has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · AssetGraphBuilder.shouldVisitChild (cyclomatic 16) · ×1
  • AssetGraphBuilder.shouldVisitChild (cyclomatic 16) packages/core/core/src/requests/AssetGraphRequest.js:345 — AssetGraphBuilder.shouldVisitChild has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MemoryFS.readdirSync (cyclomatic 16) · ×1
  • MemoryFS.readdirSync (cyclomatic 16) packages/core/fs/src/MemoryFS.js:284 — MemoryFS.readdirSync 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 · HMRServer.handle (cyclomatic 16) · ×1
  • HMRServer.handle (cyclomatic 16) REDACTED:143 — HMRServer.handle 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 · HMRServer.getUpdate (cyclomatic 16) · ×1
  • HMRServer.getUpdate (cyclomatic 16) REDACTED:243 — HMRServer.getUpdate has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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 · loadConfig.configHydrator (cyclomatic 16) · ×1
  • loadConfig.configHydrator (cyclomatic 16) packages/transformers/postcss/src/loadConfig.js:27 — loadConfig.configHydrator has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · buildExportedSymbols (cyclomatic 16) · ×1
  • buildExportedSymbols (cyclomatic 16) REDACTED:364 — buildExportedSymbols 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 · findSourceMap (cyclomatic 16) · ×1
  • findSourceMap (cyclomatic 16) REDACTED:541 — findSourceMap has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · errorToDiagnostic (cyclomatic 16) · ×1
  • errorToDiagnostic (cyclomatic 16) packages/core/diagnostic/src/diagnostic.js:132 — errorToDiagnostic has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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 · (anonymous) (cyclomatic 16) · ×1
  • (anonymous) (cyclomatic 16) packages/dev/repl/src/sw.js:105 — (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 13 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 · fork (cyclomatic 16) · ×1
  • fork (cyclomatic 16) packages/core/workers/src/Worker.js:50 — fork 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 · updateExportDeclaration (cyclomatic 16) · ×1
  • updateExportDeclaration (cyclomatic 16) packages/transformers/typescript-types/src/wrappers.js:100 — updateExportDeclaration 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 6 function literals inside it that branch (lines 108, 110, 128, …). 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 · createDependency (cyclomatic 16) · ×1
  • createDependency (cyclomatic 16) REDACTED:48 — createDependency has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · optimize (cyclomatic 16) · ×1
  • optimize (cyclomatic 16) packages/optimizers/terser/src/TerserOptimizer.js:21 — optimize 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 · package (cyclomatic 16) · ×1
  • package (cyclomatic 16) packages/packagers/webextension/src/WebExtensionPackager.js:9 — package has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 13 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.
D12 · Dependency Hygiene · Yanked release · ×1
  • Yanked release: crossbeam-channel — `crossbeam-channel` resolves to 0.5.13 in the committed REDACTED, and crates.io reports that release as YANKED. A yanked release is one the publisher has withdrawn and asked you to stop using; it keeps resolving only so existing locks do not break. The current stable release is 0.5.17. Run `cargo update -p crossbeam-channel` and commit the updated lock.
D2 · Cognitive Complexity · DefaultBundler.createIdealGraph (cognitive 418) · ×1
  • DefaultBundler.createIdealGraph (cognitive 418) REDACTED:364 — DefaultBundler.createIdealGraph has cognitive complexity 418 (threshold 15). Drivers by points: if/else 102 (254 pts), loops 41 (100 pts), boolean chains 49, ternaries 4 (15 pts) (nesting depth added 222). Of this number, 321 points are the body's own statements and 97 belong to 13 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · transform (cognitive 323) · ×1
  • transform (cognitive 323) REDACTED:336 — transform has cognitive complexity 323 (threshold 15). Drivers by points: if/else 91 (191 pts), loops 20 (45 pts), boolean chains 39, ternaries 13 (38 pts), other 8, error handling 2 (nesting depth added 150). Of this number, 265 points are the body's own statements and 58 belong to 14 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · resolvePackageTargets (cognitive 247) · ×1
  • resolvePackageTargets (cognitive 247) packages/core/core/src/requests/TargetRequest.js:440 — resolvePackageTargets has cognitive complexity 247 (threshold 15). Drivers by points: ternaries 41 (108 pts), if/else 39 (79 pts), other 34, boolean chains 23, loops 2, match/switch 1 (nesting depth added 107). Of this number, 237 points are the body's own statements and 10 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 · apply (cognitive 209) · ×1
  • apply (cognitive 209) packages/runtimes/rsc/src/RSCRuntime.js:30 — apply has cognitive complexity 209 (threshold 15). Drivers by points: if/else 44 (159 pts), ternaries 4 (19 pts), boolean chains 15, loops 4 (15 pts), other 1 (nesting depth added 141). Most of this is not in the body itself: 8 of the 209 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 40, 281, 79, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · propagateSymbols (cognitive 181) · ×1
  • propagateSymbols (cognitive 181) packages/core/core/src/SymbolPropagation.js:22 — propagateSymbols has cognitive complexity 181 (threshold 15). Drivers by points: if/else 53 (127 pts), loops 12 (25 pts), ternaries 10 (16 pts), boolean chains 11, other 2 (nesting depth added 93). Most of this is not in the body itself: 1 of the 181 points is its own statement and the rest belongs to 14 function items inside it that branch (a function literal at line 62, a function literal at line 257, a function literal at line 301, …). 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 · dumpGraphToGraphViz (cognitive 152) · ×1
  • dumpGraphToGraphViz (cognitive 152) packages/core/core/src/dumpGraphToGraphViz.js:38 — dumpGraphToGraphViz has cognitive complexity 152 (threshold 15). Drivers by points: if/else 43 (126 pts), ternaries 4 (16 pts), boolean chains 5, other 3, loops 2 (nesting depth added 95). Of this number, 137 points are the body's own statements and 15 belong to 8 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 · validateSchema · ×1
  • validateSchema::walk (cognitive 141) packages/core/utils/src/schema.js:116 — validateSchema::walk has cognitive complexity 141 (threshold 15). Drivers by points: if/else 31 (114 pts), loops 3 (13 pts), ternaries 2 (6 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 99). 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 · package (cognitive 140) · ×1
  • package (cognitive 140) packages/packagers/js/src/DevPackager.js:46 — package has cognitive complexity 140 (threshold 15). Drivers by points: if/else 43 (89 pts), loops 8 (18 pts), ternaries 7 (17 pts), boolean chains 16 (nesting depth added 66). Of this number, 65 points are the body's own statements and 75 belong to 6 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 · collectDependencies (cognitive 120) · ×1
  • collectDependencies (cognitive 120) REDACTED:39 — collectDependencies has cognitive complexity 120 (threshold 15). Drivers by points: if/else 33 (60 pts), loops 12 (29 pts), ternaries 9 (24 pts), boolean chains 6, other 1 (nesting depth added 59). Of this number, 116 points are the body's own statements and 4 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 · ESMFold · ×1
  • ESMFold::fold_module (cognitive 111) packages/transformers/js/core/src/modules.rs:280 — ESMFold::fold_module has cognitive complexity 111 (threshold 15). Drivers by points: if/else 17 (54 pts), match/switch 10 (41 pts), loops 5 (16 pts) (nesting depth added 79). To reduce it, split the body into named stages: move each independent 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 · buildAsset (cognitive 108) · ×1
  • buildAsset (cognitive 108) REDACTED:466 — buildAsset has cognitive complexity 108 (threshold 15). Drivers by points: if/else 34 (89 pts), boolean chains 10, loops 3 (7 pts), other 1, ternaries 1 (nesting depth added 59). Of this number, 57 points are the body's own statements and 51 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 · addExternal (cognitive 101) · ×1
  • addExternal (cognitive 101) REDACTED:812 — addExternal has cognitive complexity 101 (threshold 15). Drivers by points: if/else 30 (81 pts), loops 2 (8 pts), ternaries 2 (7 pts), boolean chains 4, other 1 (nesting depth added 62). 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 · createIdealGraph · ×1
  • createIdealGraph::enter (cognitive 98) REDACTED:529 — createIdealGraph::enter has cognitive complexity 98 (threshold 15). Drivers by points: if/else 24 (66 pts), boolean chains 18, ternaries 2 (10 pts), loops 1 (2 pts), other 2 (nesting depth added 51). 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 · RequestGraph.respondToFSEvents (cognitive 94) · ×1
  • RequestGraph.respondToFSEvents (cognitive 94) REDACTED:851 — RequestGraph.respondToFSEvents has cognitive complexity 94 (threshold 15). Drivers by points: if/else 15 (44 pts), loops 10 (34 pts), boolean chains 10, ternaries 1 (6 pts) (nesting depth added 58). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transform (cognitive 91) · ×1
  • transform (cognitive 91) REDACTED:44 — transform has cognitive complexity 91 (threshold 15). Drivers by points: if/else 29 (62 pts), loops 7 (16 pts), boolean chains 8, ternaries 2 (3 pts), error handling 1, other 1 (nesting depth added 43). Of this number, 76 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · resolveEntry (cognitive 90) · ×1
  • resolveEntry (cognitive 90) packages/core/core/src/requests/EntryRequest.js:160 — resolveEntry has cognitive complexity 90 (threshold 15). Drivers by points: if/else 12 (34 pts), loops 5 (26 pts), ternaries 5 (24 pts), boolean chains 5, error handling 1 (nesting depth added 62). 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 · buildAssetPrelude (cognitive 84) · ×1
  • buildAssetPrelude (cognitive 84) REDACTED:1151 — buildAssetPrelude has cognitive complexity 84 (threshold 15). Drivers by points: if/else 12 (36 pts), boolean chains 27, loops 3 (11 pts), ternaries 2 (10 pts) (nesting depth added 40). Of this number, 73 points are the body's own statements and 11 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 · codeFrame (cognitive 82) · ×1
  • codeFrame (cognitive 82) packages/core/codeframe/src/codeframe.js:42 — codeFrame has cognitive complexity 82 (threshold 15). Drivers by points: if/else 22 (54 pts), ternaries 10 (16 pts), boolean chains 7, loops 2 (4 pts), other 1 (nesting depth added 40). Of this number, 72 points are the body's own statements and 10 belong to 11 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 · shake (cognitive 81) · ×1
  • shake (cognitive 81) packages/transformers/typescript-types/src/shake.js:15 — shake has cognitive complexity 81 (threshold 15). Drivers by points: if/else 32 (56 pts), boolean chains 15, ternaries 3 (5 pts), loops 1 (4 pts), other 1 (nesting depth added 29). Most of this is not in the body itself: 2 of the 81 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 38, a function literal at line 138, a function literal at line 180, …). 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 · shake.shake · ×1
  • shake.shake::visit (cognitive 78) packages/transformers/typescript-types/src/shake.js:38 — shake.shake::visit has cognitive complexity 78 (threshold 15). Drivers by points: if/else 32 (56 pts), boolean chains 15, loops 1 (4 pts), ternaries 1 (3 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent 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 · DevPackager.this.bundle.traverse() (cognitive 75) · ×1
  • DevPackager.this.bundle.traverse() (cognitive 75) packages/packagers/js/src/DevPackager.js:72 — DevPackager.this.bundle.traverse() has cognitive complexity 75 (threshold 15). Drivers by points: if/else 21 (48 pts), loops 4 (11 pts), boolean chains 9, ternaries 2 (7 pts) (nesting depth added 39). 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 · getSymbolResolution (cognitive 67) · ×1
  • getSymbolResolution (cognitive 67) REDACTED:1658 — getSymbolResolution has cognitive complexity 67 (threshold 15). Drivers by points: if/else 24 (60 pts), boolean chains 5, loops 1, other 1 (nesting depth added 36). 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 · _report (cognitive 61) · ×1
  • _report (cognitive 61) packages/reporters/cli/src/CLIReporter.js:43 — _report has cognitive complexity 61 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 8, match/switch 3 (6 pts), loops 1 (4 pts), ternaries 1 (3 pts), other 1 (nesting depth added 27). Of this number, 60 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. 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 · resolve (cognitive 60) · ×1
  • resolve (cognitive 60) packages/core/core/src/requests/TargetRequest.js:200 — resolve has cognitive complexity 60 (threshold 15). Drivers by points: if/else 15 (34 pts), ternaries 4 (13 pts), boolean chains 7, other 6 (nesting depth added 28). Of this number, 41 points are the body's own statements and 19 belong to 7 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 · processPipeline (cognitive 60) · ×1
  • processPipeline (cognitive 60) packages/transformers/vue/src/VueTransformer.js:202 — processPipeline has cognitive complexity 60 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 5 (11 pts), match/switch 4 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 30). Of this number, 42 points are the body's own statements and 18 belong to 6 function literals inside it that branch. 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 · OxvgConfig · ×1
  • OxvgConfig::into_jobs (cognitive 58) crates/html/src/oxvg.rs:1403 — OxvgConfig::into_jobs has cognitive complexity 58 (threshold 15). Drivers by points: match/switch 54 (56 pts), if/else 2 (nesting depth added 2). 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 · Specifier · ×1
  • Specifier::parse (cognitive 57) crates/parcel-resolver/src/specifier.rs:73 — Specifier::parse has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (48 pts), match/switch 3 (7 pts), boolean chains 2 (nesting depth added 34). To reduce it, split the body into named stages: move each independent 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 · package (cognitive 57) · ×1
  • package (cognitive 57) REDACTED:21 — package has cognitive complexity 57 (threshold 15). Drivers by points: if/else 22 (40 pts), loops 3 (9 pts), boolean chains 5, ternaries 1 (2 pts), other 1 (nesting depth added 25). Most of this is not in the body itself: 12 of the 57 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 108, exit, enter, …). 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 · loadBundleUncached.loadAsset (cognitive 55) · ×1
  • loadBundleUncached.loadAsset (cognitive 55) packages/packagers/react-static/src/ReactStaticPackager.js:376 — loadBundleUncached.loadAsset has cognitive complexity 55 (threshold 15). Drivers by points: if/else 22 (44 pts), loops 2 (5 pts), ternaries 1 (4 pts), boolean chains 2 (nesting depth added 28). Of this number, 35 points are the body's own statements and 20 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · resolve (cognitive 55) · ×1
  • resolve (cognitive 55) REDACTED:247 — resolve has cognitive complexity 55 (threshold 15). Drivers by points: if/else 17 (40 pts), ternaries 3 (6 pts), boolean chains 4, error handling 1 (2 pts), other 2, loops 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent 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 · Transformation.runPipeline (cognitive 54) · ×1
  • Transformation.runPipeline (cognitive 54) REDACTED:348 — Transformation.runPipeline has cognitive complexity 54 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 5 (18 pts), boolean chains 6, error handling 1 (3 pts) (nesting depth added 35). Of this number, 50 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · loadConfig (cognitive 54) · ×1
  • loadConfig (cognitive 54) REDACTED:181 — loadConfig has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 18, if/else 11 (18 pts), ternaries 5 (15 pts), other 3 (nesting depth added 17). Of this number, 53 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · DefaultBundler.decorateLegacyGraph (cognitive 53) · ×1
  • DefaultBundler.decorateLegacyGraph (cognitive 53) REDACTED:157 — DefaultBundler.decorateLegacyGraph has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 12 (22 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 23). Of this number, 43 points are the body's own statements and 10 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 · transform (cognitive 51) · ×1
  • transform (cognitive 51) packages/transformers/postcss/src/PostCSSTransformer.js:53 — transform has cognitive complexity 51 (threshold 15). Drivers by points: if/else 19 (36 pts), loops 3 (6 pts), boolean chains 5, ternaries 2 (3 pts), other 1 (nesting depth added 21). Of this number, 42 points are the body's own statements and 9 belong to 7 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 · collect (cognitive 51) · ×1
  • collect (cognitive 51) packages/transformers/typescript-types/src/collect.js:9 — collect has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (33 pts), loops 3 (9 pts), boolean chains 4, other 3, ternaries 2 (nesting depth added 18). Most of this is not in the body itself: 2 of the 51 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 21, 118). 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 · loadPlugin (cognitive 49) · ×1
  • loadPlugin (cognitive 49) packages/core/core/src/loadParcelPlugin.js:24 — loadPlugin has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 6 (16 pts), boolean chains 9, error handling 1 (nesting depth added 21). 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 · apply (cognitive 47) · ×1
  • apply (cognitive 47) REDACTED:69 — apply has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 8, loops 3 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · collect.collect · ×1
  • collect.collect::visit (cognitive 46) packages/transformers/typescript-types/src/collect.js:21 — collect.collect::visit has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (33 pts), loops 3 (9 pts), boolean chains 4 (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 · report (cognitive 46) · ×1
  • report (cognitive 46) packages/reporters/dev-server/src/ServerReporter.js:13 — report has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (32 pts), boolean chains 11, ternaries 2, match/switch 1 (nesting depth added 18). Of this number, 45 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · applyRuntimes.applyRuntimes (cognitive 45) · ×1
  • applyRuntimes.applyRuntimes (cognitive 45) packages/core/core/src/applyRuntimes.js:45 — applyRuntimes.applyRuntimes has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 7 (12 pts), boolean chains 5, ternaries 1 (4 pts), error handling 1 (3 pts) (nesting depth added 22). Of this number, 31 points are the body's own statements and 14 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 · debugResolvedTargets (cognitive 45) · ×1
  • debugResolvedTargets (cognitive 45) packages/core/core/src/requests/TargetRequest.js:1539 — debugResolvedTargets has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 4 (10 pts), boolean chains 5, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 21). Of this number, 38 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveOptions (cognitive 45) · ×1
  • resolveOptions (cognitive 45) packages/core/core/src/resolveOptions.js:47 — resolveOptions has cognitive complexity 45 (threshold 15). Drivers by points: other 20, boolean chains 9, if/else 7, ternaries 7, error handling 1 (2 pts) (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 · reducer (cognitive 44) · ×1
  • reducer (cognitive 44) packages/dev/repl/src/components/state.js:81 — reducer has cognitive complexity 44 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 7 (16 pts), loops 2 (4 pts), boolean chains 2, match/switch 1, other 1 (nesting depth added 22). Of this number, 34 points are the body's own statements and 10 belong to 9 function literals inside it that branch. 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 · resolve (cognitive 43) · ×1
  • resolve (cognitive 43) REDACTED:80 — resolve has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 8 (15 pts), boolean chains 8, error handling 1 (2 pts), match/switch 1 (nesting depth added 14). Of this number, 36 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · patchConsole (cognitive 43) · ×1
  • patchConsole (cognitive 43) packages/utils/error-overlay/src/listenToRuntimeErrors.js:57 — patchConsole has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (33 pts), match/switch 1 (4 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 24). None of this is in the body itself: all 43 points belong to 5 function literals inside it that branch (lines 60, 79, 66, …). 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 · getSymbolResolution (cognitive 41) · ×1
  • getSymbolResolution (cognitive 41) REDACTED:983 — getSymbolResolution has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 23, if/else 15 (18 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · diagnostic (cognitive 41) · ×1
  • diagnostic (cognitive 41) packages/core/utils/src/schema.js:380 — diagnostic has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (28 pts), ternaries 3 (6 pts), other 4, boolean chains 3 (nesting depth added 13). Most of this is not in the body itself: 12 of the 41 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 417, 487, 429, …). 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 · ReactLazy · ×1
  • ReactLazy::visit_call_expr (cognitive 40) packages/transformers/js/core/src/react_lazy.rs:29 — ReactLazy::visit_call_expr has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 5, loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 21). 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 · HMRServer.serveCodeFrame (cognitive 39) · ×1
  • HMRServer.serveCodeFrame (cognitive 39) REDACTED:384 — HMRServer.serveCodeFrame has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (28 pts), ternaries 1 (5 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 23). 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 · propagateSymbolsUp (cognitive 39) · ×1
  • propagateSymbolsUp (cognitive 39) packages/core/core/src/SymbolPropagation.js:595 — propagateSymbolsUp has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (57 pts), loops 6 (15 pts), boolean chains 2, other 1, ternaries 1 (nesting depth added 45). 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 · resolve (cognitive 39) · ×1
  • resolve (cognitive 39) REDACTED:278 — resolve has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (31 pts), boolean chains 5, error handling 1 (2 pts), other 1 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · prettyDiagnostic (cognitive 39) · ×1
  • prettyDiagnostic (cognitive 39) packages/core/utils/src/prettyDiagnostic.js:33 — prettyDiagnostic has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 6 (11 pts), boolean chains 4, loops 1 (2 pts), other 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Macros · ×1
  • Macros::fold_expr (cognitive 38) crates/macros/src/lib.rs:199 — Macros::fold_expr has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (29 pts), match/switch 2 (9 pts) (nesting depth added 28). 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 · package (cognitive 38) · ×1
  • package (cognitive 38) REDACTED:130 — package has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 9, loops 3 (4 pts) (nesting depth added 12). Of this number, 34 points are the body's own statements and 4 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 · buildBundlePrelude (cognitive 38) · ×1
  • buildBundlePrelude (cognitive 38) REDACTED:1365 — buildBundlePrelude has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sendIndex (cognitive 38) · ×1
  • sendIndex (cognitive 38) packages/reporters/dev-server/src/Server.js:173 — sendIndex has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 5, ternaries 1 (4 pts), loops 1 (3 pts), other 2 (nesting depth added 18). 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 · resolve (cognitive 38) · ×1
  • resolve (cognitive 38) packages/resolvers/glob/src/GlobResolver.js:36 — resolve has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 3 (7 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), match/switch 1, other 1 (nesting depth added 14). Of this number, 37 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HTMLNanoOptimizer.mapSVG (cognitive 37) · ×1
  • HTMLNanoOptimizer.mapSVG (cognitive 37) REDACTED:160 — HTMLNanoOptimizer.mapSVG has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 21). 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 · buildReplacements (cognitive 37) · ×1
  • buildReplacements (cognitive 37) REDACTED:705 — buildReplacements has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 5 (12 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · convertSVGOConfig (cognitive 37) · ×1
  • convertSVGOConfig (cognitive 37) packages/core/utils/src/svgo.js:58 — convertSVGOConfig has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 2 (7 pts), boolean chains 5, other 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 · run (cognitive 36) · ×1
  • run (cognitive 36) packages/core/parcel/src/cli.js:277 — run has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 3 (9 pts), boolean chains 4, error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 14). Of this number, 19 points are the body's own statements and 17 belong to 9 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 · normalizeOptions (cognitive 36) · ×1
  • normalizeOptions (cognitive 36) packages/core/parcel/src/cli.js:431 — normalizeOptions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 8 (10 pts), boolean chains 7, error handling 1 (2 pts), other 2 (nesting depth added 6). Of this number, 35 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · load (cognitive 36) · ×1
  • load (cognitive 36) REDACTED:40 — load has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (27 pts), loops 2 (3 pts), boolean chains 2, other 2, ternaries 2 (nesting depth added 10). Of this number, 34 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · optimize (cognitive 35) · ×1
  • optimize (cognitive 35) packages/optimizers/css/src/CSSOptimizer.js:71 — optimize has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 4, loops 1 (3 pts), other 1 (nesting depth added 14). Most of this is not in the body itself: 12 of the 35 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 90, 106). 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 · resolveBuiltin (cognitive 34) · ×1
  • resolveBuiltin (cognitive 34) REDACTED:254 — resolveBuiltin has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 8 (11 pts), boolean chains 5, error handling 1 (3 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 · LspReporter.getDiagnosticsUnusedExports (cognitive 32) · ×1
  • LspReporter.getDiagnosticsUnusedExports (cognitive 32) packages/reporters/lsp-reporter/src/LspReporter.js:321 — LspReporter.getDiagnosticsUnusedExports has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 3 (9 pts), boolean chains 2 (nesting depth added 20). Of this number, 30 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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 · build-native.build (cognitive 32) · ×1
  • build-native.build (cognitive 32) scripts/build-native.js:13 — build-native.build has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 14). Of this number, 20 points are the body's own statements and 12 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 · handleMessage (cognitive 32) · ×1
  • handleMessage (cognitive 32) packages/runtimes/hmr/src/loaders/hmr-runtime.js:204 — handleMessage has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 5, loops 2 (5 pts), ternaries 1 (3 pts) (nesting depth added 14). Of this number, 30 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · handleRequest (cognitive 32) · ×1
  • handleRequest (cognitive 32) packages/core/workers/src/child.js:122 — handleRequest has cognitive complexity 32 (threshold 15). Drivers by points: error handling 7 (13 pts), if/else 11 (13 pts), 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 · babel7 (cognitive 32) · ×1
  • babel7 (cognitive 32) packages/transformers/babel/src/babel7.js:32 — babel7 has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 1 (3 pts), other 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 15). Of this number, 29 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JSRuntime.getLoaderRuntime (cognitive 31) · ×1
  • JSRuntime.getLoaderRuntime (cognitive 31) REDACTED:321 — JSRuntime.getLoaderRuntime has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 6, 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 · modern.resolvePathImporter.canonicalize (cognitive 31) · ×1
  • modern.resolvePathImporter.canonicalize (cognitive 31) packages/transformers/sass/src/modern.js:85 — modern.resolvePathImporter.canonicalize has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 4 (8 pts), error handling 2 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getValidateResultFromDiagnostics (cognitive 31) · ×1
  • getValidateResultFromDiagnostics (cognitive 31) packages/validators/typescript/src/TypeScriptValidator.js:142 — getValidateResultFromDiagnostics has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (17 pts), ternaries 3 (9 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 19). 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 · resolvePathImporter.canonicalize (cognitive 31) · ×1
  • resolvePathImporter.canonicalize (cognitive 31) packages/transformers/sass/src/modern.js:85 — resolvePathImporter.canonicalize has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 4 (8 pts), error handling 2 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transform (cognitive 31) · ×1
  • transform (cognitive 31) packages/transformers/typescript-types/src/TSTypesTransformer.js:23 — transform has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 5, loops 3 (4 pts), ternaries 2, other 1 (nesting depth added 9). Of this number, 18 points are the body's own statements and 13 belong to 6 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 · ESMOutputFormat.buildBundlePrelude (cognitive 30) · ×1
  • ESMOutputFormat.buildBundlePrelude (cognitive 30) packages/packagers/js/src/ESMOutputFormat.js:15 — ESMOutputFormat.buildBundlePrelude has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 2 (3 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 · HMRServer.getUpdate (cognitive 30) · ×1
  • HMRServer.getUpdate (cognitive 30) REDACTED:243 — HMRServer.getUpdate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (10 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 278, 260). 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 · buildExportedSymbols (cognitive 30) · ×1
  • buildExportedSymbols (cognitive 30) REDACTED:364 — buildExportedSymbols has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 5, ternaries 1 (4 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · hmr-runtime.hmrApply (cognitive 29) · ×1
  • hmr-runtime.hmrApply (cognitive 29) packages/runtimes/hmr/src/loaders/hmr-runtime.js:538 — hmr-runtime.hmrApply has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 18). 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 · _isSymlink (cognitive 29) · ×1
  • _isSymlink (cognitive 29) packages/core/fs/src/OverlayFS.js:79 — _isSymlink has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 2 (4 pts), error handling 1 (3 pts), boolean chains 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 · propagate (cognitive 29) · ×1
  • propagate (cognitive 29) REDACTED:201 — propagate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · serializer.mapObject (cognitive 28) · ×1
  • serializer.mapObject (cognitive 28) packages/core/core/src/serializer.js:64 — serializer.mapObject has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 3 function items inside it that branch (walk::processKey, walk, memoizedFn). 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 · AssetGraphBuilder.shouldVisitChild (cognitive 28) · ×1
  • AssetGraphBuilder.shouldVisitChild (cognitive 28) packages/core/core/src/requests/AssetGraphRequest.js:345 — AssetGraphBuilder.shouldVisitChild has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6 (nesting depth added 12). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · MemoryFS.readdirSync (cognitive 28) · ×1
  • MemoryFS.readdirSync (cognitive 28) packages/core/fs/src/MemoryFS.js:284 — MemoryFS.readdirSync has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 3, loops 3 (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 · fromAssetGraph · ×1
  • fromAssetGraph::walk (cognitive 28) REDACTED:194 — fromAssetGraph::walk has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3 (6 pts), ternaries 2 (5 pts), boolean chains 3, other 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 · unlink (cognitive 28) · ×1
  • unlink (cognitive 28) packages/core/fs/src/OverlayFS.js:187 — unlink has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 3 (6 pts), boolean chains 2, error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · startDevServer (cognitive 28) · ×1
  • startDevServer (cognitive 28) packages/reporters/dev-server/src/ServerReporter.js:111 — startDevServer has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 6, other 5, if/else 3 (4 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 · emitUpdate (cognitive 28) · ×1
  • emitUpdate (cognitive 28) packages/reporters/dev-server-sw/src/HMRServer.js:80 — emitUpdate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (10 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 112, 94). 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 · Engines · ×1
  • Engines::supports (cognitive 27) crates/core/src/environment.rs:396 — Engines::supports has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 9 (18 pts), if/else 9 (nesting depth added 9). 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 · Browsers · ×1
  • Browsers::fmt (cognitive 27) crates/core/src/environment.rs:166 — Browsers::fmt has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (27 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 · bundle (cognitive 27) · ×1
  • bundle (cognitive 27) packages/core/core/src/requests/BundleGraphRequest.js:247 — bundle has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 3 (6 pts), loops 2 (4 pts), boolean chains 2, ternaries 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 · CLIReporter.writeDiagnostic (cognitive 26) · ×1
  • CLIReporter.writeDiagnostic (cognitive 26) packages/reporters/cli/src/CLIReporter.js:215 — CLIReporter.writeDiagnostic has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 6, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HtmlSerializer · ×1
  • HtmlSerializer::start_elem (cognitive 26) crates/html/src/serialize_html.rs:154 — HtmlSerializer::start_elem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 6, match/switch 2 (3 pts), loops 1 (nesting depth added 7). 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 · processRequest (cognitive 26) · ×1
  • processRequest (cognitive 26) REDACTED:347 — processRequest has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (21 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processConfigChain (cognitive 26) · ×1
  • processConfigChain (cognitive 26) packages/core/core/src/requests/ParcelConfigRequest.js:418 — processConfigChain has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 3 (10 pts), if/else 4 (8 pts), error handling 1 (4 pts), loops 1 (3 pts), other 1 (nesting depth added 16). Of this number, 25 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 · getDependencies (cognitive 26) · ×1
  • getDependencies (cognitive 26) packages/transformers/stylus/src/StylusTransformer.js:117 — getDependencies has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (8 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 9). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 154, visitImport). 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 · SymbolPropagation.propagateSymbolsUp · ×1
  • SymbolPropagation.propagateSymbolsUp::nodeVisitor (cognitive 25) packages/core/core/src/SymbolPropagation.js:643 — SymbolPropagation.propagateSymbolsUp::nodeVisitor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExtendedMemoryFS.parseOpenFlags (cognitive 25) · ×1
  • ExtendedMemoryFS.parseOpenFlags (cognitive 25) packages/dev/repl/src/parcel/ExtendedMemoryFS.js:86 — ExtendedMemoryFS.parseOpenFlags has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (25 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 · fork (cognitive 25) · ×1
  • fork (cognitive 25) packages/core/workers/src/Worker.js:50 — fork has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (7 pts), boolean chains 5 (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 · detectSVGOVersion (cognitive 25) · ×1
  • detectSVGOVersion (cognitive 25) packages/core/utils/src/svgo.js:8 — detectSVGOVersion has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3 (7 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 11). Of this number, 23 points are the body's own statements and 2 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 · bundle (cognitive 25) · ×1
  • bundle (cognitive 25) packages/bundlers/library/src/LibraryBundler.js:9 — bundle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (4 pts), other 2, boolean chains 1 (nesting depth added 11). Of this number, 19 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 · HMRServer.handle (cognitive 24) · ×1
  • HMRServer.handle (cognitive 24) REDACTED:143 — HMRServer.handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5 (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 · LessFileManager.loadFile (cognitive 24) · ×1
  • LessFileManager.loadFile (cognitive 24) packages/transformers/less/src/LessTransformer.js:110 — LessFileManager.loadFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1, ternaries 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. This shape REPEATS in the file: one other method here (LessTransformer.resolvePathPlugin.install) 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 · LessTransformer.resolvePathPlugin.install (cognitive 24) · ×1
  • LessTransformer.resolvePathPlugin.install (cognitive 24) packages/transformers/less/src/LessTransformer.js:100 — LessTransformer.resolvePathPlugin.install has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1, ternaries 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. This shape REPEATS in the file: one other method here (LessFileManager.loadFile) 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 · handleError (cognitive 24) · ×1
  • handleError (cognitive 24) REDACTED:404 — handleError has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 3 (6 pts), match/switch 3 (5 pts) (nesting depth added 12). 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 · resolvePathPlugin.install · ×1
  • resolvePathPlugin.install::loadFile (cognitive 24) packages/transformers/less/src/LessTransformer.js:110 — resolvePathPlugin.install::loadFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1, ternaries 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 · SymbolPropagation.propagateSymbolsDown (cognitive 23) · ×1
  • SymbolPropagation.propagateSymbolsDown (cognitive 23) packages/core/core/src/SymbolPropagation.js:498 — SymbolPropagation.propagateSymbolsDown has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 7). Of this number, 22 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 · AssetGraphBuilder.build (cognitive 23) · ×1
  • AssetGraphBuilder.build (cognitive 23) packages/core/core/src/requests/AssetGraphRequest.js:198 — AssetGraphBuilder.build has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 8). Of this number, 12 points are the body's own statements and 11 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 · generateExample.linearizeState (cognitive 23) · ×1
  • generateExample.linearizeState (cognitive 23) packages/dev/esm-fuzzer/generateExample.js:335 — generateExample.linearizeState has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 2 (nesting depth added 9). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 341, 443). 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 · bundleReport.bundleReport (cognitive 23) · ×1
  • bundleReport.bundleReport (cognitive 23) packages/reporters/cli/src/bundleReport.js:21 — bundleReport.bundleReport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 2 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 23) · ×1
  • (anonymous) (cognitive 23) packages/dev/repl/src/sw.js:105 — (anonymous) has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, other 3, ternaries 1 (3 pts) (nesting depth added 7). Of this number, 16 points are the body's own statements and 7 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 · MemoryFS.ncp (cognitive 22) · ×1
  • MemoryFS.ncp (cognitive 22) packages/core/fs/src/MemoryFS.js:473 — MemoryFS.ncp has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · visitVariableDeclaration (cognitive 22) · ×1
  • visitVariableDeclaration (cognitive 22) packages/optimizers/inline-requires/src/RequireInliningVisitor.js:75 — visitVariableDeclaration has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 8, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Options (cognitive 22) · ×1
  • Options (cognitive 22) packages/dev/repl/src/components/Options.js:14 — Options has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, if/else 2, other 2, ternaries 2. Of this number, 11 points are the body's own statements and 11 belong to 21 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · configHydrator (cognitive 22) · ×1
  • configHydrator (cognitive 22) packages/transformers/postcss/src/loadConfig.js:27 — configHydrator has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 5). Of this number, 21 points are the body's own statements and 1 belongs 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 · install (cognitive 22) · ×1
  • install (cognitive 22) REDACTED:84 — install has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, loops 2, other 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). Of this number, 16 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · resolvePathImporter · ×1
  • resolvePathImporter::resolvePath (cognitive 22) REDACTED:72 — resolvePathImporter::resolvePath has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 2 (6 pts), loops 3 (6 pts), ternaries 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 · package (cognitive 22) · ×1
  • package (cognitive 22) packages/packagers/webextension/src/WebExtensionPackager.js:9 — package has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 7, loops 1, ternaries 1 (nesting depth added 7). Of this number, 11 points are the body's own statements and 11 belong to 13 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 · SerializableHandle · ×1
  • SerializableHandle::serialize (cognitive 21) crates/html/src/arena.rs:606 — SerializableHandle::serialize has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (11 pts), match/switch 3 (6 pts), if/else 1 (4 pts) (nesting depth added 13). 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 · EntryIter · ×1
  • EntryIter::next (cognitive 21) crates/parcel-resolver/src/package_json.rs:962 — EntryIter::next has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getInvalidations (cognitive 21) · ×1
  • getInvalidations (cognitive 21) REDACTED:477 — getInvalidations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 10). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (addKey, a function literal at line 529, a function literal at line 532). 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 · findSourceMap (cognitive 21) · ×1
  • findSourceMap (cognitive 21) REDACTED:541 — findSourceMap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · StackFrame (cognitive 21) · ×1
  • StackFrame (cognitive 21) REDACTED:55 — StackFrame has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 7, boolean chains 6 (nesting depth added 1). Of this number, 16 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · optimize (cognitive 21) · ×1
  • optimize (cognitive 21) packages/optimizers/terser/src/TerserOptimizer.js:21 — optimize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, ternaries 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runESM.runESM (cognitive 20) · ×1
  • runESM.runESM (cognitive 20) packages/dev/esm-fuzzer/runESM.js:6 — runESM.runESM has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (4 pts), boolean chains 1, ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (load, entry, a function literal at line 52). 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 · sw.self.addEventListener("fetch") (cognitive 20) · ×1
  • sw.self.addEventListener("fetch") (cognitive 20) packages/dev/repl/src/sw.js:105 — sw.self.addEventListener("fetch") has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 7). Of this number, 14 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 · shake.generateImports (cognitive 20) · ×1
  • shake.generateImports (cognitive 20) packages/transformers/typescript-types/src/shake.js:252 — shake.generateImports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), loops 2 (3 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 · GlobalReplacer · ×1
  • GlobalReplacer::visit_mut_expr (cognitive 20) packages/transformers/js/core/src/global_replacer.rs:63 — GlobalReplacer::visit_mut_expr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 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 · fromAssetGraph (cognitive 20) · ×1
  • fromAssetGraph (cognitive 20) REDACTED:156 — fromAssetGraph has cognitive complexity 20 (threshold 15). Drivers by points: if/else 22 (51 pts), loops 7 (15 pts), boolean chains 7, ternaries 3 (6 pts), other 4 (nesting depth added 40). 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 · assertTargetsAreNotEntries (cognitive 20) · ×1
  • assertTargetsAreNotEntries (cognitive 20) packages/core/core/src/requests/TargetRequest.js:1479 — assertTargetsAreNotEntries has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · run · ×1
  • run::parseAssetLocator (cognitive 20) REDACTED:89 — run::parseAssetLocator has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), boolean chains 2, ternaries 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 · package (cognitive 20) · ×1
  • package (cognitive 20) packages/packagers/react-static/src/ReactStaticPackager.js:108 — package has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 3 (nesting depth added 7). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (Resources, a function literal at line 168, flush, …). 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 · updateDiagnostics (cognitive 20) · ×1
  • updateDiagnostics (cognitive 20) packages/reporters/lsp-reporter/src/LspReporter.js:243 — updateDiagnostics has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts), ternaries 1 (2 pts), boolean chains 1, other 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 · loadGraphs (cognitive 20) · ×1
  • loadGraphs (cognitive 20) packages/dev/query/src/index.js:23 — loadGraphs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 4 (7 pts), boolean chains 3, loops 1 (nesting depth added 6). Of this number, 12 points are the body's own statements and 8 belong to 9 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 · cli.logUncaughtError (cognitive 19) · ×1
  • cli.logUncaughtError (cognitive 19) packages/core/parcel/src/cli.js:24 — cli.logUncaughtError has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), boolean chains 3 (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 · generateBuildMetrics.getSourcemapSizes (cognitive 19) · ×1
  • generateBuildMetrics.getSourcemapSizes (cognitive 19) packages/core/utils/src/generateBuildMetrics.js:28 — generateBuildMetrics.getSourcemapSizes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rsc-helpers.createResourcesValueProxy (cognitive 19) · ×1
  • rsc-helpers.createResourcesValueProxy (cognitive 19) packages/runtimes/rsc/rsc-helpers.jsx:22 — rsc-helpers.createResourcesValueProxy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (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 · ExportsField · ×1
  • ExportsField::convert_paths (cognitive 19) crates/parcel-resolver/src/package_json.rs:148 — ExportsField::convert_paths has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · runRequest (cognitive 19) · ×1
  • runRequest (cognitive 19) REDACTED:1177 — runRequest has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (4 pts), boolean chains 3, ternaries 2, other 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 · writeToCache (cognitive 19) · ×1
  • writeToCache (cognitive 19) REDACTED:1346 — writeToCache has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 2 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runTransformer (cognitive 19) · ×1
  • runTransformer (cognitive 19) REDACTED:564 — runTransformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 2). Of this number, 10 points are the body's own statements and 9 belong to 6 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · loadBundleUncached (cognitive 19) · ×1
  • loadBundleUncached (cognitive 19) packages/packagers/react-static/src/ReactStaticPackager.js:293 — loadBundleUncached has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), ternaries 1 (3 pts) (nesting depth added 7). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 305, 310, 335, …). 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 · getPrefix (cognitive 19) · ×1
  • getPrefix (cognitive 19) packages/packagers/js/src/DevPackager.js:415 — getPrefix has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), boolean chains 3, ternaries 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 · getInlineBundles (cognitive 19) · ×1
  • getInlineBundles (cognitive 19) packages/packagers/svg/src/SVGPackager.js:49 — getInlineBundles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (3 pts), boolean chains 2, other 2, loops 1 (nesting depth added 8). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transform (cognitive 19) · ×1
  • transform (cognitive 19) packages/transformers/image/src/ImageTransformer.js:38 — transform has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, ternaries 3, other 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · package (cognitive 19) · ×1
  • package (cognitive 19) packages/packagers/xml/src/XMLPackager.js:14 — package has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 1 (4 pts), loops 1 (2 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 · index.Status (cognitive 18) · ×1
  • index.Status (cognitive 18) packages/dev/repl/src/index.js:46 — index.Status has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EsmGraphBuilder · ×1
  • EsmGraphBuilder::build (cognitive 18) crates/dev-dep-resolver/src/lib.rs:76 — EsmGraphBuilder::build has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (2 pts), match/switch 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · convertDiagnostics (cognitive 18) · ×1
  • convertDiagnostics (cognitive 18) REDACTED:135 — convertDiagnostics has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (8 pts), if/else 2 (7 pts), boolean chains 2, other 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · Output (cognitive 18) · ×1
  • Output (cognitive 18) packages/dev/repl/src/index.js:90 — Output has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (5 pts), if/else 4, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 14 function items inside it that branch (build, toggleWatch, a function literal at line 146, …). 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 · (anonymous) · ×1
  • (anonymous)::newRequire (cognitive 18) packages/packagers/js/src/dev-prelude.js:45 — (anonymous)::newRequire has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 3 (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 · MemoryFS.rimraf (cognitive 17) · ×1
  • MemoryFS.rimraf (cognitive 17) packages/core/fs/src/MemoryFS.js:401 — MemoryFS.rimraf has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 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 · unlink.unlink (cognitive 17) · ×1
  • unlink.unlink (cognitive 17) REDACTED:34 — unlink.unlink has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · parcel_node_bindings · ×1
  • parcel_node_bindings::resolver::resolve_internal (cognitive 17) crates/node-bindings/src/resolver.rs:338 — parcel_node_bindings::resolver::resolve_internal has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 6 (7 pts) (nesting depth added 7). 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 · getHintedBundleGroups (cognitive 17) · ×1
  • getHintedBundleGroups (cognitive 17) REDACTED:491 — getHintedBundleGroups has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runAssetRequest (cognitive 17) · ×1
  • runAssetRequest (cognitive 17) packages/core/core/src/requests/AssetGraphRequest.js:514 — runAssetRequest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 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 · processCSSModule (cognitive 17) · ×1
  • processCSSModule (cognitive 17) REDACTED:261 — processCSSModule has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, other 1 (nesting depth added 6). Of this number, 13 points are the body's own statements and 4 belong to 4 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 · getConfigFrom (cognitive 17) · ×1
  • getConfigFrom (cognitive 17) REDACTED:132 — getConfigFrom has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 1, ternaries 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 · mapObject · ×1
  • mapObject::walk::processKey (cognitive 17) packages/core/core/src/serializer.js:90 — mapObject::walk::processKey has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 1 (2 pts) (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 · loadConfig (cognitive 17) · ×1
  • loadConfig (cognitive 17) packages/transformers/svg-react/src/SvgReactTransformer.js:12 — loadConfig has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 4 (6 pts), boolean chains 2, error handling 1, other 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 · detectVersion (cognitive 17) · ×1
  • detectVersion (cognitive 17) packages/transformers/sass/src/SassTransformer.js:74 — detectVersion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · run (cognitive 17) · ×1
  • run (cognitive 17) packages/dev/esm-fuzzer/index.js:9 — run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 1 (3 pts), error handling 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 · (anonymous) (cognitive 17) · ×1
  • (anonymous) (cognitive 17) packages/dev/esm-fuzzer/index.js:101 — (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (10 pts), error handling 2 (4 pts), loops 2 (3 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 · RequestGraph.invalidateOnFileCreate (cognitive 16) · ×1
  • RequestGraph.invalidateOnFileCreate (cognitive 16) REDACTED:546 — RequestGraph.invalidateOnFileCreate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, 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 · loadAssets (cognitive 16) · ×1
  • loadAssets (cognitive 16) REDACTED:310 — loadAssets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 313, 344, 314, …). 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 · prepareForSerialization (cognitive 16) · ×1
  • prepareForSerialization (cognitive 16) packages/core/core/src/serializer.js:162 — prepareForSerialization has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, other 1 (nesting depth added 6). 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 169). 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 · (anonymous) (cognitive 16) · ×1
  • (anonymous) (cognitive 16) packages/packagers/js/src/dev-prelude.js:9 — (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 12, ternaries 6 (9 pts), loops 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.
D2 · Cognitive Complexity · updateExportDeclaration (cognitive 16) · ×1
  • updateExportDeclaration (cognitive 16) packages/transformers/typescript-types/src/wrappers.js:100 — updateExportDeclaration has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 6. None of this is in the body itself: all 16 points belong to 6 function literals inside it that branch (lines 108, 110, 128, …). 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 · resolve (cognitive 16) · ×1
  • resolve (cognitive 16) packages/resolvers/repl-runtimes/src/REPLRuntimesResolver.js:152 — resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getInlineBundles (cognitive 16) · ×1
  • getInlineBundles (cognitive 16) packages/packagers/html/src/HTMLPackager.js:50 — getInlineBundles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 1 (3 pts), other 2, loops 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · enginesToBabelTargets (cognitive 16) · ×1
  • enginesToBabelTargets (cognitive 16) packages/transformers/babel/src/utils.js:49 — enginesToBabelTargets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 1 (3 pts), boolean chains 1, loops 1, other 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.
D22 · Internal API Consistency · The Cache API exposes multiple distinct methods for retrieving data based on content type or size (get, getStream, getBlob, getLargeBlob). This forces consumers to know the internal storage format or size constraints of the cached item before calling the correct method, rather than providing a unified retrieval interface. · ×1
  • The Cache API exposes multiple distinct methods for retrieving data based on content type or size (get, getStream, getBlob, getLargeBlob). This forces consumers to know the internal storage format or size constraints of the cached item before calling the correct method, rather than providing a unified retrieval interface. — Unify into a single `get(key: string): Promise<CacheEntry>` or `get<T>(key: string): Promise<T>` method that returns a structured object containing the data and metadata (size, type), or provide a `getStream` that handles all cases internally. (signatures: Cache.get(key: string): Promise<?T> | Cache.getStream(key: string): Readable | Cache.getBlob(key: string): Promise<Buffer> | Cache.getLargeBlob(key: string): Promise<Buffer>)
D22 · Internal API Consistency · The FileSystem API mixes synchronous and asynchronous methods (`readFile` vs `readFileSync`) in the same interface. While common in Node.js, this creates inconsistency in usage patterns (Promise vs direct return) and error handling within the same class, increasing cognitive load for developers using the API. · ×1
  • The FileSystem API mixes synchronous and asynchronous methods (`readFile` vs `readFileSync`) in the same interface. While common in Node.js, this creates inconsistency in usage patterns (Promise vs direct return) and error handling within the same class, increasing cognitive load for developers using the API. — Standardize on asynchronous operations only (returning Promises) for the public API surface, or split into `FileSystemAsync` and `FileSystemSync` interfaces to clearly separate concerns. (signatures: FileSystem.readFile(filePath: FilePath): Promise<Buffer> | FileSystem.readFile(filePath: FilePath, encoding: Encoding): Promise<string> | FileSystem.readFileSync(filePath: FilePath): Buffer | FileSystem.readFileSync(filePath: FilePath, encoding: Encoding): string)
D22 · Internal API Consistency · The Resolver class has three distinct methods for performing resolution that differ only by the additional parameters they accept (`options` vs `invalidations`). This creates a fragmented API where the caller must choose the correct method based on whether they need to pass extra options or track invalidations, rather than using a single method with an optional options object. · ×1
  • The Resolver class has three distinct methods for performing resolution that differ only by the additional parameters they accept (`options` vs `invalidations`). This creates a fragmented API where the caller must choose the correct method based on whether they need to pass extra options or track invalidations, rather than using a single method with an optional options object. — Consolidate into a single `resolve` method that accepts a comprehensive `ResolveOptions` object containing all optional parameters (conditions, invalidations, etc.). (signatures: Resolver.resolve(specifier: str, from: Path, specifier_type: SpecifierType): ResolveResult | Resolver.resolve_with_options(specifier: str, from: Path, specifier_type: SpecifierType, options: ResolveOptions): ResolveResult | Resolver.resolve_with_invalidations(specifier: str, from: Path, specifier_type: SpecifierType, invalidations: Invalidations, options: ResolveOptions): Result)
D22 · Internal API Consistency · The MutableBundleGraph API exposes multiple 'add' methods that seem to perform similar graph mutation operations but with different scopes (asset graph vs single asset vs entry). This lacks a unified 'add' interface, forcing developers to understand the specific graph topology implications of each method. · ×1
  • The MutableBundleGraph API exposes multiple 'add' methods that seem to perform similar graph mutation operations but with different scopes (asset graph vs single asset vs entry). This lacks a unified 'add' interface, forcing developers to understand the specific graph topology implications of each method. — Provide a single `addAsset` or `addToBundle` method that accepts a descriptor or context object specifying the type of addition (entry, asset, graph), or clearly document that these are distinct domain operations if they are not redundant. (signatures: MutableBundleGraph.addAssetGraphToBundle(...) | MutableBundleGraph.addAssetToBundle(...) | MutableBundleGraph.addEntryToBundle(...))
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyFields · ×1
  • TooManyFields: OxvgConfig crates/html/src/oxvg.rs:1241 — TooManyFields — 53 stored fields beside 2 methods. The bar is 30 stored fields; this is 23 over it, 1.77× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: MemoryFS packages/core/fs/src/MemoryFS.js:48 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Duplicated block (60 lines × 2) · ×1
  • Duplicated block (60 lines × 2) crates/parcel-resolver/src/tsconfig.rs:133 — crates/parcel-resolver/src/tsconfig.rs:133-192 | packages/utils/node-resolver-rs/src/tsconfig.rs:133-192 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) crates/html/src/serialize_html.rs:110 — crates/html/src/serialize_html.rs:110-152 | crates/html/src/serialize_xml.rs:127-169 — before extracting anything, compare `crates/html/src/serialize_html.rs` and `crates/html/src/serialize_xml.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) packages/transformers/js/core/src/hoist.rs:618 — packages/transformers/js/core/src/hoist.rs:618-642 | packages/transformers/js/core/src/hoist.rs:662-685 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) packages/transformers/js/core/src/collect.rs:494 — packages/transformers/js/core/src/collect.rs:494-516 | packages/transformers/js/core/src/collect.rs:518-540 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) crates/parcel-resolver/src/tsconfig.rs:94 — crates/parcel-resolver/src/tsconfig.rs:94-111 | packages/utils/node-resolver-rs/src/tsconfig.rs:94-111 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) crates/html/src/jsx.rs:908 — crates/html/src/jsx.rs:908-923 | crates/html/src/jsx.rs:927-942 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) crates/parcel-resolver/src/tsconfig.rs:38 — crates/parcel-resolver/src/tsconfig.rs:38-51 | packages/utils/node-resolver-rs/src/tsconfig.rs:38-51 — before extracting anything, compare `crates/parcel-resolver/src/tsconfig.rs` and `packages/utils/node-resolver-rs/src/tsconfig.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 138 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) crates/html/src/lib.rs:68 — crates/html/src/lib.rs:68-77 | crates/html/src/lib.rs:157-166 | crates/html/src/lib.rs:231-240 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) crates/html/src/oxvg.rs:884 — crates/html/src/oxvg.rs:884-891 | crates/html/src/oxvg.rs:897-904 — 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.
D5 · Coupling · Unstable project @parcel/config-default · ×1
  • Unstable project @parcel/config-default — @parcel/config-default has instability 0.92 with 3 dependents.
D5 · Coupling · Unstable project @parcel/optimizer-image · ×1
  • Unstable project @parcel/optimizer-image — @parcel/optimizer-image has instability 0.86 with 1 dependents.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. 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.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing packages/core/core/src/Environment.js:40 — The `if` and its `else` contain the same statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 23 typed · 608 plain JS — the untyped files are flow-libs/deasync.js, REDACTED, packages/bundlers/library/src/LibraryBundler.js, packages/compressors/brotli/src/BrotliCompressor.js, packages/compressors/gzip/src/GzipCompressor.js, packages/compressors/raw/src/RawCompressor.js (+602 more). 0 production file(s) opt out entirely with @ts-nocheck · 1 @ts-ignore suppression(s).
R10 · Code Duplication · Duplication concentrated across 9 sibling directories (20 clone groups) · ×1
  • Duplication concentrated across 9 sibling directories (20 clone groups) packages/transformers/typescript-types/src/TSTypesTransformer.js:102 — 20 duplicated blocks under packages/ have copies in at least two of the sibling directories core, dev, optimizers, packagers, reporters, runtimes (+3 more sibling(s) not listed) — 17 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 20 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 20 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 20 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 7 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 7 sibling directories (7 clone groups) packages/core/logger/src/Logger.js:110 — 7 duplicated blocks under packages/core/ have copies in at least two of the sibling directories cache, core, fs, graph, logger, types-internal (+1 more sibling(s) not listed) — 4 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 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (6 clone groups) packages/reporters/dev-server-sw/src/HMRServer.js:84 — 6 duplicated blocks under packages/reporters/ have copies in at least two of the sibling directories bundle-analyzer, bundle-stats, dev-server, dev-server-sw — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 8 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 8 sibling directories (5 clone groups) packages/optimizers/css/src/CSSOptimizer.js:170 — 5 of the duplicated blocks reported below have copies in at least two of the sibling directories css, cssnano, html, htmlnano, svg, svgo (+2 more sibling(s) not listed) under packages/optimizers/. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (80 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (80 matched lines × 2 locations) packages/packagers/html/src/HTMLPackager.js:26 — packages/packagers/html/src/HTMLPackager.js:26 · packages/packagers/svg/src/SVGPackager.js:25 — the two spans are one implementation copied and then locally edited — 463 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 (73 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (73 matched lines × 2 locations) REDACTED:22 — REDACTED:22 · REDACTED:22 — the two spans are one implementation copied and then locally edited — 485 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (72 matched lines × 2 locations) packages/core/core/src/requests/TargetRequest.js:860 — packages/core/core/src/requests/TargetRequest.js:860 · packages/core/core/src/requests/TargetRequest.js:1065 — the two spans are one implementation copied and then locally edited — 332 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 (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) REDACTED:51 — REDACTED:51 · packages/transformers/sass/src/modern.js:57 — the two spans are one implementation copied and then locally edited — 325 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 (45 lines × 2 locations) · ×1
  • Duplicated block (45 lines × 2 locations) packages/packagers/js/src/dev-prelude.js:97 — packages/packagers/js/src/dev-prelude.js:97 · packages/packagers/react-static/src/ReactStaticPackager.js:433 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) packages/core/core/src/public/Symbols.js:29 — packages/core/core/src/public/Symbols.js:29 · packages/core/core/src/public/Symbols.js:98 — 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 (38 lines × 2 locations) · ×1
  • Duplicated block (38 lines × 2 locations) packages/reporters/dev-server-sw/src/HMRServer.js:84 — packages/reporters/dev-server-sw/src/HMRServer.js:84 · REDACTED:250 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×1
  • Duplicated block (37 lines × 2 locations) packages/transformers/postcss/src/loadPlugins.js:6 — packages/transformers/postcss/src/loadPlugins.js:6 · packages/transformers/posthtml/src/loadPlugins.js:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) packages/transformers/vue/src/VueTransformer.js:218 — packages/transformers/vue/src/VueTransformer.js:218 · packages/transformers/vue/src/VueTransformer.js:290 — the two spans are one implementation copied and then locally edited — 188 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 (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) packages/core/core/src/public/Bundle.js:214 — packages/core/core/src/public/Bundle.js:214 · packages/core/core/src/public/Bundle.js:269 — 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 (36 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (36 matched lines × 2 locations) packages/core/core/src/requests/AssetRequest.js:81 — packages/core/core/src/requests/AssetRequest.js:81 · packages/core/core/src/requests/DevDepRequest.js:119 — the two spans are one implementation copied and then locally edited — 245 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 (34 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (34 matched lines × 2 locations) packages/core/cache/src/FSCache.js:46 — packages/core/cache/src/FSCache.js:46 · packages/core/cache/src/LMDBCache.js:65 — the two spans are one implementation copied and then locally edited — 222 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 (34 lines × 2 locations) · ×1
  • Duplicated block (34 lines × 2 locations) packages/core/graph/src/AdjacencyList.js:556 — packages/core/graph/src/AdjacencyList.js:556 · packages/core/graph/src/AdjacencyList.js:614 — 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 (27 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (27 matched lines × 2 locations) packages/reporters/lsp-reporter/src/LspReporter.js:298 — packages/reporters/lsp-reporter/src/LspReporter.js:298 · packages/reporters/lsp-reporter/src/LspReporter.js:336 — the two spans are one implementation copied and then locally edited — 148 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 (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) packages/core/graph/src/AdjacencyList.js:1410 — packages/core/graph/src/AdjacencyList.js:1410 · packages/core/graph/src/AdjacencyList.js:1453 — 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 (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) packages/core/cache/src/IDBCache.browser.js:81 — packages/core/cache/src/IDBCache.browser.js:81 · packages/core/cache/src/LMDBCache.js:72 — the two spans are one implementation copied and then locally edited — 153 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 (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) REDACTED:373 — REDACTED:373 · REDACTED:506 — 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) REDACTED:86 — REDACTED:86 · packages/dev/repl/src/parcel/BrowserPackageManager.js:100 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) packages/core/core/src/SymbolPropagation.js:59 — packages/core/core/src/SymbolPropagation.js:59 · packages/core/core/src/SymbolPropagation.js:254 — 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 (20 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (20 matched lines × 2 locations) REDACTED:858 — REDACTED:858 · REDACTED:931 — the two spans are one implementation copied and then locally edited — 93 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 (19 lines × 3 locations) · ×1
  • Duplicated block (19 lines × 3 locations) packages/core/core/src/requests/TargetRequest.js:1339 — packages/core/core/src/requests/TargetRequest.js:1339 · packages/core/core/src/requests/TargetRequest.js:1361 · packages/core/core/src/requests/TargetRequest.js:1382 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) packages/core/logger/src/Logger.js:110 — packages/core/logger/src/Logger.js:110 · packages/core/types-internal/src/index.js:1052 — the two spans are one implementation copied and then locally edited — 73 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.
R2 · Cyclomatic Complexity · Complex function transform (cyclomatic 140, cognitive 265) · ×1
  • Complex function transform (cyclomatic 140, cognitive 265) REDACTED:336 — transform has cyclomatic complexity 140 and cognitive complexity 265; 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 resolvePackageTargets (cyclomatic 133, cognitive 237) · ×1
  • Complex function resolvePackageTargets (cyclomatic 133, cognitive 237) packages/core/core/src/requests/TargetRequest.js:440 — resolvePackageTargets has cyclomatic complexity 133 and cognitive complexity 237; 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 createIdealGraph (cyclomatic 96, cognitive 236) · ×1
  • Complex function createIdealGraph (cyclomatic 96, cognitive 236) REDACTED:364 — createIdealGraph has cyclomatic complexity 96 and cognitive complexity 236; 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 57, cognitive 192) · ×1
  • Complex function (anonymous) (cyclomatic 57, cognitive 192) packages/runtimes/rsc/src/RSCRuntime.js:40 — (anonymous) has cyclomatic complexity 57 and cognitive complexity 192; 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 collectDependencies (cyclomatic 57, cognitive 116) · ×1
  • Complex function collectDependencies (cyclomatic 57, cognitive 116) REDACTED:39 — collectDependencies has cyclomatic complexity 57 and cognitive complexity 116; 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 dumpGraphToGraphViz (cyclomatic 52, cognitive 137) · ×1
  • Complex function dumpGraphToGraphViz (cyclomatic 52, cognitive 137) packages/core/core/src/dumpGraphToGraphViz.js:38 — dumpGraphToGraphViz has cyclomatic complexity 52 and cognitive complexity 137; 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 enter (cyclomatic 48, cognitive 98) · ×1
  • Complex function enter (cyclomatic 48, cognitive 98) REDACTED:529 — enter has cyclomatic complexity 48 and cognitive complexity 98; 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 47, cognitive 77) · ×1
  • Complex function (anonymous) (cyclomatic 47, cognitive 77) packages/transformers/typescript-types/src/shake.js:38 — (anonymous) has cyclomatic complexity 47 and cognitive complexity 77; 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 getSymbolResolution (cyclomatic 47, cognitive 41) · ×1
  • Complex function getSymbolResolution (cyclomatic 47, cognitive 41) REDACTED:983 — getSymbolResolution has cyclomatic complexity 47 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 _report (cyclomatic 44, cognitive 60) · ×1
  • Complex function _report (cyclomatic 44, cognitive 60) packages/reporters/cli/src/CLIReporter.js:43 — _report has cyclomatic complexity 44 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveOptions (cyclomatic 44, cognitive 45) · ×1
  • Complex function resolveOptions (cyclomatic 44, cognitive 45) packages/core/core/src/resolveOptions.js:47 — resolveOptions has cyclomatic complexity 44 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function walk (cyclomatic 43, cognitive 141) · ×1
  • Complex function walk (cyclomatic 43, cognitive 141) packages/core/utils/src/schema.js:116 — walk has cyclomatic complexity 43 and cognitive complexity 141; 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 transform (cyclomatic 41, cognitive 76) · ×1
  • Complex function transform (cyclomatic 41, cognitive 76) REDACTED:44 — transform has cyclomatic complexity 41 and cognitive complexity 76; 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 buildAssetPrelude (cyclomatic 40, cognitive 73) · ×1
  • Complex function buildAssetPrelude (cyclomatic 40, cognitive 73) REDACTED:1151 — buildAssetPrelude has cyclomatic complexity 40 and cognitive complexity 73; 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 40, cognitive 67) · ×1
  • Complex function (anonymous) (cyclomatic 40, cognitive 67) packages/core/core/src/SymbolPropagation.js:257 — (anonymous) has cyclomatic complexity 40 and cognitive complexity 67; 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 package (cyclomatic 40, cognitive 65) · ×1
  • Complex function package (cyclomatic 40, cognitive 65) packages/packagers/js/src/DevPackager.js:46 — package has cyclomatic complexity 40 and cognitive complexity 65; 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 loadConfig (cyclomatic 40, cognitive 53) · ×1
  • Complex function loadConfig (cyclomatic 40, cognitive 53) REDACTED:181 — loadConfig has cyclomatic complexity 40 and cognitive complexity 53; 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 38, cognitive 87) · ×1
  • Complex function (anonymous) (cyclomatic 38, cognitive 87) packages/core/core/src/SymbolPropagation.js:62 — (anonymous) has cyclomatic complexity 38 and cognitive complexity 87; 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 codeFrame (cyclomatic 37, cognitive 72) · ×1
  • Complex function codeFrame (cyclomatic 37, cognitive 72) packages/core/codeframe/src/codeframe.js:42 — codeFrame has cyclomatic complexity 37 and cognitive complexity 72; 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 addExternal (cyclomatic 35, cognitive 101) · ×1
  • Complex function addExternal (cyclomatic 35, cognitive 101) REDACTED:812 — addExternal has cyclomatic complexity 35 and cognitive complexity 101; 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/core/types-internal/src/index.js · ×1
  • packages/core/types-internal/src/index.js: 1995 lines of code packages/core/types-internal/src/index.js:1 — packages/core/types-internal/src/index.js has 1995 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: 1944 lines of code REDACTED:1 — REDACTED has 1944 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: 1699 lines of code REDACTED:1 — REDACTED has 1699 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/core/core/src/requests/TargetRequest.js · ×1
  • packages/core/core/src/requests/TargetRequest.js: 1578 lines of code packages/core/core/src/requests/TargetRequest.js:1 — packages/core/core/src/requests/TargetRequest.js has 1578 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/core/graph/src/AdjacencyList.js · ×1
  • packages/core/graph/src/AdjacencyList.js: 1509 lines of code packages/core/graph/src/AdjacencyList.js:1 — packages/core/graph/src/AdjacencyList.js has 1509 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: 1365 lines of code REDACTED:1 — REDACTED has 1365 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: 1359 lines of code REDACTED:1 — REDACTED has 1359 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: 1300 lines of code REDACTED:1 — REDACTED has 1300 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: 1129 lines of code REDACTED:1 — REDACTED has 1129 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: 1046 lines of code REDACTED:1 — REDACTED has 1046 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/core/fs/src/MemoryFS.js · ×1
  • packages/core/fs/src/MemoryFS.js: 923 lines of code packages/core/fs/src/MemoryFS.js:1 — packages/core/fs/src/MemoryFS.js has 923 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: 801 lines of code REDACTED:1 — REDACTED has 801 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: 769 lines of code REDACTED:1 — REDACTED has 769 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/core/core/src/SymbolPropagation.js · ×1
  • packages/core/core/src/SymbolPropagation.js: 730 lines of code packages/core/core/src/SymbolPropagation.js:1 — packages/core/core/src/SymbolPropagation.js has 730 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: 686 lines of code REDACTED:1 — REDACTED has 686 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/dev/repl/src/utils/assets.js · ×1
  • packages/dev/repl/src/utils/assets.js: 665 lines of code packages/dev/repl/src/utils/assets.js:1 — packages/dev/repl/src/utils/assets.js has 665 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/runtimes/hmr/src/loaders/hmr-runtime.js · ×1
  • packages/runtimes/hmr/src/loaders/hmr-runtime.js: 660 lines of code packages/runtimes/hmr/src/loaders/hmr-runtime.js:1 — packages/runtimes/hmr/src/loaders/hmr-runtime.js has 660 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/core/core/src/requests/ParcelConfigRequest.js · ×1
  • packages/core/core/src/requests/ParcelConfigRequest.js: 648 lines of code packages/core/core/src/requests/ParcelConfigRequest.js:1 — packages/core/core/src/requests/ParcelConfigRequest.js has 648 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/packagers/react-static/src/ReactStaticPackager.js · ×1
  • packages/packagers/react-static/src/ReactStaticPackager.js: 642 lines of code packages/packagers/react-static/src/ReactStaticPackager.js:1 — packages/packagers/react-static/src/ReactStaticPackager.js has 642 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: 641 lines of code REDACTED:1 — REDACTED has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 620 lines of code REDACTED:1 — REDACTED has 620 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: 617 lines of code REDACTED:1 — REDACTED has 617 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: 603 lines of code REDACTED:1 — REDACTED has 603 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: 590 lines of code REDACTED:1 — REDACTED has 590 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 587 lines of code REDACTED:1 — REDACTED has 587 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/transformers/webextension/src/schema.js · ×1
  • packages/transformers/webextension/src/schema.js: 562 lines of code packages/transformers/webextension/src/schema.js:1 — packages/transformers/webextension/src/schema.js has 562 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/core/core/src/types.js · ×1
  • packages/core/core/src/types.js: 529 lines of code packages/core/core/src/types.js:1 — packages/core/core/src/types.js has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/dev/esm-fuzzer/generateExample.js · ×1
  • packages/dev/esm-fuzzer/generateExample.js: 526 lines of code packages/dev/esm-fuzzer/generateExample.js:1 — packages/dev/esm-fuzzer/generateExample.js has 526 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/core/core/src/requests/AssetGraphRequest.js · ×1
  • packages/core/core/src/requests/AssetGraphRequest.js: 518 lines of code packages/core/core/src/requests/AssetGraphRequest.js:1 — packages/core/core/src/requests/AssetGraphRequest.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/core/parcel/src/cli.js · ×1
  • packages/core/parcel/src/cli.js: 515 lines of code packages/core/parcel/src/cli.js:1 — packages/core/parcel/src/cli.js has 515 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/core/utils/src/schema.js · ×1
  • packages/core/utils/src/schema.js: 490 lines of code packages/core/utils/src/schema.js:1 — packages/core/utils/src/schema.js has 490 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/core/core/src/Parcel.js · ×1
  • packages/core/core/src/Parcel.js: 489 lines of code packages/core/core/src/Parcel.js:1 — packages/core/core/src/Parcel.js has 489 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/transformers/vue/src/VueTransformer.js · ×1
  • packages/transformers/vue/src/VueTransformer.js: 488 lines of code packages/transformers/vue/src/VueTransformer.js:1 — packages/transformers/vue/src/VueTransformer.js has 488 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/core/core/src/requests/BundleGraphRequest.js · ×1
  • packages/core/core/src/requests/BundleGraphRequest.js: 487 lines of code packages/core/core/src/requests/BundleGraphRequest.js:1 — packages/core/core/src/requests/BundleGraphRequest.js has 487 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/reporters/dev-server/src/Server.js · ×1
  • packages/reporters/dev-server/src/Server.js: 481 lines of code packages/reporters/dev-server/src/Server.js:1 — packages/reporters/dev-server/src/Server.js has 481 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/core/core/src/ParcelConfig.js · ×1
  • packages/core/core/src/ParcelConfig.js: 451 lines of code packages/core/core/src/ParcelConfig.js:1 — packages/core/core/src/ParcelConfig.js has 451 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: 446 lines of code REDACTED:1 — REDACTED has 446 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/runtimes/rsc/src/RSCRuntime.js · ×1
  • packages/runtimes/rsc/src/RSCRuntime.js: 439 lines of code packages/runtimes/rsc/src/RSCRuntime.js:1 — packages/runtimes/rsc/src/RSCRuntime.js has 439 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/dev/repl/src/index.js · ×1
  • packages/dev/repl/src/index.js: 426 lines of code packages/dev/repl/src/index.js:1 — packages/dev/repl/src/index.js has 426 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: 425 lines of code REDACTED:1 — REDACTED has 425 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~276 LoC) · ×1
  • Dead file (~276 LoC) packages/dev/repl/SimplePackageInstaller/index.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~75 LoC) · ×1
  • Dead file (~75 LoC) packages/dev/repl/SimplePackageInstaller/untar.js — no import path from any entry point (289 application, 23 tooling, 187 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/dev/repl/SimplePackageInstaller/index.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 (~35 LoC) · ×1
  • Dead file (~35 LoC) packages/core/utils/src/bundle-url.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~31 LoC) · ×1
  • Dead file (~31 LoC) REDACTED — no import path from any entry point (289 application, 23 tooling, 187 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 (~20 LoC) · ×1
  • Dead file (~20 LoC) packages/core/utils/src/getExisting.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~17 LoC) · ×1
  • Dead file (~17 LoC) scripts/postinstall.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~16 LoC) · ×1
  • Dead file (~16 LoC) packages/core/types-internal/scripts/build-ts.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~14 LoC) · ×1
  • Dead file (~14 LoC) packages/dev/esm-fuzzer/writeExample.js — no import path from any entry point (289 application, 23 tooling, 187 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 (~1 LoC) · ×1
  • Dead file (~1 LoC) packages/utils/parcelforvscode/src/server.ts — no import path from any entry point (289 application, 23 tooling, 187 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
R8 · Dependency Hygiene · Unlisted import '@mischnic/json-sourcemap' · ×1
  • Unlisted import '@mischnic/json-sourcemap' packages/core/utils/src/schema.js:7 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
R8 · Dependency Hygiene · Unused dependency 'clone' · ×1
  • Unused dependency 'clone' — Declared in packages/core/core/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 'utility-types' · ×1
  • Unused dependency 'utility-types' — Declared in packages/core/fs/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 '@mdx-js/react' · ×1
  • Unused dependency '@mdx-js/react' — Declared in packages/core/integration-tests/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.
Minor — 365 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×248
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/core/types-internal/src/index.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 crates/parcel-resolver/src/package_json.rs: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/core/core/src/requests/TargetRequest.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/core/graph/src/AdjacencyList.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 REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file crates/html/src/oxvg.rs: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 crates/html/src/jsx.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/transformers/js/core/src/collect.rs: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 crates/html/src/optimize.rs: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 crates/macros/src/lib.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/core/core/src/SymbolPropagation.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/transformers/js/core/src/lib.rs: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/core/fs/src/MemoryFS.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 REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file crates/html/src/dependencies.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/transformers/js/core/src/modules.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/transformers/js/core/src/env_replacer.rs: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.
  • + 223 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×39
  • Disabled test packages/core/integration-tests/test/babel.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 packages/core/integration-tests/test/babel.js:65 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/babel.js:119 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/babel.js:152 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/babel.js:366 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/cache.js:1316 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/cache.js:1318 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/css.js:89 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/fs.js:78 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/fs.js:86 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/fs.js:102 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/fs.js:212 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:445 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:683 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:760 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:872 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:1007 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/html.js:1031 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:176 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:304 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:507 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:529 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:1827 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:1958 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/core/integration-tests/test/javascript.js:1982 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 14 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×23
  • Duplicated predicate packages/core/package-manager/src/Npm.js:40 — `!key.startsWith('npm_') && key !== 'INIT_CWD' && key !== 'NODE_ENV'` appears character-identically in 2 files — packages/core/package-manager/src/Npm.js, 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/packagers/react-static/src/ReactStaticPackager.js:170 — `Array.isArray(a.meta.directives) && a.meta.directives.includes('use client-entry')` appears character-identically in 2 files — packages/packagers/react-static/src/ReactStaticPackager.js, packages/runtimes/rsc/src/RSCRuntime.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/reporters/cli/src/emoji.js:11 — `Boolean(process.env.CI) || Boolean(process.env.WT_SESSION) || process.env.ConEmuTask === '{cmd::Cmder}' || process.env.TERM_PROGRAM === 'vsc…` appears character-identically in 3 files — packages/reporters/cli/src/emoji.js, REDACTED, packages/utils/create-react-app/src/emoji.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/reporters/dev-server-sw/src/HMRServer.js:88 — `asset.type !== 'js' && asset.type !== 'css'` appears character-identically in 2 files — packages/reporters/dev-server-sw/src/HMRServer.js, 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/optimizers/swc/src/SwcOptimizer.js:43 — `bundle.env.outputFormat === 'esmodule' || bundle.env.outputFormat === 'commonjs'` appears character-identically in 2 files — packages/optimizers/swc/src/SwcOptimizer.js, packages/optimizers/terser/src/TerserOptimizer.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/packagers/html/src/HTMLPackager.js:126 — `bundle.type === 'css' && !isDirectlyReferenced` appears character-identically in 2 files — packages/packagers/html/src/HTMLPackager.js, packages/packagers/svg/src/SVGPackager.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/packagers/html/src/HTMLPackager.js:133 — `bundle.type === 'js' && !isDirectlyReferenced` appears character-identically in 2 files — packages/packagers/html/src/HTMLPackager.js, packages/packagers/svg/src/SVGPackager.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/transformers/typescript-types/src/TSTypesTransformer.js:106 — `file != null && diagnostic.start != null` appears character-identically in 2 files — packages/transformers/typescript-types/src/TSTypesTransformer.js, packages/validators/typescript/src/TypeScriptValidator.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/packagers/js/src/dev-prelude.js:111 — `key === 'default' || key === '__esModule' || Object.prototype.hasOwnProperty.call(m, key)` appears character-identically in 2 files — packages/packagers/js/src/dev-prelude.js, packages/packagers/react-static/src/ReactStaticPackager.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/utils/create-parcel/templates/react-server/src/client.tsx:42 — `link && link instanceof HTMLAnchorElement && link.href && (!link.target || link.target === '_self') && link.origin === location.origin && !l…` appears character-identically in 2 files — packages/utils/create-parcel/templates/react-server/src/client.tsx, packages/utils/create-parcel/templates/react-static/src/client.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/optimizers/swc/src/SwcOptimizer.js:70 — `mapping && mapping.original && mapping.source` appears character-identically in 2 files — packages/optimizers/swc/src/SwcOptimizer.js, packages/optimizers/terser/src/TerserOptimizer.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/utils/babel-plugin-transform-runtime/src/index.js:12 — `name === 'parcel' && typeof version === 'string' && semver.satisfies(version, COMPATIBLE_PARCEL_BABEL_TRANSFORMER_SEMVER)` appears character-identically in 2 files — packages/utils/babel-plugin-transform-runtime/src/index.js, packages/utils/babel-preset-env/src/index.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:538 — `node.type === 'asset' || node.type === 'dependency'` appears character-identically in 2 files — REDACTED, packages/core/core/src/applyRuntimes.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/core/core/src/requests/BundleGraphRequest.js:113 — `options.shouldBuildLazily && requestedAssetIds.size > 0` appears character-identically in 2 files — packages/core/core/src/requests/BundleGraphRequest.js, packages/core/core/src/requests/ParcelBuildRequest.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/core/utils/src/import-map.js:54 — `parent.env.context !== bundle.env.context || parent.type !== 'js'` appears character-identically in 2 files — packages/core/utils/src/import-map.js, 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/core/parcel/src/bin.js:6 — `process.env.PARCEL_BUILD_ENV !== 'production' || process.env.PARCEL_SELF_BUILD` appears character-identically in 4 files — packages/core/parcel/src/bin.js, packages/dev/bundle-stats-cli/src/bin.js, packages/dev/query/src/bin.js, packages/dev/repl/src/parcel/BrowserPackageManager.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/core/core/src/worker.js:36 — `process.env.PARCEL_BUILD_REPL && process.browser` appears character-identically in 2 files — packages/core/core/src/worker.js, packages/runtimes/hmr/src/HMRRuntime.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/reporters/dev-server-sw/src/HMRServer.js:96 — `resolved?.type === 'js' && resolved !== asset` appears character-identically in 2 files — packages/reporters/dev-server-sw/src/HMRServer.js, 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 REDACTED:615 — `result.diagnostics && result.diagnostics.length > 0` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:53 — `ts.isQualifiedName(node) && ts.isIdentifier(node.left)` appears character-identically in 2 files — REDACTED, packages/transformers/typescript-types/src/shake.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/core/core/src/CommittedAsset.js:63 — `typeof content === 'string' || content instanceof Buffer` appears character-identically in 2 files — packages/core/core/src/CommittedAsset.js, 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/transformers/typescript-types/src/TSTypesTransformer.js:125 — `typeof diagnostic.start === 'number' && typeof diagnostic.length === 'number'` appears character-identically in 2 files — packages/transformers/typescript-types/src/TSTypesTransformer.js, packages/validators/typescript/src/TypeScriptValidator.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate crates/parcel-resolver/src/tsconfig.rs:160 — `(best_key.is_none() || prefix.len() > longest_prefix_length) && full_specifier.starts_with(prefix) && full_specifier.ends_with(suffix)` appears character-identically in 2 files — crates/parcel-resolver/src/tsconfig.rs, packages/utils/node-resolver-rs/src/tsconfig.rs. 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.
D30 · Dependency Vulnerabilities · Low CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R7 · Dead Code · Unused export 'default' · ×6
  • Unused export 'default' packages/core/workers/src/process/ProcessWorker.js:16 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' packages/core/workers/src/threads/ThreadsWorker.js:16 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' packages/core/workers/src/web/WebWorker.js:15 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' packages/utils/error-overlay/src/utils/getPrettyURL.js:47 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' packages/utils/error-overlay/src/utils/isBultinErrorName.js:25 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' packages/utils/error-overlay/src/utils/parser.js:101 — Nothing imports this binding — it is safe to review for removal.
M4 · Documentation accuracy · README/code drift · ×5
  • README/code drift CONTRIBUTING.md:44 — CONTRIBUTING.md runs `yarn flow check`, but no package.json declares a `flow` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING.md:86 — CONTRIBUTING.md names the package `@parcel/*`, but no package.json of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift README.md:30 — README.md names Parcel 1, but the manifest declares `parcel` ^2.14.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.
  • README/code drift packages/core/parcel/README.md:30 — packages/core/parcel/README.md names Parcel 1, but the manifest declares `parcel` ^2.14.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.
  • README/code drift packages/core/parcel/README.md:44 — packages/core/parcel/README.md links to `CONTRIBUTING.md`, but `packages/core/parcel/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file packages/transformers/js/core/src/hoist.rs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file crates/parcel-resolver/src/lib.rs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file packages/transformers/js/core/src/dependency_collector.rs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
P2 · Observability · Console output used as the logging channel · ×3
  • Console output used as the logging channel packages/core/core/src/dumpGraphToGraphViz.js:222 — `packages/core/core/src/dumpGraphToGraphViz.js` reports through `console.*` at line 222 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/optimizers/inline-requires/src/RequireInliningVisitor.js:185 — `packages/optimizers/inline-requires/src/RequireInliningVisitor.js` reports through `console.*` at line 185 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel packages/optimizers/inline-requires/src/RequireInliningVisitor.js:190 — `packages/optimizers/inline-requires/src/RequireInliningVisitor.js` reports through `console.*` at line 190 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch packages/core/integration-tests/test/integration/resolve-entries/pkg-ignore-fs/index.js:6 — `default` swallows every exception into `return 'test-pkg-ignore-fs-ok'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch REDACTED:13 — `exec` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/core/workers/src/backend.js:17 — `detectBackend` swallows every exception into `return 'process'` — 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, 4 significant file(s) lose their only recent owner: REDACTED, packages/packagers/react-static/src/ReactStaticPackager.js, packages/runtimes/rsc/src/RSCRuntime.js, packages/reporters/dev-server/src/ServerReporter.js. Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 141 project(s) overshoot their size bounds, lowering Project Cohesion to 9.9/10. The most over is `packages/core/core` (18811 LoC, 165 module-visible types across 3 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 251 of 251 significant files have no living knowledge — the codebase as a whole is dormant, not 251 separate risks. Counted over 251 of the 529 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D9 · Test Distribution · Inverted test pyramid · ×1
  • Inverted test pyramid — Only 30 % of tests are unit tests (722 unit vs 1706 integration, 0 BDD); a broader unit base gives faster, more localised feedback.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 28/38 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/dev-dep-resolver`, `packages/core/parcel`, `packages/dev/bundle-stats-cli`, `packages/dev/parcel-link`, `packages/dev/query` and 5 more.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add cargo-audit / cargo-deny (or clippy) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 16482 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.
R7 · Dead Code · Unused export 'create' · ×1
  • Unused export 'create' packages/core/core/src/requests/ParcelConfigRequest.js:205 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'cacheSerializedObject' · ×1
  • Unused export 'cacheSerializedObject' packages/core/core/src/serializer.js:243 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'deserializeToCache' · ×1
  • Unused export 'deserializeToCache' packages/core/core/src/serializer.js:247 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'removeSerializedObjectFromCache' · ×1
  • Unused export 'removeSerializedObjectFromCache' packages/core/core/src/serializer.js:253 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'toInternalSymbols' · ×1
  • Unused export 'toInternalSymbols' packages/core/core/src/utils.js:193 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'run' · ×1
  • Unused export 'run' REDACTED:25 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'useBodyClass' · ×1
  • Unused export 'useBodyClass' packages/dev/repl/src/components/helper.js:319 — Nothing ultimately consumes this binding: its only referrer is the re-export in packages/dev/repl/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/dev/repl/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'BUILTINS' · ×1
  • Unused export 'BUILTINS' packages/dev/repl/src/parcel/BrowserPackageManager.js:43 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'warning' · ×1
  • Unused export 'warning' packages/utils/create-react-app/src/emoji.js:26 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'hint' · ×1
  • Unused export 'hint' packages/utils/create-react-app/src/emoji.js:28 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Write-only private field '#pkgFilePath' · ×1
  • Write-only private field '#pkgFilePath' REDACTED:32 — This private field is assigned but never read: every reference in its class is a plain assignment, no string key or test reads it by name, and the instance never escapes as a whole (so nothing serialises or destructures it). The value it holds is dead state — read it where it was meant to take effect, or remove the field and its assignments.
R8 · Dependency Hygiene · Type-only dependency '@parcel/source-map' in production deps · ×1
  • Type-only dependency '@parcel/source-map' in production deps packages/core/types-internal/src/index.js:4 — Every import is type-only — move it to devDependencies.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/4 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 7/23 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 — ~0.9 `!` null assertions per 1k TypeScript source lines — 1 assertion(s) across the 1101 source line(s) of the 20 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/utils/create-parcel/templates/react-client/src/index.tsx (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 86 finding(s)
D10 · Test Quality · Skipped (documented) · ×66
  • Skipped (documented): should compile node_modules when symlinked with a source field in package.json packages/core/integration-tests/test/transpilation.js:471 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): (unnamed test) packages/core/integration-tests/test/sourcemaps.js:626 — 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/core/integration-tests/test/sourcemaps.js:669 — 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/core/integration-tests/test/sourcemaps.js:670 — 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/core/integration-tests/test/sourcemaps.js:674 — 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/core/integration-tests/test/sourcemaps.js:757 — 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/core/integration-tests/test/sourcemaps.js:758 — 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/core/integration-tests/test/sourcemaps.js:762 — 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/core/integration-tests/test/sourcemaps.js:808 — 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/core/integration-tests/test/sourcemaps.js:809 — 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/core/integration-tests/test/sourcemaps.js:856 — 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/core/integration-tests/test/sourcemaps.js:914 — 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/core/integration-tests/test/sourcemaps.js:915 — 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/core/integration-tests/test/sourcemaps.js:919 — 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/core/integration-tests/test/sourcemaps.js:962 — 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/core/integration-tests/test/sourcemaps.js:963 — 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/core/integration-tests/test/sourcemaps.js:1154 — 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/core/integration-tests/test/sourcemaps.js:1230 — 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/core/integration-tests/test/sourcemaps.js:1231 — 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/core/integration-tests/test/scope-hoisting.js:3476 — 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/core/integration-tests/test/javascript.js:2287 — 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): should invalidate when there are symlinked plugins packages/core/integration-tests/test/cache.js:919 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a this.skip()/t.skip() call
  • Skipped (documented): (unnamed test) packages/core/integration-tests/test/integration/entry-point/index.js:1 — 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/core/integration-tests/test/integration/env-disabled/index.js:4 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • Skipped (documented): (unnamed test) packages/core/integration-tests/test/integration/env-disabled/index.js:7 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
  • + 41 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×20
  • Outdated: anyhow — `anyhow` is locked at 1.0.93 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"*"` requirement declared in crates/html/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
  • Outdated: bitflags — `bitflags` is locked at 2.8.0 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.7.0"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
  • Outdated: dashmap — `dashmap` is locked at 6.1.0 but 6.2.1 is the current stable release on crates.io, and it already satisfies the `"6.1.0"` requirement declared in crates/dev-dep-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p dashmap` and commit the updated REDACTED.
  • Outdated: data-encoding — `data-encoding` is locked at 2.6.0 but 2.11.1 is the current stable release on crates.io, and it already satisfies the `"2.3.2"` requirement declared in packages/transformers/js/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p data-encoding` and commit the updated REDACTED.
  • Outdated: glob — `glob` is locked at 0.3.1 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3.1"` requirement declared in crates/dev-dep-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
  • Outdated: libc — `libc` is locked at 0.2.164 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/node-bindings/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
  • Outdated: markdown — `markdown` is locked at 1.0.0-alpha.22 but 1.0.0 is the current stable release on crates.io, and it already satisfies the `"1.0.0-alpha.22"` requirement declared in packages/transformers/js/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p markdown` and commit the updated REDACTED.
  • Outdated: mimalloc — `mimalloc` is locked at 0.1.43 but 0.1.52 is the current stable release on crates.io, and it already satisfies the `"0.1.25"` requirement declared in crates/node-bindings/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mimalloc` and commit the updated REDACTED.
  • Outdated: mozjpeg-sys — `mozjpeg-sys` is locked at 2.2.1 but 2.2.3 is the current stable release on crates.io, and it already satisfies the `"2.0.0"` requirement declared in crates/node-bindings/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mozjpeg-sys` and commit the updated REDACTED.
  • Outdated: napi-build — `napi-build` is locked at 2.1.3 but 2.6.0 is the current stable release on crates.io, and it already satisfies the `"2.1.3"` requirement declared in crates/node-bindings/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p napi-build` and commit the updated REDACTED.
  • Outdated: pathdiff — `pathdiff` is locked at 0.2.2 but 0.2.3 is the current stable release on crates.io, and it already satisfies the `"0.2.0"` requirement declared in packages/transformers/js/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p pathdiff` and commit the updated REDACTED.
  • Outdated: percent-encoding — `percent-encoding` is locked at 2.3.1 but 2.3.2 is the current stable release on crates.io, and it already satisfies the `"2.2.0"` requirement declared in crates/parcel-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p percent-encoding` and commit the updated REDACTED.
  • Outdated: rayon — `rayon` is locked at 1.10.0 but 1.12.0 is the current stable release on crates.io, and it already satisfies the `"1.7.0"` requirement declared in crates/dev-dep-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rayon` and commit the updated REDACTED.
  • Outdated: ref-cast — `ref-cast` is locked at 1.0.24 but 1.0.27 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in crates/html/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ref-cast` and commit the updated REDACTED.
  • Outdated: rustc-hash — `rustc-hash` is locked at 2.0.0 but 2.1.3 is the current stable release on crates.io, and it already satisfies the `"2.0.0"` requirement declared in crates/parcel-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustc-hash` and commit the updated REDACTED.
  • Outdated: serde — `serde` is locked at 1.0.215 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0.123"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
  • Outdated: serde_bytes — `serde_bytes` is locked at 0.11.15 but 0.11.19 is the current stable release on crates.io, and it already satisfies the `"0.11.5"` requirement declared in crates/core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_bytes` and commit the updated REDACTED.
  • Outdated: serde_json — `serde_json` is locked at 1.0.133 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.91"` requirement declared in crates/dev-dep-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
  • Outdated: url — `url` is locked at 2.5.4 but 2.5.8 is the current stable release on crates.io, and it already satisfies the `"2.5.4"` requirement declared in crates/parcel-resolver/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p url` and commit the updated REDACTED.
  • Outdated: xxhash-rust — `xxhash-rust` is locked at 0.8.12 but 0.8.19 is the current stable release on crates.io, and it already satisfies the `"0.8.2"` requirement declared in crates/node-bindings/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p xxhash-rust` and commit the updated REDACTED.

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-f81576db26554dacb240c62506f96093/history.json --exit-code 0 --source .3artifacts/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-f81576db26554dacb240c62506f96093/tree.json --exit-code 0 --source .3artifacts/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 .176artifacts/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-update105artifacts/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 111 file(s) — `flow-libs/deasync.js`, `flow-typed/npm/@swc/core_v1.x.x.js`, `flow-typed/npm/chalk_v4.x.x.js`, `flow-typed/npm/express_v4.x.x.js`, `flow-typed/npm/mime_v2.x.x.js`, … (+106 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a16e92-cca3-7e81-badc-6afe30d4bc45 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 175 · Warnings: 1103 · Recommendations: 365 · Info: 86 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 24-10-2026 @ 15:41 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