Public report of zloirock/core-js, published 15 November 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.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 03:48 UTC · Survey ID cd_b9aba1e6bdcc4401871cc21d5ef5bf6f

zloirock/core-js

Measured 15 November 2026, 03:47 UTC, at code version 04ef14c

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 57out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey

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

A medium codebase: 55,653 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Code Health, 50

Findings by how serious they are

70 critical 375 serious 65 minor

11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 03:47 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work 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 ▸

57of 57 dimensions measured by tools.
488of 510 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
57dimensions across 6 lenses, read from 55,653 lines of product code in 10 projects.
Chapters

Executive summary

zloirock/core-js falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 57 out of 100 and is rated Adequate, and 68 of its 70 critical findings are security problems.

Code Health, at 50, is the weakest lens and counts most in the score. The best first step is adding type checking, worth about 5 points. Simplifying the most tangled methods comes next, worth about 2 points. Raising Code Health to 70 would lift the score to about 62.

Forty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-two secrets can leak from the build pipeline, and three known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The two sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 55,653 lines, about €130,000 to rebuild.

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

How the score is built: what each lens counts 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.
Code Health 50 · counts for 46%Production Readiness 53 · counts for 25%Maturity 63 · counts for 14%Security and Compliance 67 · counts for 8%Architecture 95 · counts for 4%Performance 100 · counts for 2%

If Code Health rose from 50 to 70, the lowest score rated Strong, the score would rise from 57 to about 62.

Code composition: what the lines of code are
Product code 45%Tests 55%
New since the last survey: 189 findings

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

  • Cyclomatic Complexity · parse (cyclomatic 190) packages/core-js/modules/web.url.constructor.js
  • Cyclomatic Complexity · url-domain-to-ascii.mapCodePoint (cyclomatic 48) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 44) packages/core-js/internals/iterator-define.js
  • Cyclomatic Complexity · exports (cyclomatic 43) packages/core-js-pure/override/internals/export.js
  • Cyclomatic Complexity · web.structured-clone.prepareTransfer (cyclomatic 37) packages/core-js/modules/web.structured-clone.js
  • Cyclomatic Complexity · url-search-params-body.patchFetch (cyclomatic 32) packages/core-js/internals/url-search-params-body.js
  • Cyclomatic Complexity · web.structured-clone.cloneView (cyclomatic 26) packages/core-js/modules/web.structured-clone.js
  • Cyclomatic Complexity · url-domain-to-ascii.default (cyclomatic 26) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 26) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 26) packages/core-js-compat/targets-parser.js
  • Cyclomatic Complexity · (anonymous) (cyclomatic 26) REDACTED
  • Cyclomatic Complexity · string-punycode.decode (cyclomatic 25) packages/core-js/internals/string-punycode.js
  • Cyclomatic Complexity · url-search-params-body.patchXMLHttpRequest (cyclomatic 24) packages/core-js/internals/url-search-params-body.js
  • Cyclomatic Complexity · url-domain-to-ascii.isIgnored (cyclomatic 24) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · async-iterator-iteration.createMethod.<returned closure> (cyclomatic 22) packages/core-js/internals/async-iterator-iteration.js
  • Cyclomatic Complexity · createMethod (cyclomatic 22) packages/core-js/internals/async-iterator-iteration.js
  • Cyclomatic Complexity · toExponential (cyclomatic 21) packages/core-js/modules/es.number.to-exponential.js
  • Cyclomatic Complexity · zip (cyclomatic 20) packages/core-js/modules/es.iterator.zip.js
  • Cyclomatic Complexity · createMethod (cyclomatic 20) packages/core-js/internals/array-iteration.js
  • Cyclomatic Complexity · array-iteration.createMethod.<returned closure> (cyclomatic 19) packages/core-js/internals/array-iteration.js
  • Cyclomatic Complexity · exports (cyclomatic 19) packages/core-js/internals/export.js
  • Cyclomatic Complexity · (anonymous) (cyclomatic 18) packages/core-js/modules/web.url-search-params.delete.js
  • Cyclomatic Complexity · array-buffer-is-detached.default (cyclomatic 17) packages/core-js/internals/array-buffer-is-detached.js
  • Cyclomatic Complexity · url-domain-to-ascii.checkJoiners (cyclomatic 17) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 17) packages/core-js/internals/array-buffer-is-detached.js
  • Cyclomatic Complexity · es.json.parse.internalizeProperty (cyclomatic 16) packages/core-js/modules/es.json.parse.js
  • Cyclomatic Complexity · fix-regexp-well-known-symbol-logic.default (cyclomatic 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js
  • Cyclomatic Complexity · number-decimal-digits.exactDigits (cyclomatic 16) packages/core-js/internals/number-decimal-digits.js
  • Cyclomatic Complexity · url-domain-to-ascii.mapDomain (cyclomatic 16) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · url-domain-to-ascii.checkBidi (cyclomatic 16) packages/core-js/internals/url-domain-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js
  • Cyclomatic Complexity · toPrecision (cyclomatic 16) packages/core-js/modules/es.number.to-precision.js
  • Cognitive Complexity · parse (cognitive 347) packages/core-js/modules/web.url.constructor.js
  • Cognitive Complexity · patchFetch (cognitive 68) packages/core-js/internals/url-search-params-body.js
  • Cognitive Complexity · exports (cognitive 56) packages/core-js/internals/iterator-define.js
  • Cognitive Complexity · exports (cognitive 55) packages/core-js-pure/override/internals/export.js
  • Cognitive Complexity · zip (cognitive 54) packages/core-js/modules/es.iterator.zip.js
  • Cognitive Complexity · prepareTransfer (cognitive 50) packages/core-js/modules/web.structured-clone.js
  • Cognitive Complexity · decode (cognitive 45) packages/core-js/internals/string-punycode.js
  • Cognitive Complexity · async-iterator-iteration.createMethod.<returned closure> (cognitive 44) packages/core-js/internals/async-iterator-iteration.js
  • Cognitive Complexity · cloneView (cognitive 44) packages/core-js/modules/web.structured-clone.js
  • Cognitive Complexity · createMethod (cognitive 44) packages/core-js/internals/async-iterator-iteration.js
  • Cognitive Complexity · exports (cognitive 41) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · url-domain-to-ascii.default (cognitive 40) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · url-search-params-body.patchXMLHttpRequest (cognitive 37) packages/core-js/internals/url-search-params-body.js
  • Cognitive Complexity · mapDomain (cognitive 37) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · exports (cognitive 37) packages/core-js-compat/targets-parser.js
  • Cognitive Complexity · exports (cognitive 37) packages/core-js/internals/export.js
  • Cognitive Complexity · mapCodePoint (cognitive 32) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · array-iteration.createMethod.<returned closure> (cognitive 31) packages/core-js/internals/array-iteration.js
  • Cognitive Complexity · createMethod (cognitive 30) packages/core-js/internals/array-iteration.js
  • Cognitive Complexity · web.structured-clone.replaceReferences (cognitive 28) packages/core-js/modules/web.structured-clone.js
  • Cognitive Complexity · encode (cognitive 26) packages/core-js/internals/string-punycode.js
  • Cognitive Complexity · number-decimal-digits.exactDigits (cognitive 25) packages/core-js/internals/number-decimal-digits.js
  • Cognitive Complexity · (anonymous) (cognitive 25) packages/core-js/modules/web.url-search-params.delete.js
  • Cognitive Complexity · number-decimal-digits.default (cognitive 23) packages/core-js/internals/number-decimal-digits.js
  • Cognitive Complexity · url-domain-to-ascii.checkJoiners (cognitive 23) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · url-domain-to-ascii.bidiClass (cognitive 23) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · internalizeProperty (cognitive 23) packages/core-js/modules/es.json.parse.js
  • Cognitive Complexity · exports (cognitive 23) packages/core-js/internals/number-decimal-digits.js
  • Cognitive Complexity · parseObject (cognitive 22) packages/core-js/modules/web.url-search-params.constructor.js
  • Cognitive Complexity · (anonymous) (cognitive 21) packages/core-js/internals/array-buffer-transfer.js
  • Cognitive Complexity · assign (cognitive 21) packages/core-js/internals/object-assign.js
  • Cognitive Complexity · web.structured-clone.performTransfer (cognitive 20) packages/core-js/modules/web.structured-clone.js
  • Cognitive Complexity · array-includes.createMethod.<returned closure> (cognitive 19) packages/core-js/internals/array-includes.js
  • Cognitive Complexity · es.typed-array.sort.getSortCompare.<returned closure> (cognitive 19) packages/core-js/modules/es.typed-array.sort.js
  • Cognitive Complexity · array-from-async.fromAsync (cognitive 18) packages/core-js/internals/array-from-async.js
  • Cognitive Complexity · array-reduce.createMethod.<returned closure> (cognitive 18) packages/core-js/internals/array-reduce.js
  • Cognitive Complexity · delete (cognitive 18) packages/core-js/modules/web.url-search-params.constructor.js
  • Cognitive Complexity · isIgnored (cognitive 18) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · checkBidi (cognitive 18) packages/core-js/internals/url-domain-to-ascii.js
  • Cognitive Complexity · toPrecision (cognitive 18) packages/core-js/modules/es.number.to-precision.js
  • Cognitive Complexity · exports (cognitive 17) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js
  • Cognitive Complexity · fix-regexp-well-known-symbol-logic.default (cognitive 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js
  • Cognitive Complexity · exports (cognitive 16) packages/core-js/internals/array-buffer-is-detached.js
  • Cognitive Complexity · getSortCompare (cognitive 16) packages/core-js/modules/es.typed-array.sort.js
  • God Classes · FileTooLong: modules/web.structured-clone.js packages/core-js/modules/web.structured-clone.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/modules/web.structured-clone.js packages/core-js/modules/web.structured-clone.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js-pure/override/internals/export.js packages/core-js-pure/override/internals/export.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/internals/string-punycode.js packages/core-js/internals/string-punycode.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js-compat/targets-parser.js packages/core-js-compat/targets-parser.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/internals/array-buffer-is-detached.js packages/core-js/internals/array-buffer-is-detached.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/modules/web.url-search-params.delete.js packages/core-js/modules/web.url-search-params.delete.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/modules/es.iterator.zip.js packages/core-js/modules/es.iterator.zip.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/internals/iterate.js packages/core-js/internals/iterate.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/internals/array-buffer-transfer.js packages/core-js/internals/array-buffer-transfer.js
  • Churn × Complexity Hotspots · Hotspot: tests/unit-global/esnext.function.is-constructor.js tests/unit-global/esnext.function.is-constructor.js
  • Churn × Complexity Hotspots · Hotspot: packages/core-js/internals/iterator-create-proxy.js packages/core-js/internals/iterator-create-proxy.js
  • Churn × Complexity Hotspots · Hotspot: tests/unit-pure/esnext.function.is-constructor.js tests/unit-pure/esnext.function.is-constructor.js
  • Churn × Complexity Hotspots · Repeated repair: tests/unit-global/web.url.js tests/unit-global/web.url.js
  • Churn × Complexity Hotspots · Repeated repair: packages/core-js/modules/web.url-search-params.constructor.js packages/core-js/modules/web.url-search-params.constructor.js
  • Churn × Complexity Hotspots · Repeated repair: website/scripts/helpers.mjs website/scripts/helpers.mjs
  • Churn × Complexity Hotspots · Repeated repair: tests/unit-global/es.array-buffer.detached.js tests/unit-global/es.array-buffer.detached.js
  • Churn × Complexity Hotspots · Repeated repair: packages/core-js/modules/es.array.iterator.js packages/core-js/modules/es.array.iterator.js
  • Churn × Complexity Hotspots · Repeated repair: packages/core-js/modules/web.self.js packages/core-js/modules/web.self.js
  • Churn × Complexity Hotspots · Repeated repair: tests/unit-pure/es.set.js tests/unit-pure/es.set.js
  • Churn × Complexity Hotspots · Repeated repair: packages/core-js/modules/es.symbol.constructor.js packages/core-js/modules/es.symbol.constructor.js
  • Churn × Complexity Hotspots · Repeated repair: tests/unit-node/structured-clone.mjs tests/unit-node/structured-clone.mjs
  • Churn × Complexity Hotspots · Repeated repair: packages/core-js/modules/es.number.to-exponential.js packages/core-js/modules/es.number.to-exponential.js
  • Churn × Complexity Hotspots · Repeated repair: tests/helpers/constants.js tests/helpers/constants.js

We compare 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: 168 findings

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

  • Cyclomatic Complexity · parse (cyclomatic 196) packages/core-js/modules/web.url.constructor.js
  • Cyclomatic Complexity · exports (cyclomatic 41) packages/core-js/internals/iterator-define.js
  • Cyclomatic Complexity · exports (cyclomatic 36) packages/core-js-pure/override/internals/export.js
  • Cyclomatic Complexity · web.structured-clone.tryToTransfer (cyclomatic 26) packages/core-js/modules/web.structured-clone.js
  • Cyclomatic Complexity · exports (cyclomatic 22) packages/core-js-compat/targets-parser.js
  • Cyclomatic Complexity · array-iteration.createMethod (cyclomatic 20) packages/core-js/internals/array-iteration.js
  • Cyclomatic Complexity · async-iterator-iteration.createMethod (cyclomatic 20) packages/core-js/internals/async-iterator-iteration.js
  • Cyclomatic Complexity · web.url.constructor.isDisallowedCodePoint (cyclomatic 20) packages/core-js/modules/web.url.constructor.js
  • Cyclomatic Complexity · isIgnoredCodePoint (cyclomatic 20) packages/core-js/modules/web.url.constructor.js
  • Cyclomatic Complexity · wrap-error-constructor-with-cause.default (cyclomatic 19) packages/core-js/internals/wrap-error-constructor-with-cause.js
  • Cyclomatic Complexity · zip (cyclomatic 18) packages/core-js/modules/es.iterator.zip.js
  • Cyclomatic Complexity · string-punycode-to-ascii.encode (cyclomatic 17) packages/core-js/internals/string-punycode-to-ascii.js
  • Cyclomatic Complexity · exports (cyclomatic 17) packages/core-js/internals/export.js
  • Cognitive Complexity · parse (cognitive 364) packages/core-js/modules/web.url.constructor.js
  • Cognitive Complexity · exports (cognitive 51) packages/core-js/internals/iterator-define.js
  • Cognitive Complexity · exports (cognitive 48) packages/core-js-pure/override/internals/export.js
  • Cognitive Complexity · zip (cognitive 47) packages/core-js/modules/es.iterator.zip.js
  • Cognitive Complexity · async-iterator-iteration.createMethod (cognitive 42) packages/core-js/internals/async-iterator-iteration.js
  • Cognitive Complexity · string-punycode-to-ascii.encode (cognitive 42) packages/core-js/internals/string-punycode-to-ascii.js
  • Cognitive Complexity · tryToTransfer (cognitive 34) packages/core-js/modules/web.structured-clone.js
  • Cognitive Complexity · array-iteration.createMethod (cognitive 32) packages/core-js/internals/array-iteration.js
  • Cognitive Complexity · exports (cognitive 32) packages/core-js/internals/export.js
  • Cognitive Complexity · exports (cognitive 32) packages/core-js-compat/targets-parser.js
  • Cognitive Complexity · (anonymous) (cognitive 26) packages/core-js/internals/array-buffer-transfer.js
  • Cognitive Complexity · toFixed (cognitive 22) packages/core-js/modules/es.number.to-fixed.js
  • Cognitive Complexity · check-dependencies.checkPackage (cognitive 20) scripts/check-dependencies/check-dependencies.mjs
  • Cognitive Complexity · array-includes.createMethod (cognitive 19) packages/core-js/internals/array-includes.js
  • Cognitive Complexity · es.typed-array.sort.getSortCompare (cognitive 19) packages/core-js/modules/es.typed-array.sort.js
  • Cognitive Complexity · array-reduce.createMethod (cognitive 18) packages/core-js/internals/array-reduce.js
  • Cognitive Complexity · isDisallowedCodePoint (cognitive 18) packages/core-js/modules/web.url.constructor.js
  • Cognitive Complexity · slice (cognitive 17) packages/core-js/modules/es.array.slice.js
  • Cognitive Complexity · reduce (cognitive 16) packages/core-js/modules/esnext.async-iterator.reduce.js
  • Churn × Complexity Hotspots · Hotspot: website/scripts/helpers.mjs website/scripts/helpers.mjs
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: watchdog-floating-toolchain-version-in-setup-action REDACTED
  • Change Coupling · Change-coupling hub: es.string.match.js → es.string.replace.js, es.string.search.js, es.string.split.js packages/core-js/modules/es.string.match.js
  • Change Coupling · Change coupling: es.string.search.js ↔ es.string.split.js packages/core-js/modules/es.string.search.js
  • Change Coupling · Change coupling: es.string.replace.js ↔ es.string.search.js packages/core-js/modules/es.string.replace.js
  • Change Coupling · Change coupling: es.string.match-all.js ↔ es.string.replace-all.js packages/core-js/modules/es.string.match-all.js
  • Change Coupling · Change coupling: es.string.replace-all.js ↔ es.string.replace.js packages/core-js/modules/es.string.replace-all.js
  • Change Coupling · Change coupling: array-buffer.js ↔ object-get-own-property-names-external.js packages/core-js/internals/array-buffer.js
  • Supply-chain Provenance & Signing · Unpinned build actions
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/core-js/modules/web.atob.js
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/core-js/modules/es.array.with.js
  • Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/core-js/modules/esnext.observable.constructor.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/core-js/modules/web.url.constructor.js
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/core-js/internals/array-iteration-from-last.js
  • Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) packages/core-js/internals/set-is-disjoint-from.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/core-js/modules/es.array.find-index.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/core-js/modules/es.object.is-frozen.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/core-js/modules/es.string.iterator.js
  • Code Duplication · Duplicated block (9 lines × 4 locations) packages/core-js/modules/esnext.map.delete-all.js
  • Code Duplication · Duplicated block (8 lines × 22 locations) packages/core-js/internals/array-buffer-transfer.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/internals/collection-strong.js
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/core-js/internals/string-parse.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/internals/string-punycode-to-ascii.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/es.array.iterator.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/es.array.slice.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/es.object.lookup-getter.js
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/core-js/modules/es.string.match.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/es.symbol.async-dispose.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/esnext.map.emplace.js
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/core-js/modules/esnext.map.filter.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/esnext.map.find-key.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/esnext.reflect.get-own-metadata.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/esnext.set.add-all.js
  • Code Duplication · Duplicated block (8 lines × 3 locations) packages/core-js/modules/esnext.set.every.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/esnext.set.filter.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/web.url-search-params.constructor.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/web.url.constructor.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/core-js/modules/web.url.constructor.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js-pure/override/internals/collection.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/core-js-pure/override/internals/set-to-string-tag.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js-pure/override/modules/es.date.to-json.js
  • Code Duplication · Duplicated block (7 lines × 3 locations) packages/core-js/es/instance/at.js
  • Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) packages/core-js/internals/get-iterator-method-internal.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/internals/url-percent-coding.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.aggregate-error.constructor.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.array.at.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.escape.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.object.define-getter.js
  • Code Duplication · Duplicated block (7 lines × 3 locations) packages/core-js/modules/es.object.freeze.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.object.prevent-extensions.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.string.at-alternative.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/es.weak-map.constructor.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/esnext.map.every.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/esnext.reflect.get-metadata-keys.js
  • Code Duplication · Duplicated block (7 lines × 4 locations) packages/core-js/modules/esnext.reflect.get-metadata.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/esnext.set.every.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/web.dom-exception.constructor.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/web.url-search-params.constructor.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/core-js/modules/web.url.constructor.js
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/core-js-pure/override/internals/a-map.js
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/core-js-pure/override/internals/a-set.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/core-js/internals/array-buffer.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/core-js/internals/array-from-async.js
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/core-js/internals/array-from.js
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/core-js/internals/set-is-disjoint-from.js
  • Code Duplication · Duplicated block (6 lines × 4 locations) packages/core-js/modules/es.array.every.js
  • Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) packages/core-js/modules/es.string.match-all.js
Rebuild cost: about €130,000 · Estimate
Cost to rebuild€42,000 to €210,000, for 707 to 2,244 hours of work, about 0.9 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.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 55,653 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 1 finding(s) in Type Safety.
Raises the score by about 5 points · Medium effort · Type Safety
2
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with parse (cyclomatic 190), web.structured-clone.structuredCloneInternal (cyclomatic 104).
Raises the score by about 2 points · Medium effort · Cyclomatic Complexity
3
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Raises the score by about 3 points · Medium effort · Security & performance tooling

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.

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 2.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 15% to 34% on every change. The history of the code shows how much it changes: about 28,500 lines over the last 90 days, which is about 115,583 lines a year. At that pace, the extra work comes to an estimated 43.3 to 260.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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.
Where the investment is most exposed · Value at risk
This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Code Health, at 50 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 finding(s) in Type Safety. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort, because it clears the 1 Type Safety findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch core-js core-js core-js-builder core-js-builder core-js-builder->core-js core-js-compat core-js-compat core-js-builder->core-js-compat core-js-bundle core-js-bundle core-js-pure core-js-pure website website

At a glance — Code Health · 50% · Adequate · gated by D1, D2, R1 ·

At a glance — Architecture · 95% · Exemplary ·

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

At a glance — Readiness · 53% · Adequate · gated by P3 ·

At a glance — Security · 67% · Adequate · gated by D29 ·

At a glance — Performance · 100% · Exemplary ·

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 — Injection70High / Critical
A03:2025 — Software Supply Chain Failures6High / Critical

Roadmap

Top priorities: Resolve the 1 finding(s) in Type Safety; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing; 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.

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

Do thisHelpsEffortDimension
Resolve the 1 finding(s) in Type Safety.+4.5 ptsMediumType Safety
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with parse (cyclomatic 190), web.structured-clone.structuredCloneInternal (cyclomatic 104).+2.0 ptsMediumCyclomatic Complexity
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+3.4 ptsMediumSecurity & performance tooling
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.+2.7 ptsMediumArchitecture documentation
Swallowed exception (empty catch)+2.2 ptsMediumException handling
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13).+1.8 ptsMediumDependency Hygiene
Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with parse (cognitive 347), structuredCloneInternal (cognitive 88), uint8-from-base64.default (cognitive 82).+1.6 ptsHighCognitive Complexity
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.+1.5 ptsMediumDeployment & Rollback

File quality

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

FileScoreBandWorst signal
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
packages/core-js-pure/override/internals/export.js5.2MixedChange Coupling: Boundary-crossing change coupling: export.js ↔ export.js
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
packages/core-js/internals/iterator-define.js6.7MixedCyclomatic Complexity: iterator-define.default (cyclomatic 44)
packages/core-js/modules/web.structured-clone.js7.0MixedCyclomatic Complexity: web.structured-clone.structuredCloneInternal (cyclomatic 104)
packages/core-js/internals/url-domain-to-ascii.js7.0MixedCyclomatic Complexity: url-domain-to-ascii.mapCodePoint (cyclomatic 48)
packages/core-js/modules/es.array.sort.js7.0MixedCyclomatic Complexity: (anonymous) (cyclomatic 16)
packages/core-js/modules/web.url-search-params.constructor.js7.0MixedCognitive Complexity: parseObject (cognitive 22)
packages/core-js/modules/web.url.constructor.js7.0MixedCyclomatic Complexity: parse (cyclomatic 190)
packages/core-js/internals/collection.js7.2MixedCyclomatic Complexity: collection.default (cyclomatic 36)
packages/core-js/internals/url-search-params-body.js7.2MixedCyclomatic Complexity: url-search-params-body.patchFetch (cyclomatic 32)
packages/core-js/internals/uint8-from-base64.js7.2MixedCyclomatic Complexity: uint8-from-base64.default (cyclomatic 31)
packages/core-js/modules/es.regexp.constructor.js7.2MixedCyclomatic Complexity: RegExp (cyclomatic 29)
packages/core-js-compat/targets-parser.js7.2MixedCyclomatic Complexity: targets-parser.default (cyclomatic 26)
packages/core-js/internals/string-parse.js7.2MixedCyclomatic Complexity: string-parse.default (cyclomatic 26)

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

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

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

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

Could not be resolved — 11

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

This survey 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. All 57 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 57 dimensions across the health lenses
D1D2D3D5D10D12D13D14D15D17D19D23D24D26D27D28D29D30D34D35D37D43AX10AX3AX4GD1IC1M1M2M3M4P1P10P3P4P6PF3R1R10R11R2R3R4R5R6R7R8R9X1X12X16X21X24X28X29X3X30

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, 488 of 510 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 or a scanner, 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
Canine Code Analyzer 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

Every finding is locatable in findings.md. Run 01a1dd50-d6ee-7cb7-bc82-536e3831357f.

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.

  • D4 Code Duplication — not measured this run — We 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. The language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — tests/unit-karma/ (karma) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.ts, .js, .mjs) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but every JavaScript/TypeScript test package this repository declares runs its suite in a real browser, which the re-runner has no way to launch. `tests/unit-karma` declares `karma` and its `scripts.test` is absent. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's browser-driven test support, not a missing .ts/.js/.mjs runner and not a finding about this repository.
  • D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (146 contributor(s) across 8223 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 145 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/core-js-pure/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `website/build.mjs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AX6 Interface segregation — not measured this run — We 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 59 further occurrence(s) are not listed individually; the score already reflects all 99.
  • R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 85 further occurrence(s) are not listed individually; the score already reflects all 125.
  • S1 Web-Security Posture — not measured this run — We 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. 3278 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 11 further occurrence(s) are not listed individually; the score already reflects all 51.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • 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.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

97 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was parse at 190. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being url-domain-to-ascii.isUnassignedMathematical at 25 — they are counted neither in the figure above nor in this dimension's score.

exports (cyclomatic 26) · ×4packages/core-js/internals/url-domain-to-ascii.js:311
(anonymous) (cyclomatic 26) · ×2packages/core-js/modules/es.string.split.js:46
exports (cyclomatic 22) · ×2packages/core-js-pure/override/internals/collection.js:22
exports (cyclomatic 19) · ×2packages/core-js/internals/export.js:30
parse (cyclomatic 190)packages/core-js/modules/web.url.constructor.js:401

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with parse (cyclomatic 190), web.structured-clone.structuredCloneInternal (cyclomatic 104). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 2.0 to about 3.7/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

143 method(s) exceeded the cognitive complexity threshold of 15; the worst was parse at 347.

exports (cognitive 37) · ×2packages/core-js-compat/targets-parser.js:56
exports (cognitive 31) · ×2packages/core-js/internals/string-parse.js:43
parse (cognitive 347)packages/core-js/modules/web.url.constructor.js:401
structuredCloneInternal (cognitive 88)packages/core-js/modules/web.structured-clone.js:275
uint8-from-base64.default (cognitive 82)packages/core-js/internals/uint8-from-base64.js:72

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

What to do

  1. Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with parse (cognitive 347), structuredCloneInternal (cognitive 88), uint8-from-base64.default (cognitive 82). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes9.6 / 10Stronggated by 5 serious findings✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Prevented

5 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: web.structured-clone.structuredCloneInternal · ×3packages/core-js/modules/web.structured-clone.js:275
FileTooLong: modules/web.url.constructor.js · ×2packages/core-js/modules/web.url.constructor.js

What to do

  1. Resolve the 3 FunctionTooLong finding(s) in God Classes — start with web.structured-clone.js, playground.js, main.js. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with web.url.constructor.js, web.structured-clone.js. — One of this dimension's main actionable groups (2 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

6 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

2 skipped (2 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 2 tests.

Skipped (documented): (unnamed test) · ×2tests/compat/browsers-runner.js:52

✓ On the Gold path — maintain.

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

D12 · Dependency Hygiene9.2 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

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

Floating npm dependency: mkdirp · ×2
Deprecated: copy-concurrently · ×13REDACTED:2120
Outdated (npm): mkdirppackages/core-js-builder/package.json:31
Outdated (npm): @babel/standalone · ×6

What to do

  1. Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13). — One of this dimension's main actionable groups (13 recommendation-level).
  2. Resolve the 2 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).

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 512 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 512 package(s) this repository's committed lockfile installs for a consumer — its 13 production, optional and peer dependency(ies), across 3 product package.json manifest(s), and everything those install in turn. Its 100 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

Top hotspots: packages/core-js/modules/web.structured-clone.js (14×104=1456); packages/core-js-pure/override/internals/export.js (6×43=258); packages/core-js/internals/string-punycode.js (5×25=125) Repeated repair below the complexity floor: tests/compat/tests.js (22 of 36 changes were fixes); tests/unit-global/web.url.js (13 of 24 changes were fixes); packages/core-js/modules/web.url-search-params.constructor.js (8 of 11 changes were fixes)

Repeated repair: tests/compat/tests.js · ×16tests/compat/tests.js:673
Hotspot: packages/core-js/modules/web.structured-clone.js · ×14packages/core-js/modules/web.structured-clone.js:275

What to do

  1. Resolve the 16 Repeated repair finding(s) in Churn × Complexity Hotspots — start with es.set.js (2), tests.js, web.url.js. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with esnext.function.is-constructor.js (2), web.structured-clone.js, export.js. — One of this dimension's main actionable groups (14 warning-level).

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

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

0 deducted task-comment markers across 0 LoC (0.0/KLoC) → score 10.0. 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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

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

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

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

2 of 2 documentation facets pass in full. 53 document(s) read across 12 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

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

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

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

No domain types leak across context boundaries (3 contexts). Contexts: core-js, core-js-compat, core-js-pure.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value9.3 6.9 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

11 of 1657 judged comments only repeat the code they sit on (0.7 %). 861 comment(s) in another language or script were not judged.

redundant comment · ×11packages/core-js/internals/iterator-define.js:65

What to do

  1. Resolve the 11 redundant comment finding(s) in Comment Value — start with web.dom-exception.constructor.js (4), es.regexp.escape.js (4), web.url-search-params.constructor.js (2). — One of this dimension's main actionable groups (11 recommendation-level).

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

D26 · Project Cohesion8.0 / 10Strong✓ Tool-verified

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

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

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

1 of 10 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

24 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

70 finding(s): 0 critical, 65 high, 5 medium, 0 low. 41 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 4 file(s) — `deno/corejs/index.js`, `packages/core-js/modules/web.structured-clone.js`, `website/build.mjs` (line 250), `website/src/playground.html` (line 25, line 44) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (7), REDACTED (2). — One of this dimension's main actionable groups (16 issue-level).
  2. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
  3. No action in Static Analysis (SAST) — all 41 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 (41 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities7.8 / 10Adequategated by 3 critical findings✓ 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 98 of the 3269 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Adequategated by 2 critical 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: es.string.match.js↔es.string.search.js 95%; es.string.ends-with.js↔es.string.starts-with.js 88%; es.string.replace.js↔es.string.search.js 84%

Boundary-crossing change coupling: export.js ↔ export.js · ×2packages/core-js-pure/override/internals/export.js:1
Change coupling: es.string.ends-with.js ↔ es.string.starts-with.js · ×5packages/core-js/modules/es.string.ends-with.js:1
Change coupling clique: es.string.match.js, es.string.replace.js, es.string.search.js, es.string.split.jspackages/core-js/modules/es.string.match.js

What to do

  1. Resolve the 2 Boundary-crossing change coupling finding(s) in Change Coupling — start with export.js, data.mjs. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 5 Change coupling finding(s) in Change Coupling — start with es.string.ends-with.js, esnext.async-disposable-stack.constructor.js, get-iterator-method.js. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with es.string.match.js. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition8.8 / 10Strong✓ 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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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 & stubs10.0 / 10Exemplary○ Nothing flagged

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.

M1 · Documentation (README)8.2 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

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.

What to do

  • Run the test suite in CI via an explicit runner step (`pytest` for the toolchain this pipeline already uses) and gate merges on it.
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's code 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.

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
  • `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:71

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ 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.

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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 each language's code 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.

R1 · Type Safety0.0 / 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.

  • 2 typed · 4147 plain JS — the untyped files are packages/core-js-builder/config.js, packages/core-js-builder/index.js, packages/core-js-compat/compat.js, packages/core-js-compat/get-modules-list-for-target-version.js, packages/core-js-compat/helpers.js, packages/core-js-compat/index.js (+4141 more).
R10 · Code Duplication7.4 / 10Strong✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 23 duplicated blocks under packages/core-js/ have copies in at least two of the sibling directories actual, es, full, internals, modules — 10 of them are reported below, and 13 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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-js/internals/async-iterator-map.js:26
  • packages/core-js/modules/es.async-disposable-stack.constructor.js:17 · packages/core-js/modules/es.disposable-stack.constructor.js:15 — the two spans are one implementation copied and then locally edited — 496 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-js/modules/es.async-disposable-stack.constructor.js:17
  • packages/core-js/modules/es.iterator.drop.js:14 · packages/core-js/modules/es.iterator.take.js:14 — the two spans are one implementation copied and then locally edited — 239 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-js/modules/es.iterator.drop.js:14
  • packages/core-js/modules/esnext.async-iterator.filter.js:12 · packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core-js/modules/esnext.async-iterator.filter.js:12
  • packages/core-js/modules/esnext.promise.all-keyed.js:12 · packages/core-js/modules/esnext.promise.all-settled-keyed.js:12 — 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/core-js/modules/esnext.promise.all-keyed.js:12
  • packages/core-js/modules/es.iterator.filter.js:14 · packages/core-js/modules/es.iterator.map.js:14 — the two spans are one implementation copied and then locally edited — 154 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-js/modules/es.iterator.filter.js:14
  • packages/core-js/internals/async-iterator-map.js:26 · packages/core-js/modules/esnext.async-iterator.filter.js:28 — 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/core-js/internals/async-iterator-map.js:26
  • packages/core-js/modules/web.atob.js:28 · packages/core-js/modules/web.btoa.js:18 — the two spans are one implementation copied and then locally edited — 121 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-js/modules/web.atob.js:28
  • packages/core-js/internals/async-iterator-iteration.js:24 · packages/core-js/modules/esnext.async-iterator.reduce.js:9 — the two spans are one implementation copied and then locally edited — 126 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-js/internals/async-iterator-iteration.js:24
  • packages/core-js/modules/es.promise.all-settled.js:12 · packages/core-js/modules/es.promise.all.js:12 — 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/core-js/modules/es.promise.all-settled.js:12
  • packages/core-js/internals/url-domain-to-ascii.js:61 · scripts/build-url-idna-data.mjs:165 — the two spans are one implementation copied and then locally edited — 97 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-js/internals/url-domain-to-ascii.js:61
  • packages/core-js/modules/es.number.to-exponential.js:59 · packages/core-js/modules/es.number.to-precision.js:46 — the two spans are one implementation copied and then locally edited — 86 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-js/modules/es.number.to-exponential.js:59
  • packages/core-js/modules/es.iterator.every.js:16 · packages/core-js/modules/es.iterator.find.js:16 · packages/core-js/modules/es.iterator.for-each.js:16 · packages/core-js/modules/es.iterator.some.js:16 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/core-js/modules/es.iterator.every.js:16
  • packages/core-js/modules/es.iterator.find.js:16 · packages/core-js/modules/es.iterator.some.js:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/es.iterator.find.js:16
  • packages/core-js/modules/esnext.map.reduce.js:12 · packages/core-js/modules/esnext.set.reduce.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/esnext.map.reduce.js:12
  • packages/core-js/internals/string-cooked.js:7 · packages/core-js/modules/es.string.raw.js:7 — the two spans are one implementation copied and then locally edited — 94 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-js/internals/string-cooked.js:7
  • packages/core-js/modules/es.array.push.js:11 · packages/core-js/modules/es.array.unshift.js:10 — 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/core-js/modules/es.array.push.js:11
  • packages/core-js/modules/es.regexp.dot-all.js:8 · packages/core-js/modules/es.regexp.sticky.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/es.regexp.dot-all.js:8
  • packages/core-js/modules/esnext.map.emplace.js:13 · packages/core-js/modules/esnext.weak-map.emplace.js:13 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/esnext.map.emplace.js:13
  • packages/core-js/modules/es.array.with.js:15 · packages/core-js/modules/es.typed-array.with.js:35 — the two spans are one implementation copied and then locally edited — 96 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-js/modules/es.array.with.js:15
  • packages/core-js/modules/es.regexp.constructor.js:53 · packages/core-js/modules/es.regexp.constructor.js:77 — the two spans are one implementation copied and then locally edited — 77 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-js/modules/es.regexp.constructor.js:53
  • packages/core-js/modules/es.string.ends-with.js:12 · packages/core-js/modules/es.string.starts-with.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/es.string.ends-with.js:12
  • packages/core-js/modules/esnext.async-iterator.filter.js:40 · packages/core-js/modules/esnext.async-iterator.reduce.js:50 — 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/core-js/modules/esnext.async-iterator.filter.js:40
  • packages/core-js/internals/async-iterator-map.js:11 · packages/core-js/modules/esnext.async-iterator.filter.js:12 · packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core-js/internals/async-iterator-map.js:11
  • packages/core-js/modules/es.iterator.filter.js:32 · packages/core-js/modules/es.iterator.flat-map.js:54 · packages/core-js/modules/es.iterator.map.js:25 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core-js/modules/es.iterator.filter.js:32
  • packages/core-js/modules/esnext.async-iterator.drop.js:36 · packages/core-js/modules/esnext.async-iterator.take.js:35 — 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/core-js/modules/esnext.async-iterator.drop.js:36
  • packages/core-js/internals/async-from-sync-iterator.js:49 · packages/core-js/internals/async-from-sync-iterator.js:61 — 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-js/internals/async-from-sync-iterator.js:49
  • packages/core-js/modules/es.array.splice.js:28 · packages/core-js/modules/es.array.to-spliced.js:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/es.array.splice.js:28
  • packages/core-js/modules/es.iterator.zip-keyed.js:16 · packages/core-js/modules/es.iterator.zip.js:15 — 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/core-js/modules/es.iterator.zip-keyed.js:16
  • packages/core-js/modules/esnext.math.imulh.js:8 · packages/core-js/modules/esnext.math.umulh.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/esnext.math.imulh.js:8
  • packages/core-js-pure/override/modules/es.date.to-json.js:10 · packages/core-js/modules/es.date.to-json.js:7 — 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/core-js-pure/override/modules/es.date.to-json.js:10
  • packages/core-js/internals/array-buffer-transfer.js:8 · packages/core-js/internals/task.js:10 · packages/core-js/internals/typed-array-constructor.js:30 · packages/core-js/internals/uint8-from-base64.js:6 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/core-js/internals/array-buffer-transfer.js:8
  • packages/core-js/internals/url-domain-to-ascii.js:8 · packages/core-js/modules/web.url.constructor.js:45 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — packages/core-js/internals/url-domain-to-ascii.js:8
  • packages/core-js/modules/es.map.get-or-insert-computed.js:13 · packages/core-js/modules/es.weak-map.get-or-insert-computed.js:26 — the two spans are one implementation copied and then locally edited — 56 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-js/modules/es.map.get-or-insert-computed.js:13
  • packages/core-js/modules/es.map.get-or-insert.js:6 · packages/core-js/modules/es.weak-map.get-or-insert.js:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/es.map.get-or-insert.js:6
  • packages/core-js/modules/es.promise.any.js:11 · packages/core-js/modules/es.promise.race.js:8 — the two spans are one implementation copied and then locally edited — 79 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-js/modules/es.promise.any.js:11
  • packages/core-js/modules/es.uint8-array.to-base64.js:20 · packages/core-js/modules/es.uint8-array.to-hex.js:8 — the two spans are one implementation copied and then locally edited — 76 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-js/modules/es.uint8-array.to-base64.js:20
  • packages/core-js/modules/web.url.can-parse.js:26 · packages/core-js/modules/web.url.parse.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/core-js/modules/web.url.can-parse.js:26
  • packages/core-js/modules/web.url.constructor.js:975 · packages/core-js/modules/web.url.constructor.js:995 — 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-js/modules/web.url.constructor.js:975
  • packages/core-js/stable/instance/entries.js:8 · packages/core-js/stable/instance/for-each.js:8 · packages/core-js/stable/instance/keys.js:8 · packages/core-js/stable/instance/values.js:8 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — packages/core-js/stable/instance/entries.js:8

What to do

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

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

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

  • tests/unit-node/structured-clone.mjs:24 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/configurator) — 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. — tests/unit-node/structured-clone.mjs:24
  • tests/unit-node/structured-clone.mjs:32 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/configurator) — 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. — tests/unit-node/structured-clone.mjs:32
  • tests/unit-node/structured-clone.mjs:35 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.array-buffer.transfer) — 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. — tests/unit-node/structured-clone.mjs:35
  • tests/unit-node/structured-clone.mjs:36 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.array-buffer.transfer-to-fixed-length) — 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. — tests/unit-node/structured-clone.mjs:36
  • tests/unit-node/structured-clone.mjs:58 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.typed-array.set) — 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. — tests/unit-node/structured-clone.mjs:58
  • tests/unit-node/structured-clone.mjs:63 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/actual/structured-clone) — 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. — tests/unit-node/structured-clone.mjs:63

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 Complexity8.0 / 10Strong✓ Tool-verified

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

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

  • parse has cyclomatic complexity 190 and cognitive complexity 347; 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-js/modules/web.url.constructor.js:401
  • structuredCloneInternal has cyclomatic complexity 104 and cognitive complexity 88; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/web.structured-clone.js:275
  • (anonymous) has cyclomatic complexity 66 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — tests/unit-pure/web.structured-clone.js:30
  • (anonymous) has cyclomatic complexity 65 and cognitive complexity 74; 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. — tests/unit-global/web.structured-clone.js:14
  • mapCodePoint has cyclomatic complexity 48 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/url-domain-to-ascii.js:136
  • exports has cyclomatic complexity 43 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js-pure/override/internals/export.js:60
  • prepareTransfer has cyclomatic complexity 37 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/modules/web.structured-clone.js:573
  • exports has cyclomatic complexity 36 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/iterator-define.js:28
  • (anonymous) has cyclomatic complexity 36 and cognitive complexity 39; 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. — tests/unit-global/es.string.split.js:8
  • sumPrecise has cyclomatic complexity 32 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/es.math.sum-precise.js:100
  • (anonymous) has cyclomatic complexity 31 and cognitive complexity 89; 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. (×2) — tests/unit-global/es.json.parse.js:6, tests/unit-pure/es.json.parse.js:13
  • exports has cyclomatic complexity 31 and cognitive complexity 82; 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-js/internals/uint8-from-base64.js:72
  • parseIPv6 has cyclomatic complexity 31 and cognitive complexity 74; 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-js/modules/web.url.constructor.js:160
  • RegExp has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/modules/es.regexp.constructor.js:139
  • (anonymous) has cyclomatic complexity 28 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — tests/unit-global/web.structured-clone.js:1090, tests/unit-pure/web.structured-clone.js:1123
  • exec has cyclomatic complexity 28 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/regexp-exec.js:47
  • decode has cyclomatic complexity 27 and cognitive complexity 80; 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-js/internals/url-percent-coding.js:30
  • exports has cyclomatic complexity 26 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/url-domain-to-ascii.js:311
  • exports has cyclomatic complexity 26 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/internals/string-parse.js:43
  • (anonymous) has cyclomatic complexity 26 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:16
  • decode has cyclomatic complexity 25 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-js/internals/string-punycode.js:235
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — tests/unit-global/esnext.iterator.range.js:3, tests/unit-pure/esnext.iterator.range.js:9
  • (anonymous) has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — tests/unit-global/web.url-search-params.js:875, tests/unit-pure/web.url-search-params.js:817
  • isIgnored has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/url-domain-to-ascii.js:108
  • cloneView has cyclomatic complexity 23 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/modules/web.structured-clone.js:215
  • exports has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/internals/make-built-in.js:26
  • NumericRangeIterator has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/numeric-range-iterator.js:20
  • (anonymous) has cyclomatic complexity 21 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/es.string.split.js:66
  • toExponential has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/es.number.to-exponential.js:68
  • zip has cyclomatic complexity 20 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/es.iterator.zip.js:22
  • exports has cyclomatic complexity 20 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js-compat/targets-parser.js:56
  • exports has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/internals/iterate.js:22
  • (anonymous) has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-js/internals/array-buffer-transfer.js:33
  • exports has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/internals/export.js:30
  • parseIPv4 has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/web.url.constructor.js:120
  • dedentStringsArray has cyclomatic complexity 19 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core-js/modules/esnext.string.dedent.js:56
R3 · Large Files9.9 / 10Exemplary✓ 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-js-compat/src/data.mjs has 3472 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-js-compat/src/data.mjs:1
  • packages/core-js/modules/web.url.constructor.js has 1078 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-js/modules/web.url.constructor.js:1
  • packages/core-js/modules/web.structured-clone.js has 682 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-js/modules/web.structured-clone.js:1
  • packages/core-js/modules/web.url-search-params.constructor.js has 463 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-js/modules/web.url-search-params.constructor.js:1
  • packages/core-js-compat/src/mapping.mjs has 427 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-js-compat/src/mapping.mjs:1

What to do

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

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

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

R5 · Dependency Freshness10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling6.7 / 10Adequate✓ 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.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code10.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.

  • 155 file(s) (~527 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/core-js-pure
R8 · Dependency Hygiene6.0 / 10Adequate✓ 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.

  • Declared in scripts/check-actions/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 scripts/check-dependencies/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 tests/observables/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 tests/promises/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
  • Declared in tests/publint/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 tests/test262/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 tests/unit-karma/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.

What to do

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

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.

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.

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.

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

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

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

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 handling4.9 / 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. (×38) — packages/core-js-pure/override/internals/export.js:34, packages/core-js/postinstall.js:53, packages/core-js/modules/es.array.iterator.js:74, …
  • `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×2) — packages/core-js/modules/es.uint8-array.set-from-base64.js:17, packages/core-js/modules/es.uint8-array.to-base64.js:29

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.

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 Health50%Adequate — gated by D1, D2, R1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture95%ExemplarySolid.
Maturity63%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness53%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security67%Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest 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 — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 69 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 — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — Test reliability not included — no browser-driven test runner (karma)
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — Naming consistency does not read html yet; not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D25 ADR Conformance — no ADRs to check
  • 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 12 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (11 with fewer than two methods, 1 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — JavaScript/TypeScript suite
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repository's JavaScript/TypeScript source (5 module(s), 3280 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: 3278 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
  • 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 — 70 finding(s)
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
  • + 16 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
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×2
  • Boundary-crossing change coupling: export.js ↔ export.js packages/core-js-pure/override/internals/export.js:1 — `packages/core-js-pure/override/internals/export.js` (context core-js-pure) and `packages/core-js/internals/export.js` (context core-js) sit in DIFFERENT parts of the tree yet change together 52% of the time (13 of the 25 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `f68187d1` document missed options of internals/export; `82ab7962` minor fix of prototype methods export logic in the pure version; `ef0aac76` improve polyfilled functions `.name` and `.toString()` in many differ… — run `git show` on any of them.
  • Boundary-crossing change coupling: data.mjs ↔ web.atob.js packages/core-js-compat/src/data.mjs:1 — `packages/core-js-compat/src/data.mjs` (context core-js-compat) and `packages/core-js/modules/web.atob.js` (context core-js) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e51d24df` improve detection of incorrect errors from native `atob` / `btoa`; `bed45f4d` fix detection of incorrect errors from native `atob` / `btoa`; `319c69a7` add `.toBase64` method — run `git show` on any of them.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
Serious — 375 finding(s)
X3 · Exception handling · Swallowed exception (empty catch) · ×38
  • Swallowed exception (empty catch) packages/core-js-pure/override/internals/export.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-js/postinstall.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-js/modules/es.array.iterator.js:74 — 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-js/modules/es.iterator.concat.js:28 — 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-js/modules/es.math.sum-precise.js:40 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core-js/modules/es.math.sum-precise.js:48 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core-js/modules/es.object.proto.js:33 — 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-js/modules/es.promise.constructor.js:275 — 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-js/modules/es.regexp.constructor.js:193 — 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-js/modules/es.uint8-array.from-base64.js:14 — 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-js/modules/es.uint8-array.set-from-base64.js:24 — 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-js/modules/es.uint8-array.set-from-base64.js:29 — 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-js/modules/esnext.function.is-callable.js:19 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core-js/modules/web.self.js:62 — 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-js/modules/web.structured-clone.js:125 — 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-js/modules/web.structured-clone.js:172 — 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-js/modules/web.structured-clone.js:372 — 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-js/modules/web.structured-clone.js:375 — 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-js/modules/web.structured-clone.js:673 — 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-js/modules/web.structured-clone.js:680 — 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-js/internals/array-buffer-view-core.js:99 — 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-js/internals/array-buffer-view-core.js:116 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/core-js/internals/array-buffer-view-core.js:122 — 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-js/internals/async-iterator-prototype.js:26 — 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-js/internals/check-correctness-of-iteration.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.
  • + 13 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Repeated repair · ×16
  • Repeated repair: tests/compat/tests.js tests/compat/tests.js:673 — tests/compat/tests.js changed 36 times in last 90 days and 22 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is es.array.sort at line 673), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix `Number.prototype.{ toExponential, toFixed, toPrecision }` polyfills: own `toPrecision` implementation, up to 100 digits, missed native bugs detection”; “fix missed runtime compatibility boundaries”; “fix Array.from and TypedArray.from detection in Safari 14”; “fix `Reflect.construct` detection in Firefox 44”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/compat/tests.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/unit-global/web.url.js tests/unit-global/web.url.js:1802 — tests/unit-global/web.url.js changed 24 times in last 90 days and 13 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is (anonymous) at line 1802), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix url tests on firefox 94-105 and ios 14.3-14.4”; “fix utf-8 lead byte validation in url decoding”; “fix url error handling on punycode overflow”; “fix removal of ignored unicode characters in url domains”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-global/web.url.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core-js/modules/web.url-search-params.constructor.js packages/core-js/modules/web.url-search-params.constructor.js:148 — packages/core-js/modules/web.url-search-params.constructor.js changed 11 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is web.url-search-params.constructor.URLSearchParamsState at line 148), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix urlsearchparams body integration and request init handling”; “fix urlsearchparams sequence conversion order”; “fix urlsearchparams usvstring conversion”; “fix urlsearchparams record key enumeration”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/web.url-search-params.constructor.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: website/build.mjs website/build.mjs:255 — website/build.mjs changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is build.buildBlogMenu at line 255), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix races of website deploys and exit codes of site builds”; “fix website heading anchors, TOC labels and the blog index, drop jsdom”; “improve website accessibility and fix it in old browsers”; “fix site URLs of versions, anchors and the run button”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- website/build.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: website/scripts/helpers.mjs website/scripts/helpers.mjs:93 — website/scripts/helpers.mjs changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is helpers.buildAndCopyCoreJS at line 93), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix website deploys broken by the fix of their races”; “fix races of website deploys and exit codes of site builds”; “fix deploy workflows and drop source map references from website bundles”; “fix site URLs of versions, anchors and the run button”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- website/scripts/helpers.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/unit-global/es.array-buffer.detached.js tests/unit-global/es.array-buffer.detached.js:5 — tests/unit-global/es.array-buffer.detached.js changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is (anonymous) at line 5), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “work around some native bugs in unit tests”; “fix ArrayBuffer transfer detection in Deno 1.13”; “fix ArrayBuffer transfers in Firefox 41-44”; “fix detached ArrayBuffer detection and transfer handling”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-global/es.array-buffer.detached.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: scripts/build-compat/data.mjs scripts/build-compat/data.mjs:93 — scripts/build-compat/data.mjs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is data.write at line 93), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix Opera 120 and some early Electron versions compat data mapping”; “fix Chromium-based Edge and Opera compat data inherited from EdgeHTML and Presto”; “fix quest mapping”; “review, fix, and improve documentation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- scripts/build-compat/data.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core-js/modules/es.array.iterator.js packages/core-js/modules/es.array.iterator.js:29 — packages/core-js/modules/es.array.iterator.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is es.array.iterator.default at line 29), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix length conversion in the array iterator polyfill”; “fix names and built-in metadata of iterator next methods”; “fix handling `arguments[@@iterator]` in `core-js` internals in engines with native `Array` iterator, but without native `arguments` iterator (Firefox < 46), close #1576”; “review, fix, and improve documentation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/es.array.iterator.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core-js/modules/web.self.js packages/core-js/modules/web.self.js:15 — packages/core-js/modules/web.self.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is web.self.validateReceiver at line 15), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix an ordinary assignment to `self` with the polyfilled setter in FF < 12, where it left `undefined` instead of the assigned value”; “fix self fallback export options”; “fix self accessor receiver handling and native detection”; “review, fix, and improve documentation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/web.self.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/unit-pure/es.set.js tests/unit-pure/es.set.js:19 — tests/unit-pure/es.set.js changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is (anonymous) at line 19), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix property descriptors in the pure version”; “fix missing iterator result validation in `Array.from`, typed arrays, collection and iterator consumers, and `URLSearchParams` polyfills”; “fix names and built-in metadata of iterator next methods”; “fix the iterator name correction adding a `name` property to collection prototypes in old engines”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-pure/es.set.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core-js/modules/es.symbol.constructor.js packages/core-js/modules/es.symbol.constructor.js:94 — packages/core-js/modules/es.symbol.constructor.js changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is es.symbol.constructor.$defineProperty at line 94), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix an extra own property check of non-symbol keys in `Object.prototype.propertyIsEnumerable` from the `Symbol` polyfill, observable with proxies in FF33-35”; “fix symbol wrapper arity”; “review, fix, and improve documentation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/es.symbol.constructor.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/unit-node/structured-clone.mjs tests/unit-node/structured-clone.mjs:42 — tests/unit-node/structured-clone.mjs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is cloneShared at line 42), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix `structuredClone` and `ArrayBuffer` transfer polyfills without a proper native `structuredClone`”; “fix `structuredClone` to snapshot `Map` / `Set` entries and skip deleted own properties”; “fix structuredClone error propagation and detached view validation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-node/structured-clone.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: packages/core-js/modules/es.number.to-exponential.js packages/core-js/modules/es.number.to-exponential.js:47 — packages/core-js/modules/es.number.to-exponential.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is es.number.to-exponential.throwsOnInfinityFraction at line 47), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix `Number.prototype.{ toExponential, toFixed, toPrecision }` polyfills: own `toPrecision` implementation, up to 100 digits, missed native bugs detection”; “fix some polyfills depending on global `TypeError`, `isFinite`, `parseInt`, `String` or `Object` replaced after loading `core-js`”; “fix `Number.prototype.toExponential` polyfill accuracy”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/es.number.to-exponential.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/helpers/constants.js tests/helpers/constants.js:14 — tests/helpers/constants.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is (anonymous) at line 14), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix property enumeration in Object.{ assign, entries, values }”; “fix native Float16Array support in typed array polyfills and tests”; “work around some native bugs in unit tests”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/helpers/constants.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: scripts/check-compat-data-mapping.mjs scripts/check-compat-data-mapping.mjs:22 — scripts/check-compat-data-mapping.mjs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is check-compat-data-mapping.getLatestFromMDN.version at line 22), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix check-compat-data-mapping for node”; “fix Opera 120 and some early Electron versions compat data mapping”; “review, fix, and improve documentation”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- scripts/check-compat-data-mapping.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: tests/unit-global/es.set.js tests/unit-global/es.set.js:11 — tests/unit-global/es.set.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is (anonymous) at line 11), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix missing iterator result validation in `Array.from`, typed arrays, collection and iterator consumers, and `URLSearchParams` polyfills”; “fix names and built-in metadata of iterator next methods”; “fix the iterator name correction adding a `name` property to collection prototypes in old engines”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-global/es.set.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D15 · Churn × Complexity Hotspots · Hotspot · ×14
  • Hotspot: packages/core-js/modules/web.structured-clone.js packages/core-js/modules/web.structured-clone.js:275 — packages/core-js/modules/web.structured-clone.js changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 104 in web.structured-clone.structuredCloneInternal at line 275. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/web.structured-clone.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js-pure/override/internals/export.js packages/core-js-pure/override/internals/export.js:60 — packages/core-js-pure/override/internals/export.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in export.default at line 60. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js-pure/override/internals/export.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/internals/string-punycode.js packages/core-js/internals/string-punycode.js:235 — packages/core-js/internals/string-punycode.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in string-punycode.decode at line 235. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/internals/string-punycode.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js-compat/targets-parser.js packages/core-js-compat/targets-parser.js:56 — packages/core-js-compat/targets-parser.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in targets-parser.default at line 56. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js-compat/targets-parser.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: website/src/js/playground.js website/src/js/playground.js:36 — website/src/js/playground.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in playground.init at line 36. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- website/src/js/playground.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/internals/array-buffer-is-detached.js packages/core-js/internals/array-buffer-is-detached.js:37 — packages/core-js/internals/array-buffer-is-detached.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in array-buffer-is-detached.default at line 37. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/internals/array-buffer-is-detached.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/modules/web.url-search-params.delete.js packages/core-js/modules/web.url-search-params.delete.js:24 — packages/core-js/modules/web.url-search-params.delete.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in (anonymous) at line 24. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/web.url-search-params.delete.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/modules/es.iterator.zip.js packages/core-js/modules/es.iterator.zip.js:22 — packages/core-js/modules/es.iterator.zip.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in zip at line 22. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/modules/es.iterator.zip.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: website/src/js/main.js website/src/js/main.js:43 — website/src/js/main.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in main.init at line 43. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- website/src/js/main.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/internals/iterate.js packages/core-js/internals/iterate.js:22 — packages/core-js/internals/iterate.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in iterate.default at line 22. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/internals/iterate.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/internals/array-buffer-transfer.js packages/core-js/internals/array-buffer-transfer.js:33 — packages/core-js/internals/array-buffer-transfer.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in array-buffer-transfer.default at line 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/internals/array-buffer-transfer.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: tests/unit-global/esnext.function.is-constructor.js tests/unit-global/esnext.function.is-constructor.js:5 — tests/unit-global/esnext.function.is-constructor.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in (anonymous) at line 5. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-global/esnext.function.is-constructor.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/core-js/internals/iterator-create-proxy.js packages/core-js/internals/iterator-create-proxy.js:24 — packages/core-js/internals/iterator-create-proxy.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in iterator-create-proxy.createIteratorProxyPrototype at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- packages/core-js/internals/iterator-create-proxy.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: tests/unit-pure/esnext.function.is-constructor.js tests/unit-pure/esnext.function.is-constructor.js:5 — tests/unit-pure/esnext.function.is-constructor.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in (anonymous) at line 5. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 01:41:03 +07:00' --until='2026-11-15 01:41:03 +07:00' --full-history --no-merges -- tests/unit-pure/esnext.function.is-constructor.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
R11 · Import Boundaries · Boundary violation [package · ×6
  • Boundary violation [package:test-cross-package-internals] tests/unit-node/structured-clone.mjs:24 — tests/unit-node/structured-clone.mjs:24 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/configurator) — 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] tests/unit-node/structured-clone.mjs:32 — tests/unit-node/structured-clone.mjs:32 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/configurator) — 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] tests/unit-node/structured-clone.mjs:35 — tests/unit-node/structured-clone.mjs:35 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.array-buffer.transfer) — 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] tests/unit-node/structured-clone.mjs:36 — tests/unit-node/structured-clone.mjs:36 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.array-buffer.transfer-to-fixed-length) — 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] tests/unit-node/structured-clone.mjs:58 — tests/unit-node/structured-clone.mjs:58 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/modules/es.typed-array.set) — 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] tests/unit-node/structured-clone.mjs:63 — tests/unit-node/structured-clone.mjs:63 reaches past another workspace package's public entry into its internals with a relative path (../../packages/core-js/actual/structured-clone) — 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.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: es.string.ends-with.js ↔ es.string.starts-with.js packages/core-js/modules/es.string.ends-with.js:1 — `packages/core-js/modules/es.string.ends-with.js` and `packages/core-js/modules/es.string.starts-with.js` change together 88% of the time (14 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 14 shared commits counted here, the most recent 3 are `766ff3b2` fix order of arguments validation in `String.prototype.{ startsWith, …; `6d687424` drop fallbacks to native buggy `endsWith` / `startsWith` as useless -…; `3bcbad2d` avoid a check of the target in the internal `function-uncurry-this` h… — run `git show` on any of them.
  • Change coupling: esnext.async-disposable-stack.constructor.js ↔ esnext.disposable-stack.constructor.js packages/core-js/modules/esnext.async-disposable-stack.constructor.js:1 — `packages/core-js/modules/esnext.async-disposable-stack.constructor.js` and `packages/core-js/modules/esnext.disposable-stack.constructor.js` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). Neither file is a module — they declare no import/export and are loaded together into one shared scope by a script tag or a bundle — so there is no dependency edge that COULD be declared between them, and this pass cannot tell a real relationship from a coincidence of release. Read the pair before acting: if one defines what the other uses through the shared global, that is the coupling, and making it explicit (a module boundary, or one named object they both go through) is what removes it; if they duplicate structure, extract the common part; if neither holds, the co-change is incidental and there is nothing to do. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `d1fd92bb` use `undefined` insted of `null` for cleaning internal `(Async)Dispos…; `096cb451` move validation of pending stacks to helper; `3493e88e` `(Async)DisposableStack.prototype.move` marks the original stack as d… — run `git show` on any of them.
  • Change coupling: get-iterator-method.js ↔ is-iterable.js packages/core-js/internals/get-iterator-method.js:1 — `packages/core-js/internals/get-iterator-method.js` and `packages/core-js/internals/is-iterable.js` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 8 shared commits counted here, the most recent 3 are `508e6d7e` some get-iterator fixes; `ae1c6609` consider `document.all` as an object in some missed cases; `5c9f9559` remove special cases for native prototypes from iterator helpers, rev… (at that commit the files were still `modules/core.get-iterator-method.js` and `modules/core.is-iterable.js`) — run `git show` on any of them.
  • Change coupling: es.array.sort.js ↔ es.typed-array.sort.js packages/core-js/modules/es.array.sort.js:1 — `packages/core-js/modules/es.array.sort.js` and `packages/core-js/modules/es.typed-array.sort.js` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `13d56107` align default sort comparators with the spec text; `0400deaa` some stylistic changes and minor fixes; `d07fee6d` reuse `internals/array-sort` in `URLSearchParams`, simplify it — run `git show` on any of them.
  • Change coupling: es.regexp.to-string.js ↔ es.string.match-all.js packages/core-js/modules/es.regexp.to-string.js:1 — `packages/core-js/modules/es.regexp.to-string.js` and `packages/core-js/modules/es.string.match-all.js` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `93aee471` refactoring; `4b764e90` Refactoring; `0cdb1245` Use regexp flags via helper — run `git show` on any of them.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×5
  • Duplicated block (10 lines × 2 locations) packages/core-js-pure/override/modules/es.date.to-json.js:10 — packages/core-js-pure/override/modules/es.date.to-json.js:10 · packages/core-js/modules/es.date.to-json.js:7 — 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 (10 lines × 2 locations) packages/core-js/internals/url-domain-to-ascii.js:8 — packages/core-js/internals/url-domain-to-ascii.js:8 · packages/core-js/modules/web.url.constructor.js:45 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2 locations) packages/core-js/modules/es.map.get-or-insert.js:6 — packages/core-js/modules/es.map.get-or-insert.js:6 · packages/core-js/modules/es.weak-map.get-or-insert.js:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (10 lines × 2 locations) packages/core-js/modules/web.url.can-parse.js:26 — packages/core-js/modules/web.url.can-parse.js:26 · packages/core-js/modules/web.url.parse.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (10 lines × 2 locations) packages/core-js/modules/web.url.constructor.js:975 — packages/core-js/modules/web.url.constructor.js:975 · packages/core-js/modules/web.url.constructor.js:995 — 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.
D1 · Cyclomatic Complexity · exports (cyclomatic 26) · ×4
  • exports (cyclomatic 26) packages/core-js/internals/url-domain-to-ascii.js:311 — exports has cyclomatic complexity 26 (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.
  • exports (cyclomatic 26) packages/core-js/internals/typed-array-constructor.js:113 — exports has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 146, a function literal at line 188, setter, …). 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.
  • exports (cyclomatic 26) packages/core-js/internals/string-parse.js:43 — exports has cyclomatic complexity 26 (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.
  • exports (cyclomatic 26) packages/core-js-compat/targets-parser.js:56 — exports has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 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.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×4
  • Duplicated block (11 lines × 2 locations) packages/core-js/internals/async-from-sync-iterator.js:49 — packages/core-js/internals/async-from-sync-iterator.js:49 · packages/core-js/internals/async-from-sync-iterator.js:61 — 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 (11 lines × 2 locations) packages/core-js/modules/es.array.splice.js:28 — packages/core-js/modules/es.array.splice.js:28 · packages/core-js/modules/es.array.to-spliced.js:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (11 lines × 2 locations) packages/core-js/modules/es.iterator.zip-keyed.js:16 — packages/core-js/modules/es.iterator.zip-keyed.js:16 · packages/core-js/modules/es.iterator.zip.js:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (11 lines × 2 locations) packages/core-js/modules/esnext.math.imulh.js:8 — packages/core-js/modules/esnext.math.imulh.js:8 · packages/core-js/modules/esnext.math.umulh.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×3
  • FunctionTooLong: web.structured-clone.structuredCloneInternal packages/core-js/modules/web.structured-clone.js:275 — FunctionTooLong — structuredCloneInternal runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: playground.init website/src/js/playground.js:36 — FunctionTooLong — init runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: main.init website/src/js/main.js:43 — FunctionTooLong — init runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×3
  • Duplicated block (14 lines × 2 locations) packages/core-js/modules/es.array.push.js:11 — packages/core-js/modules/es.array.push.js:11 · packages/core-js/modules/es.array.unshift.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (14 lines × 2 locations) packages/core-js/modules/es.regexp.dot-all.js:8 — packages/core-js/modules/es.regexp.dot-all.js:8 · packages/core-js/modules/es.regexp.sticky.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (14 lines × 2 locations) packages/core-js/modules/esnext.map.emplace.js:13 — packages/core-js/modules/esnext.map.emplace.js:13 · packages/core-js/modules/esnext.weak-map.emplace.js:13 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×3
  • Duplicated block with local edits (10 matched lines × 2 locations) packages/core-js/modules/es.map.get-or-insert-computed.js:13 — packages/core-js/modules/es.map.get-or-insert-computed.js:13 · packages/core-js/modules/es.weak-map.get-or-insert-computed.js:26 — the two spans are one implementation copied and then locally edited — 56 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 (10 matched lines × 2 locations) packages/core-js/modules/es.promise.any.js:11 — packages/core-js/modules/es.promise.any.js:11 · packages/core-js/modules/es.promise.race.js:8 — the two spans are one implementation copied and then locally edited — 79 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 (10 matched lines × 2 locations) packages/core-js/modules/es.uint8-array.to-base64.js:20 — packages/core-js/modules/es.uint8-array.to-base64.js:20 · packages/core-js/modules/es.uint8-array.to-hex.js:8 — the two spans are one implementation copied and then locally edited — 76 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.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 26) · ×2
  • (anonymous) (cyclomatic 26) packages/core-js/modules/es.string.split.js:46 — (anonymous) has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 66, a function literal at line 47, split). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
  • (anonymous) (cyclomatic 26) REDACTED:16 — (anonymous) has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · exports (cyclomatic 22) · ×2
  • exports (cyclomatic 22) packages/core-js-pure/override/internals/collection.js:22 — exports 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 6 function items inside it that branch (a function literal at line 53, a function literal at line 50, a function literal at line 38, …). 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.
  • exports (cyclomatic 22) packages/core-js/internals/make-built-in.js:26 — exports has cyclomatic complexity 22 (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 · exports (cyclomatic 19) · ×2
  • exports (cyclomatic 19) packages/core-js/internals/export.js:30 — exports 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.
  • exports (cyclomatic 19) packages/core-js/internals/wrap-error-constructor-with-cause.js:16 — exports has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: 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.
D12 · Dependency Hygiene · Floating npm dependency · ×2
  • Floating npm dependency: mkdirp — `mkdirp` is declared as `>=0.5.6 <1` in packages/core-js-builder/package.json, which names no releasable version: `>=0.5.6 <1` is an open range with no upper bound on the major. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
  • Floating npm dependency: webpack — `webpack` is declared as `>=4.47.0 <5` in packages/core-js-builder/package.json, which names no releasable version: `>=4.47.0 <5` is an open range with no upper bound on the major. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
D2 · Cognitive Complexity · exports (cognitive 37) · ×2
  • exports (cognitive 37) packages/core-js-compat/targets-parser.js:56 — exports has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 6 (8 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 11). Of this number, 32 points are the body's own statements and 5 belong to 5 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.
  • exports (cognitive 37) packages/core-js/internals/export.js:30 — exports has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 7, ternaries 2 (6 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 31) · ×2
  • exports (cognitive 31) packages/core-js/internals/string-parse.js:43 — exports has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 2, loops 2, match/switch 1 (2 pts), ternaries 1 (2 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.
  • exports (cognitive 31) packages/core-js-pure/override/internals/collection.js:22 — exports has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (14 pts), if/else 6 (10 pts), boolean chains 7 (nesting depth added 13). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 53, a function literal at line 50, a function literal at line 38, …). 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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: modules/web.url.constructor.js packages/core-js/modules/web.url.constructor.js — FileTooLong — 868 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 368 over it, 1.74× 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: modules/web.structured-clone.js packages/core-js/modules/web.structured-clone.js — FileTooLong — 547 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 47 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×2
  • Duplicated block (24 lines × 2 locations) packages/core-js/modules/esnext.async-iterator.filter.js:12 — packages/core-js/modules/esnext.async-iterator.filter.js:12 · packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (24 lines × 2 locations) packages/core-js/modules/esnext.promise.all-keyed.js:12 — packages/core-js/modules/esnext.promise.all-keyed.js:12 · packages/core-js/modules/esnext.promise.all-settled-keyed.js:12 — 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 (16 lines × 2 locations) · ×2
  • Duplicated block (16 lines × 2 locations) packages/core-js/modules/es.iterator.find.js:16 — packages/core-js/modules/es.iterator.find.js:16 · packages/core-js/modules/es.iterator.some.js:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (16 lines × 2 locations) packages/core-js/modules/esnext.map.reduce.js:12 — packages/core-js/modules/esnext.map.reduce.js:12 · packages/core-js/modules/esnext.set.reduce.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (13 matched lines × 2 locations) packages/core-js/modules/es.array.with.js:15 — packages/core-js/modules/es.array.with.js:15 · packages/core-js/modules/es.typed-array.with.js:35 — the two spans are one implementation copied and then locally edited — 96 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 (13 matched lines × 2 locations) packages/core-js/modules/es.regexp.constructor.js:53 — packages/core-js/modules/es.regexp.constructor.js:53 · packages/core-js/modules/es.regexp.constructor.js:77 — the two spans are one implementation copied and then locally edited — 77 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 (13 lines × 2 locations) · ×2
  • Duplicated block (13 lines × 2 locations) packages/core-js/modules/es.string.ends-with.js:12 — packages/core-js/modules/es.string.ends-with.js:12 · packages/core-js/modules/es.string.starts-with.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (13 lines × 2 locations) packages/core-js/modules/esnext.async-iterator.filter.js:40 — packages/core-js/modules/esnext.async-iterator.filter.js:40 · packages/core-js/modules/esnext.async-iterator.reduce.js:50 — 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 (12 lines × 3 locations) · ×2
  • Duplicated block (12 lines × 3 locations) packages/core-js/internals/async-iterator-map.js:11 — packages/core-js/internals/async-iterator-map.js:11 · packages/core-js/modules/esnext.async-iterator.filter.js:12 · packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (12 lines × 3 locations) packages/core-js/modules/es.iterator.filter.js:32 — packages/core-js/modules/es.iterator.filter.js:32 · packages/core-js/modules/es.iterator.flat-map.js:54 · packages/core-js/modules/es.iterator.map.js:25 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 89) · ×2
  • Complex function (anonymous) (cyclomatic 31, cognitive 89) tests/unit-global/es.json.parse.js:6 — (anonymous) has cyclomatic complexity 31 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 31, cognitive 89) tests/unit-pure/es.json.parse.js:13 — (anonymous) has cyclomatic complexity 31 and cognitive complexity 89; 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 28, cognitive 36) · ×2
  • Complex function (anonymous) (cyclomatic 28, cognitive 36) tests/unit-global/web.structured-clone.js:1090 — (anonymous) has cyclomatic complexity 28 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 28, cognitive 36) tests/unit-pure/web.structured-clone.js:1123 — (anonymous) has cyclomatic complexity 28 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 49) · ×2
  • Complex function (anonymous) (cyclomatic 24, cognitive 49) tests/unit-global/esnext.iterator.range.js:3 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 24, cognitive 49) tests/unit-pure/esnext.iterator.range.js:9 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 24, cognitive 40) · ×2
  • Complex function (anonymous) (cyclomatic 24, cognitive 40) tests/unit-global/web.url-search-params.js:875 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function (anonymous) (cyclomatic 24, cognitive 40) tests/unit-pure/web.url-search-params.js:817 — (anonymous) has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) packages/core-js/modules/es.uint8-array.set-from-base64.js:17 — `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) packages/core-js/modules/es.uint8-array.to-base64.js:29 — `catch (error)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
D1 · Cyclomatic Complexity · parse (cyclomatic 190) · ×1
  • parse (cyclomatic 190) packages/core-js/modules/web.url.constructor.js:401 — parse has cyclomatic complexity 190 (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 · web.structured-clone.structuredCloneInternal (cyclomatic 104) · ×1
  • web.structured-clone.structuredCloneInternal (cyclomatic 104) packages/core-js/modules/web.structured-clone.js:275 — web.structured-clone.structuredCloneInternal has cyclomatic complexity 104 (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 · url-domain-to-ascii.mapCodePoint (cyclomatic 48) · ×1
  • url-domain-to-ascii.mapCodePoint (cyclomatic 48) packages/core-js/internals/url-domain-to-ascii.js:136 — url-domain-to-ascii.mapCodePoint has cyclomatic complexity 48 (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 · iterator-define.default (cyclomatic 44) · ×1
  • iterator-define.default (cyclomatic 44) packages/core-js/internals/iterator-define.js:28 — iterator-define.default has cyclomatic complexity 44 (threshold 15). Of this number, 36 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sumPrecise (cyclomatic 44) · ×1
  • sumPrecise (cyclomatic 44) packages/core-js/modules/es.math.sum-precise.js:100 — sumPrecise has cyclomatic complexity 44 (threshold 15). Of this number, 32 points are the body's own statements and 12 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 · exports (cyclomatic 44) · ×1
  • exports (cyclomatic 44) packages/core-js/internals/iterator-define.js:28 — exports has cyclomatic complexity 44 (threshold 15). Of this number, 36 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · export.default (cyclomatic 43) · ×1
  • export.default (cyclomatic 43) packages/core-js-pure/override/internals/export.js:60 — export.default 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 · exports (cyclomatic 43) · ×1
  • exports (cyclomatic 43) packages/core-js-pure/override/internals/export.js:60 — exports 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 · web.structured-clone.prepareTransfer (cyclomatic 37) · ×1
  • web.structured-clone.prepareTransfer (cyclomatic 37) packages/core-js/modules/web.structured-clone.js:573 — web.structured-clone.prepareTransfer 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 · collection.default (cyclomatic 36) · ×1
  • collection.default (cyclomatic 36) packages/core-js/internals/collection.js:18 — collection.default has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 8 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 · exports (cyclomatic 36) · ×1
  • exports (cyclomatic 36) packages/core-js/internals/collection.js:18 — exports has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 11 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 · url-search-params-body.patchFetch (cyclomatic 32) · ×1
  • url-search-params-body.patchFetch (cyclomatic 32) packages/core-js/internals/url-search-params-body.js:45 — url-search-params-body.patchFetch has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 10 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (ResponseConstructor, wrapRequestOptions, a function literal at line 104, …). 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 · uint8-from-base64.default (cyclomatic 31) · ×1
  • uint8-from-base64.default (cyclomatic 31) packages/core-js/internals/uint8-from-base64.js:72 — uint8-from-base64.default has cyclomatic complexity 31 (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 · web.url.constructor.parseIPv6 (cyclomatic 31) · ×1
  • web.url.constructor.parseIPv6 (cyclomatic 31) packages/core-js/modules/web.url.constructor.js:160 — web.url.constructor.parseIPv6 has cyclomatic complexity 31 (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 · stringify (cyclomatic 31) · ×1
  • stringify (cyclomatic 31) packages/core-js/modules/es.json.stringify.js:187 — stringify has cyclomatic complexity 31 (threshold 15). Of this number, 17 points are the body's own statements and 14 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 · exports (cyclomatic 31) · ×1
  • exports (cyclomatic 31) packages/core-js/internals/uint8-from-base64.js:72 — exports has cyclomatic complexity 31 (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 · getConstructor (cyclomatic 30) · ×1
  • getConstructor (cyclomatic 30) packages/core-js/internals/collection-strong.js:20 — getConstructor has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 11 function items inside it that branch (delete, define, forEach, …). 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 · exec (cyclomatic 30) · ×1
  • exec (cyclomatic 30) packages/core-js/internals/regexp-exec.js:47 — exec has cyclomatic complexity 30 (threshold 15). Of this number, 28 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 · main.init (cyclomatic 29) · ×1
  • main.init (cyclomatic 29) website/src/js/main.js:43 — main.init has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to 11 function items inside it that branch (highlightActiveDocsMenuItem, setActiveDocsMenuItem, processVersions, …). 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 · RegExp (cyclomatic 29) · ×1
  • RegExp (cyclomatic 29) packages/core-js/modules/es.regexp.constructor.js:139 — RegExp 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 · url-percent-coding.decode (cyclomatic 27) · ×1
  • url-percent-coding.decode (cyclomatic 27) packages/core-js/internals/url-percent-coding.js:30 — url-percent-coding.decode 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 · targets-parser.default (cyclomatic 26) · ×1
  • targets-parser.default (cyclomatic 26) packages/core-js-compat/targets-parser.js:56 — targets-parser.default has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, 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 · web.structured-clone.cloneView (cyclomatic 26) · ×1
  • web.structured-clone.cloneView (cyclomatic 26) packages/core-js/modules/web.structured-clone.js:215 — web.structured-clone.cloneView has cyclomatic complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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 · url-domain-to-ascii.default (cyclomatic 26) · ×1
  • url-domain-to-ascii.default (cyclomatic 26) packages/core-js/internals/url-domain-to-ascii.js:311 — url-domain-to-ascii.default has cyclomatic complexity 26 (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 · string-parse.default (cyclomatic 26) · ×1
  • string-parse.default (cyclomatic 26) packages/core-js/internals/string-parse.js:43 — string-parse.default has cyclomatic complexity 26 (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 · string-punycode.decode (cyclomatic 25) · ×1
  • string-punycode.decode (cyclomatic 25) packages/core-js/internals/string-punycode.js:235 — string-punycode.decode 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 · iterate.default (cyclomatic 24) · ×1
  • iterate.default (cyclomatic 24) packages/core-js/internals/iterate.js:22 — iterate.default has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · url-search-params-body.patchXMLHttpRequest (cyclomatic 24) · ×1
  • url-search-params-body.patchXMLHttpRequest (cyclomatic 24) packages/core-js/internals/url-search-params-body.js:171 — url-search-params-body.patchXMLHttpRequest has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 184, 232, 219). 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 · url-domain-to-ascii.isIgnored (cyclomatic 24) · ×1
  • url-domain-to-ascii.isIgnored (cyclomatic 24) packages/core-js/internals/url-domain-to-ascii.js:108 — url-domain-to-ascii.isIgnored has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: url-domain-to-ascii.isUnassignedMathematical (cyclomatic 25) 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 method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · exports (cyclomatic 24) · ×1
  • exports (cyclomatic 24) packages/core-js/internals/iterate.js:22 — exports has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · collection.default (cyclomatic 22) · ×1
  • collection.default (cyclomatic 22) packages/core-js-pure/override/internals/collection.js:22 — collection.default 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 3 function literals inside it that branch (lines 53, 50, 38). 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 · async-iterator-iteration.createMethod.<returned closure> (cyclomatic 22) · ×1
  • async-iterator-iteration.createMethod.<returned closure> (cyclomatic 22) packages/core-js/internals/async-iterator-iteration.js:20 — async-iterator-iteration.createMethod.<returned closure> has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 42, 56, 35). 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 · async-iterator-create-proxy.createAsyncIteratorProxyPrototype (cyclomatic 22) · ×1
  • async-iterator-create-proxy.createAsyncIteratorProxyPrototype (cyclomatic 22) packages/core-js/internals/async-iterator-create-proxy.js:23 — async-iterator-create-proxy.createAsyncIteratorProxyPrototype has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 63, getStateOrEarlyExit, a function literal at line 41, …). 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 · numeric-range-iterator.$RangeIterator (cyclomatic 22) · ×1
  • numeric-range-iterator.$RangeIterator (cyclomatic 22) packages/core-js/internals/numeric-range-iterator.js:20 — numeric-range-iterator.$RangeIterator has cyclomatic complexity 22 (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 · playground.init · ×1
  • playground.init::serializeLog (cyclomatic 22) website/src/js/playground.js:118 — playground.init::serializeLog has cyclomatic complexity 22 (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 · NumericRangeIterator (cyclomatic 22) · ×1
  • NumericRangeIterator (cyclomatic 22) packages/core-js/internals/numeric-range-iterator.js:20 — NumericRangeIterator has cyclomatic complexity 22 (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 · createMethod (cyclomatic 22) · ×1
  • createMethod (cyclomatic 22) packages/core-js/internals/async-iterator-iteration.js:15 — createMethod has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 42, (anonymous)::(anonymous)::loop::(anonymous)::handler, a function literal at line 20, …). 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 · (anonymous) (cyclomatic 21) · ×1
  • (anonymous) (cyclomatic 21) packages/core-js/modules/es.string.replace.js:61 — (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 76, replace). 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 · toExponential (cyclomatic 21) · ×1
  • toExponential (cyclomatic 21) packages/core-js/modules/es.number.to-exponential.js:68 — toExponential has cyclomatic complexity 21 (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 · array-buffer-transfer.default (cyclomatic 20) · ×1
  • array-buffer-transfer.default (cyclomatic 20) packages/core-js/internals/array-buffer-transfer.js:33 — array-buffer-transfer.default has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 20) · ×1
  • (anonymous) (cyclomatic 20) packages/core-js/internals/array-buffer-transfer.js:33 — (anonymous) has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · zip (cyclomatic 20) · ×1
  • zip (cyclomatic 20) packages/core-js/modules/es.iterator.zip.js:22 — zip 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 · createMethod (cyclomatic 20) · ×1
  • createMethod (cyclomatic 20) packages/core-js/internals/array-iteration.js:10 — createMethod has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 18). 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 · export.default (cyclomatic 19) · ×1
  • export.default (cyclomatic 19) packages/core-js/internals/export.js:30 — export.default 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 · array-iteration.createMethod.<returned closure> (cyclomatic 19) · ×1
  • array-iteration.createMethod.<returned closure> (cyclomatic 19) packages/core-js/internals/array-iteration.js:18 — array-iteration.createMethod.<returned closure> 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 · iterator-create-proxy.createIteratorProxyPrototype (cyclomatic 19) · ×1
  • iterator-create-proxy.createIteratorProxyPrototype (cyclomatic 19) packages/core-js/internals/iterator-create-proxy.js:24 — iterator-create-proxy.createIteratorProxyPrototype has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 49, 28). 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 · web.url.constructor.parseIPv4 (cyclomatic 19) · ×1
  • web.url.constructor.parseIPv4 (cyclomatic 19) packages/core-js/modules/web.url.constructor.js:120 — web.url.constructor.parseIPv4 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 · esnext.string.dedent.dedentStringsArray (cyclomatic 19) · ×1
  • esnext.string.dedent.dedentStringsArray (cyclomatic 19) packages/core-js/modules/esnext.string.dedent.js:56 — esnext.string.dedent.dedentStringsArray 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 · array-buffer-view-core.exportTypedArrayStaticMethod (cyclomatic 18) · ×1
  • array-buffer-view-core.exportTypedArrayStaticMethod (cyclomatic 18) packages/core-js/internals/array-buffer-view-core.js:108 — array-buffer-view-core.exportTypedArrayStaticMethod 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 · es.regexp.constructor.handleNCG (cyclomatic 18) · ×1
  • es.regexp.constructor.handleNCG (cyclomatic 18) packages/core-js/modules/es.regexp.constructor.js:77 — es.regexp.constructor.handleNCG 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 · exports (cyclomatic 18) · ×1
  • exports (cyclomatic 18) packages/core-js-builder/index.js:27 — exports has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs 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 · (anonymous) (cyclomatic 18) · ×1
  • (anonymous) (cyclomatic 18) packages/core-js/modules/web.url-search-params.delete.js:24 — (anonymous) has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · array-buffer-is-detached.default (cyclomatic 17) · ×1
  • array-buffer-is-detached.default (cyclomatic 17) packages/core-js/internals/array-buffer-is-detached.js:37 — array-buffer-is-detached.default 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, 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 · url-domain-to-ascii.checkJoiners (cyclomatic 17) · ×1
  • url-domain-to-ascii.checkJoiners (cyclomatic 17) packages/core-js/internals/url-domain-to-ascii.js:235 — url-domain-to-ascii.checkJoiners has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions. This is NOT this file's highest cyclomatic complexity: url-domain-to-ascii.isUnassignedMathematical (cyclomatic 25) 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 method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · exports (cyclomatic 17) · ×1
  • exports (cyclomatic 17) packages/core-js/internals/array-buffer-is-detached.js:37 — exports has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · fromString (cyclomatic 17) · ×1
  • fromString (cyclomatic 17) packages/core-js/modules/esnext.number.from-string.js:40 — fromString 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 · es.json.parse.internalizeProperty (cyclomatic 16) · ×1
  • es.json.parse.internalizeProperty (cyclomatic 16) packages/core-js/modules/es.json.parse.js:88 — es.json.parse.internalizeProperty 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 · fix-regexp-well-known-symbol-logic.default (cyclomatic 16) · ×1
  • fix-regexp-well-known-symbol-logic.default (cyclomatic 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js:14 — fix-regexp-well-known-symbol-logic.default has cyclomatic complexity 16 (threshold 15). Of this number, 11 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 · es.number.constructor.toNumber (cyclomatic 16) · ×1
  • es.number.constructor.toNumber (cyclomatic 16) packages/core-js/modules/es.number.constructor.js:40 — es.number.constructor.toNumber 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 · number-decimal-digits.exactDigits (cyclomatic 16) · ×1
  • number-decimal-digits.exactDigits (cyclomatic 16) packages/core-js/internals/number-decimal-digits.js:74 — number-decimal-digits.exactDigits 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 · url-domain-to-ascii.mapDomain (cyclomatic 16) · ×1
  • url-domain-to-ascii.mapDomain (cyclomatic 16) packages/core-js/internals/url-domain-to-ascii.js:195 — url-domain-to-ascii.mapDomain 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. This is NOT this file's highest cyclomatic complexity: url-domain-to-ascii.isUnassignedMathematical (cyclomatic 25) 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 method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · url-domain-to-ascii.checkBidi (cyclomatic 16) · ×1
  • url-domain-to-ascii.checkBidi (cyclomatic 16) packages/core-js/internals/url-domain-to-ascii.js:281 — url-domain-to-ascii.checkBidi 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. This is NOT this file's highest cyclomatic complexity: url-domain-to-ascii.isUnassignedMathematical (cyclomatic 25) 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 method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 16) · ×1
  • (anonymous) (cyclomatic 16) packages/core-js/modules/es.array.sort.js:32 — (anonymous) has cyclomatic complexity 16 (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 · exports (cyclomatic 16) · ×1
  • exports (cyclomatic 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js:14 — exports has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 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 · toPrecision (cyclomatic 16) · ×1
  • toPrecision (cyclomatic 16) packages/core-js/modules/es.number.to-precision.js:52 — toPrecision 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.
D2 · Cognitive Complexity · parse (cognitive 347) · ×1
  • parse (cognitive 347) packages/core-js/modules/web.url.constructor.js:401 — parse has cognitive complexity 347 (threshold 15). Drivers by points: if/else 101 (262 pts), boolean chains 57, ternaries 4 (17 pts), match/switch 2 (6 pts), loops 2 (5 pts) (nesting depth added 181). To reduce it, split the body into named stages: move each independent 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 · structuredCloneInternal (cognitive 88) · ×1
  • structuredCloneInternal (cognitive 88) packages/core-js/modules/web.structured-clone.js:275 — structuredCloneInternal has cognitive complexity 88 (threshold 15). Drivers by points: if/else 17 (32 pts), error handling 9 (28 pts), ternaries 3 (12 pts), loops 4 (9 pts), match/switch 4 (7 pts) (nesting depth added 51). To reduce it, split the body into named stages: move each independent 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 · uint8-from-base64.default (cognitive 82) · ×1
  • uint8-from-base64.default (cognitive 82) packages/core-js/internals/uint8-from-base64.js:72 — uint8-from-base64.default has cognitive complexity 82 (threshold 15). Drivers by points: if/else 22 (73 pts), boolean chains 5, loops 1 (2 pts), ternaries 2 (nesting depth added 52). 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 · exports (cognitive 82) · ×1
  • exports (cognitive 82) packages/core-js/internals/uint8-from-base64.js:72 — exports has cognitive complexity 82 (threshold 15). Drivers by points: if/else 22 (73 pts), boolean chains 5, loops 1 (2 pts), ternaries 2 (nesting depth added 52). 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 · url-percent-coding.decode (cognitive 81) · ×1
  • url-percent-coding.decode (cognitive 81) packages/core-js/internals/url-percent-coding.js:30 — url-percent-coding.decode has cognitive complexity 81 (threshold 15). Drivers by points: if/else 14 (59 pts), ternaries 2 (9 pts), boolean chains 8, loops 2 (5 pts) (nesting depth added 55). 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 · web.url.constructor.parseIPv6 (cognitive 74) · ×1
  • web.url.constructor.parseIPv6 (cognitive 74) packages/core-js/modules/web.url.constructor.js:160 — web.url.constructor.parseIPv6 has cognitive complexity 74 (threshold 15). Drivers by points: if/else 23 (58 pts), loops 5 (12 pts), boolean chains 4 (nesting depth added 42). To reduce it, split the body into named stages: move each independent 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 · collection.default (cognitive 68) · ×1
  • collection.default (cognitive 68) packages/core-js/internals/collection.js:18 — collection.default has cognitive complexity 68 (threshold 15). Drivers by points: ternaries 13 (45 pts), boolean chains 12, if/else 7 (11 pts) (nesting depth added 36). Of this number, 21 points are the body's own statements and 47 belong to 8 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 · patchFetch (cognitive 68) · ×1
  • patchFetch (cognitive 68) packages/core-js/internals/url-search-params-body.js:45 — patchFetch has cognitive complexity 68 (threshold 15). Drivers by points: ternaries 8 (28 pts), if/else 12 (27 pts), boolean chains 10, error handling 1 (3 pts) (nesting depth added 37). Most of this is not in the body itself: 11 of the 68 points are its own statements and the rest belongs to 8 function items inside it that branch (wrapRequestOptions, Response, fetch, …). 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 · exports (cognitive 56) · ×1
  • exports (cognitive 56) packages/core-js/internals/iterator-define.js:28 — exports has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 16, error handling 1 (3 pts), loops 1 (3 pts), ternaries 2 (3 pts), match/switch 1 (nesting depth added 19). Of this number, 51 points are the body's own statements and 5 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 55) · ×1
  • exports (cognitive 55) packages/core-js-pure/override/internals/export.js:60 — exports has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 20, ternaries 6 (9 pts), loops 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 · sumPrecise (cognitive 55) · ×1
  • sumPrecise (cognitive 55) packages/core-js/modules/es.math.sum-precise.js:100 — sumPrecise has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (23 pts), ternaries 6 (18 pts), boolean chains 12, loops 1, match/switch 1 (nesting depth added 20). Of this number, 38 points are the body's own statements and 17 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 · iterator-define.default (cognitive 54) · ×1
  • iterator-define.default (cognitive 54) packages/core-js/internals/iterator-define.js:28 — iterator-define.default has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 16, error handling 1 (3 pts), loops 1 (3 pts), match/switch 1, ternaries 1 (nesting depth added 18). Of this number, 49 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · zip (cognitive 54) · ×1
  • zip (cognitive 54) packages/core-js/modules/es.iterator.zip.js:22 — zip has cognitive complexity 54 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 5 (17 pts), loops 3 (7 pts), ternaries 3 (7 pts), boolean chains 1 (nesting depth added 32). 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 · iterator-zip.IteratorProxy (cognitive 50) · ×1
  • iterator-zip.IteratorProxy (cognitive 50) packages/core-js/internals/iterator-zip.js:14 — iterator-zip.IteratorProxy has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (34 pts), error handling 2 (9 pts), loops 2 (6 pts), ternaries 1 (nesting depth added 34). 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 · prepareTransfer (cognitive 50) · ×1
  • prepareTransfer (cognitive 50) packages/core-js/modules/web.structured-clone.js:573 — prepareTransfer has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (35 pts), boolean chains 6, match/switch 1 (3 pts), ternaries 1 (3 pts), error handling 1 (2 pts), 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 · (anonymous) (cognitive 50) · ×1
  • (anonymous) (cognitive 50) packages/core-js/internals/iterator-zip.js:14 — (anonymous) has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (34 pts), error handling 2 (9 pts), loops 2 (6 pts), ternaries 1 (nesting depth added 34). 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 · export.default (cognitive 49) · ×1
  • export.default (cognitive 49) packages/core-js-pure/override/internals/export.js:60 — export.default has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 19, ternaries 3 (4 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 48) · ×1
  • exports (cognitive 48) packages/core-js/internals/typed-array-constructor.js:113 — exports has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (39 pts), ternaries 4 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 21). Most of this is not in the body itself: 12 of the 48 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 146, a function literal at line 188, setter, …). 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 · getConstructor (cognitive 46) · ×1
  • getConstructor (cognitive 46) packages/core-js/internals/collection-strong.js:20 — getConstructor has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (33 pts), ternaries 5 (6 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 13). Most of this is not in the body itself: 2 of the 46 points are its own statements and the rest belongs to 11 function items inside it that branch (delete, define, forEach, …). 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 · decode (cognitive 45) · ×1
  • decode (cognitive 45) packages/core-js/internals/string-punycode.js:235 — decode has cognitive complexity 45 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 8 (11 pts), ternaries 3 (8 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent 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 · async-iterator-iteration.createMethod.<returned closure> (cognitive 44) · ×1
  • async-iterator-iteration.createMethod.<returned closure> (cognitive 44) packages/core-js/internals/async-iterator-iteration.js:20 — async-iterator-iteration.createMethod.<returned closure> has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 4 (12 pts), error handling 5 (9 pts), boolean chains 4 (nesting depth added 18). Most of this is not in the body itself: 3 of the 44 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 42, 56, 35). 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 · cloneView (cognitive 44) · ×1
  • cloneView (cognitive 44) packages/core-js/modules/web.structured-clone.js:215 — cloneView has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (28 pts), boolean chains 10, ternaries 3 (6 pts) (nesting depth added 17). Of this number, 35 points are the body's own statements and 9 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 · createMethod (cognitive 44) · ×1
  • createMethod (cognitive 44) packages/core-js/internals/async-iterator-iteration.js:15 — createMethod has cognitive complexity 44 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 4 (12 pts), error handling 5 (9 pts), boolean chains 4 (nesting depth added 18). None of this is in the body itself: all 44 points belong to 6 function items inside it that branch (a function literal at line 42, (anonymous)::(anonymous)::loop::(anonymous)::handler, a function literal at line 20, …). 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 · exports (cognitive 42) · ×1
  • exports (cognitive 42) packages/core-js/internals/collection.js:18 — exports has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 14 (15 pts), if/else 8 (14 pts), boolean chains 11, loops 1 (2 pts) (nesting depth added 8). Of this number, 22 points are the body's own statements and 20 belong to 11 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · exports (cognitive 41) · ×1
  • exports (cognitive 41) packages/core-js/internals/url-domain-to-ascii.js:311 — exports has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 7, loops 3 (5 pts), ternaries 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 · (anonymous) (cognitive 41) · ×1
  • (anonymous) (cognitive 41) packages/core-js/modules/es.string.split.js:46 — (anonymous) has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (19 pts), ternaries 10 (15 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 66, a function literal at line 47, split). 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 · url-domain-to-ascii.default (cognitive 40) · ×1
  • url-domain-to-ascii.default (cognitive 40) packages/core-js/internals/url-domain-to-ascii.js:311 — url-domain-to-ascii.default has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6, loops 3 (5 pts), ternaries 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 · targets-parser.default (cognitive 37) · ×1
  • targets-parser.default (cognitive 37) packages/core-js-compat/targets-parser.js:56 — targets-parser.default has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 5 (8 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 12). Of this number, 31 points are the body's own statements and 6 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 · url-search-params-body.patchXMLHttpRequest (cognitive 37) · ×1
  • url-search-params-body.patchXMLHttpRequest (cognitive 37) packages/core-js/internals/url-search-params-body.js:171 — url-search-params-body.patchXMLHttpRequest has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 3 (9 pts), boolean chains 7, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 17). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 184, 232, 219). 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 · parseIPv4 (cognitive 37) · ×1
  • parseIPv4 (cognitive 37) packages/core-js/modules/web.url.constructor.js:120 — parseIPv4 has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 4 (14 pts), loops 3, boolean chains 2 (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 · mapDomain (cognitive 37) · ×1
  • mapDomain (cognitive 37) packages/core-js/internals/url-domain-to-ascii.js:195 — mapDomain has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 4 (16 pts), if/else 9 (15 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent 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 · stringify (cognitive 37) · ×1
  • stringify (cognitive 37) packages/core-js/modules/es.json.stringify.js:187 — stringify has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (26 pts), boolean chains 8, ternaries 2, loops 1 (nesting depth added 8). Of this number, 18 points are the body's own statements and 19 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 · exports (cognitive 36) · ×1
  • exports (cognitive 36) packages/core-js/internals/iterate.js:22 — exports has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 7, loops 2 (4 pts), ternaries 3 (4 pts), error handling 1 (2 pts) (nesting depth added 12). Of this number, 31 points are the body's own statements and 5 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 · iterate.default (cognitive 35) · ×1
  • iterate.default (cognitive 35) packages/core-js/internals/iterate.js:22 — iterate.default has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 7, loops 2 (4 pts), ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 12). Of this number, 30 points are the body's own statements and 5 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 · array-buffer-view-core.exportTypedArrayStaticMethod (cognitive 34) · ×1
  • array-buffer-view-core.exportTypedArrayStaticMethod (cognitive 34) packages/core-js/internals/array-buffer-view-core.js:108 — array-buffer-view-core.exportTypedArrayStaticMethod has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (8 pts), boolean chains 6, loops 2 (4 pts), ternaries 1 (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 · exec (cognitive 34) · ×1
  • exec (cognitive 34) packages/core-js/internals/regexp-exec.js:47 — exec has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 9, ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 29 points are the body's own statements and 5 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 · collection.default (cognitive 32) · ×1
  • collection.default (cognitive 32) packages/core-js-pure/override/internals/collection.js:22 — collection.default has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 9, if/else 5 (8 pts) (nesting depth added 13). Most of this is not in the body itself: 9 of the 32 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 53, 50, 38). 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 · mapCodePoint (cognitive 32) · ×1
  • mapCodePoint (cognitive 32) packages/core-js/internals/url-domain-to-ascii.js:136 — mapCodePoint has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 10, ternaries 2 (4 pts), loops 1 (2 pts), match/switch 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 · export.default (cognitive 31) · ×1
  • export.default (cognitive 31) packages/core-js/internals/export.js:30 — export.default has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 7, loops 1 (2 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 · array-iteration.createMethod.<returned closure> (cognitive 31) · ×1
  • array-iteration.createMethod.<returned closure> (cognitive 31) packages/core-js/internals/array-iteration.js:18 — array-iteration.createMethod.<returned closure> has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 2 (10 pts), ternaries 4 (6 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · main.init (cognitive 31) · ×1
  • main.init (cognitive 31) website/src/js/main.js:43 — main.init has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 11, loops 3, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 11 function items inside it that branch (highlightActiveDocsMenuItem, setActiveDocsMenuItem, processVersions, …). 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 · RegExp (cognitive 31) · ×1
  • RegExp (cognitive 31) packages/core-js/modules/es.regexp.constructor.js:139 — RegExp has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 8, ternaries 3, 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 · esnext.string.dedent.dedentStringsArray (cognitive 30) · ×1
  • esnext.string.dedent.dedentStringsArray (cognitive 30) packages/core-js/modules/esnext.string.dedent.js:56 — esnext.string.dedent.dedentStringsArray has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 6 (9 pts), boolean chains 4, 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 · (anonymous) (cognitive 30) · ×1
  • (anonymous) (cognitive 30) packages/core-js/modules/es.string.replace.js:61 — (anonymous) has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, loops 3 (4 pts), ternaries 3 (nesting depth added 9). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 76, replace). 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 · createMethod (cognitive 30) · ×1
  • createMethod (cognitive 30) packages/core-js/internals/array-iteration.js:10 — createMethod has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 2 (10 pts), boolean chains 4, ternaries 4, loops 1 (nesting depth added 14). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to one function literal inside it that branches (line 18). 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 · async-iterator-create-proxy.createAsyncIteratorProxyPrototype (cognitive 29) · ×1
  • async-iterator-create-proxy.createAsyncIteratorProxyPrototype (cognitive 29) packages/core-js/internals/async-iterator-create-proxy.js:23 — async-iterator-create-proxy.createAsyncIteratorProxyPrototype has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 4 (5 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 63, getStateOrEarlyExit, a function literal at line 41, …). 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 · es.regexp.constructor.handleNCG (cognitive 29) · ×1
  • es.regexp.constructor.handleNCG (cognitive 29) packages/core-js/modules/es.regexp.constructor.js:77 — es.regexp.constructor.handleNCG has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 3 (4 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · string-parse.default (cognitive 29) · ×1
  • string-parse.default (cognitive 29) packages/core-js/internals/string-parse.js:43 — string-parse.default has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · web.structured-clone.replaceReferences (cognitive 28) · ×1
  • web.structured-clone.replaceReferences (cognitive 28) packages/core-js/modules/web.structured-clone.js:529 — web.structured-clone.replaceReferences has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (7 pts), boolean chains 2, ternaries 1 (nesting depth added 13). None of this is in the body itself: all 28 points belong to 2 function items inside it that branch (a function literal at line 533, replace). 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 · exports (cognitive 28) · ×1
  • exports (cognitive 28) packages/core-js-builder/index.js:27 — exports has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (8 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 9). Of this number, 25 points are the body's own statements and 3 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · from (cognitive 28) · ×1
  • from (cognitive 28) packages/core-js/internals/array-from.js:21 — from has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 6 (13 pts), error handling 2 (6 pts), loops 2 (4 pts), if/else 3, 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 · es.json.parse.internalize (cognitive 26) · ×1
  • es.json.parse.internalize (cognitive 26) packages/core-js/modules/es.json.parse.js:62 — es.json.parse.internalize has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 5 (14 pts), loops 2 (6 pts), if/else 3 (4 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · encode (cognitive 26) · ×1
  • encode (cognitive 26) packages/core-js/internals/string-punycode.js:131 — encode has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 5 (9 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 11). 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 · toExponential (cognitive 26) · ×1
  • toExponential (cognitive 26) packages/core-js/modules/es.number.to-exponential.js:68 — toExponential has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, loops 2 (4 pts), ternaries 3 (4 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · es.promise.constructor.callReaction (cognitive 25) · ×1
  • es.promise.constructor.callReaction (cognitive 25) packages/core-js/modules/es.promise.constructor.js:59 — es.promise.constructor.callReaction has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 1, error handling 1, 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 · number-decimal-digits.exactDigits (cognitive 25) · ×1
  • number-decimal-digits.exactDigits (cognitive 25) packages/core-js/internals/number-decimal-digits.js:74 — number-decimal-digits.exactDigits has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 5 (7 pts), boolean chains 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 · serializeHost (cognitive 25) · ×1
  • serializeHost (cognitive 25) packages/core-js/modules/web.url.constructor.js:259 — serializeHost has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), ternaries 1 (4 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 · (anonymous) (cognitive 25) · ×1
  • (anonymous) (cognitive 25) packages/core-js/modules/web.url-search-params.delete.js:24 — (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 5 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 7). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cloneBuffer (cognitive 24) · ×1
  • cloneBuffer (cognitive 24) packages/core-js/modules/web.structured-clone.js:177 — cloneBuffer has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 24) · ×1
  • exports (cognitive 24) packages/core-js/internals/make-built-in.js:26 — exports has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 8, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · zipKeyed (cognitive 24) · ×1
  • zipKeyed (cognitive 24) packages/core-js/modules/es.iterator.zip-keyed.js:22 — zipKeyed has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (8 pts), error handling 2 (5 pts), ternaries 2, boolean chains 1 (nesting depth added 10). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent 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 · array-buffer-view-core.exportTypedArrayMethod (cognitive 23) · ×1
  • array-buffer-view-core.exportTypedArrayMethod (cognitive 23) packages/core-js/internals/array-buffer-view-core.js:89 — array-buffer-view-core.exportTypedArrayMethod has cognitive complexity 23 (threshold 15). Drivers by points: error handling 2 (9 pts), if/else 4 (6 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · iterator-create-proxy.createIteratorProxyPrototype (cognitive 23) · ×1
  • iterator-create-proxy.createIteratorProxyPrototype (cognitive 23) packages/core-js/internals/iterator-create-proxy.js:24 — iterator-create-proxy.createIteratorProxyPrototype has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), error handling 3 (5 pts), ternaries 3 (4 pts), boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 49, 28). 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 · number-decimal-digits.default (cognitive 23) · ×1
  • number-decimal-digits.default (cognitive 23) packages/core-js/internals/number-decimal-digits.js:129 — number-decimal-digits.default has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · url-domain-to-ascii.checkJoiners (cognitive 23) · ×1
  • url-domain-to-ascii.checkJoiners (cognitive 23) packages/core-js/internals/url-domain-to-ascii.js:235 — url-domain-to-ascii.checkJoiners has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 8, loops 3 (5 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 · url-domain-to-ascii.bidiClass (cognitive 23) · ×1
  • url-domain-to-ascii.bidiClass (cognitive 23) packages/core-js/internals/url-domain-to-ascii.js:270 — url-domain-to-ascii.bidiClass has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 7 (20 pts), boolean chains 2, if/else 1 (nesting depth added 13). 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 · internalizeProperty (cognitive 23) · ×1
  • internalizeProperty (cognitive 23) packages/core-js/modules/es.json.parse.js:88 — internalizeProperty has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 5, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 23) · ×1
  • exports (cognitive 23) packages/core-js/internals/number-decimal-digits.js:129 — exports has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · splice (cognitive 23) · ×1
  • splice (cognitive 23) packages/core-js/modules/es.array.splice.js:23 — splice has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 5 (8 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 · fromString (cognitive 23) · ×1
  • fromString (cognitive 23) packages/core-js/modules/esnext.number.from-string.js:40 — fromString has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 2 (4 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · es.number.constructor.toNumber (cognitive 22) · ×1
  • es.number.constructor.toNumber (cognitive 22) packages/core-js/modules/es.number.constructor.js:40 — es.number.constructor.toNumber has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, loops 1 (3 pts), match/switch 1 (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 · parseObject (cognitive 22) · ×1
  • parseObject (cognitive 22) packages/core-js/modules/web.url-search-params.constructor.js:179 — parseObject has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (9 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 · pack (cognitive 22) · ×1
  • pack (cognitive 22) packages/core-js/internals/ieee754.js:10 — pack has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (4 pts), boolean chains 3, loops 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 · array-buffer-transfer.default (cognitive 21) · ×1
  • array-buffer-transfer.default (cognitive 21) packages/core-js/internals/array-buffer-transfer.js:33 — array-buffer-transfer.default has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 6, error handling 3 (4 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · playground.init · ×1
  • playground.init::serializeLog (cognitive 21) website/src/js/playground.js:118 — playground.init::serializeLog has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, boolean chains 5, ternaries 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 · NumericRangeIterator (cognitive 21) · ×1
  • NumericRangeIterator (cognitive 21) packages/core-js/internals/numeric-range-iterator.js:20 — NumericRangeIterator has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 7, ternaries 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 · (anonymous) (cognitive 21) · ×1
  • (anonymous) (cognitive 21) packages/core-js/internals/array-buffer-transfer.js:33 — (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 6, error handling 3 (4 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · assign (cognitive 21) · ×1
  • assign (cognitive 21) packages/core-js/internals/object-assign.js:44 — assign has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, ternaries 2 (6 pts), if/else 2 (5 pts), loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 21) · ×1
  • exports (cognitive 21) packages/core-js/internals/wrap-error-constructor-with-cause.js:16 — exports has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, ternaries 3, error handling 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · web.dom-collections.iterator.handlePrototype (cognitive 20) · ×1
  • web.dom-collections.iterator.handlePrototype (cognitive 20) packages/core-js/modules/web.dom-collections.iterator.js:13 — web.dom-collections.iterator.handlePrototype has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (8 pts), loops 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · esnext.async-iterator.flat-map.AsyncIteratorProxy (cognitive 20) · ×1
  • esnext.async-iterator.flat-map.AsyncIteratorProxy (cognitive 20) packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — esnext.async-iterator.flat-map.AsyncIteratorProxy has cognitive complexity 20 (threshold 15). Drivers by points: error handling 6 (10 pts), if/else 8 (10 pts) (nesting depth added 6). None of this is in the body itself: all 20 points belong to 5 function literals inside it that branch (lines 30, 56, 60, …). 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 · es.reflect.set.$set (cognitive 20) · ×1
  • es.reflect.set.$set (cognitive 20) packages/core-js/modules/es.reflect.set.js:16 — es.reflect.set.$set has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), error handling 1 (3 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 · web.structured-clone.performTransfer (cognitive 20) · ×1
  • web.structured-clone.performTransfer (cognitive 20) packages/core-js/modules/web.structured-clone.js:650 — web.structured-clone.performTransfer has cognitive complexity 20 (threshold 15). Drivers by points: error handling 2 (8 pts), if/else 4 (7 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parseHost (cognitive 20) · ×1
  • parseHost (cognitive 20) packages/core-js/modules/web.url.constructor.js:808 — parseHost has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 20) · ×1
  • (anonymous) (cognitive 20) packages/core-js/modules/esnext.async-iterator.flat-map.js:13 — (anonymous) has cognitive complexity 20 (threshold 15). Drivers by points: error handling 6 (10 pts), if/else 8 (10 pts) (nesting depth added 6). None of this is in the body itself: all 20 points belong to 8 function items inside it that branch (a function literal at line 30, (anonymous)::innerLoop, a function literal at line 60, …). 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 · array-includes.createMethod.<returned closure> (cognitive 19) · ×1
  • array-includes.createMethod.<returned closure> (cognitive 19) packages/core-js/internals/array-includes.js:8 — array-includes.createMethod.<returned closure> has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · es.typed-array.sort.getSortCompare.<returned closure> (cognitive 19) · ×1
  • es.typed-array.sort.getSortCompare.<returned closure> (cognitive 19) packages/core-js/modules/es.typed-array.sort.js:52 — es.typed-array.sort.getSortCompare.<returned closure> has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 4, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · numeric-range-iterator.$RangeIterator (cognitive 19) · ×1
  • numeric-range-iterator.$RangeIterator (cognitive 19) packages/core-js/internals/numeric-range-iterator.js:20 — numeric-range-iterator.$RangeIterator has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 7. 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 · array-from-async.fromAsync (cognitive 18) · ×1
  • array-from-async.fromAsync (cognitive 18) packages/core-js/internals/array-from-async.js:23 — array-from-async.fromAsync has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 6, error handling 3, boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 29, 53, 60, …). 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 · array-reduce.createMethod.<returned closure> (cognitive 18) · ×1
  • array-reduce.createMethod.<returned closure> (cognitive 18) packages/core-js/internals/array-reduce.js:13 — array-reduce.createMethod.<returned closure> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (4 pts), loops 2 (3 pts), boolean chains 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 · parse-json-string.default (cognitive 18) · ×1
  • parse-json-string.default (cognitive 18) packages/core-js/internals/parse-json-string.js:27 — parse-json-string.default has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), 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 · delete (cognitive 18) · ×1
  • delete (cognitive 18) packages/core-js/modules/web.url-search-params.constructor.js:330 — delete has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4 (6 pts), boolean chains 3, 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 · isIgnored (cognitive 18) · ×1
  • isIgnored (cognitive 18) packages/core-js/internals/url-domain-to-ascii.js:108 — isIgnored has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 18. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · checkBidi (cognitive 18) · ×1
  • checkBidi (cognitive 18) packages/core-js/internals/url-domain-to-ascii.js:281 — checkBidi has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, ternaries 2 (4 pts), 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 · replaceAll (cognitive 18) · ×1
  • replaceAll (cognitive 18) packages/core-js/modules/es.string.replace-all.js:26 — replaceAll has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · toPrecision (cognitive 18) · ×1
  • toPrecision (cognitive 18) packages/core-js/modules/es.number.to-precision.js:52 — toPrecision has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · get-substitution.default (cognitive 17) · ×1
  • get-substitution.default (cognitive 17) packages/core-js/internals/get-substitution.js:15 — get-substitution.default has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (5 pts), match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 23). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · helpers.buildAndCopyCoreJS (cognitive 17) · ×1
  • helpers.buildAndCopyCoreJS (cognitive 17) website/scripts/helpers.mjs:93 — helpers.buildAndCopyCoreJS has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 4, error handling 1 (2 pts), ternaries 2, loops 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (isCached, bundlePackage). 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 · defineProperty (cognitive 17) · ×1
  • defineProperty (cognitive 17) packages/core-js/modules/es.symbol.constructor.js:94 — defineProperty has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · exports (cognitive 17) · ×1
  • exports (cognitive 17) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js:14 — exports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 7 (nesting depth added 4). Of this number, 9 points are the body's own statements and 8 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 · define-built-in.default (cognitive 16) · ×1
  • define-built-in.default (cognitive 16) packages/core-js/internals/define-built-in.js:7 — define-built-in.default has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 1 (2 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · wrap-error-constructor-with-cause.default (cognitive 16) · ×1
  • wrap-error-constructor-with-cause.default (cognitive 16) packages/core-js/internals/wrap-error-constructor-with-cause.js:16 — wrap-error-constructor-with-cause.default has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · fix-regexp-well-known-symbol-logic.default (cognitive 16) · ×1
  • fix-regexp-well-known-symbol-logic.default (cognitive 16) packages/core-js/internals/fix-regexp-well-known-symbol-logic.js:14 — fix-regexp-well-known-symbol-logic.default has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7 (nesting depth added 4). 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, split the body into named stages: move each independent 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 · getConstructor (cognitive 16) · ×1
  • getConstructor (cognitive 16) packages/core-js/internals/collection-weak.js:60 — getConstructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 7 function items inside it that branch (get, delete, has, …). 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 · exports (cognitive 16) · ×1
  • exports (cognitive 16) packages/core-js/internals/array-buffer-is-detached.js:37 — exports has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 5, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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 · getSortCompare (cognitive 16) · ×1
  • getSortCompare (cognitive 16) packages/core-js/modules/es.typed-array.sort.js:51 — getSortCompare has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 4, boolean chains 2 (nesting depth added 4). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 52). 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: es.string.match.js, es.string.replace.js, es.string.search.js, es.string.split.js packages/core-js/modules/es.string.match.js — 4 files — `packages/core-js/modules/es.string.match.js`, `packages/core-js/modules/es.string.replace.js`, `packages/core-js/modules/es.string.search.js`, `packages/core-js/modules/es.string.split.js` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 2 typed · 4147 plain JS — the untyped files are packages/core-js-builder/config.js, packages/core-js-builder/index.js, packages/core-js-compat/compat.js, packages/core-js-compat/get-modules-list-for-target-version.js, packages/core-js-compat/helpers.js, packages/core-js-compat/index.js (+4141 more).
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (23 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (23 clone groups) packages/core-js/internals/async-iterator-map.js:26 — 23 duplicated blocks under packages/core-js/ have copies in at least two of the sibling directories actual, es, full, internals, modules — 10 of them are reported below, and 13 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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 (78 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (78 matched lines × 2 locations) packages/core-js/modules/es.async-disposable-stack.constructor.js:17 — packages/core-js/modules/es.async-disposable-stack.constructor.js:17 · packages/core-js/modules/es.disposable-stack.constructor.js:15 — the two spans are one implementation copied and then locally edited — 496 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 (37 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (37 matched lines × 2 locations) packages/core-js/modules/es.iterator.drop.js:14 — packages/core-js/modules/es.iterator.drop.js:14 · packages/core-js/modules/es.iterator.take.js:14 — the two spans are one implementation copied and then locally edited — 239 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 (22 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (22 matched lines × 2 locations) packages/core-js/modules/es.iterator.filter.js:14 — packages/core-js/modules/es.iterator.filter.js:14 · packages/core-js/modules/es.iterator.map.js:14 — the two spans are one implementation copied and then locally edited — 154 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 (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) packages/core-js/internals/async-iterator-map.js:26 — packages/core-js/internals/async-iterator-map.js:26 · packages/core-js/modules/esnext.async-iterator.filter.js:28 — 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 (20 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (20 matched lines × 2 locations) packages/core-js/modules/web.atob.js:28 — packages/core-js/modules/web.atob.js:28 · packages/core-js/modules/web.btoa.js:18 — the two spans are one implementation copied and then locally edited — 121 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 (19 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (19 matched lines × 2 locations) packages/core-js/internals/async-iterator-iteration.js:24 — packages/core-js/internals/async-iterator-iteration.js:24 · packages/core-js/modules/esnext.async-iterator.reduce.js:9 — the two spans are one implementation copied and then locally edited — 126 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 (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) packages/core-js/modules/es.promise.all-settled.js:12 — packages/core-js/modules/es.promise.all-settled.js:12 · packages/core-js/modules/es.promise.all.js:12 — 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 (18 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (18 matched lines × 2 locations) packages/core-js/internals/url-domain-to-ascii.js:61 — packages/core-js/internals/url-domain-to-ascii.js:61 · scripts/build-url-idna-data.mjs:165 — the two spans are one implementation copied and then locally edited — 97 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 (17 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (17 matched lines × 2 locations) packages/core-js/modules/es.number.to-exponential.js:59 — packages/core-js/modules/es.number.to-exponential.js:59 · packages/core-js/modules/es.number.to-precision.js:46 — the two spans are one implementation copied and then locally edited — 86 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 (16 lines × 4 locations) · ×1
  • Duplicated block (16 lines × 4 locations) packages/core-js/modules/es.iterator.every.js:16 — packages/core-js/modules/es.iterator.every.js:16 · packages/core-js/modules/es.iterator.find.js:16 · packages/core-js/modules/es.iterator.for-each.js:16 · packages/core-js/modules/es.iterator.some.js:16 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) packages/core-js/internals/string-cooked.js:7 — packages/core-js/internals/string-cooked.js:7 · packages/core-js/modules/es.string.raw.js:7 — the two spans are one implementation copied and then locally edited — 94 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 (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) packages/core-js/modules/esnext.async-iterator.drop.js:36 — packages/core-js/modules/esnext.async-iterator.drop.js:36 · packages/core-js/modules/esnext.async-iterator.take.js:35 — 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 (10 lines × 5 locations) · ×1
  • Duplicated block (10 lines × 5 locations) packages/core-js/internals/array-buffer-transfer.js:8 — packages/core-js/internals/array-buffer-transfer.js:8 · packages/core-js/internals/task.js:10 · packages/core-js/internals/typed-array-constructor.js:30 · packages/core-js/internals/uint8-from-base64.js:6 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (10 lines × 4 locations) · ×1
  • Duplicated block (10 lines × 4 locations) packages/core-js/stable/instance/entries.js:8 — packages/core-js/stable/instance/entries.js:8 · packages/core-js/stable/instance/for-each.js:8 · packages/core-js/stable/instance/keys.js:8 · packages/core-js/stable/instance/values.js:8 — the 4 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R2 · Cyclomatic Complexity · Complex function parse (cyclomatic 190, cognitive 347) · ×1
  • Complex function parse (cyclomatic 190, cognitive 347) packages/core-js/modules/web.url.constructor.js:401 — parse has cyclomatic complexity 190 and cognitive complexity 347; 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 structuredCloneInternal (cyclomatic 104, cognitive 88) · ×1
  • Complex function structuredCloneInternal (cyclomatic 104, cognitive 88) packages/core-js/modules/web.structured-clone.js:275 — structuredCloneInternal has cyclomatic complexity 104 and cognitive complexity 88; 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 (anonymous) (cyclomatic 66, cognitive 75) · ×1
  • Complex function (anonymous) (cyclomatic 66, cognitive 75) tests/unit-pure/web.structured-clone.js:30 — (anonymous) has cyclomatic complexity 66 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 65, cognitive 74) · ×1
  • Complex function (anonymous) (cyclomatic 65, cognitive 74) tests/unit-global/web.structured-clone.js:14 — (anonymous) has cyclomatic complexity 65 and cognitive complexity 74; 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 mapCodePoint (cyclomatic 48, cognitive 32) · ×1
  • Complex function mapCodePoint (cyclomatic 48, cognitive 32) packages/core-js/internals/url-domain-to-ascii.js:136 — mapCodePoint has cyclomatic complexity 48 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 43, cognitive 55) · ×1
  • Complex function exports (cyclomatic 43, cognitive 55) packages/core-js-pure/override/internals/export.js:60 — exports has cyclomatic complexity 43 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function prepareTransfer (cyclomatic 37, cognitive 50) · ×1
  • Complex function prepareTransfer (cyclomatic 37, cognitive 50) packages/core-js/modules/web.structured-clone.js:573 — prepareTransfer has cyclomatic complexity 37 and cognitive complexity 50; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 exports (cyclomatic 36, cognitive 51) · ×1
  • Complex function exports (cyclomatic 36, cognitive 51) packages/core-js/internals/iterator-define.js:28 — exports has cyclomatic complexity 36 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 36, cognitive 39) · ×1
  • Complex function (anonymous) (cyclomatic 36, cognitive 39) tests/unit-global/es.string.split.js:8 — (anonymous) has cyclomatic complexity 36 and cognitive complexity 39; 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 sumPrecise (cyclomatic 32, cognitive 38) · ×1
  • Complex function sumPrecise (cyclomatic 32, cognitive 38) packages/core-js/modules/es.math.sum-precise.js:100 — sumPrecise has cyclomatic complexity 32 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 31, cognitive 82) · ×1
  • Complex function exports (cyclomatic 31, cognitive 82) packages/core-js/internals/uint8-from-base64.js:72 — exports has cyclomatic complexity 31 and cognitive complexity 82; 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 parseIPv6 (cyclomatic 31, cognitive 74) · ×1
  • Complex function parseIPv6 (cyclomatic 31, cognitive 74) packages/core-js/modules/web.url.constructor.js:160 — parseIPv6 has cyclomatic complexity 31 and cognitive complexity 74; 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 RegExp (cyclomatic 29, cognitive 31) · ×1
  • Complex function RegExp (cyclomatic 29, cognitive 31) packages/core-js/modules/es.regexp.constructor.js:139 — RegExp has cyclomatic complexity 29 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 exec (cyclomatic 28, cognitive 29) · ×1
  • Complex function exec (cyclomatic 28, cognitive 29) packages/core-js/internals/regexp-exec.js:47 — exec has cyclomatic complexity 28 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function decode (cyclomatic 27, cognitive 80) · ×1
  • Complex function decode (cyclomatic 27, cognitive 80) packages/core-js/internals/url-percent-coding.js:30 — decode has cyclomatic complexity 27 and cognitive complexity 80; 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 exports (cyclomatic 26, cognitive 41) · ×1
  • Complex function exports (cyclomatic 26, cognitive 41) packages/core-js/internals/url-domain-to-ascii.js:311 — exports has cyclomatic complexity 26 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 26, cognitive 31) · ×1
  • Complex function exports (cyclomatic 26, cognitive 31) packages/core-js/internals/string-parse.js:43 — exports has cyclomatic complexity 26 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 26, cognitive 15) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 15) REDACTED:16 — (anonymous) has cyclomatic complexity 26 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 decode (cyclomatic 25, cognitive 45) · ×1
  • Complex function decode (cyclomatic 25, cognitive 45) packages/core-js/internals/string-punycode.js:235 — decode has cyclomatic complexity 25 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 isIgnored (cyclomatic 24, cognitive 18) · ×1
  • Complex function isIgnored (cyclomatic 24, cognitive 18) packages/core-js/internals/url-domain-to-ascii.js:108 — isIgnored has cyclomatic complexity 24 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function cloneView (cyclomatic 23, cognitive 35) · ×1
  • Complex function cloneView (cyclomatic 23, cognitive 35) packages/core-js/modules/web.structured-clone.js:215 — cloneView has cyclomatic complexity 23 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 exports (cyclomatic 22, cognitive 24) · ×1
  • Complex function exports (cyclomatic 22, cognitive 24) packages/core-js/internals/make-built-in.js:26 — exports has cyclomatic complexity 22 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 NumericRangeIterator (cyclomatic 22, cognitive 21) · ×1
  • Complex function NumericRangeIterator (cyclomatic 22, cognitive 21) packages/core-js/internals/numeric-range-iterator.js:20 — NumericRangeIterator has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 21, cognitive 36) · ×1
  • Complex function (anonymous) (cyclomatic 21, cognitive 36) packages/core-js/modules/es.string.split.js:66 — (anonymous) has cyclomatic complexity 21 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function toExponential (cyclomatic 21, cognitive 26) · ×1
  • Complex function toExponential (cyclomatic 21, cognitive 26) packages/core-js/modules/es.number.to-exponential.js:68 — toExponential has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function zip (cyclomatic 20, cognitive 54) · ×1
  • Complex function zip (cyclomatic 20, cognitive 54) packages/core-js/modules/es.iterator.zip.js:22 — zip has cyclomatic complexity 20 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 20, cognitive 32) · ×1
  • Complex function exports (cyclomatic 20, cognitive 32) packages/core-js-compat/targets-parser.js:56 — exports has cyclomatic complexity 20 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 20, cognitive 31) · ×1
  • Complex function exports (cyclomatic 20, cognitive 31) packages/core-js/internals/iterate.js:22 — exports has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 20, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 20, cognitive 21) packages/core-js/internals/array-buffer-transfer.js:33 — (anonymous) has cyclomatic complexity 20 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 exports (cyclomatic 19, cognitive 37) · ×1
  • Complex function exports (cyclomatic 19, cognitive 37) packages/core-js/internals/export.js:30 — exports has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseIPv4 (cyclomatic 19, cognitive 37) · ×1
  • Complex function parseIPv4 (cyclomatic 19, cognitive 37) packages/core-js/modules/web.url.constructor.js:120 — parseIPv4 has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function dedentStringsArray (cyclomatic 19, cognitive 30) · ×1
  • Complex function dedentStringsArray (cyclomatic 19, cognitive 30) packages/core-js/modules/esnext.string.dedent.js:56 — dedentStringsArray has cyclomatic complexity 19 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/core-js-compat/src/data.mjs · ×1
  • packages/core-js-compat/src/data.mjs: 3472 lines of code packages/core-js-compat/src/data.mjs:1 — packages/core-js-compat/src/data.mjs has 3472 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-js/modules/web.url.constructor.js · ×1
  • packages/core-js/modules/web.url.constructor.js: 1078 lines of code packages/core-js/modules/web.url.constructor.js:1 — packages/core-js/modules/web.url.constructor.js has 1078 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-js/modules/web.structured-clone.js · ×1
  • packages/core-js/modules/web.structured-clone.js: 682 lines of code packages/core-js/modules/web.structured-clone.js:1 — packages/core-js/modules/web.structured-clone.js has 682 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-js/modules/web.url-search-params.constructor.js · ×1
  • packages/core-js/modules/web.url-search-params.constructor.js: 463 lines of code packages/core-js/modules/web.url-search-params.constructor.js:1 — packages/core-js/modules/web.url-search-params.constructor.js has 463 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-js-compat/src/mapping.mjs · ×1
  • packages/core-js-compat/src/mapping.mjs: 427 lines of code packages/core-js-compat/src/mapping.mjs:1 — packages/core-js-compat/src/mapping.mjs has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
R8 · Dependency Hygiene · Unused dependency 'actions-up' · ×1
  • Unused dependency 'actions-up' — Declared in scripts/check-actions/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 'updates' · ×1
  • Unused dependency 'updates' — Declared in scripts/check-dependencies/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 'moon-unit' · ×1
  • Unused dependency 'moon-unit' — Declared in tests/observables/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 'promises-aplus-tests' · ×1
  • Unused dependency 'promises-aplus-tests' — Declared in tests/promises/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 'promises-es6-tests' · ×1
  • Unused dependency 'promises-es6-tests' — Declared in tests/promises/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 'publint' · ×1
  • Unused dependency 'publint' — Declared in tests/publint/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 'test262-harness' · ×1
  • Unused dependency 'test262-harness' — Declared in tests/test262/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 'phantomjs-prebuilt' · ×1
  • Unused dependency 'phantomjs-prebuilt' — Declared in tests/unit-karma/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 — 57 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×19
  • Duplicated predicate packages/core-js/modules/es.array.reduce-right.js:10 — `!IS_NODE && CHROME_VERSION > 79 && CHROME_VERSION < 83` appears character-identically in 2 files — packages/core-js/modules/es.array.reduce-right.js, packages/core-js/modules/es.array.reduce.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-js/modules/es.string.ends-with.js:17 — `!IS_PURE && !CORRECT_IS_REGEXP_LOGIC && !!` appears character-identically in 2 files — packages/core-js/modules/es.string.ends-with.js, packages/core-js/modules/es.string.starts-with.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-js/modules/es.promise.catch.js:21 — `!IS_PURE && isCallable(NativePromiseConstructor)` appears character-identically in 2 files — packages/core-js/modules/es.promise.catch.js, packages/core-js/modules/es.promise.finally.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-js/modules/es.string.ends-with.js:24 — `!MDN_POLYFILL_BUG && !CORRECT_IS_REGEXP_LOGIC` appears character-identically in 2 files — packages/core-js/modules/es.string.ends-with.js, packages/core-js/modules/es.string.starts-with.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-js/internals/object-is-extensible.js:15 — `ARRAY_BUFFER_NON_EXTENSIBLE && classof(it) === 'ArrayBuffer'` appears character-identically in 3 files — packages/core-js/internals/object-is-extensible.js, packages/core-js/modules/es.object.is-frozen.js, packages/core-js/modules/es.object.is-sealed.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-js-pure/override/internals/collection.js:27 — `NativeConstructor && NativeConstructor.prototype` appears character-identically in 3 files — packages/core-js-pure/override/internals/collection.js, packages/core-js-pure/override/internals/get-built-in-prototype-method.js, packages/core-js/internals/collection.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-js/internals/promise-constructor-detection.js:12 — `NativePromiseConstructor && NativePromiseConstructor.prototype` appears character-identically in 4 files — packages/core-js/internals/promise-constructor-detection.js, packages/core-js/modules/es.promise.catch.js, packages/core-js/modules/es.promise.constructor.js, packages/core-js/modules/es.promise.finally.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-js/modules/web.dom-collections.for-each.js:19 — `globalThis[COLLECTION_NAME] && globalThis[COLLECTION_NAME].prototype` appears character-identically in 2 files — packages/core-js/modules/web.dom-collections.for-each.js, packages/core-js/modules/web.dom-collections.iterator.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-js-pure/override/internals/export.js:66 — `globalThis[TARGET] && globalThis[TARGET].prototype` appears character-identically in 2 files — packages/core-js-pure/override/internals/export.js, packages/core-js/internals/export.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-js/es/instance/at.js:11 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.at)` appears character-identically in 2 files — packages/core-js/es/instance/at.js, packages/core-js/full/instance/at.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-js/actual/instance/find-last.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.findLast)` appears character-identically in 2 files — packages/core-js/actual/instance/find-last.js, packages/core-js/es/instance/find-last.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-js/actual/instance/find-last-index.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.findLastIndex)` appears character-identically in 2 files — packages/core-js/actual/instance/find-last-index.js, packages/core-js/es/instance/find-last-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 packages/core-js/actual/instance/to-reversed.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.toReversed)` appears character-identically in 2 files — packages/core-js/actual/instance/to-reversed.js, packages/core-js/es/instance/to-reversed.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-js/actual/instance/to-sorted.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.toSorted)` appears character-identically in 2 files — packages/core-js/actual/instance/to-sorted.js, packages/core-js/es/instance/to-sorted.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-js/actual/instance/to-spliced.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype.toSpliced)` appears character-identically in 2 files — packages/core-js/actual/instance/to-spliced.js, packages/core-js/es/instance/to-spliced.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-js/actual/instance/with.js:9 — `it === ArrayPrototype || (isPrototypeOf(ArrayPrototype, it) && own === ArrayPrototype['with'])` appears character-identically in 2 files — packages/core-js/actual/instance/with.js, packages/core-js/es/instance/with.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-js/modules/web.url.can-parse.js:29 — `length < 2 || arguments[1] === undefined` appears character-identically in 2 files — packages/core-js/modules/web.url.can-parse.js, packages/core-js/modules/web.url.parse.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-js/modules/es.iterator.drop.js:55 — `remaining > 0x1FFFFFFFFFFFFF && remaining !== $Infinity` appears character-identically in 2 files — packages/core-js/modules/es.iterator.drop.js, packages/core-js/modules/es.iterator.take.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-js/es/instance/at.js:12 — `typeof it == 'string' || it === StringPrototype || (isPrototypeOf(StringPrototype, it) && own === StringPrototype.at)` appears character-identically in 2 files — packages/core-js/es/instance/at.js, packages/core-js/full/instance/at.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.
D12 · Dependency Hygiene · Deprecated · ×13
  • Deprecated: copy-concurrently REDACTED:2120 — copy-concurrently 1.0.5 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: figgy-pudding REDACTED:2760 — figgy-pudding 3.5.2 is resolved in REDACTED and is marked deprecated by its publisher: "This module is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: fs-write-stream-atomic REDACTED:2892 — fs-write-stream-atomic 1.0.10 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:2990 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:3213 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: move-concurrently REDACTED:3763 — move-concurrently 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: path-dirname REDACTED:4122 — path-dirname 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: resolve-url REDACTED:4539 — resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: rimraf REDACTED:4555 — rimraf 2.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: source-map-resolve REDACTED:5002 — source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: source-map-url REDACTED:5035 — source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: urix REDACTED:5535 — urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: fsevents REDACTED:5672 — fsevents 1.2.13 is resolved in REDACTED and is marked deprecated by its publisher: "Upgrade to fsevents v2 to mitigate potential security issues". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D24 · Comment Value · redundant comment · ×11
  • redundant comment packages/core-js/internals/iterator-define.js:65 — "Set @@toStringTag to native iterators" repeats the code it sits on: 4 of its 5 words (set, string, tag, iterators) are already in `setToStringTag(CurrentIteratorPrototype, TO_STRING_TAG, true, true);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.dom-exception.constructor.js:82 — "`DOMException.prototype.code` getter" repeats the code it sits on: 5 of its 5 words (dom, exception, prototype, code, getter) are already in `defineBuiltInAccessor(DOMExceptionPrototype, 'code', getterFor('code'));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.dom-exception.constructor.js:84 — "`DOMException.prototype.message` getter" repeats the code it sits on: 5 of its 5 words (dom, exception, prototype, message, getter) are already in `defineBuiltInAccessor(DOMExceptionPrototype, 'message', getterFor('message'));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.dom-exception.constructor.js:86 — "`DOMException.prototype.name` getter" repeats the code it sits on: 5 of its 5 words (dom, exception, prototype, name, getter) are already in `defineBuiltInAccessor(DOMExceptionPrototype, 'name', getterFor('name'));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.dom-exception.constructor.js:134 — "`DOMException` constants" repeats the code it sits on: 3 of its 3 words (dom, exception, constants) are already in `for (var key in DOMExceptionConstants) if (hasOwn(DOMExceptionConstants, key))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.url-search-params.constructor.js:459 — "`URLSearchParams.prototype[@@iterator]` method" repeats the code it sits on: 5 of its 6 words (url, search, params, prototype, iterator) are already in `defineBuiltIn(URLSearchParamsPrototype, ITERATOR, URLSearchParamsPrototype.entries, { name: 'entries' });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/core-js/modules/web.url-search-params.constructor.js:487 — "the state of `searchParams` of the `URL` polyfill" repeats the code it sits on: 4 of its 5 words (state, search, params, url) are already in `module.exports = URLSearchParamsState;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/unit-global/es.regexp.escape.js:93 — "Escaping initial digits" repeats the code it sits on: 3 of its 3 words (escaping, initial, digits) are already in `assert.same(escape('1111'), '\\x31111', 'Initial decimal digit 1 is escaped');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/unit-global/es.regexp.escape.js:105 — "Escaping initial ASCII letters" repeats the code it sits on: 4 of its 4 words (escaping, initial, ascii, letters) are already in `assert.same(escape('aaa'), '\\x61aa', 'Initial ASCII letter a is escaped');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/unit-pure/es.regexp.escape.js:92 — "Escaping initial digits" repeats the code it sits on: 3 of its 3 words (escaping, initial, digits) are already in `assert.same(escape('1111'), '\\x31111', 'Initial decimal digit 1 is escaped');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment tests/unit-pure/es.regexp.escape.js:104 — "Escaping initial ASCII letters" repeats the code it sits on: 4 of its 4 words (escaping, initial, ascii, letters) are already in `assert.same(escape('aaa'), '\\x61aa', 'Initial ASCII letter a is escaped');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X7 · Silent fallback defaults · Silent fallback default in catch · ×5
  • Silent fallback default in catch packages/core-js/internals/try-to-string.js:7 — `default` swallows every exception into `return 'Object'` — 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-js/internals/set-method-accept-set-like.js:55 — `default` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/core-js/modules/es.reflect.set.js:32 — `$set` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch tests/compat/tests.js:348 — `createSetMethodTest.<returned closure>` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch tests/unit-node/quiet-reporter.js:14 — `printable` swallows every exception into `return '<uninspectable>'` — 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.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Outdated (npm) · ×1
  • Outdated (npm): mkdirp packages/core-js-builder/package.json:31 — mkdirp is pinned at 0.5.6; registry.npmjs.org publishes 3.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 10 project(s) overshoot their size bounds, lowering Project Cohesion to 8.0/10. The most over is `packages/core-js` (33076 LoC, 451 module-visible types across 12 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:4 — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 5 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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation package.json:71 — `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Minor — 8 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×6
  • Outdated (npm): @babel/standalone — @babel/standalone is pinned at 8.1.1; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @vitejs/plugin-legacy — @vitejs/plugin-legacy is pinned at 8.2.3; registry.npmjs.org publishes 8.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): marked — marked is pinned at 18.1.3; registry.npmjs.org publishes 18.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): sass — sass is pinned at 1.107.1; registry.npmjs.org publishes 1.108.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): vite — vite is pinned at 8.3.5; registry.npmjs.org publishes 8.3.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): webpack — webpack is pinned at 4.47.0; registry.npmjs.org publishes 5.112.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
D10 · Test Quality · Skipped (documented) · ×2
  • Skipped (documented): (unnamed test) tests/compat/browsers-runner.js:52 — 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) tests/compat/common-runner.js:11 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41706a224fd140749611729895da967d/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-41706a224fd140749611729895da967d/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .70artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .6artifacts/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 1 file(s) — `website/build.mjs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dd50-d6ee-7cb7-bc82-536e3831357f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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