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

facebook/stylex

Measured 30 October 2026, 03:13 UTC, at code version 0f958bb

No regression since the last survey Supply-chain provenance & signing: not measured

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

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 58out of 100 At risk Down 2 since the last survey

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

Architecture 97 Exemplary Accessibility 78 Strong Security and Compliance 74 Adequate Performance 73 Strong Code Health 62 Adequate Maturity 62 Adequate Production Readiness 48 Adequate

A medium codebase: 63,563 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Production Readiness, 48

Findings by how serious they are

73 critical 553 serious 158 minor

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

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
30 October 2026, 03:13 UTC

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

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

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

78of 78 dimensions measured by tools.
726of 784 findings point to an exact file and line, so you can open each one in the code. The other 58 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 63,563 lines of product code in 16 projects.
Chapters

Executive summary

facebook/stylex is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because it has uses of packages that aren't listed. It scores 58 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Production Readiness, at 48, is the weakest lens and counts most in the score. The best first step is replacing the 13 deprecated dependencies, worth about 8 points. Tidying the declared packages would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 62 would lift the score to about 64.

Forty-five known security holes in the packages the code depends on can be used by attackers. Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two automatic updates take new releases before a bad one can be spotted. Updating the vulnerable packages, pinning each tool to an exact version and setting a waiting period for automatic updates would close these risks. The password or key in the code's history needs replacing, with the old one switched off. The place where the code runs text as code or as a command needs a direct call instead. The six uses of packages that aren't listed need adding to the project's list of dependencies.

The product code is 63,563 lines, about €120,000 to rebuild.

Code Health 62 Adequate, capped by Cyclomatic Complexity and Cognitive Complexity Architecture 97 ★ Exemplary Maturity 62 Adequate, capped by Architecture documentation Production Readiness 48 Adequate, capped by Dependency Hygiene and Security & performance tooling Security and Compliance 74 Adequate, capped by Static Analysis (SAST) and Dependency Vulnerabilities Accessibility 78 Strong Performance 73 Strong

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

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

If Production Readiness rose from 48 to 62, the lowest score rated Strong, the score would rise from 58 to about 64.

Code composition: what the lines of code are
Product code 53%Tests 47%
New since the last survey: 92 findings

These 92 critical or serious findings weren't in the previous survey, on 16 October 2026.

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

Fixed since the last survey: 114 findings

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

  • Dependency Vulnerabilities · Critical CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Critical vulnerability: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js
  • Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) packages/scripts/flow-translator/generate-types.js
  • Code Duplication · Duplicated block (17 lines × 2 locations) packages/style-value-parser/src/css-types/calc.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/utils/Rule.js
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/utils/split-css-value.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/@stylexjs/babel-plugin/src/utils/dev-classname.js
  • Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js
  • Code Duplication · Duplicated block (16 lines × 2 locations) packages/style-value-parser/src/at-queries/media-query.js
  • Code Duplication · Duplicated block (15 lines × 3 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js
  • Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/@stylexjs/devtools-extension/src/panel/declarations/documentPrinter.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js
  • Code Duplication · Duplicated block (15 lines × 2 locations) packages/style-value-parser/src/css-types/easing-function.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/stylex-keyframes.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/leading-zero.js
  • Code Duplication · Duplicated block (14 lines × 3 locations) packages/@stylexjs/babel-plugin/src/utils/validate.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/style-value-parser/src/css-types/basic-shape.js
  • Code Duplication · Duplicated block (14 lines × 2 locations) packages/style-value-parser/src/css-types/color.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/basic-validation.js
  • Code Duplication · Duplicated block (13 lines × 3 locations) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js
  • Code Duplication · Duplicated block (13 lines × 3 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js
  • Code Duplication · Duplicated block (13 lines × 3 locations) packages/@stylexjs/unplugin/src/esbuild.js
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/style-value-parser/src/css-types/color.js
  • Code Duplication · Duplicated block (13 lines × 4 locations) packages/style-value-parser/src/css-types/filter-function.js
  • Code Duplication · Duplicated block (13 lines × 4 locations) REDACTED
  • Code Duplication · Duplicated block (13 lines × 2 locations) packages/style-value-parser/src/token-parser.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/@stylexjs/cli/rollup.config.mjs
  • Code Duplication · Duplicated block (12 lines × 5 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js
  • Code Duplication · Duplicated block (12 lines × 3 locations) packages/style-value-parser/src/css-types/color.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/style-value-parser/src/css-types/custom-ident.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/style-value-parser/src/css-types/length.js
  • Code Duplication · Duplicated block (12 lines × 2 locations) packages/style-value-parser/src/token-parser.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/@stylexjs/atoms/src/babel-transform.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/detect-unclosed-fns.js
  • Code Duplication · Duplicated block (11 lines × 3 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (11 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (10 lines × 4 locations) packages/@stylexjs/stylex/src/stylex.js
  • Code Duplication · Duplicated block (10 lines × 3 locations) packages/@stylexjs/unplugin/src/esbuild.js
  • Code Duplication · Duplicated block (10 lines × 4 locations) packages/style-value-parser/src/css-types/basic-shape.js
  • Code Duplication · Duplicated block (10 lines × 2 locations) packages/style-value-parser/src/css-types/common-types.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/@stylexjs/atoms/src/babel-transform.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/@stylexjs/atoms/src/babel-transform.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/@stylexjs/create-stylex-app/src/index.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/@stylexjs/devtools-extension/src/inspected/declarationAnalysis.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/@stylexjs/unplugin/babel-plugins/add-mjs-extension.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/style-value-parser/src/css-types/basic-shape.js
  • Code Duplication · Duplicated block (9 lines × 2 locations) packages/style-value-parser/src/css-types/easing-function.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/stylex-nested-utils.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js
  • Code Duplication · Duplicated block (8 lines × 4 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/@stylexjs/devtools-extension/src/inspected/collector.js
  • Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) packages/@stylexjs/devtools-extension/src/panel/components/OverridesSection.js
  • Code Duplication · Duplicated block (8 lines × 2 locations) packages/@stylexjs/rollup-plugin/src/index.js
  • Code Duplication · Duplicated block (8 lines × 5 locations) packages/style-value-parser/src/css-types/basic-shape.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js
  • Code Duplication · Duplicated block (7 lines × 2 locations) REDACTED
  • Code Duplication · Duplicated block (6 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js
  • Code Duplication · Duplicated block (6 lines × 4 locations) packages/@stylexjs/unplugin/src/esbuild.js
Rebuild cost: about €120,000 · Estimate
Cost to rebuild€41,000 to €210,000, for 692 to 2,194 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 58. 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: 63,563 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13).
Raises the score by about 8 points · Medium effort · Dependency Hygiene
2
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
Raises the score by about 7 points · Medium effort · Dependency Hygiene
3
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Raises the score by about 4 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.2 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 14% to 33% on every change. The history of the code shows how much it changes: about 15,102 lines over the last 90 days, which is about 61,247 lines a year. At that pace, the extra work comes to an estimated 22.2 to 133 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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 €120,000 to build again, about 0.9 person-years of work. Its weakest lens is Production Readiness, at 48 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 13 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort, because it clears the 13 Dependency Hygiene 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 @stylexjs/atoms atoms @stylexjs/stylex stylex @stylexjs/atoms->@stylexjs/stylex @stylexjs/babel-plugin babel-plugin @stylexjs/shared shared @stylexjs/babel-plugin->@stylexjs/shared @stylexjs/babel-plugin->@stylexjs/stylex @stylexjs/cli cli @stylexjs/cli->@stylexjs/babel-plugin @stylexjs/devtools-extension devtools-extension @stylexjs/devtools-extension->@stylexjs/stylex @stylexjs/eslint-plugin eslint-plugin @stylexjs/eslint-plugin->@stylexjs/shared @stylexjs/postcss-plugin postcss-plugin @stylexjs/postcss-plugin->@stylexjs/babel-plugin @stylexjs/rollup-plugin rollup-plugin @stylexjs/rollup-plugin->@stylexjs/babel-plugin @stylexjs/shared-ui shared-ui @stylexjs/shared-ui->@stylexjs/stylex @stylexjs/unplugin unplugin @stylexjs/unplugin->@stylexjs/babel-plugin create-stylex-app create-stylex-app docs-new docs-new docs-new->@stylexjs/babel-plugin docs-new->@stylexjs/stylex scripts scripts style-value-parser style-value-parser

Architecture: which parts of the code depend on which

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

164 modules, with 111 dependencies between them. One loop runs through 4 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 flow-typed.environments.cssom2 flow-typed.npm.@babel.types3 flow-typed.npm.@csstools.css-tokenizer_v3_x_x4 flow-typed.npm.js-yaml_v4_x_x5 flow-typed.npm.postcss-value-parser_vx_x_x6 packages.@stylexjs.babel-plugin.src.shared7 packages.@stylexjs.babel-plugin.src.shared.common-types8 packages.@stylexjs.babel-plugin.src.shared.types9 packages.@stylexjs.babel-plugin.src.utils.state-manager10 packages.@stylexjs.devtools-extension.src.types11 packages.@stylexjs.eslint-plugin.src.reference.cssProperties12 packages.docs.src.components.layout13 packages.style-value-parser.src.token-parser14 flow-typed.environments.html15 packages.@stylexjs.babel-plugin.src.shared.utils16 packages.@stylexjs.babel-plugin.src.shared.when17 packages.@stylexjs.babel-plugin.src.visitors.stylex-props18 packages.@stylexjs.devtools-extension.src.devtools19 packages.@stylexjs.devtools-extension.src.panel.declarations20 packages.style-value-parser.src.css-types.color21 packages.style-value-parser.src.css-types.transform-function22 packages.style-value-parser.src.properties.border-radius23 flow-typed.environments.dom24 packages.docs.src.components.mdx.CodeBlock25 flow-typed.environments.node26 flow-typed.npm.@babel.traverse27 packages.@stylexjs.devtools-extension.src.inspected28 packages.@stylexjs.eslint-plugin.src29 packages.@stylexjs.eslint-plugin.src.reference30 packages.@stylexjs.eslint-plugin.src.rules31 packages.@stylexjs.eslint-plugin.src.utils32 packages.@stylexjs.stylex.src.stylesheet33 packages.docs.src.components.mdx34 flow-typed.environments.bom35 flow-typed.npm.@babel.core36 packages.@stylexjs.babel-plugin.src.utils37 packages.@stylexjs.babel-plugin.src.visitors38 flow-typed.npm.@babel.generator39 packages.@stylexjs.babel-plugin40 packages.@stylexjs.rollup-plugin
1 flow-typed.environments.cssom
2 flow-typed.npm.@babel.types
3 flow-typed.npm.@csstools.css-tokenizer_v3_x_x
4 flow-typed.npm.js-yaml_v4_x_x
5 flow-typed.npm.postcss-value-parser_vx_x_x
6 packages.@stylexjs.babel-plugin.src.shared
7 packages.@stylexjs.babel-plugin.src.shared.common-types
8 packages.@stylexjs.babel-plugin.src.shared.types
9 packages.@stylexjs.babel-plugin.src.utils.state-manager
10 packages.@stylexjs.devtools-extension.src.types
11 packages.@stylexjs.eslint-plugin.src.reference.cssProperties
12 packages.docs.src.components.layout
13 packages.style-value-parser.src.token-parser
14 flow-typed.environments.html1432
15 packages.@stylexjs.babel-plugin.src.shared.utils151
16 packages.@stylexjs.babel-plugin.src.shared.when1
17 packages.@stylexjs.babel-plugin.src.visitors.stylex-props1
18 packages.@stylexjs.devtools-extension.src.devtools3
19 packages.@stylexjs.devtools-extension.src.panel.declarations1
20 packages.style-value-parser.src.css-types.color1
21 packages.style-value-parser.src.css-types.transform-function151
22 packages.style-value-parser.src.properties.border-radius22
23 flow-typed.environments.dom81
24 packages.docs.src.components.mdx.CodeBlock1
25 flow-typed.environments.node1321
26 flow-typed.npm.@babel.traverse43
27 packages.@stylexjs.devtools-extension.src.inspected735
28 packages.@stylexjs.eslint-plugin.src39
29 packages.@stylexjs.eslint-plugin.src.reference111
30 packages.@stylexjs.eslint-plugin.src.rules176
31 packages.@stylexjs.eslint-plugin.src.utils1112
32 packages.@stylexjs.stylex.src.stylesheet211
33 packages.docs.src.components.mdx2
34 flow-typed.environments.bom4412
35 flow-typed.npm.@babel.core113
36 packages.@stylexjs.babel-plugin.src.utils51234
37 packages.@stylexjs.babel-plugin.src.visitors2417117
38 flow-typed.npm.@babel.generator11
39 packages.@stylexjs.babel-plugin11111
40 packages.@stylexjs.rollup-plugin11
Uses a module listed above itPart of a loopThe module itself
1 flow-typed.environments.cssom2 flow-typed.npm.@babel.types3 flow-typed.npm.@csstools.css-tokenizer_v3_x_x4 flow-typed.npm.js-yaml_v4_x_x5 flow-typed.npm.postcss-value-parser_vx_x_x6 packages.@stylexjs.babel-plugin.src.shared7 packages.@stylexjs.babel-plugin.src.shared.common-types8 packages.@stylexjs.babel-plugin.src.shared.types9 packages.@stylexjs.babel-plugin.src.utils.state-manager10 packages.@stylexjs.devtools-extension.src.types11 packages.@stylexjs.eslint-plugin.src.reference.cssProperties12 packages.docs.src.components.layout13 packages.style-value-parser.src.token-parser14 flow-typed.environments.html15 packages.@stylexjs.babel-plugin.src.shared.utils16 packages.@stylexjs.babel-plugin.src.shared.when17 packages.@stylexjs.babel-plugin.src.visitors.stylex-props18 packages.@stylexjs.devtools-extension.src.devtools19 packages.@stylexjs.devtools-extension.src.panel.declarations20 packages.style-value-parser.src.css-types.color21 packages.style-value-parser.src.css-types.transform-function22 packages.style-value-parser.src.properties.border-radius23 flow-typed.environments.dom24 packages.docs.src.components.mdx.CodeBlock25 flow-typed.environments.node26 flow-typed.npm.@babel.traverse27 packages.@stylexjs.devtools-extension.src.inspected28 packages.@stylexjs.eslint-plugin.src29 packages.@stylexjs.eslint-plugin.src.reference30 packages.@stylexjs.eslint-plugin.src.rules31 packages.@stylexjs.eslint-plugin.src.utils32 packages.@stylexjs.stylex.src.stylesheet33 packages.docs.src.components.mdx34 flow-typed.environments.bom35 flow-typed.npm.@babel.core36 packages.@stylexjs.babel-plugin.src.utils37 packages.@stylexjs.babel-plugin.src.visitors38 flow-typed.npm.@babel.generator39 packages.@stylexjs.babel-plugin40 packages.@stylexjs.rollup-pluginflow-typed.environments.cssom1flow-typed.npm.@babel.types2flow-typed.npm.@csstools.css-tokenizer_v3_x_x3flow-typed.npm.js-yaml_v4_x_x4flow-typed.npm.postcss-value-parser_vx_x_x5packages.@stylexjs.babel-plugin.src.shared6packages.@stylexjs.babel-plugin.src.shared.common-types7packages.@stylexjs.babel-plugin.src.shared.types8packages.@stylexjs.babel-plugin.src.utils.state-manager9packages.@stylexjs.devtools-extension.src.types10packages.@stylexjs.eslint-plugin.src.reference.cssProperties11packages.docs.src.components.layout12packages.style-value-parser.src.token-parser13flow-typed.environments.html14packages.@stylexjs.babel-plugin.src.shared.utils15packages.@stylexjs.babel-plugin.src.shared.when16packages.@stylexjs.babel-plugin.src.visitors.stylex-props17packages.@stylexjs.devtools-extension.src.devtools18packages.@stylexjs.devtools-extension.src.panel.declarations19packages.style-value-parser.src.css-types.color20packages.style-value-parser.src.css-types.transform-function21packages.style-value-parser.src.properties.border-radius22flow-typed.environments.dom23packages.docs.src.components.mdx.CodeBlock24flow-typed.environments.node25flow-typed.npm.@babel.traverse26packages.@stylexjs.devtools-extension.src.inspected27packages.@stylexjs.eslint-plugin.src28packages.@stylexjs.eslint-plugin.src.reference29packages.@stylexjs.eslint-plugin.src.rules30packages.@stylexjs.eslint-plugin.src.utils31packages.@stylexjs.stylex.src.stylesheet32packages.docs.src.components.mdx33flow-typed.environments.bom34flow-typed.npm.@babel.core35packages.@stylexjs.babel-plugin.src.utils36packages.@stylexjs.babel-plugin.src.visitors37flow-typed.npm.@babel.generator38packages.@stylexjs.babel-plugin39packages.@stylexjs.rollup-plugin401432151113111512281113214373539111176111221124412113512342417117111111111+124 more modules (most-connected shown)

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

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

At a glance — Architecture · 97% · Exemplary ·

The Good
D5 · JavaScript Coupling 10.0 D23 · JavaScript Boundary Type-Coupling 10.0 D26 · JavaScript Project Cohesion 8.8 D35 · JavaScript Change Coupling 10.0 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R11 · React / TS Import Boundaries 9.2 R9 · React / TS Circular Imports 10.0

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

The Good
D15 · JavaScript Churn × Complexity Hotspots 9.4 D16 · JavaScript Bus Factor 9.6 D19 · JavaScript Documentation Quality 10.0 D34 · JavaScript Knowledge Freshness 8.7 M1 · Repo Documentation (README) 9.0 M3 · Repo Folder & project structure 8.0
The Ugly
M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 48% · Adequate · gated by R8, P3 ·

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

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

The Good
D28 · JavaScript Secrets (history) 9.0 D31 · JavaScript IaC & Container Security 10.0 D43 · JavaScript Malicious Dependencies 10.0 D44 · JavaScript Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.5 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D29 · JavaScript Static Analysis (SAST) 0.2 D30 · JavaScript Dependency Vulnerabilities 0.0

At a glance — Accessibility · 78% · Strong ·

The Good
AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 10.0 AC4 · Repo Keyboard semantics 10.0 AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0
The Bad
AC3 · Repo Page structure 5.4 AC7 · Repo A11y enforcement 6.0

At a glance — Performance · 73% · Strong ·

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

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection87High / Critical
A03:2025 — Software Supply Chain Failures71High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

Begin by cleaning up dependencies to resolve deprecated items, remove unused packages, and properly categorize type and test-only modules. Next, integrate a static analysis security step into the CI pipeline to prevent security regressions from reaching production. Finally, extend structured logging across all runnable modules for better observability and document key architectural decisions in a dedicated folder to preserve institutional knowledge.

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

Do thisHelpsEffortDimension
Resolve the 13 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (13).+8.1 ptsMediumDependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+6.9 ptsMediumDependency Hygiene
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+4.2 ptsMediumSecurity & performance tooling
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.+2.4 ptsMediumObservability
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.0 ptsMediumArchitecture documentation
Swallowed exception (empty catch)+1.1 ptsMediumException handling
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with _evaluate (cyclomatic 206), evaluate-path._evaluate (cyclomatic 190).+0.5 ptsMediumCyclomatic Complexity
Bring the 23 bodies over 60 down to 60 or less in Cognitive Complexity — start with _evaluate (cognitive 343), evaluate-path._evaluate (cognitive 325), create.checkStyleProperty (cognitive 215).+0.9 ptsHighCognitive Complexity

File quality

Per-file score 0–10 — a quality signature. Of 109 files carrying findings, judged against the Preview bar: 3% slop · 12% mixed · 85% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js5.9MixedCyclomatic Complexity: transformStyleXCreateTheme (cyclomatic 24)
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js7.0Near-cleanCyclomatic Complexity: stylex-enforce-extension.reportErrors (cyclomatic 30)
packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js7.0Near-cleanCyclomatic Complexity: stylex-props.transformStylexProps (cyclomatic 34)
packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js7.0Near-cleanCyclomatic Complexity: _evaluate (cyclomatic 206)
packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js7.0Near-cleanCyclomatic Complexity: create.checkStyleProperty (cyclomatic 55)

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

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

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

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

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

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

What we checked — 78 dimensions across the health lenses
D1D2D3D5D9D10D12D13D14D15D16D17D19D23D26D28D29D30D31D34D35D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX6AX8GD1IC1M1M2M3P1P10P2P3P4P6PF1PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X5

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, 726 of 784 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a18acc-cb1c-7d10-881e-6b7f8296e536.

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.

  • D6 Cohesion (LCOM4) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 140 of 146 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in examples/example-storybook/ was NOT MEASURED: the dependency install for examples/example-storybook/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/babel-plugin/ was NOT MEASURED: the dependency install for packages/@stylexjs/babel-plugin/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/cli/ was NOT MEASURED: the dependency install for packages/@stylexjs/cli/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/devtools-extension/ was NOT MEASURED: the dependency install for packages/@stylexjs/devtools-extension/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/eslint-plugin/ was NOT MEASURED: the dependency install for packages/@stylexjs/eslint-plugin/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/postcss-plugin/ was NOT MEASURED: the dependency install for packages/@stylexjs/postcss-plugin/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/rollup-plugin/ was NOT MEASURED: the dependency install for packages/@stylexjs/rollup-plugin/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/shared/ was NOT MEASURED: the dependency install for packages/@stylexjs/shared/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/stylex/ was NOT MEASURED: the dependency install for packages/@stylexjs/stylex/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/@stylexjs/unplugin/ was NOT MEASURED: the dependency install for packages/@stylexjs/unplugin/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in packages/style-value-parser/ was NOT MEASURED: the dependency install for packages/style-value-parser/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `REDACTED`, `packages/@stylexjs/babel-plugin/src/shared/common-types.js`, `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-ltr.js`, `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-rtl.js`, `packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/PreRule.js`, … (+81 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 79 further occurrence(s) are not listed individually; the score already reflects all 119.
  • X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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.4 / 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.4 / 10 · rule-coverage 100% · ceiling Prevented

132 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was _evaluate at 206.

create.Program (cyclomatic 24) · ×2REDACTED:1024
(anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec (cyclomatic 20) · ×2packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:18
_evaluate (cyclomatic 206)packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483
create.checkStyleProperty (cyclomatic 97)REDACTED:640
stylex-valid-styles.checkStyleProperty (cyclomatic 95)REDACTED:640

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

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with _evaluate (cyclomatic 206), evaluate-path._evaluate (cyclomatic 190). — 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.4 to about 3.6/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

181 method(s) exceeded the cognitive complexity threshold of 15; the worst was _evaluate at 343.

create.Program (cognitive 18) · ×2REDACTED:1024
(anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec (cognitive 18) · ×2packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:18
_evaluate (cognitive 343)packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483
create.checkStyleProperty (cognitive 215)REDACTED:640
transformStyleXCreate (cognitive 215)packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:108

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

What to do

  1. Bring the 23 bodies over 60 down to 60 or less in Cognitive Complexity — start with _evaluate (cognitive 343), evaluate-path._evaluate (cognitive 325), create.checkStyleProperty (cognitive 215). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 23 together lifts Cognitive Complexity from 2.0 to about 4.0/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes7.6 / 10Strong✓ Tool-verified

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

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

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

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

FunctionTooLong: evaluate-path._evaluate · ×22packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483
FileTooLong: reference/cssProperties.js · ×12packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js

What to do

  1. Resolve the 22 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), REDACTED (2), evaluate-path.js. — One of this dimension's main actionable groups (22 warning-level).
  2. Resolve the 12 FileTooLong finding(s) in God Classes — start with cssProperties.js, StyleXCSSTypes.js, REDACTED. — One of this dimension's main actionable groups (12 warning-level).
  3. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D5 · 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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.9 / 10Stronggated by 11 serious findings✓ Tool-verified

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

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

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

11 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1595 tests (1 harness-style project(s) excluded from the assertion penalty).

Skipped test: rejects invalid calc spacing · ×11packages/style-value-parser/src/css-types/__tests__/calc-test.js:274
No direct assertions: basic create · ×4packages/benchmarks/perf/tests/transform-create-tests.js:22
Mock-dominated test: creates a Firefox sidebar without calling unsupported setHeight · ×2packages/@stylexjs/devtools-extension/__tests__/browserAdapters-test.js:41
Test project verifies nothing: packages/benchmarkspackages/benchmarks/perf/tests/transform-create-tests.js:22

What to do

  1. Resolve the 11 Skipped test finding(s) in Test Quality — start with transform-polyfills-test.js (3), media-query-transform-test.js (2), validation-stylex-create-test.js (2). — One of this dimension's main actionable groups (11 warning-level).
  2. Resolve the 4 No direct assertions finding(s) in Test Quality — start with transform-create-tests.js (2), transform-create-theme-tests.js (2). — One of this dimension's main actionable groups (4 recommendation-level).
  3. Resolve the 2 Mock-dominated test finding(s) in Test Quality — start with browserAdapters-test.js (2). — One of this dimension's main actionable groups (2 recommendation-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D12 · Dependency Hygiene7.0 / 10Strong✓ Tool-verified

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

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

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

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

Deprecated: eslint · ×2REDACTED:36
Deprecated: @humanwhocodes/config-array · ×13REDACTED:2448
Outdated (npm): @babel/core · ×46

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 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 71 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 71 production dependency(ies) this repository's committed lockfile resolves, across 14 product REDACTED manifest(s). Its 268 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 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.4 / 10Stronggated by 5 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.4 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js (3×190=570); REDACTED (5×45=225); packages/docs/src/components/Playground/index.tsx (2×53=106) Repeated repair below the complexity floor: packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js (3 of 4 changes were fixes)

Hotspot: packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js · ×4packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483
Repeated repair: packages/@stylexjs/eslint-plugin/src/reference/cssProperties.jspackages/@stylexjs/eslint-plugin/src/reference/cssProperties.js:547

What to do

  1. Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with evaluate-path.js, REDACTED, index.tsx. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with cssProperties.js. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/style-value-parser/src/token-parser.js. Counted over 142 of the 306 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

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

✓ On the Gold path — maintain.

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

D17 · Explicit Debt10.0 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

3 deducted task-comment markers across 17817 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.

TodoComment · ×2packages/docs/src/components/layout/page.tsx:109
HackCommentpackages/docs/src/pages/blog/_layout.tsx:13

What to do

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

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

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

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

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

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

1 of 1 documentation facets pass in full. 75 document(s) read across 1 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 (31 contexts). Contexts: atoms, babel-plugin, benchmarks, cli, create-stylex-app, devtools-extension, docs, eslint-plugin, example-bun, example-cli, example-esbuild, example-nextjs and 19 more.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D26 · Project Cohesion8.8 / 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, LLM-independent.

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

1 of 16 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.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

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

87 finding(s): 0 critical, 19 high, 68 medium, 0 low. 16 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 99 file(s) — `examples/example-react-router/src/routes/config.ts` (line 28), `REDACTED` (line 695, line 1039), `packages/@stylexjs/babel-plugin/src/shared/common-types.js` (line 22, line 23, line 24, …), `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-ltr.js` (line 22, line 45), `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-rtl.js` (line 88, line 114), … (+94 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

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

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

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

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

71 finding(s): 5 critical, 40 high, 21 medium, 5 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Documented

19 of 142 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js. Counted over 142 of the 306 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×19packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:1
Orphaned files with no living knowledge

What to do

  1. Resolve the 19 Orphaned file finding(s) in Knowledge Freshness — start with stylex-no-nonstandard-styles.js, discovery.js, stylex-nested-utils.js. — One of this dimension's main actionable groups (19 recommendation-level).
  2. Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: stylex-create-theme.js↔stylex-define-vars.js 80%

Change coupling: stylex-create-theme.js ↔ stylex-define-vars.jspackages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with stylex-create-theme.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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

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

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

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

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

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

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

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

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

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — packages/@stylexjs/devtools-extension/panel.html:2
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — packages/docs/src/pages/_root.tsx:56
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/docs/src/pages/_root.tsx:56

What to do

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

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC6 · Visual & motion safety10.0 / 10Exemplary○ Nothing flagged

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

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

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

AC7 · A11y enforcement6.0 / 10Adequate✓ Tool-verified

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

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

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

  • An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 67 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Accessibility linting is already configured — assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

What to do

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

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

IC1 · Incompleteness & stubs9.0 / 10Exemplary✓ Tool-verified

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

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

  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — REDACTED:409
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×15) — packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:28, packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:37, packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:50, …

What to do

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

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

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Add a README to the 5 of 32 project(s) that lack one — worth up to 0.3 pts.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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

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

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

What to do

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

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

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

What to do

  • Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · Observability5.0 / 10Adequate✓ Tool-verified

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

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

  • Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/@stylexjs/cli`, `packages/scripts`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6129 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:3

What to do

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

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

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

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

What to do

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

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

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

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

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

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

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

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

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

  • `fs.existsSync` in `callback to filesToDelete.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/cli/src/transform.js:49
  • `fs.rmSync` in `callback to filesToDelete.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/cli/src/transform.js:51
  • `fs.existsSync` in `compileFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/cli/src/transform.js:112
  • `fs.existsSync` in `build` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/postcss-plugin/src/builder.js:178
  • `fs.statSync` in `build` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/postcss-plugin/src/builder.js:179
  • `fs.readFileSync` in `callback to filesToTransform.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/postcss-plugin/src/builder.js:199
  • `fs.readdirSync` in `callback to build.onEnd` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/unplugin/src/esbuild.js:46
  • `fs.readFileSync` in `callback to build.onEnd` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/@stylexjs/unplugin/src/esbuild.js:62
  • `fs.existsSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/@stylexjs/unplugin/src/rollup.js:53, packages/@stylexjs/unplugin/src/vite.js:190
  • `fs.readdirSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/@stylexjs/unplugin/src/rollup.js:55, packages/@stylexjs/unplugin/src/vite.js:192
  • `fs.readFileSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/@stylexjs/unplugin/src/rollup.js:77, packages/@stylexjs/unplugin/src/vite.js:214

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

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

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

R10 · Code Duplication8.7 / 10Exemplary✓ Tool-verified

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

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

  • 13 duplicated blocks under packages/@stylexjs/ have copies in at least two of the sibling directories babel-plugin, cli, devtools-extension, eslint-plugin, postcss-plugin, rollup-plugin (+3 more sibling(s) not listed) — 7 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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/@stylexjs/babel-plugin/src/shared/hash.js:25
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:128 · packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:191 — the two spans are one implementation copied and then locally edited — 911 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/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:128
  • packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315 · REDACTED:1024 — 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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26 · packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js:30 — the two spans are one implementation copied and then locally edited — 520 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/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26
  • packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14 · packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:14 — 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/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14
  • packages/@stylexjs/unplugin/src/rollup.js:25 · packages/@stylexjs/unplugin/src/vite.js:159 — the two spans are one implementation copied and then locally edited — 453 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/@stylexjs/unplugin/src/rollup.js:25
  • packages/style-value-parser/src/css-types/easing-function.js:64 · REDACTED:73 — the two spans are one implementation copied and then locally edited — 428 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/style-value-parser/src/css-types/easing-function.js:64
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:96 · packages/@stylexjs/babel-plugin/src/visitors/visitor-utils.js:134 — 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/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:96
  • packages/@stylexjs/babel-plugin/src/shared/hash.js:25 · packages/@stylexjs/cli/src/hash.js:25 — 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/@stylexjs/babel-plugin/src/shared/hash.js:25
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:102 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:114 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:102
  • REDACTED:404 · REDACTED:469 — the two spans are one implementation copied and then locally edited — 271 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:404
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:64 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:65 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:64
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:71 · packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:66 — 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/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:71
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:103 · packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:173 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:103
  • packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:85 · packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:85
  • packages/@stylexjs/babel-plugin/src/shared/stylex-keyframes.js:66 · packages/@stylexjs/babel-plugin/src/shared/stylex-position-try.js:54 — 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/@stylexjs/babel-plugin/src/shared/stylex-keyframes.js:66
  • packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:87 · packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:87
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:139 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:90 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create.js:139
  • packages/style-value-parser/src/at-queries/media-query.js:233 · packages/style-value-parser/src/at-queries/media-query.js:264 — 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/style-value-parser/src/at-queries/media-query.js:233
  • packages/style-value-parser/src/css-types/color.js:540 · packages/style-value-parser/src/css-types/color.js:594 — 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/style-value-parser/src/css-types/color.js:540
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:212 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:404 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:212
  • packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165 · packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:231 — 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/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165
  • packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:49 · packages/@stylexjs/eslint-plugin/src/stylex-no-lookahead-selectors.js:29 · REDACTED:62 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:49
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js:27 — 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/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28
  • packages/style-value-parser/src/css-types/color.js:571 · packages/style-value-parser/src/css-types/color.js:619 — 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/style-value-parser/src/css-types/color.js:571
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:39 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:115 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:416 — 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/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:115
  • packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:102 · packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:102
  • packages/@stylexjs/postcss-plugin/src/discovery.js:65 · REDACTED:149 — the two spans are one implementation copied and then locally edited — 117 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/@stylexjs/postcss-plugin/src/discovery.js:65
  • packages/@stylexjs/eslint-plugin/src/rules/isAbsoluteLength.js:19 · packages/@stylexjs/eslint-plugin/src/rules/isRelativeLength.js:42 — 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/@stylexjs/eslint-plugin/src/rules/isAbsoluteLength.js:19
  • packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:61 · packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:132 — 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/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:61
  • packages/@stylexjs/babel-plugin/src/visitors/imports.js:156 · packages/@stylexjs/babel-plugin/src/visitors/imports.js:247 — the two spans are one implementation copied and then locally edited — 136 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/@stylexjs/babel-plugin/src/visitors/imports.js:156
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-define-marker.js:85 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:411 — 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/@stylexjs/babel-plugin/src/visitors/stylex-define-marker.js:85
  • packages/style-value-parser/src/css-types/filter-function.js:50 · packages/style-value-parser/src/css-types/filter-function.js:70 · packages/style-value-parser/src/css-types/filter-function.js:90 · packages/style-value-parser/src/css-types/filter-function.js:175 · +3 more site(s) not listed — all 7 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/style-value-parser/src/css-types/filter-function.js:50
  • packages/style-value-parser/src/properties/border-radius.js:87 · packages/style-value-parser/src/properties/border-radius.js:112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/style-value-parser/src/properties/border-radius.js:87
  • packages/@stylexjs/babel-plugin/src/utils/validate.js:247 · packages/@stylexjs/babel-plugin/src/utils/validate.js:277 — 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/@stylexjs/babel-plugin/src/utils/validate.js:247
  • packages/style-value-parser/src/css-types/color.js:305 · packages/style-value-parser/src/css-types/color.js:419 — 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/style-value-parser/src/css-types/color.js:305
  • packages/style-value-parser/src/token-parser.js:383 · packages/style-value-parser/src/token-parser.js:424 — 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/style-value-parser/src/token-parser.js:383
  • packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/leading-zero.js:17 · packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/timings.js:18 — 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/@stylexjs/babel-plugin/src/shared/utils/normalizers/leading-zero.js:17
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:27 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js:27 — 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/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:27

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.2 / 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.

  • REDACTED:16 imports style-value-parser, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:16
  • REDACTED:47 imports @stylexjs/atoms/babel-transform, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — REDACTED:47
  • packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:13 imports style-value-parser, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:13

What to do

  • Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (3 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.
R2 · Cyclomatic Complexity7.0 / 10Strong✓ Tool-verified

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

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

  • _evaluate has cyclomatic complexity 198 and cognitive complexity 328; 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/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483
  • checkStyleProperty has cyclomatic complexity 85 and cognitive complexity 197; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:640
  • splitSpecificShorthands has cyclomatic complexity 79 and cognitive complexity 120; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1058
  • mergeIntervalsForAnd has cyclomatic complexity 49 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/style-value-parser/src/at-queries/media-query.js:356
  • checkStyleProperty has cyclomatic complexity 49 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155
  • readRequires has cyclomatic complexity 48 and cognitive complexity 130; 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/@stylexjs/babel-plugin/src/visitors/imports.js:150
  • readImportDeclarations has cyclomatic complexity 43 and cognitive complexity 170; 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/@stylexjs/babel-plugin/src/visitors/imports.js:18
  • findMatchingClosingBraceLine has cyclomatic complexity 43 and cognitive complexity 103; 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/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:15
  • transformStylexProps has cyclomatic complexity 33 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/@stylexjs/babel-plugin/src/visitors/stylex-props.js:62
  • resolveMediaTypes has cyclomatic complexity 31 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/style-value-parser/src/at-queries/media-query.js:623
  • validateStyleValue has cyclomatic complexity 31 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. — REDACTED:496
  • _flattenRawStyleObject has cyclomatic complexity 30 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:39
  • reportErrors has cyclomatic complexity 30 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/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316
  • expandAnimationShorthand has cyclomatic complexity 29 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. — REDACTED:711
  • expandBackgroundShorthand has cyclomatic complexity 28 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:856
  • parseNullableStyle has cyclomatic complexity 27 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/@stylexjs/babel-plugin/src/visitors/stylex-props.js:357
  • validateProperty has cyclomatic complexity 27 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148
  • (anonymous) has cyclomatic complexity 26 and cognitive complexity 123; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:214
  • Property has cyclomatic complexity 26 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/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:255
  • setOptions has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:215

What to do

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

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

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

  • packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js has 2328 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/@stylexjs/eslint-plugin/src/reference/cssProperties.js:1
  • REDACTED has 1236 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1236 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js has 1183 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/@stylexjs/babel-plugin/src/utils/evaluate-path.js:1
  • REDACTED has 945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/style-value-parser/src/at-queries/media-query.js has 870 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/style-value-parser/src/at-queries/media-query.js:1
  • packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js has 860 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/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js:1
  • REDACTED has 853 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 731 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/style-value-parser/src/css-types/color.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/style-value-parser/src/css-types/color.js:1
  • packages/style-value-parser/src/token-parser.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/style-value-parser/src/token-parser.js:1
  • packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js has 571 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/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:1
  • REDACTED has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js has 539 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/@stylexjs/babel-plugin/src/visitors/stylex-create.js:1
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js has 532 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/@stylexjs/babel-plugin/src/visitors/stylex-props.js:1
  • packages/@stylexjs/devtools-extension/src/inspected/collector.js has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/@stylexjs/devtools-extension/src/inspected/collector.js:1
  • packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js has 500 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/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js:1
  • packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js:1
  • REDACTED has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js has 441 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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:1
  • packages/@stylexjs/postcss-plugin/src/discovery.js has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/@stylexjs/postcss-plugin/src/discovery.js:1
  • packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js has 419 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/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.7 / 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.

  • packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11
  • packages/@stylexjs/cli/__tests__/__mocks__/source/index.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source/index.js:11
  • packages/@stylexjs/cli/__tests__/__mocks__/source/pages/home.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source/pages/home.js:11
  • packages/@stylexjs/cli/__tests__/__mocks__/source2/components/button.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source2/components/button.js:11
  • packages/@stylexjs/cli/__tests__/__mocks__/source2/index.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source2/index.js:11
  • packages/@stylexjs/cli/__tests__/__mocks__/source2/pages/home.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/@stylexjs/cli/__tests__/__mocks__/source2/pages/home.js:11
  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×33) — packages/@stylexjs/stylex/src/types/StyleXCSSTypes.js:1, packages/@stylexjs/create-stylex-app/src/index.js:1, packages/@stylexjs/stylex/src/types/StyleXTypes.js:1, …

What to do

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

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

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

  • This repository declares test tooling, and the ✓ above records that declaration — but packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js and 5 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11
R7 · Dead Code9.1 / 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.

  • 4 file(s) (~47 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/@stylexjs/postcss-plugin/__tests__/__auto_discovery_fixtures__
  • 13 file(s) (~1212 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — packages/typescript-tests
  • Unreachable from the 54 application, 48 tooling and 162 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×5) — packages/@stylexjs/babel-plugin/src/shared/utils/Rule.js, packages/style-value-parser/src/base-types.js, packages/@stylexjs/create-stylex-app/src/utils/files.js, …
  • Nothing imports this binding — it is safe to review for removal. (×10) — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/index.js:22, packages/@stylexjs/babel-plugin/src/shared/utils/object-utils.js:26, packages/@stylexjs/babel-plugin/src/shared/utils/object-utils.js:57, …
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×7) — packages/typescript-tests/src/test1.tsx:30, packages/typescript-tests/src/test1.tsx:34, packages/typescript-tests/src/test2.tsx:35, …

What to do

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

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

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

  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×6) — packages/@stylexjs/atoms/src/babel-transform.js:10, packages/@stylexjs/devtools-extension/rollup.config.mjs:17, packages/@stylexjs/devtools-extension/rollup.config.mjs:18, …
  • Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — packages/@stylexjs/cli/src/plugins.js:11
  • Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Declared in packages/@stylexjs/postcss-plugin/__tests__/__auto_discovery_fixtures__/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.

S1 · Web-Security Posture8.5 / 10Strong✓ Tool-verified

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

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

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

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

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

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

X3 · Exception handling4.1 / 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. (×35) — packages/@stylexjs/unplugin/src/bun.js:42, REDACTED:216, REDACTED:358, …
  • `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/@stylexjs/devtools-extension/src/panel/components/OverridesSection.js:113
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — REDACTED:877, REDACTED:914

What to do

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

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

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

X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

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

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

  • ~0.3 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 11328 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/docs/src/components/Playground/index.tsx (2), packages/docs/src/waku.server.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

WCAG coverage — what static analysis assessed

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

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

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

Reference — by lens

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

LensScoreRatingImpact
Code Health62%Adequate — gated by D1, D2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture97%ExemplaryStrongest area.
Maturity62%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness48%Adequate — gated by R8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security74%Adequate — gated by D29, D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility78%StrongSolid.
Performance73%StrongSolid.
Unscored — 3 check(s) recorded observations but carry no score

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

  • D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). 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.
  • P12 CI test-gate honesty — 3 observation(s) recorded · 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'.
  • X10 Duplicated predicate — 25 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 — 50 check(s) not relevant to this codebase

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

  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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 is measured on C# only; JavaScript, TypeScript not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript surface was not measured.
  • D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.jsx,.mjs,.ts,.tsx), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 86 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.cjs, .js, .jsx, .mjs, .svelte, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
  • 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
  • M4 Documentation accuracy — Not applicable: the 75 current-state document(s) make no claim of a kind M4 checks. 80 claim(s) of kinds M4 does not check were not checked (path 7, command argument 10, install 17, environment variable 1, package 45); M4 checks only links and versions and artefact counts.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — 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 — 73 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×39
  • 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
  • + 14 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
D30 · Dependency Vulnerabilities · Critical CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'browserslist' · ×2
  • Unlisted import 'browserslist' packages/@stylexjs/devtools-extension/rollup.config.mjs:17 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import 'browserslist' packages/@stylexjs/rollup-plugin/src/index.js:25 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC3 · Page structure · <html> without a lang · ×1
  • <html> without a lang packages/@stylexjs/devtools-extension/panel.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> packages/docs/src/pages/_root.tsx:56 — A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@babel/types' · ×1
  • Unlisted import '@babel/types' packages/@stylexjs/atoms/src/babel-transform.js:10 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'lightningcss' · ×1
  • Unlisted import 'lightningcss' packages/@stylexjs/devtools-extension/rollup.config.mjs:18 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react-strict-dom' · ×1
  • Unlisted import 'react-strict-dom' packages/@stylexjs/postcss-plugin/__tests__/__auto_discovery_fixtures__/src/local-rsd.js:7 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R8 · Dependency Hygiene · Unlisted import 'react' · ×1
  • Unlisted import 'react' packages/typescript-tests/src/test1.tsx:12 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Serious — 553 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
  • + 35 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×36
  • Swallowed exception (empty catch) packages/@stylexjs/unplugin/src/bun.js:42 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:216 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:358 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:370 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED: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) REDACTED:392 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:399 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:411 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:488 — 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/@stylexjs/unplugin/src/esbuild.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/@stylexjs/unplugin/src/esbuild.js:70 — 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/@stylexjs/unplugin/src/esbuild.js:71 — 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/@stylexjs/unplugin/src/rollup.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/@stylexjs/unplugin/src/rollup.js:63 — 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/@stylexjs/unplugin/src/rollup.js:68 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) packages/@stylexjs/unplugin/src/rollup.js:85 — 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/@stylexjs/unplugin/src/vite.js:59 — 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/@stylexjs/unplugin/src/vite.js:89 — 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/@stylexjs/unplugin/src/vite.js:158 — 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/@stylexjs/unplugin/src/vite.js:185 — 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/@stylexjs/unplugin/src/vite.js:200 — 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/@stylexjs/unplugin/src/vite.js:205 — 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/@stylexjs/unplugin/src/vite.js:222 — 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/@stylexjs/stylex/src/stylesheet/createOrderedCSSStyleSheet.js:153 — 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/@stylexjs/postcss-plugin/src/discovery.js:128 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 11 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×33
  • No test reaches this file packages/@stylexjs/stylex/src/types/StyleXCSSTypes.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/create-stylex-app/src/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/stylex/src/types/StyleXTypes.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file tools/npm/release.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/devtools-extension/src/types.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/cli/src/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/scripts/flow-translator/generate-types.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/cli/src/watcher.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/create-stylex-app/src/utils/fetch-template.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/babel-plugin/src/shared/utils/Rule.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/create-stylex-app/src/utils/packages.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/babel-plugin/src/shared/common-types.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/devtools-extension/scripts/package.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/cli/src/options.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/scripts/flow-translator/rewrite-imports.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/devtools-extension/scripts/lint-firefox.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/unplugin/babel-plugins/add-mjs-extension.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/style-value-parser/src/base-types.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/create-stylex-app/src/templates.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/cli/src/config.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/eslint-plugin/src/index.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/shared-ui/src/index.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/create-stylex-app/src/utils/files.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/@stylexjs/babel-plugin/src/shared/validate.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • + 8 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×22
  • FunctionTooLong: evaluate-path._evaluate packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483 — FunctionTooLong — _evaluate runs 478 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 378 over it, 4.78× 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: stylex-valid-styles.checkStyleProperty REDACTED:640 — FunctionTooLong — checkStyleProperty runs 292 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 192 over it, 2.92× 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: stylex-create.transformStyleXCreate packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:108 — FunctionTooLong — transformStyleXCreate runs 282 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 182 over it, 2.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: search-dialog.SearchDialog packages/docs/src/components/search-dialog.tsx:232 — FunctionTooLong — SearchDialog runs 260 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 160 over it, 2.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: MetaOpenSource.MetaOpenSource packages/docs/src/components/icons/MetaOpenSource.tsx:9 — FunctionTooLong — MetaOpenSource runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.styleXTransform REDACTED:60 — FunctionTooLong — styleXTransform runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: stylex-props.transformStylexProps packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:62 — FunctionTooLong — transformStylexProps runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× 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: splitShorthands.splitSpecificShorthands REDACTED:1058 — FunctionTooLong — splitSpecificShorthands runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: stylex-sort-keys.createFix packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:358 — FunctionTooLong — createFix runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Logo.Logo packages/docs/src/components/Logo.tsx:31 — FunctionTooLong — Logo runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Logo.Logo packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:24 — FunctionTooLong — Logo runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: vite.attachViteHooks packages/@stylexjs/unplugin/src/vite.js:27 — FunctionTooLong — attachViteHooks runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.main packages/@stylexjs/create-stylex-app/src/index.js:131 — FunctionTooLong — main runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: stylex-merge.transformStyleXMerge packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:47 — FunctionTooLong — transformStyleXMerge runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Footer.Footer packages/docs/src/components/Footer.tsx:66 — FunctionTooLong — Footer runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: stylex-no-nonstandard-styles.checkStyleProperty packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — FunctionTooLong — checkStyleProperty runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: stylex-define-vars.transformStyleXDefineVars packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:48 — FunctionTooLong — transformStyleXDefineVars runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: stylex-create-theme.transformStyleXCreateTheme packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 — FunctionTooLong — transformStyleXCreateTheme runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: SourceRow.SourceRow packages/@stylexjs/devtools-extension/src/panel/components/SourceRow.js:24 — FunctionTooLong — SourceRow runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: ComboBox.ComboBox packages/@stylexjs/devtools-extension/src/panel/components/ComboBox.js:16 — FunctionTooLong — ComboBox runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: stylex-valid-styles.validateStyleValue REDACTED:496 — FunctionTooLong — validateStyleValue runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Dial.Dial packages/docs/src/components/Dial.tsx:70 — FunctionTooLong — Dial runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×14
  • Sync-over-async blocking packages/@stylexjs/cli/src/transform.js:49 — `fs.existsSync` in `callback to filesToDelete.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/cli/src/transform.js:51 — `fs.rmSync` in `callback to filesToDelete.forEach` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/cli/src/transform.js:112 — `fs.existsSync` in `compileFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/postcss-plugin/src/builder.js:178 — `fs.existsSync` in `build` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/postcss-plugin/src/builder.js:179 — `fs.statSync` in `build` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/postcss-plugin/src/builder.js:199 — `fs.readFileSync` in `callback to filesToTransform.map` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/esbuild.js:46 — `fs.readdirSync` in `callback to build.onEnd` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/esbuild.js:62 — `fs.readFileSync` in `callback to build.onEnd` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/rollup.js:53 — `fs.existsSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/rollup.js:55 — `fs.readdirSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/rollup.js:77 — `fs.readFileSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/vite.js:190 — `fs.existsSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/vite.js:192 — `fs.readdirSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/@stylexjs/unplugin/src/vite.js:214 — `fs.readFileSync` in `writeBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
D3 · God Classes · FileTooLong · ×12
  • FileTooLong: reference/cssProperties.js packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js — FileTooLong — 2034 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 1500 significant lines; this is 534 over it, 1.36× 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: types/StyleXCSSTypes.js packages/@stylexjs/stylex/src/types/StyleXCSSTypes.js — FileTooLong — 1500 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1000 over it, 3.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 941 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 441 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 915 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: stylexValidStyles (192-1299). The bar is 500 significant lines; this is 415 over it, 1.83× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: utils/evaluate-path.js packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js — FileTooLong — 813 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 313 over it, 1.63× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 69% of them inside a single declaration: DEFAULT_INJECT_PATH (161-817). The bar is 500 significant lines; this is 168 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: at-queries/media-query.js packages/style-value-parser/src/at-queries/media-query.js — FileTooLong — 657 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 157 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 640 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 140 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: components/search-dialog.tsx packages/docs/src/components/search-dialog.tsx — FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 76% of them inside a single declaration: shorthandsOfShorthands (17-656). The bar is 500 significant lines; this is 81 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: components/sidebar.tsx packages/docs/src/components/sidebar.tsx — FileTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 54 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: css-types/color.js packages/style-value-parser/src/css-types/color.js — FileTooLong — 511 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 11 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D10 · Test Quality · Skipped test · ×11
  • Skipped test: rejects invalid calc spacing packages/style-value-parser/src/css-types/__tests__/calc-test.js:274 — Skipped — switched off by test.skip
  • Skipped test: handles and media queries packages/style-value-parser/src/at-queries/__tests__/media-query-transform-test.js:316 — Skipped — switched off by test.skip
  • Skipped test: combination of keywords and rules packages/style-value-parser/src/at-queries/__tests__/media-query-transform-test.js:340 — Skipped — switched off by test.skip
  • Skipped test: lineClamp packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:28 — Skipped — switched off by test.skip
  • Skipped test: pointerEvents packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:37 — Skipped — switched off by test.skip
  • Skipped test: scrollbarWidth packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:50 — Skipped — switched off by test.skip
  • Skipped test: works with firstThatWorks packages/@stylexjs/babel-plugin/__tests__/transform-stylex-defineConsts-test.js:615 — Skipped — switched off by test.skip
  • Skipped test: using contextual styles packages/@stylexjs/babel-plugin/__tests__/transform-stylex-viewTransitionClass-test.js:248 — Skipped — switched off by test.skip
  • Skipped test: invalid value: empty object packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:352 — Skipped — switched off by test.skip
  • Skipped test: invalid object value: contains disallowed key packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:537 — Skipped — switched off by test.skip
  • Skipped test: valid value: keyframes packages/@stylexjs/babel-plugin/__tests__/validation-stylex-defineConsts-test.js:231 — Skipped — switched off by test.skip
D29 · Static Analysis (SAST) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R4 · Test Coverage · This test file cannot be loaded · ×6
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source/index.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source/index.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source/pages/home.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source/pages/home.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source2/components/button.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source2/components/button.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source2/index.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source2/index.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source2/pages/home.js:11 — packages/@stylexjs/cli/__tests__/__mocks__/source2/pages/home.js:11 imports './otherStyles', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
D15 · Churn × Complexity Hotspots · Hotspot · ×4
  • Hotspot: packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483 — packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 190 in evaluate-path._evaluate at line 483. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 23:08:08 -04:00' --until='2026-10-29 23:08:08 -04:00' --full-history --no-merges -- packages/@stylexjs/babel-plugin/src/utils/evaluate-path.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: REDACTED REDACTED:680 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in index.processStylexRules at line 680. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 23:08:08 -04:00' --until='2026-10-29 23:08:08 -04:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/docs/src/components/Playground/index.tsx packages/docs/src/components/Playground/index.tsx:271 — packages/docs/src/components/Playground/index.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in index.PlaygroundNew at line 271. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 23:08:08 -04:00' --until='2026-10-29 23:08:08 -04:00' --full-history --no-merges -- packages/docs/src/components/Playground/index.tsx`: 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/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.js packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.js:24 — packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in zero-dimensions.normalizeZeroDimensions at line 24. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 23:08:08 -04:00' --until='2026-10-29 23:08:08 -04:00' --full-history --no-merges -- packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.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.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×3
  • Duplicated block (18 lines × 2 locations) packages/@stylexjs/babel-plugin/src/utils/validate.js:247 — packages/@stylexjs/babel-plugin/src/utils/validate.js:247 · packages/@stylexjs/babel-plugin/src/utils/validate.js:277 — 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 (18 lines × 2 locations) packages/style-value-parser/src/css-types/color.js:305 — packages/style-value-parser/src/css-types/color.js:305 · packages/style-value-parser/src/css-types/color.js:419 — 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 (18 lines × 2 locations) packages/style-value-parser/src/token-parser.js:383 — packages/style-value-parser/src/token-parser.js:383 · packages/style-value-parser/src/token-parser.js:424 — 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.
R11 · Import Boundaries · Boundary violation [package · ×3
  • Boundary violation [package:undeclared-workspace-dep] REDACTED:16 — REDACTED:16 imports style-value-parser, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
  • Boundary violation [package:undeclared-workspace-dep] REDACTED:47 — REDACTED:47 imports @stylexjs/atoms/babel-transform, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
  • Boundary violation [package:undeclared-workspace-dep] packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:13 — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:13 imports style-value-parser, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
D1 · Cyclomatic Complexity · create.Program (cyclomatic 24) · ×2
  • create.Program (cyclomatic 24) REDACTED:1024 — create.Program has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 1076, 1093, 1060, …). 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.
  • create.Program (cyclomatic 24) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315 — create.Program has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 367, 384, 351, …). 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 · (anonymous) · ×2
  • (anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec (cyclomatic 20) packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:18 — (anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec 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.
  • (anonymous)::isAnimationName::isAnimationNameRec (cyclomatic 20) packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:18 — (anonymous)::isAnimationName::isAnimationNameRec 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.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: eslint REDACTED:36 — eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: glob REDACTED:43 — glob 10.5.0, declared in REDACTED, 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". Replace it with the package or version that message names, or record why this one must stay.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment packages/docs/src/components/layout/page.tsx:109 — // TODO: Move `prose` to stylex as a component. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment packages/docs/src/components/Playground/DynamicPlayground.tsx:55 — // TODO: Add a better placeholder with a shimmer version of the playground layout — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · create.Program (cognitive 18) · ×2
  • create.Program (cognitive 18) REDACTED:1024 — create.Program has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 2 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 1076, 1110, 1060, …). 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.
  • create.Program (cognitive 18) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315 — create.Program has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 2 (nesting depth added 4). None of this is in the body itself: all 18 points belong to 8 function literals inside it that branch (lines 367, 401, 351, …). 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 · (anonymous) · ×2
  • (anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec (cognitive 18) packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:18 — (anonymous)::isPositionTryFallbacks::isPositionTryFallbacksRec has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (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.
  • (anonymous)::isAnimationName::isAnimationNameRec (cognitive 18) packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:18 — (anonymous)::isAnimationName::isAnimationNameRec has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (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.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×2
  • REDACTED
  • REDACTED
P12 · CI test-gate honesty · Runner config excludes tests no gate runs · ×2
  • Runner config excludes tests no gate runs packages/@stylexjs/babel-plugin/jest.config.js:29 — `/__fixtures__/` removes 2 test(s) in 2 file(s) (e.g. `packages/@stylexjs/babel-plugin/__tests__/__fixtures__/constants.stylex.js`, `packages/@stylexjs/babel-plugin/__tests__/__fixtures__/themeVars.stylex.js`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
  • Runner config excludes tests no gate runs packages/@stylexjs/postcss-plugin/jest.config.js:11 — `/__fixtures__/` removes 5 test(s) in 5 file(s) (e.g. `packages/@stylexjs/postcss-plugin/__tests__/__fixtures__/.babelrc.js`, `packages/@stylexjs/postcss-plugin/__tests__/__fixtures__/import-sources-object.js`) from what jest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×2
  • Duplicated block (25 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:212 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:212 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:404 — 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 (25 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165 — packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165 · packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:231 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×2
  • Duplicated block (24 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28 — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js:27 — 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/style-value-parser/src/css-types/color.js:571 — packages/style-value-parser/src/css-types/color.js:571 · packages/style-value-parser/src/css-types/color.js:619 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×2
  • Duplicated block (22 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:115 — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:115 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:416 — 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 (22 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:102 — packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:102 · packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-marker.js:85 — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-marker.js:85 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:411 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (19 lines × 2 locations) packages/style-value-parser/src/properties/border-radius.js:87 — packages/style-value-parser/src/properties/border-radius.js:87 · packages/style-value-parser/src/properties/border-radius.js:112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) REDACTED:877 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:914 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC3 · Page structure · Page without a main landmark · ×1
  • Page without a main landmark packages/docs/src/pages/_root.tsx:56 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D1 · Cyclomatic Complexity · _evaluate (cyclomatic 206) · ×1
  • _evaluate (cyclomatic 206) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483 — _evaluate has cyclomatic complexity 206 (threshold 15). Of this number, 198 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 · create.checkStyleProperty (cyclomatic 97) · ×1
  • create.checkStyleProperty (cyclomatic 97) REDACTED:640 — create.checkStyleProperty has cyclomatic complexity 97 (threshold 15). Of this number, 85 points are the body's own statements and 12 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stylex-valid-styles.checkStyleProperty (cyclomatic 95) · ×1
  • stylex-valid-styles.checkStyleProperty (cyclomatic 95) REDACTED:640 — stylex-valid-styles.checkStyleProperty has cyclomatic complexity 95 (threshold 15). Of this number, 84 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · splitSpecificShorthands (cyclomatic 79) · ×1
  • splitSpecificShorthands (cyclomatic 79) REDACTED:1058 — splitSpecificShorthands has cyclomatic complexity 79 (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 · transformStyleXCreate (cyclomatic 68) · ×1
  • transformStyleXCreate (cyclomatic 68) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:108 — transformStyleXCreate has cyclomatic complexity 68 (threshold 15). Of this number, 24 points are the body's own statements and 44 belong to 27 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 · index.styleXTransform (cyclomatic 62) · ×1
  • index.styleXTransform (cyclomatic 62) REDACTED:60 — index.styleXTransform has cyclomatic complexity 62 (threshold 15). Most of this is not in the body itself: 12 of the 62 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 214, 98, 77, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · core.unpluginFactory (cyclomatic 61) · ×1
  • core.unpluginFactory (cyclomatic 61) REDACTED:229 — core.unpluginFactory has cyclomatic complexity 61 (threshold 15). Of this number, 29 points are the body's own statements and 32 belong to 9 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 · create.checkStyleProperty (cyclomatic 55) · ×1
  • create.checkStyleProperty (cyclomatic 55) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — create.checkStyleProperty has cyclomatic complexity 55 (threshold 15). Of this number, 49 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stylex-no-nonstandard-styles.checkStyleProperty (cyclomatic 53) · ×1
  • stylex-no-nonstandard-styles.checkStyleProperty (cyclomatic 53) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — stylex-no-nonstandard-styles.checkStyleProperty has cyclomatic complexity 53 (threshold 15). Of this number, 48 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.PlaygroundNew (cyclomatic 53) · ×1
  • index.PlaygroundNew (cyclomatic 53) packages/docs/src/components/Playground/index.tsx:271 — index.PlaygroundNew has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 12 of the 53 points are its own statements and the rest belongs to 23 function items inside it that branch (renameFile, deleteFile, updateSandpack, …). 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 · processStylexRules (cyclomatic 50) · ×1
  • processStylexRules (cyclomatic 50) REDACTED:680 — processStylexRules has cyclomatic complexity 50 (threshold 15). Most of this is not in the body itself: 14 of the 50 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 776, a function literal at line 912, resolveConstant, …). 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 · mergeIntervalsForAnd (cyclomatic 50) · ×1
  • mergeIntervalsForAnd (cyclomatic 50) packages/style-value-parser/src/at-queries/media-query.js:356 — mergeIntervalsForAnd has cyclomatic complexity 50 (threshold 15). Of this number, 49 points are the body's own statements and 1 belongs to 4 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 · imports.readRequires (cyclomatic 48) · ×1
  • imports.readRequires (cyclomatic 48) packages/@stylexjs/babel-plugin/src/visitors/imports.js:150 — imports.readRequires has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · search-dialog.SearchDialog (cyclomatic 45) · ×1
  • search-dialog.SearchDialog (cyclomatic 45) packages/docs/src/components/search-dialog.tsx:232 — search-dialog.SearchDialog has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 10 of the 45 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 338, 461, 393, …). 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 · imports.readImportDeclarations (cyclomatic 43) · ×1
  • imports.readImportDeclarations (cyclomatic 43) packages/@stylexjs/babel-plugin/src/visitors/imports.js:18 — imports.readImportDeclarations 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 · findMatchingClosingBraceLine (cyclomatic 43) · ×1
  • findMatchingClosingBraceLine (cyclomatic 43) packages/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:15 — findMatchingClosingBraceLine 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 · createFix (cyclomatic 41) · ×1
  • createFix (cyclomatic 41) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:358 — createFix has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 20 function items inside it that branch (getSortableGroup, getSortableProperty, getNodeIndentation, …). 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 · flatten-raw-style-obj._flattenRawStyleObject (cyclomatic 36) · ×1
  • flatten-raw-style-obj._flattenRawStyleObject (cyclomatic 36) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:39 — flatten-raw-style-obj._flattenRawStyleObject has cyclomatic complexity 36 (threshold 15). Of this number, 30 points are the body's own statements and 6 belong to 4 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 · stylex-props.transformStylexProps (cyclomatic 34) · ×1
  • stylex-props.transformStylexProps (cyclomatic 34) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:62 — stylex-props.transformStylexProps has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (stylex-props.transformStylexProps::MemberExpression) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · stylex-valid-styles.validateStyleValue (cyclomatic 31) · ×1
  • stylex-valid-styles.validateStyleValue (cyclomatic 31) REDACTED:496 — stylex-valid-styles.validateStyleValue 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 · createOrderedCSSStyleSheet.createOrderedCSSStyleSheet (cyclomatic 31) · ×1
  • createOrderedCSSStyleSheet.createOrderedCSSStyleSheet (cyclomatic 31) packages/@stylexjs/stylex/src/stylesheet/createOrderedCSSStyleSheet.js:34 — createOrderedCSSStyleSheet.createOrderedCSSStyleSheet has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (update, insert, sheetInsert, …). 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 · create.validateStyleValue (cyclomatic 31) · ×1
  • create.validateStyleValue (cyclomatic 31) REDACTED:496 — create.validateStyleValue 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 · resolveMediaTypes (cyclomatic 31) · ×1
  • resolveMediaTypes (cyclomatic 31) packages/style-value-parser/src/at-queries/media-query.js:623 — resolveMediaTypes 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 · stylex-enforce-extension.reportErrors (cyclomatic 30) · ×1
  • stylex-enforce-extension.reportErrors (cyclomatic 30) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316 — stylex-enforce-extension.reportErrors has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stylex-valid-shorthands.validateProperty (cyclomatic 30) · ×1
  • stylex-valid-shorthands.validateProperty (cyclomatic 30) packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148 — stylex-valid-shorthands.validateProperty 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, 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 · create.Property (cyclomatic 30) · ×1
  • create.Property (cyclomatic 30) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:255 — create.Property has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 belong 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 · create.reportErrors (cyclomatic 30) · ×1
  • create.reportErrors (cyclomatic 30) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316 — create.reportErrors has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create.validateProperty (cyclomatic 30) · ×1
  • create.validateProperty (cyclomatic 30) packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148 — create.validateProperty has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · splitShorthands.expandAnimationShorthand (cyclomatic 29) · ×1
  • splitShorthands.expandAnimationShorthand (cyclomatic 29) REDACTED:711 — splitShorthands.expandAnimationShorthand 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 · SourceRow (cyclomatic 29) · ×1
  • SourceRow (cyclomatic 29) packages/@stylexjs/devtools-extension/src/panel/components/SourceRow.js:24 — SourceRow has cyclomatic complexity 29 (threshold 15). Of this number, 20 points are the body's own statements and 9 belong to 12 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · splitShorthands.expandBackgroundShorthand (cyclomatic 28) · ×1
  • splitShorthands.expandBackgroundShorthand (cyclomatic 28) REDACTED:856 — splitShorthands.expandBackgroundShorthand has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · #toString (cyclomatic 28) · ×1
  • #toString (cyclomatic 28) packages/style-value-parser/src/at-queries/media-query.js:726 — #toString has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 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 · stylex-props.parseNullableStyle (cyclomatic 27) · ×1
  • stylex-props.parseNullableStyle (cyclomatic 27) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:357 — stylex-props.parseNullableStyle 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 · create (cyclomatic 27) · ×1
  • create (cyclomatic 27) REDACTED:272 — create has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 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 · create.ImportDeclaration (cyclomatic 27) · ×1
  • create.ImportDeclaration (cyclomatic 27) REDACTED:1119 — create.ImportDeclaration has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 1147, 1194, 1128, …). 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 · Tabs.Tab (cyclomatic 26) · ×1
  • Tabs.Tab (cyclomatic 26) packages/docs/src/components/Playground/Tabs.tsx:244 — Tabs.Tab has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · setOptions (cyclomatic 26) · ×1
  • setOptions (cyclomatic 26) REDACTED:215 — setOptions has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, 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 · transformStyleXCreateTheme (cyclomatic 24) · ×1
  • transformStyleXCreateTheme (cyclomatic 24) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 — transformStyleXCreateTheme has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to 10 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 · ComboBox (cyclomatic 24) · ×1
  • ComboBox (cyclomatic 24) packages/@stylexjs/devtools-extension/src/panel/components/ComboBox.js:16 — ComboBox has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 7 of the 24 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 96, commit, a function literal at line 90, …). 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 · index.main (cyclomatic 22) · ×1
  • index.main (cyclomatic 22) packages/@stylexjs/create-stylex-app/src/index.js:131 — index.main has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · valueSyntax.walkCssSyntax (cyclomatic 22) · ×1
  • valueSyntax.walkCssSyntax (cyclomatic 22) packages/@stylexjs/devtools-extension/src/utils/valueSyntax.js:29 — valueSyntax.walkCssSyntax has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · isAnimationName.isAnimationName (cyclomatic 22) · ×1
  • isAnimationName.isAnimationName (cyclomatic 22) packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14 — isAnimationName.isAnimationName 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 2 function literals inside it that branch (lines 18, 67). 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 · isPositionTryFallbacks.isPositionTryFallbacks (cyclomatic 22) · ×1
  • isPositionTryFallbacks.isPositionTryFallbacks (cyclomatic 22) packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:14 — isPositionTryFallbacks.isPositionTryFallbacks 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 2 function literals inside it that branch (lines 18, 67). 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 · unpluginFactory · ×1
  • unpluginFactory::transform (cyclomatic 22) REDACTED:430 — unpluginFactory::transform has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · transformStyleXMerge (cyclomatic 22) · ×1
  • transformStyleXMerge (cyclomatic 22) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:47 — transformStyleXMerge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · evaluate-path.isMutated (cyclomatic 21) · ×1
  • evaluate-path.isMutated (cyclomatic 21) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:194 — evaluate-path.isMutated has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · split-css-value.borderSplitter (cyclomatic 21) · ×1
  • split-css-value.borderSplitter (cyclomatic 21) packages/@stylexjs/eslint-plugin/src/utils/split-css-value.js:65 — split-css-value.borderSplitter has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · esbuild.attachEsbuildHooks (cyclomatic 21) · ×1
  • esbuild.attachEsbuildHooks (cyclomatic 21) packages/@stylexjs/unplugin/src/esbuild.js:15 — esbuild.attachEsbuildHooks has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 21). 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 · evaluatePartialObjectRecursively (cyclomatic 21) · ×1
  • evaluatePartialObjectRecursively (cyclomatic 21) REDACTED:119 — evaluatePartialObjectRecursively has cyclomatic complexity 21 (threshold 15). Of this number, 19 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 · declarationAnalysis.splitTopLevel (cyclomatic 20) · ×1
  • declarationAnalysis.splitTopLevel (cyclomatic 20) packages/@stylexjs/devtools-extension/src/inspected/declarationAnalysis.js:34 — declarationAnalysis.splitTopLevel 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 · (anonymous) (cyclomatic 20) · ×1
  • (anonymous) (cyclomatic 20) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js:264 — (anonymous) 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 · transformStyleXDefineVars (cyclomatic 20) · ×1
  • transformStyleXDefineVars (cyclomatic 20) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:48 — transformStyleXDefineVars has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 13 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · transform-value.transformValue (cyclomatic 19) · ×1
  • transform-value.transformValue (cyclomatic 19) packages/@stylexjs/babel-plugin/src/shared/utils/transform-value.js:18 — transform-value.transformValue has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · index.finishSetup (cyclomatic 19) · ×1
  • index.finishSetup (cyclomatic 19) packages/@stylexjs/create-stylex-app/src/index.js:375 — index.finishSetup 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 · getPropertyPriorityAndType.getPropertyPriorityAndType (cyclomatic 19) · ×1
  • getPropertyPriorityAndType.getPropertyPriorityAndType (cyclomatic 19) packages/@stylexjs/eslint-plugin/src/utils/getPropertyPriorityAndType.js:38 — getPropertyPriorityAndType.getPropertyPriorityAndType 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 · stylex-merge.parseNullableStyle (cyclomatic 18) · ×1
  • stylex-merge.parseNullableStyle (cyclomatic 18) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:222 — stylex-merge.parseNullableStyle has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · stylex-props.transformStylexProps · ×1
  • stylex-props.transformStylexProps::MemberExpression (cyclomatic 18) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:206 — stylex-props.transformStylexProps::MemberExpression 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. This shape REPEATS in the file: one other method here (stylex-props.transformStylexProps) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · isNumber.isNumber (cyclomatic 18) · ×1
  • isNumber.isNumber (cyclomatic 18) packages/@stylexjs/eslint-plugin/src/rules/isNumber.js:25 — isNumber.isNumber has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · splitShorthands.splitTopLevelValueTokens (cyclomatic 18) · ×1
  • splitShorthands.splitTopLevelValueTokens (cyclomatic 18) REDACTED:201 — splitShorthands.splitTopLevelValueTokens has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 223, flushCurrent). 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 · splitShorthands.expandFontShorthand (cyclomatic 18) · ×1
  • splitShorthands.expandFontShorthand (cyclomatic 18) REDACTED:972 — splitShorthands.expandFontShorthand 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 · vite.attachViteHooks.writeBundle (cyclomatic 18) · ×1
  • vite.attachViteHooks.writeBundle (cyclomatic 18) packages/@stylexjs/unplugin/src/vite.js:174 — vite.attachViteHooks.writeBundle 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 · Tabs.Tabs (cyclomatic 18) · ×1
  • Tabs.Tabs (cyclomatic 18) packages/docs/src/components/Playground/Tabs.tsx:16 — Tabs.Tabs has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · attachViteHooks.writeBundle (cyclomatic 18) · ×1
  • attachViteHooks.writeBundle (cyclomatic 18) packages/@stylexjs/unplugin/src/vite.js:174 — attachViteHooks.writeBundle 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 · getStaticPropertyName (cyclomatic 18) · ×1
  • getStaticPropertyName (cyclomatic 18) packages/@stylexjs/eslint-plugin/src/utils/getPropertyName.js:54 — getStaticPropertyName 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 · (anonymous) (cyclomatic 18) · ×1
  • (anonymous) (cyclomatic 18) packages/@stylexjs/eslint-plugin/src/rules/isNumber.js:30 — (anonymous) has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · basic-validation.validateConditionalStyles (cyclomatic 17) · ×1
  • basic-validation.validateConditionalStyles (cyclomatic 17) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/basic-validation.js:55 — basic-validation.validateConditionalStyles 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 · stylex-merge.transformStyleXMerge · ×1
  • stylex-merge.transformStyleXMerge::MemberExpression (cyclomatic 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:143 — stylex-merge.transformStyleXMerge::MemberExpression 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 · stylex-props.getPropsLikeCall (cyclomatic 17) · ×1
  • stylex-props.getPropsLikeCall (cyclomatic 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:537 — stylex-props.getPropsLikeCall has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · index.collectWidthBounds (cyclomatic 17) · ×1
  • index.collectWidthBounds (cyclomatic 17) REDACTED:520 — index.collectWidthBounds 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 · getDistance.getDistance (cyclomatic 17) · ×1
  • getDistance.getDistance (cyclomatic 17) packages/@stylexjs/eslint-plugin/src/utils/getDistance.js:36 — getDistance.getDistance has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.stylexPlugin.transform (cyclomatic 17) · ×1
  • index.stylexPlugin.transform (cyclomatic 17) packages/@stylexjs/rollup-plugin/src/index.js:118 — index.stylexPlugin.transform has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · rollup.attachRollupHooks.writeBundle (cyclomatic 17) · ×1
  • rollup.attachRollupHooks.writeBundle (cyclomatic 17) packages/@stylexjs/unplugin/src/rollup.js:39 — rollup.attachRollupHooks.writeBundle 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 · isVariableNamedExported (cyclomatic 17) · ×1
  • isVariableNamedExported (cyclomatic 17) packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:216 — isVariableNamedExported has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (ExportNamedDeclaration, a function literal at line 244). 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 · stylexPlugin.transform (cyclomatic 17) · ×1
  • stylexPlugin.transform (cyclomatic 17) packages/@stylexjs/rollup-plugin/src/index.js:118 — stylexPlugin.transform has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · transformStyleXKeyframes (cyclomatic 17) · ×1
  • transformStyleXKeyframes (cyclomatic 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:26 — transformStyleXKeyframes has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · create.JSXOpeningElement (cyclomatic 17) · ×1
  • create.JSXOpeningElement (cyclomatic 17) packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:91 — create.JSXOpeningElement has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong 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 · attachRollupHooks.writeBundle (cyclomatic 17) · ×1
  • attachRollupHooks.writeBundle (cyclomatic 17) packages/@stylexjs/unplugin/src/rollup.js:39 — attachRollupHooks.writeBundle 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 · normalizeZeroDimensions (cyclomatic 17) · ×1
  • normalizeZeroDimensions (cyclomatic 17) packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.js:24 — normalizeZeroDimensions has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 34). 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 · stylex-enforce-extension.checkExports (cyclomatic 16) · ×1
  • stylex-enforce-extension.checkExports (cyclomatic 16) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:267 — stylex-enforce-extension.checkExports has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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 · search-dialog.transformDocSearchResults (cyclomatic 16) · ×1
  • search-dialog.transformDocSearchResults (cyclomatic 16) packages/docs/src/components/search-dialog.tsx:110 — search-dialog.transformDocSearchResults 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 · create.checkExports (cyclomatic 16) · ×1
  • create.checkExports (cyclomatic 16) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:267 — create.checkExports has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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 · transformStyleXViewTransitionClass (cyclomatic 16) · ×1
  • transformStyleXViewTransitionClass (cyclomatic 16) packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js:30 — transformStyleXViewTransitionClass has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · transformStyleXPositionTry (cyclomatic 16) · ×1
  • transformStyleXPositionTry (cyclomatic 16) packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26 — transformStyleXPositionTry has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · findBestMatchingResource · ×1
  • findBestMatchingResource::scoreResourceUrl (cyclomatic 16) packages/@stylexjs/devtools-extension/src/utils/resourceMatching.js:84 — findBestMatchingResource::scoreResourceUrl has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · validateNamespace (cyclomatic 16) · ×1
  • validateNamespace (cyclomatic 16) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/basic-validation.js:13 — validateNamespace 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×1
  • Repeated repair: packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js:547 — packages/@stylexjs/eslint-plugin/src/reference/cssProperties.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 11 (its worst body is cssProperties.border at line 547), 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: recognize progress pseudo-elements (#1968)”; “Fix #1701: allow numeric values for grid line properties (#1730)”; “Fix signals (#1804)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 23:08:08 -04:00' --until='2026-10-29 23:08:08 -04:00' --full-history --no-merges -- packages/@stylexjs/eslint-plugin/src/reference/cssProperties.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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment packages/docs/src/pages/blog/_layout.tsx:13 — // HACK: — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · _evaluate (cognitive 343) · ×1
  • _evaluate (cognitive 343) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483 — _evaluate has cognitive complexity 343 (threshold 15). Drivers by points: if/else 115 (258 pts), boolean chains 38, ternaries 7 (22 pts), other 14, match/switch 3 (6 pts), loops 3 (5 pts) (nesting depth added 163). Of this number, 328 points are the body's own statements and 15 belong to 6 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 · create.checkStyleProperty (cognitive 215) · ×1
  • create.checkStyleProperty (cognitive 215) REDACTED:640 — create.checkStyleProperty has cognitive complexity 215 (threshold 15). Drivers by points: if/else 40 (124 pts), ternaries 14 (52 pts), boolean chains 29, loops 2 (8 pts), other 2 (nesting depth added 128). Of this number, 197 points are the body's own statements and 18 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · transformStyleXCreate (cognitive 215) · ×1
  • transformStyleXCreate (cognitive 215) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:108 — transformStyleXCreate has cognitive complexity 215 (threshold 15). Drivers by points: if/else 32 (120 pts), ternaries 11 (62 pts), boolean chains 17, loops 2 (13 pts), other 3 (nesting depth added 150). Of this number, 30 points are the body's own statements and 185 belong to 27 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 · stylex-valid-styles.checkStyleProperty (cognitive 210) · ×1
  • stylex-valid-styles.checkStyleProperty (cognitive 210) REDACTED:640 — stylex-valid-styles.checkStyleProperty has cognitive complexity 210 (threshold 15). Drivers by points: if/else 40 (126 pts), ternaries 12 (51 pts), boolean chains 25, loops 2 (8 pts) (nesting depth added 131). Of this number, 196 points are the body's own statements and 14 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · index.styleXTransform (cognitive 182) · ×1
  • index.styleXTransform (cognitive 182) REDACTED:60 — index.styleXTransform has cognitive complexity 182 (threshold 15). Drivers by points: if/else 39 (99 pts), ternaries 6 (54 pts), loops 6 (18 pts), boolean chains 11 (nesting depth added 120). Most of this is not in the body itself: 12 of the 182 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 214, 98, 77, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · imports.readImportDeclarations (cognitive 170) · ×1
  • imports.readImportDeclarations (cognitive 170) packages/@stylexjs/babel-plugin/src/visitors/imports.js:18 — imports.readImportDeclarations has cognitive complexity 170 (threshold 15). Drivers by points: if/else 32 (151 pts), ternaries 2 (9 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 128). 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 · imports.readRequires (cognitive 130) · ×1
  • imports.readRequires (cognitive 130) packages/@stylexjs/babel-plugin/src/visitors/imports.js:150 — imports.readRequires has cognitive complexity 130 (threshold 15). Drivers by points: if/else 29 (120 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 95). 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 · splitSpecificShorthands (cognitive 120) · ×1
  • splitSpecificShorthands (cognitive 120) REDACTED:1058 — splitSpecificShorthands has cognitive complexity 120 (threshold 15). Drivers by points: if/else 37 (65 pts), ternaries 11 (27 pts), boolean chains 16, other 8, loops 2 (4 pts) (nesting depth added 46). To reduce it, split the body into named stages: move each independent 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 · findMatchingClosingBraceLine (cognitive 103) · ×1
  • findMatchingClosingBraceLine (cognitive 103) packages/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:15 — findMatchingClosingBraceLine has cognitive complexity 103 (threshold 15). Drivers by points: if/else 24 (83 pts), boolean chains 11, loops 2 (3 pts), other 3, ternaries 2 (3 pts) (nesting depth added 61). To reduce it, split the body into named stages: move each independent 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 · flatten-raw-style-obj._flattenRawStyleObject (cognitive 102) · ×1
  • flatten-raw-style-obj._flattenRawStyleObject (cognitive 102) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:39 — flatten-raw-style-obj._flattenRawStyleObject has cognitive complexity 102 (threshold 15). Drivers by points: if/else 15 (37 pts), ternaries 8 (33 pts), loops 9 (28 pts), boolean chains 4 (nesting depth added 66). Of this number, 76 points are the body's own statements and 26 belong to 4 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · core.unpluginFactory (cognitive 78) · ×1
  • core.unpluginFactory (cognitive 78) REDACTED:229 — core.unpluginFactory has cognitive complexity 78 (threshold 15). Drivers by points: if/else 24 (41 pts), boolean chains 13, error handling 8 (11 pts), loops 5 (8 pts), ternaries 5 (nesting depth added 23). Of this number, 39 points are the body's own statements and 39 belong to 9 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mergeIntervalsForAnd (cognitive 77) · ×1
  • mergeIntervalsForAnd (cognitive 77) packages/style-value-parser/src/at-queries/media-query.js:356 — mergeIntervalsForAnd has cognitive complexity 77 (threshold 15). Drivers by points: if/else 18 (41 pts), boolean chains 15, ternaries 4 (14 pts), loops 5 (7 pts) (nesting depth added 35). Of this number, 73 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create.checkStyleProperty (cognitive 73) · ×1
  • create.checkStyleProperty (cognitive 73) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — create.checkStyleProperty has cognitive complexity 73 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 20, ternaries 8 (16 pts), loops 2 (6 pts), other 2 (nesting depth added 22). Of this number, 66 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stylex-no-nonstandard-styles.checkStyleProperty (cognitive 70) · ×1
  • stylex-no-nonstandard-styles.checkStyleProperty (cognitive 70) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — stylex-no-nonstandard-styles.checkStyleProperty has cognitive complexity 70 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 18, ternaries 6 (17 pts), loops 2 (6 pts) (nesting depth added 25). Of this number, 66 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stylex-props.transformStylexProps (cognitive 67) · ×1
  • stylex-props.transformStylexProps (cognitive 67) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:62 — stylex-props.transformStylexProps has cognitive complexity 67 (threshold 15). Drivers by points: if/else 42 (100 pts), boolean chains 18, ternaries 3 (6 pts), loops 2 (3 pts) (nesting depth added 62). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · resolveMediaTypes (cognitive 62) · ×1
  • resolveMediaTypes (cognitive 62) packages/style-value-parser/src/at-queries/media-query.js:623 — resolveMediaTypes has cognitive complexity 62 (threshold 15). Drivers by points: if/else 21 (51 pts), loops 3 (7 pts), boolean chains 2, match/switch 1, other 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · processStylexRules (cognitive 60) · ×1
  • processStylexRules (cognitive 60) REDACTED:680 — processStylexRules has cognitive complexity 60 (threshold 15). Drivers by points: if/else 23 (32 pts), ternaries 9 (11 pts), boolean chains 7, loops 5, other 5 (nesting depth added 11). Most of this is not in the body itself: 13 of the 60 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 823, a function literal at line 844, resolveConstant, …). 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 · evaluatePartialObjectRecursively (cognitive 57) · ×1
  • evaluatePartialObjectRecursively (cognitive 57) REDACTED:119 — evaluatePartialObjectRecursively has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (37 pts), ternaries 3 (15 pts), boolean chains 3, loops 1, other 1 (nesting depth added 36). Of this number, 56 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · index.PlaygroundNew (cognitive 53) · ×1
  • index.PlaygroundNew (cognitive 53) packages/docs/src/components/Playground/index.tsx:271 — index.PlaygroundNew has cognitive complexity 53 (threshold 15). Drivers by points: if/else 25 (28 pts), boolean chains 11, ternaries 8 (9 pts), loops 3, error handling 2 (nesting depth added 4). Most of this is not in the body itself: 8 of the 53 points are its own statements and the rest belongs to 23 function items inside it that branch (updateSandpack, deleteFile, renameFile, …). 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 · create (cognitive 53) · ×1
  • create (cognitive 53) REDACTED:272 — create has cognitive complexity 53 (threshold 15). Drivers by points: if/else 11 (26 pts), ternaries 6 (11 pts), boolean chains 8, loops 3 (8 pts) (nesting depth added 25). Of this number, 46 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 · create.ImportDeclaration (cognitive 48) · ×1
  • create.ImportDeclaration (cognitive 48) REDACTED:1119 — create.ImportDeclaration has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (39 pts), boolean chains 9 (nesting depth added 22). Most of this is not in the body itself: 10 of the 48 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 1147, 1194, 1128, …). 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 · search-dialog.SearchDialog (cognitive 43) · ×1
  • search-dialog.SearchDialog (cognitive 43) packages/docs/src/components/search-dialog.tsx:232 — search-dialog.SearchDialog has cognitive complexity 43 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 19, ternaries 3, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 8 of the 43 points are its own statements and the rest belongs to 13 function literals inside it that branch (lines 338, 461, 329, …). 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 · create.validateStyleValue (cognitive 39) · ×1
  • create.validateStyleValue (cognitive 39) REDACTED:496 — create.validateStyleValue has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 10, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expandAnimationShorthand (cognitive 39) · ×1
  • expandAnimationShorthand (cognitive 39) REDACTED:711 — expandAnimationShorthand has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 7, 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 · splitShorthands.expandBackgroundShorthand (cognitive 38) · ×1
  • splitShorthands.expandBackgroundShorthand (cognitive 38) REDACTED:856 — splitShorthands.expandBackgroundShorthand has cognitive complexity 38 (threshold 15). Drivers by points: if/else 19 (29 pts), boolean chains 5, loops 2, ternaries 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 · SourceRow.SourceRow (cognitive 37) · ×1
  • SourceRow.SourceRow (cognitive 37) packages/@stylexjs/devtools-extension/src/panel/components/SourceRow.js:24 — SourceRow.SourceRow has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 17 (29 pts), boolean chains 4, if/else 4 (nesting depth added 12). Of this number, 26 points are the body's own statements and 11 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stylex-valid-styles.validateStyleValue (cognitive 37) · ×1
  • stylex-valid-styles.validateStyleValue (cognitive 37) REDACTED:496 — stylex-valid-styles.validateStyleValue has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 8, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStyleXMerge (cognitive 37) · ×1
  • transformStyleXMerge (cognitive 37) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:47 — transformStyleXMerge has cognitive complexity 37 (threshold 15). Drivers by points: if/else 25 (58 pts), boolean chains 10, ternaries 3 (10 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 42). 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 · state-manager.filePathResolver (cognitive 36) · ×1
  • state-manager.filePathResolver (cognitive 36) REDACTED:864 — state-manager.filePathResolver has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 4 (11 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent 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 36) · ×1
  • (anonymous) (cognitive 36) REDACTED:869 — (anonymous) has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 4 (11 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent 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 · evaluate-path.isMutated (cognitive 35) · ×1
  • evaluate-path.isMutated (cognitive 35) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:194 — evaluate-path.isMutated has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 6, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parseNullableStyle (cognitive 35) · ×1
  • parseNullableStyle (cognitive 35) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:357 — parseNullableStyle has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 11 (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 · #toString (cognitive 34) · ×1
  • #toString (cognitive 34) packages/style-value-parser/src/at-queries/media-query.js:726 — #toString has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 5 (11 pts), boolean chains 8, match/switch 1 (nesting depth added 13). Of this number, 27 points are the body's own statements and 7 belong to 3 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · valueSyntax.walkCssSyntax (cognitive 33) · ×1
  • valueSyntax.walkCssSyntax (cognitive 33) packages/@stylexjs/devtools-extension/src/utils/valueSyntax.js:29 — valueSyntax.walkCssSyntax has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · unpluginFactory · ×1
  • unpluginFactory::transform (cognitive 32) REDACTED:430 — unpluginFactory::transform has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · createOrderedCSSStyleSheet.createOrderedCSSStyleSheet · ×1
  • createOrderedCSSStyleSheet.createOrderedCSSStyleSheet::update (cognitive 31) packages/@stylexjs/stylex/src/stylesheet/createOrderedCSSStyleSheet.js:117 — createOrderedCSSStyleSheet.createOrderedCSSStyleSheet::update has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (6 pts), error handling 1 (5 pts), 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 · stylex-enforce-extension.reportErrors (cognitive 30) · ×1
  • stylex-enforce-extension.reportErrors (cognitive 30) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316 — stylex-enforce-extension.reportErrors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 11, ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · (anonymous) (cognitive 30) · ×1
  • (anonymous) (cognitive 30) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js:264 — (anonymous) has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 7, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create.reportErrors (cognitive 30) · ×1
  • create.reportErrors (cognitive 30) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316 — create.reportErrors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 11, ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ComboBox (cognitive 30) · ×1
  • ComboBox (cognitive 30) packages/@stylexjs/devtools-extension/src/panel/components/ComboBox.js:16 — ComboBox has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 7 (10 pts), boolean chains 6, error handling 1 (2 pts), other 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 96, commit, a function literal at line 101, …). 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 · renderMatchedStyles (cognitive 30) · ×1
  • renderMatchedStyles (cognitive 30) packages/@stylexjs/devtools-extension/src/utils/exportMetadata.js:43 — renderMatchedStyles has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 5 (9 pts), ternaries 2 (5 pts), other 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 · transformStyleXCreateTheme (cognitive 29) · ×1
  • transformStyleXCreateTheme (cognitive 29) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 — transformStyleXCreateTheme has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 5, other 3 (nesting depth added 9). Of this number, 24 points are the body's own statements and 5 belong to 10 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 · validateNamespace (cognitive 28) · ×1
  • validateNamespace (cognitive 28) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/basic-validation.js:13 — validateNamespace has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStylexProps · ×1
  • transformStylexProps::MemberExpression (cognitive 27) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:206 — transformStylexProps::MemberExpression has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7, ternaries 2 (5 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 · declarationAnalysis.splitTopLevel (cognitive 26) · ×1
  • declarationAnalysis.splitTopLevel (cognitive 26) packages/@stylexjs/devtools-extension/src/inspected/declarationAnalysis.js:34 — declarationAnalysis.splitTopLevel has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stylex-valid-shorthands.validateProperty (cognitive 26) · ×1
  • stylex-valid-shorthands.validateProperty (cognitive 26) packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148 — stylex-valid-shorthands.validateProperty has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 11, if/else 10, ternaries 3 (5 pts) (nesting depth added 2). Of this number, 22 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · generate-types.generateTypes (cognitive 26) · ×1
  • generate-types.generateTypes (cognitive 26) packages/scripts/flow-translator/generate-types.js:16 — generate-types.generateTypes has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), error handling 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStyleXDefineVars (cognitive 26) · ×1
  • transformStyleXDefineVars (cognitive 26) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:48 — transformStyleXDefineVars has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (2 pts), other 1 (nesting depth added 10). Of this number, 21 points are the body's own statements and 5 belong to 13 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · finishSetup (cognitive 26) · ×1
  • finishSetup (cognitive 26) packages/@stylexjs/create-stylex-app/src/index.js:375 — finishSetup has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 3 (6 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStyleXMerge · ×1
  • transformStyleXMerge::MemberExpression (cognitive 26) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:143 — transformStyleXMerge::MemberExpression has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6, ternaries 2 (5 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 · create.validateProperty (cognitive 26) · ×1
  • create.validateProperty (cognitive 26) packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148 — create.validateProperty has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 10, ternaries 3. Of this number, 23 points are the body's own statements and 3 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · stylexPlugin.transform (cognitive 26) · ×1
  • stylexPlugin.transform (cognitive 26) packages/@stylexjs/rollup-plugin/src/index.js:118 — stylexPlugin.transform has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 11). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.main (cognitive 25) · ×1
  • index.main (cognitive 25) packages/@stylexjs/create-stylex-app/src/index.js:131 — index.main has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 3 (6 pts), error handling 2, loops 2, boolean chains 1 (nesting depth added 5). Of this number, 21 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · splitShorthands.expandFontShorthand (cognitive 25) · ×1
  • splitShorthands.expandFontShorthand (cognitive 25) REDACTED:972 — splitShorthands.expandFontShorthand has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getPropertyPriorityAndType.getPropertyPriorityAndType (cognitive 25) · ×1
  • getPropertyPriorityAndType.getPropertyPriorityAndType (cognitive 25) packages/@stylexjs/eslint-plugin/src/utils/getPropertyPriorityAndType.js:38 — getPropertyPriorityAndType.getPropertyPriorityAndType has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17 (24 pts), 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 · setOptions (cognitive 25) · ×1
  • setOptions (cognitive 25) REDACTED:215 — setOptions has cognitive complexity 25 (threshold 15). Drivers by points: other 20, ternaries 4, if/else 1. Of this number, 24 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · (anonymous) (cognitive 25) · ×1
  • (anonymous) (cognitive 25) packages/style-value-parser/src/token-parser.js:554 — (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). Of this number, 23 points are the body's own statements and 2 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · attachViteHooks.writeBundle (cognitive 25) · ×1
  • attachViteHooks.writeBundle (cognitive 25) packages/@stylexjs/unplugin/src/vite.js:174 — attachViteHooks.writeBundle has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 4 (7 pts), ternaries 2 (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 · styleXCompile (cognitive 25) · ×1
  • styleXCompile (cognitive 25) packages/@stylexjs/cli/src/index.js:92 — styleXCompile has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 3 (7 pts), error handling 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). Of this number, 22 points are the body's own statements and 3 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 · styleXCreateSet (cognitive 25) · ×1
  • styleXCreateSet (cognitive 25) packages/@stylexjs/babel-plugin/src/shared/stylex-create.js:41 — styleXCreateSet has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 3 (9 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 14). Of this number, 13 points are the body's own statements and 12 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.
D2 · Cognitive Complexity · vite.attachViteHooks.writeBundle (cognitive 24) · ×1
  • vite.attachViteHooks.writeBundle (cognitive 24) packages/@stylexjs/unplugin/src/vite.js:174 — vite.attachViteHooks.writeBundle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 4 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · collectWidthBounds (cognitive 24) · ×1
  • collectWidthBounds (cognitive 24) REDACTED:520 — collectWidthBounds has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (6 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create.Property (cognitive 24) · ×1
  • create.Property (cognitive 24) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:255 — create.Property has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 10, other 1 (nesting depth added 3). Of this number, 21 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · addSourceMapData (cognitive 24) · ×1
  • addSourceMapData (cognitive 24) packages/@stylexjs/babel-plugin/src/utils/add-sourcemap-data.js:79 — addSourceMapData has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 9, ternaries 1 (3 pts), loops 1 (nesting depth added 8). Of this number, 19 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 · attachRollupHooks.writeBundle (cognitive 24) · ×1
  • attachRollupHooks.writeBundle (cognitive 24) packages/@stylexjs/unplugin/src/rollup.js:39 — attachRollupHooks.writeBundle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 4 (7 pts), ternaries 2 (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 · attachEsbuildHooks (cognitive 24) · ×1
  • attachEsbuildHooks (cognitive 24) packages/@stylexjs/unplugin/src/esbuild.js:15 — attachEsbuildHooks has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 3 (5 pts), error handling 3 (4 pts) (nesting depth added 5). None of this is in the body itself: all 24 points belong to 8 function items inside it that branch (a function literal at line 21, setup, a function literal at line 34, …). 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 · stylex-enforce-extension.checkDefaultExport (cognitive 23) · ×1
  • stylex-enforce-extension.checkDefaultExport (cognitive 23) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165 — stylex-enforce-extension.checkDefaultExport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.stylexPlugin.transform (cognitive 23) · ×1
  • index.stylexPlugin.transform (cognitive 23) packages/@stylexjs/rollup-plugin/src/index.js:118 — index.stylexPlugin.transform has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (2 pts), 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 · core.replaceBundleReferences (cognitive 23) · ×1
  • core.replaceBundleReferences (cognitive 23) REDACTED:88 — core.replaceBundleReferences has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 11). Of this number, 19 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rollup.attachRollupHooks.writeBundle (cognitive 23) · ×1
  • rollup.attachRollupHooks.writeBundle (cognitive 23) packages/@stylexjs/unplugin/src/rollup.js:39 — rollup.attachRollupHooks.writeBundle has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 4 (7 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createFix · ×1
  • createFix::getSortableGroup (cognitive 23) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:405 — createFix::getSortableGroup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 2, loops 1, other 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · create.checkDefaultExport (cognitive 23) · ×1
  • create.checkDefaultExport (cognitive 23) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:165 — create.checkDefaultExport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validateConditionalStyles (cognitive 23) · ×1
  • validateConditionalStyles (cognitive 23) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/basic-validation.js:55 — validateConditionalStyles has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 5, loops 2 (4 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 · ast-helpers.isVariableNamedExported (cognitive 22) · ×1
  • ast-helpers.isVariableNamedExported (cognitive 22) packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:216 — ast-helpers.isVariableNamedExported has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2, 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 · getDistance.getDistance (cognitive 22) · ×1
  • getDistance.getDistance (cognitive 22) packages/@stylexjs/eslint-plugin/src/utils/getDistance.js:36 — getDistance.getDistance has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 7 (9 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · splitShorthands.expandFlexShorthand (cognitive 22) · ×1
  • splitShorthands.expandFlexShorthand (cognitive 22) REDACTED:580 — splitShorthands.expandFlexShorthand has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getStaticPropertyName (cognitive 22) · ×1
  • getStaticPropertyName (cognitive 22) packages/@stylexjs/eslint-plugin/src/utils/getPropertyName.js:54 — getStaticPropertyName has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, match/switch 1, other 1 (nesting depth added 9). 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 · createCSSStyleSheet.createCSSStyleSheet (cognitive 20) · ×1
  • createCSSStyleSheet.createCSSStyleSheet (cognitive 20) packages/@stylexjs/stylex/src/stylesheet/createCSSStyleSheet.js:12 — createCSSStyleSheet.createCSSStyleSheet has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (5 pts) (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · collectComputedData (cognitive 20) · ×1
  • collectComputedData (cognitive 20) packages/@stylexjs/devtools-extension/src/inspected/collector.js:353 — collectComputedData has cognitive complexity 20 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (6 pts), error handling 1 (2 pts), boolean chains 1, other 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · compileDirectory (cognitive 20) · ×1
  • compileDirectory (cognitive 20) packages/@stylexjs/cli/src/transform.js:40 — compileDirectory has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 2 (6 pts), boolean chains 1, loops 1, other 1, ternaries 1 (nesting depth added 8). Of this number, 15 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 · overrideStore.applyOverrideMutation (cognitive 19) · ×1
  • overrideStore.applyOverrideMutation (cognitive 19) packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js:432 — overrideStore.applyOverrideMutation has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · isNumber.isNumber (cognitive 19) · ×1
  • isNumber.isNumber (cognitive 19) packages/@stylexjs/eslint-plugin/src/rules/isNumber.js:25 — isNumber.isNumber has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 2 (4 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.
D2 · Cognitive Complexity · isAnimationName.isAnimationName (cognitive 19) · ×1
  • isAnimationName.isAnimationName (cognitive 19) packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14 — isAnimationName.isAnimationName has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6 (nesting depth added 4). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 18, 67). 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 · isPositionTryFallbacks.isPositionTryFallbacks (cognitive 19) · ×1
  • isPositionTryFallbacks.isPositionTryFallbacks (cognitive 19) packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:14 — isPositionTryFallbacks.isPositionTryFallbacks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 6 (nesting depth added 4). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 18, 67). 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 · Tabs.Tab (cognitive 19) · ×1
  • Tabs.Tab (cognitive 19) packages/docs/src/components/Playground/Tabs.tsx:244 — Tabs.Tab has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 7 (8 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (commitRename, startLongPress, a function literal at line 358, …). 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 · create.CallExpression (cognitive 19) · ×1
  • create.CallExpression (cognitive 19) REDACTED:1224 — create.CallExpression has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 3 (nesting depth added 7). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 1239, 1277, 1265, …). 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 · registerStyles (cognitive 19) · ×1
  • registerStyles (cognitive 19) REDACTED:719 — registerStyles has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (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 · parseNullableStyle (cognitive 19) · ×1
  • parseNullableStyle (cognitive 19) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:222 — parseNullableStyle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 8 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformValue (cognitive 19) · ×1
  • transformValue (cognitive 19) packages/@stylexjs/babel-plugin/src/shared/utils/transform-value.js:18 — transformValue has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 93, 75, 71, …). 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 · isVariableNamedExported · ×1
  • isVariableNamedExported::ExportNamedDeclaration (cognitive 19) packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:235 — isVariableNamedExported::ExportNamedDeclaration has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, loops 1, other 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 · groupDeclarations (cognitive 19) · ×1
  • groupDeclarations (cognitive 19) packages/@stylexjs/devtools-extension/src/panel/declarations/model.js:38 — groupDeclarations has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), other 4, loops 2 (3 pts) (nesting depth added 8). Of this number, 15 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · transformStyleXKeyframes (cognitive 19) · ×1
  • transformStyleXKeyframes (cognitive 19) packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:26 — transformStyleXKeyframes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 6). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · borderSplitter (cognitive 19) · ×1
  • borderSplitter (cognitive 19) packages/@stylexjs/eslint-plugin/src/utils/split-css-value.js:65 — borderSplitter has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (7 pts), ternaries 3 (nesting depth added 1). Of this number, 11 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · createImportTracker.handleImportDeclaration (cognitive 19) · ×1
  • createImportTracker.handleImportDeclaration (cognitive 19) packages/@stylexjs/eslint-plugin/src/utils/createImportTracker.js:34 — createImportTracker.handleImportDeclaration has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2 (nesting depth added 7). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 54, 73, 42). 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 · (anonymous) (cognitive 19) · ×1
  • (anonymous) (cognitive 19) packages/@stylexjs/eslint-plugin/src/rules/isNumber.js:30 — (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 2 (4 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.
D2 · Cognitive Complexity · collector.collectStyleRule (cognitive 18) · ×1
  • collector.collectStyleRule (cognitive 18) packages/@stylexjs/devtools-extension/src/inspected/collector.js:194 — collector.collectStyleRule has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stylex-enforce-extension.checkExports (cognitive 18) · ×1
  • stylex-enforce-extension.checkExports (cognitive 18) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:267 — stylex-enforce-extension.checkExports has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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 · createSheet.createSheet (cognitive 18) · ×1
  • createSheet.createSheet (cognitive 18) packages/@stylexjs/stylex/src/stylesheet/createSheet.js:23 — createSheet.createSheet has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (6 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 · search-dialog.transformDocSearchResults (cognitive 18) · ×1
  • search-dialog.transformDocSearchResults (cognitive 18) packages/docs/src/components/search-dialog.tsx:110 — search-dialog.transformDocSearchResults has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 6, ternaries 1 (3 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 · evaluateImportedFile (cognitive 18) · ×1
  • evaluateImportedFile (cognitive 18) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:367 — evaluateImportedFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (ExportNamedDeclaration::finder, ExportNamedDeclaration). 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 · create.checkExports (cognitive 18) · ×1
  • create.checkExports (cognitive 18) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:267 — create.checkExports has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 281). 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 · create.CallExpression (cognitive 18) · ×1
  • create.CallExpression (cognitive 18) packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:87 — create.CallExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6 (nesting depth added 6). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 104, 94). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · create.JSXOpeningElement (cognitive 18) · ×1
  • create.JSXOpeningElement (cognitive 18) packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:91 — create.JSXOpeningElement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 6). 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, split the body into named stages: move each independent 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 · stylex-props.canHoistObject (cognitive 17) · ×1
  • stylex-props.canHoistObject (cognitive 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:512 — stylex-props.canHoistObject has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · makeVariableCheckingRule.makeVariableCheckingRule · ×1
  • makeVariableCheckingRule.makeVariableCheckingRule::varCheckingRule (cognitive 17) packages/@stylexjs/eslint-plugin/src/utils/makeVariableCheckingRule.js:19 — makeVariableCheckingRule.makeVariableCheckingRule::varCheckingRule has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · split-css-value.splitValue (cognitive 17) · ×1
  • split-css-value.splitValue (cognitive 17) packages/@stylexjs/eslint-plugin/src/utils/split-css-value.js:10 — split-css-value.splitValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getPropertyName.getStaticStringValue (cognitive 17) · ×1
  • getPropertyName.getStaticStringValue (cognitive 17) packages/@stylexjs/eslint-plugin/src/utils/getPropertyName.js:23 — getPropertyName.getStaticStringValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · (anonymous) (cognitive 17) · ×1
  • (anonymous) (cognitive 17) packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js:547 — (anonymous) has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3 (nesting depth added 7). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 548, 576, 561). 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 · styleXTransform · ×1
  • styleXTransform::exit::Identifier (cognitive 17) REDACTED:138 — styleXTransform::exit::Identifier has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStyleXViewTransitionClass (cognitive 17) · ×1
  • transformStyleXViewTransitionClass (cognitive 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js:30 — transformStyleXViewTransitionClass has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · transformStyleXPositionTry (cognitive 17) · ×1
  • transformStyleXPositionTry (cognitive 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26 — transformStyleXPositionTry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 5). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · transformStyleXDefineConsts (cognitive 17) · ×1
  • transformStyleXDefineConsts (cognitive 17) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:27 — transformStyleXDefineConsts has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, other 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · isStylexDefineVarsToken (cognitive 17) · ×1
  • isStylexDefineVarsToken (cognitive 17) packages/@stylexjs/eslint-plugin/src/rules/isStylexResolvedVarsToken.js:39 — isStylexDefineVarsToken has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 8). Of this number, 9 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · makeVariableCheckingRule (cognitive 17) · ×1
  • makeVariableCheckingRule (cognitive 17) packages/@stylexjs/eslint-plugin/src/utils/makeVariableCheckingRule.js:18 — makeVariableCheckingRule has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 6). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 24). 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 · documentPrinter.printDoc (cognitive 16) · ×1
  • documentPrinter.printDoc (cognitive 16) packages/@stylexjs/devtools-extension/src/panel/declarations/documentPrinter.js:117 — documentPrinter.printDoc has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 2 (6 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolveKey.resolveKey (cognitive 16) · ×1
  • resolveKey.resolveKey (cognitive 16) packages/@stylexjs/eslint-plugin/src/utils/resolveKey.js:13 — resolveKey.resolveKey has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), 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 · cssProperties.border (cognitive 16) · ×1
  • cssProperties.border (cognitive 16) packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js:547 — cssProperties.border has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2 (nesting depth added 7). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 548, 576). 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 · core.discoverStylexPackages (cognitive 16) · ×1
  • core.discoverStylexPackages (cognitive 16) REDACTED:180 — core.discoverStylexPackages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (4 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · evaluateStyleXCreateArg (cognitive 16) · ×1
  • evaluateStyleXCreateArg (cognitive 16) REDACTED:41 — evaluateStyleXCreateArg has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1, other 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 · findBestMatchingResource · ×1
  • findBestMatchingResource::scoreResourceUrl (cognitive 16) packages/@stylexjs/devtools-extension/src/utils/resourceMatching.js:84 — findBestMatchingResource::scoreResourceUrl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), other 5, ternaries 2, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · collectVarsByAtRule (cognitive 16) · ×1
  • collectVarsByAtRule (cognitive 16) packages/@stylexjs/babel-plugin/src/shared/stylex-vars-utils.js:22 — collectVarsByAtRule has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 5 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useDebugData (cognitive 16) · ×1
  • useDebugData (cognitive 16) packages/@stylexjs/devtools-extension/src/panel/hooks/useDebugData.js:15 — useDebugData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (6 pts), error handling 2 (nesting depth added 4). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 29, 59, 37, …). 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 · normalizeZeroDimensions (cognitive 16) · ×1
  • normalizeZeroDimensions (cognitive 16) packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/zero-dimensions.js:24 — normalizeZeroDimensions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, other 1. Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 34). 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.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: stylex-create-theme.js ↔ stylex-define-vars.js packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:1 — `packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js` and `packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js` change together 80% of the time (8 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 8 shared commits counted here, the most recent 3 are `8000a6c9` [babel-plugin] refactor defineVars and defineConsts var naming (#1129); `643ee39b` [babel-plugin] Fix theming in dev/debug mode; `a68e51dd` fix: typo in comment (at that commit the files were still `packages/babel-plugin/src/visitors/stylex-create-theme.js` and `packages/babel-plugin/src/visitors/stylex-define-vars.js`) — run `git show` on any of them.
IC1 · Incompleteness & stubs · Both branches are identical · ×1
  • Both branches are identical — the condition decides nothing REDACTED:409 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
P12 · CI test-gate honesty · Workspace package's tests never run by CI · ×1
  • Workspace package's tests never run by CI packages/@stylexjs/stylex/package.json:37 — `packages/@stylexjs/stylex` is a workspace package with 71 test(s) in 4 file(s) (e.g. `packages/@stylexjs/stylex/__tests__/createOrderedCSSStyleSheet-test.js`, `packages/@stylexjs/stylex/__tests__/createSheet-test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
R10 · Code Duplication · Duplication concentrated across 9 sibling directories (13 clone groups) · ×1
  • Duplication concentrated across 9 sibling directories (13 clone groups) packages/@stylexjs/babel-plugin/src/shared/hash.js:25 — 13 duplicated blocks under packages/@stylexjs/ have copies in at least two of the sibling directories babel-plugin, cli, devtools-extension, eslint-plugin, postcss-plugin, rollup-plugin (+3 more sibling(s) not listed) — 7 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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 (157 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (157 matched lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:128 — packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:128 · packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:191 — the two spans are one implementation copied and then locally edited — 911 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (85 lines × 2 locations) · ×1
  • Duplicated block (85 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315 — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:315 · REDACTED:1024 — 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 (81 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (81 matched lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26 — packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:26 · packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js:30 — the two spans are one implementation copied and then locally edited — 520 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 (72 lines × 2 locations) · ×1
  • Duplicated block (72 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14 — packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:14 · packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:14 — 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 (67 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (67 matched lines × 2 locations) packages/@stylexjs/unplugin/src/rollup.js:25 — packages/@stylexjs/unplugin/src/rollup.js:25 · packages/@stylexjs/unplugin/src/vite.js:159 — the two spans are one implementation copied and then locally edited — 453 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 (56 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (56 matched lines × 2 locations) packages/style-value-parser/src/css-types/easing-function.js:64 — packages/style-value-parser/src/css-types/easing-function.js:64 · REDACTED:73 — the two spans are one implementation copied and then locally edited — 428 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 (52 lines × 2 locations) · ×1
  • Duplicated block (52 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:96 — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:96 · packages/@stylexjs/babel-plugin/src/visitors/visitor-utils.js:134 — 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 (46 lines × 2 locations) · ×1
  • Duplicated block (46 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/hash.js:25 — packages/@stylexjs/babel-plugin/src/shared/hash.js:25 · packages/@stylexjs/cli/src/hash.js:25 — 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 (41 lines × 2 locations) · ×1
  • Duplicated block (41 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:102 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:102 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:114 — 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 (40 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (40 matched lines × 2 locations) REDACTED:404 — REDACTED:404 · REDACTED:469 — the two spans are one implementation copied and then locally edited — 271 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:64 — packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:64 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts.js:65 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:71 — packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:71 · packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js:66 — 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 (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:103 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:103 · packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:173 — 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 (32 lines × 2 locations) · ×1
  • Duplicated block (32 lines × 2 locations) packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:85 — packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:85 · packages/@stylexjs/babel-plugin/src/utils/ast-helpers.js:132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1
  • Duplicated block (31 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/stylex-keyframes.js:66 — packages/@stylexjs/babel-plugin/src/shared/stylex-keyframes.js:66 · packages/@stylexjs/babel-plugin/src/shared/stylex-position-try.js:54 — 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 (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:87 — packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:87 · packages/@stylexjs/devtools-extension/src/panel/components/Logo.js:117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:139 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:139 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:90 — 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 (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) packages/style-value-parser/src/at-queries/media-query.js:233 — packages/style-value-parser/src/at-queries/media-query.js:233 · packages/style-value-parser/src/at-queries/media-query.js:264 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) packages/style-value-parser/src/css-types/color.js:540 — packages/style-value-parser/src/css-types/color.js:540 · packages/style-value-parser/src/css-types/color.js:594 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (25 lines × 3 locations) · ×1
  • Duplicated block (25 lines × 3 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:49 — packages/@stylexjs/eslint-plugin/src/stylex-no-conflicting-props.js:49 · packages/@stylexjs/eslint-plugin/src/stylex-no-lookahead-selectors.js:29 · REDACTED:62 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme.js:34 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars.js:39 — 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 (22 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (22 matched lines × 2 locations) packages/@stylexjs/postcss-plugin/src/discovery.js:65 — packages/@stylexjs/postcss-plugin/src/discovery.js:65 · REDACTED:149 — the two spans are one implementation copied and then locally edited — 117 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/@stylexjs/eslint-plugin/src/rules/isAbsoluteLength.js:19 — packages/@stylexjs/eslint-plugin/src/rules/isAbsoluteLength.js:19 · packages/@stylexjs/eslint-plugin/src/rules/isRelativeLength.js:42 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:61 — packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:61 · packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:132 — 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 (19 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (19 matched lines × 2 locations) packages/@stylexjs/babel-plugin/src/visitors/imports.js:156 — packages/@stylexjs/babel-plugin/src/visitors/imports.js:156 · packages/@stylexjs/babel-plugin/src/visitors/imports.js:247 — the two spans are one implementation copied and then locally edited — 136 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (19 lines × 7 locations) · ×1
  • Duplicated block (19 lines × 7 locations) packages/style-value-parser/src/css-types/filter-function.js:50 — packages/style-value-parser/src/css-types/filter-function.js:50 · packages/style-value-parser/src/css-types/filter-function.js:70 · packages/style-value-parser/src/css-types/filter-function.js:90 · packages/style-value-parser/src/css-types/filter-function.js:175 · +3 more site(s) not listed — all 7 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/leading-zero.js:17 — packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/leading-zero.js:17 · packages/@stylexjs/babel-plugin/src/shared/utils/normalizers/timings.js:18 — 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 (17 lines × 3 locations) · ×1
  • Duplicated block (17 lines × 3 locations) packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:27 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:27 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:28 · packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js:27 — 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 _evaluate (cyclomatic 198, cognitive 328) · ×1
  • Complex function _evaluate (cyclomatic 198, cognitive 328) packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:483 — _evaluate has cyclomatic complexity 198 and cognitive complexity 328; 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 checkStyleProperty (cyclomatic 85, cognitive 197) · ×1
  • Complex function checkStyleProperty (cyclomatic 85, cognitive 197) REDACTED:640 — checkStyleProperty has cyclomatic complexity 85 and cognitive complexity 197; 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 splitSpecificShorthands (cyclomatic 79, cognitive 120) · ×1
  • Complex function splitSpecificShorthands (cyclomatic 79, cognitive 120) REDACTED:1058 — splitSpecificShorthands has cyclomatic complexity 79 and cognitive complexity 120; 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 mergeIntervalsForAnd (cyclomatic 49, cognitive 73) · ×1
  • Complex function mergeIntervalsForAnd (cyclomatic 49, cognitive 73) packages/style-value-parser/src/at-queries/media-query.js:356 — mergeIntervalsForAnd has cyclomatic complexity 49 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function checkStyleProperty (cyclomatic 49, cognitive 66) · ×1
  • Complex function checkStyleProperty (cyclomatic 49, cognitive 66) packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:155 — checkStyleProperty has cyclomatic complexity 49 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 readRequires (cyclomatic 48, cognitive 130) · ×1
  • Complex function readRequires (cyclomatic 48, cognitive 130) packages/@stylexjs/babel-plugin/src/visitors/imports.js:150 — readRequires has cyclomatic complexity 48 and cognitive complexity 130; 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 readImportDeclarations (cyclomatic 43, cognitive 170) · ×1
  • Complex function readImportDeclarations (cyclomatic 43, cognitive 170) packages/@stylexjs/babel-plugin/src/visitors/imports.js:18 — readImportDeclarations has cyclomatic complexity 43 and cognitive complexity 170; 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 findMatchingClosingBraceLine (cyclomatic 43, cognitive 103) · ×1
  • Complex function findMatchingClosingBraceLine (cyclomatic 43, cognitive 103) packages/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:15 — findMatchingClosingBraceLine has cyclomatic complexity 43 and cognitive complexity 103; 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 transformStylexProps (cyclomatic 33, cognitive 66) · ×1
  • Complex function transformStylexProps (cyclomatic 33, cognitive 66) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:62 — transformStylexProps has cyclomatic complexity 33 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 resolveMediaTypes (cyclomatic 31, cognitive 62) · ×1
  • Complex function resolveMediaTypes (cyclomatic 31, cognitive 62) packages/style-value-parser/src/at-queries/media-query.js:623 — resolveMediaTypes has cyclomatic complexity 31 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function validateStyleValue (cyclomatic 31, cognitive 39) · ×1
  • Complex function validateStyleValue (cyclomatic 31, cognitive 39) REDACTED:496 — validateStyleValue has cyclomatic complexity 31 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 _flattenRawStyleObject (cyclomatic 30, cognitive 77) · ×1
  • Complex function _flattenRawStyleObject (cyclomatic 30, cognitive 77) packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/flatten-raw-style-obj.js:39 — _flattenRawStyleObject has cyclomatic complexity 30 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function reportErrors (cyclomatic 30, cognitive 30) · ×1
  • Complex function reportErrors (cyclomatic 30, cognitive 30) packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:316 — reportErrors has cyclomatic complexity 30 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.
R2 · Cyclomatic Complexity · Complex function expandAnimationShorthand (cyclomatic 29, cognitive 39) · ×1
  • Complex function expandAnimationShorthand (cyclomatic 29, cognitive 39) REDACTED:711 — expandAnimationShorthand has cyclomatic complexity 29 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 expandBackgroundShorthand (cyclomatic 28, cognitive 38) · ×1
  • Complex function expandBackgroundShorthand (cyclomatic 28, cognitive 38) REDACTED:856 — expandBackgroundShorthand has cyclomatic complexity 28 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 parseNullableStyle (cyclomatic 27, cognitive 35) · ×1
  • Complex function parseNullableStyle (cyclomatic 27, cognitive 35) packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:357 — parseNullableStyle has cyclomatic complexity 27 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 validateProperty (cyclomatic 27, cognitive 23) · ×1
  • Complex function validateProperty (cyclomatic 27, cognitive 23) packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.js:148 — validateProperty has cyclomatic complexity 27 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 26, cognitive 123) · ×1
  • Complex function (anonymous) (cyclomatic 26, cognitive 123) REDACTED:214 — (anonymous) has cyclomatic complexity 26 and cognitive complexity 123; 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 Property (cyclomatic 26, cognitive 21) · ×1
  • Complex function Property (cyclomatic 26, cognitive 21) packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:255 — Property has cyclomatic complexity 26 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 setOptions (cyclomatic 25, cognitive 24) · ×1
  • Complex function setOptions (cyclomatic 25, cognitive 24) REDACTED:215 — setOptions has cyclomatic complexity 25 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js · ×1
  • packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js: 2328 lines of code packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js:1 — packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js has 2328 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1236 lines of code REDACTED:1 — REDACTED has 1236 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1236 lines of code REDACTED:1 — REDACTED has 1236 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/@stylexjs/babel-plugin/src/utils/evaluate-path.js · ×1
  • packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js: 1183 lines of code packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js:1 — packages/@stylexjs/babel-plugin/src/utils/evaluate-path.js has 1183 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 945 lines of code REDACTED:1 — REDACTED has 945 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/style-value-parser/src/at-queries/media-query.js · ×1
  • packages/style-value-parser/src/at-queries/media-query.js: 870 lines of code packages/style-value-parser/src/at-queries/media-query.js:1 — packages/style-value-parser/src/at-queries/media-query.js has 870 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/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js · ×1
  • packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js: 860 lines of code packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js:1 — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/application-order.js has 860 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 853 lines of code REDACTED:1 — REDACTED has 853 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 731 lines of code REDACTED:1 — REDACTED has 731 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/style-value-parser/src/css-types/color.js · ×1
  • packages/style-value-parser/src/css-types/color.js: 603 lines of code packages/style-value-parser/src/css-types/color.js:1 — packages/style-value-parser/src/css-types/color.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/style-value-parser/src/token-parser.js · ×1
  • packages/style-value-parser/src/token-parser.js: 603 lines of code packages/style-value-parser/src/token-parser.js:1 — packages/style-value-parser/src/token-parser.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js · ×1
  • packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js: 571 lines of code packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:1 — packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js has 571 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 547 lines of code REDACTED:1 — REDACTED has 547 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/@stylexjs/babel-plugin/src/visitors/stylex-create.js · ×1
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js: 539 lines of code packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js:1 — packages/@stylexjs/babel-plugin/src/visitors/stylex-create.js has 539 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/@stylexjs/babel-plugin/src/visitors/stylex-props.js · ×1
  • packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js: 532 lines of code packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js:1 — packages/@stylexjs/babel-plugin/src/visitors/stylex-props.js has 532 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/@stylexjs/devtools-extension/src/inspected/collector.js · ×1
  • packages/@stylexjs/devtools-extension/src/inspected/collector.js: 509 lines of code packages/@stylexjs/devtools-extension/src/inspected/collector.js:1 — packages/@stylexjs/devtools-extension/src/inspected/collector.js has 509 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js · ×1
  • packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js: 500 lines of code packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js:1 — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/legacy-expand-shorthands.js has 500 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/@stylexjs/devtools-extension/src/inspected/overrideStore.js · ×1
  • packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js: 481 lines of code packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js:1 — packages/@stylexjs/devtools-extension/src/inspected/overrideStore.js has 481 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 476 lines of code REDACTED:1 — REDACTED has 476 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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js · ×1
  • packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js: 441 lines of code packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:1 — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js has 441 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/@stylexjs/postcss-plugin/src/discovery.js · ×1
  • packages/@stylexjs/postcss-plugin/src/discovery.js: 426 lines of code packages/@stylexjs/postcss-plugin/src/discovery.js:1 — packages/@stylexjs/postcss-plugin/src/discovery.js has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js · ×1
  • packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js: 419 lines of code packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js:1 — packages/@stylexjs/eslint-plugin/src/stylex-enforce-extension.js has 419 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js:11 — This repository declares test tooling, and the ✓ above records that declaration — but packages/@stylexjs/cli/__tests__/__mocks__/source/components/button.js and 5 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~91 LoC) · ×1
  • Dead file (~91 LoC) packages/@stylexjs/babel-plugin/src/shared/utils/Rule.js — no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~49 LoC) · ×1
  • Dead file (~49 LoC) packages/style-value-parser/src/base-types.js — no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~37 LoC) · ×1
  • Dead file (~37 LoC) packages/@stylexjs/create-stylex-app/src/utils/files.js — no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~26 LoC) · ×1
  • Dead file (~26 LoC) packages/@stylexjs/babel-plugin/src/shared/validate.js — no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~12 LoC) · ×1
  • Dead file (~12 LoC) packages/@stylexjs/babel-plugin/src/utils/helpers.js — no import path from any entry point (54 application, 48 tooling, 162 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unlisted import '@babel/traverse' · ×1
  • Unlisted import '@babel/traverse' packages/@stylexjs/cli/src/plugins.js:11 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.
R8 · Dependency Hygiene · Unused dependency 'flow-bin' · ×1
  • Unused dependency 'flow-bin' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'non-stylex-lib' · ×1
  • Unused dependency 'non-stylex-lib' — Declared in packages/@stylexjs/postcss-plugin/__tests__/__auto_discovery_fixtures__/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 — 112 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:619 — `!!tokenBefore && isSameLine(tokenBefore, node)` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js, packages/@stylexjs/eslint-plugin/src/utils/getNodeIndentation.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/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:131 — `!state.options.enableInlinedConditionalMerge && conditional` appears character-identically in 2 files — packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-props.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/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:65 — `(node.type === 'MemberExpression' && node.object.type === 'Identifier' && importTracker.isStylexDefaultImport(node.object.name) && node.prop…` appears character-identically in 3 files — packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js, packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, packages/@stylexjs/eslint-plugin/src/stylex-valid-shorthands.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/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:156 — `(property.type === 'StringLiteral' || property.type === 'NumericLiteral') && computed` appears character-identically in 2 files — packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-props.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/@stylexjs/eslint-plugin/src/reference/cssProperties.js:527 — `NUMERIC_LITERAL_PROPERTIES.has(propertyKey) && NUMERIC_LITERAL_VALUE_REGEX.test(val)` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:643 — `aNode.loc && bNode.loc && aNode.loc?.start.line === bNode.loc?.start.line` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js, packages/@stylexjs/eslint-plugin/src/utils/getNodeIndentation.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/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:164 — `bailOutIndex != null && index > bailOutIndex` appears character-identically in 2 files — packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-props.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/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:52 — `character === '*' && nextCharacter === '/'` appears character-identically in 2 files — packages/@stylexjs/devtools-extension/src/utils/sourceSnippet.js, packages/@stylexjs/devtools-extension/src/utils/valueSyntax.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/@stylexjs/devtools-extension/src/utils/sourceSnippet.js:106 — `character === '/' && nextCharacter === '*'` appears character-identically in 2 files — packages/@stylexjs/devtools-extension/src/utils/sourceSnippet.js, packages/@stylexjs/devtools-extension/src/utils/valueSyntax.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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:353 — `decl.init != null && decl.init.type === 'CallExpression' && decl.init.callee.type === 'Identifier' && decl.init.callee.name === 'require'` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:370 — `decl.init != null && decl.init.type === 'CallExpression' && decl.init.callee.type === 'Identifier' && decl.init.callee.name === 'require' &&…` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js:64 — `init == null || !init.isCallExpression()` appears character-identically in 3 files — packages/@stylexjs/babel-plugin/src/visitors/stylex-keyframes.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-position-try.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.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/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:622 — `isTokenBeforeSameLineAsNode && tokenBefore?.loc` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js, packages/@stylexjs/eslint-plugin/src/utils/getNodeIndentation.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/@stylexjs/babel-plugin/src/shared/preprocess-rules/index.js:40 — `key.startsWith('var(') && key.endsWith(')')` appears character-identically in 2 files — packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/index.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:197 — `keyName.startsWith('@') || keyName.startsWith(':') || keyName === 'default'` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js:110 — `leftResolved !== 'other' || rightResolved === 'other'` appears character-identically in 2 files — packages/@stylexjs/babel-plugin/src/visitors/stylex-merge.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-props.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/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:167 — `level > 0 && propName == null && !(outerIsPseudoElement && level === 1)` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js:189 — `node && node.type === 'CallExpression' && isStylexCallee(node.callee) && node.arguments.length === 1` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-sort-keys.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:77 — `node && node.type === 'CallExpression' && isStylexCreateCallee(node.callee) && node.arguments.length === 1` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js, packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:1121 — `node.source.type !== 'Literal' || typeof node.source.value !== 'string'` appears character-identically in 2 files — REDACTED, packages/@stylexjs/eslint-plugin/src/utils/createImportTracker.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/@stylexjs/babel-plugin/src/shared/utils/split-css-value.js:44 — `node.type !== 'space' && node.type !== 'div'` appears character-identically in 3 files — packages/@stylexjs/babel-plugin/src/shared/utils/split-css-value.js, packages/@stylexjs/babel-plugin/src/shared/utils/transform-value.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/@stylexjs/eslint-plugin/src/utils/evaluate.js:25 — `node.type === 'Identifier' && variables != null` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/utils/evaluate.js, packages/@stylexjs/eslint-plugin/src/utils/makeVariableCheckingRule.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/@stylexjs/eslint-plugin/src/rules/isAnimationName.js:41 — `node.type === 'Identifier' && variables && variables.has(node.name)` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/rules/isAnimationName.js, packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.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/@stylexjs/eslint-plugin/src/reference/cssProperties.js:64 — `node.type === 'Literal' && typeof node.value === 'string'` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/reference/cssProperties.js, packages/@stylexjs/eslint-plugin/src/rules/isString.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/@stylexjs/eslint-plugin/src/utils/evaluate.js:19 — `node.type === 'TSSatisfiesExpression' || node.type === 'TSAsExpression'` appears character-identically in 2 files — packages/@stylexjs/eslint-plugin/src/utils/evaluate.js, packages/@stylexjs/eslint-plugin/src/utils/makeVariableCheckingRule.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.
D34 · Knowledge Freshness · Orphaned file · ×19
  • Orphaned file packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/postcss-plugin/src/discovery.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/shared/stylex-nested-utils.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/visitors/visitor-utils.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/postcss-plugin/src/plugin.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/visitors/stylex-create-theme-nested.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/typescript-tests/src/themes.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/visitors/stylex-define-consts-nested.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/babel-plugin/src/visitors/stylex-define-vars-nested.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/eslint-plugin/src/utils/getPropertyName.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/benchmarks/compare.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/eslint-plugin/src/utils/createImportTracker.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/benchmarks/size/run.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/create-stylex-app/src/utils/fetch-template.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/eslint-plugin/src/rules/isPositionTryFallbacks.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/@stylexjs/create-stylex-app/src/utils/packages.js:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
IC1 · Incompleteness & stubs · Disabled test · ×15
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:28 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:37 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-polyfills-test.js:50 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-stylex-create-test.js:1830 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-stylex-defineConsts-test.js:615 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/transform-stylex-viewTransitionClass-test.js:248 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:352 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:537 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:828 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/validation-stylex-create-test.js:864 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/@stylexjs/babel-plugin/__tests__/validation-stylex-defineConsts-test.js:231 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/style-value-parser/src/at-queries/__tests__/media-query-transform-test.js:316 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/style-value-parser/src/at-queries/__tests__/media-query-transform-test.js:340 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/style-value-parser/src/css-types/__tests__/calc-test.js:274 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test packages/style-value-parser/src/css-types/__tests__/filter-function-test.js:25 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D12 · Dependency Hygiene · Deprecated · ×13
  • Deprecated: @humanwhocodes/config-array REDACTED:2448 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @humanwhocodes/object-schema REDACTED:2462 — @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @ungap/structured-clone REDACTED:5872 — @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: eslint REDACTED:9561 — eslint 9.39.4 is resolved in REDACTED and is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: eslint REDACTED:9601 — eslint 9.39.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". 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:10726 — 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: glob REDACTED:10738 — glob 11.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: inflight REDACTED:11311 — 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: intersection-observer REDACTED:11368 — intersection-observer 0.10.0 is resolved in REDACTED and is marked deprecated by its publisher: "The Intersection Observer polyfill is no longer needed and can safely be removed. Intersection Observer has been Baseline since 2019.". 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:15677 — rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: tsconfck REDACTED:17323 — tsconfck 3.1.6 is resolved in REDACTED and is marked deprecated by its publisher: "unmaintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: uuid REDACTED:17821 — uuid 8.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: whatwg-encoding REDACTED:18252 — whatwg-encoding 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use @exodus/bytes instead for a more spec-conformant and faster implementation". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
D30 · Dependency Vulnerabilities · Low CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No direct assertions · ×4
  • No direct assertions: basic create packages/benchmarks/perf/tests/transform-create-tests.js:22 — No conventional assertion call was detected, and 4 of 4 tests in `packages/benchmarks` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: complex create packages/benchmarks/perf/tests/transform-create-tests.js:26 — No conventional assertion call was detected, and 4 of 4 tests in `packages/benchmarks` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: basic themes packages/benchmarks/perf/tests/transform-create-theme-tests.js:31 — No conventional assertion call was detected, and 4 of 4 tests in `packages/benchmarks` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: complex themes packages/benchmarks/perf/tests/transform-create-theme-tests.js:35 — No conventional assertion call was detected, and 4 of 4 tests in `packages/benchmarks` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
R7 · Dead Code · Unused module-local declaration 'OtherComponent' · ×4
  • Unused module-local declaration 'OtherComponent' packages/typescript-tests/src/test1.tsx:30 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
  • Unused module-local declaration 'OtherComponent' packages/typescript-tests/src/test2.tsx:35 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
  • Unused module-local declaration 'OtherComponent' packages/typescript-tests/src/test3.tsx:35 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
  • Unused module-local declaration 'OtherComponent' packages/typescript-tests/src/test4.tsx:35 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
D10 · Test Quality · Mock-dominated test · ×2
  • Mock-dominated test: creates a Firefox sidebar without calling unsupported setHeight packages/@stylexjs/devtools-extension/__tests__/browserAdapters-test.js:41 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: polls selection identity when Safari has no selection event packages/@stylexjs/devtools-extension/__tests__/browserAdapters-test.js:164 — This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 67 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D10 · Test Quality · Test project verifies nothing · ×1
  • Test project verifies nothing: packages/benchmarks packages/benchmarks/perf/tests/transform-create-tests.js:22 — No conventional assertion call was detected in 4 of 4 tests in `packages/benchmarks` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: packages/style-value-parser/src/token-parser.js. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (5 single-owned of 142 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 142 of the 306 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/@stylexjs/create-stylex-app/src/index.js, packages/@stylexjs/cli/src/cache.js, packages/@stylexjs/unplugin/src/consts.js, packages/@stylexjs/babel-plugin/src/shared/stylex-view-transition-class.js.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 16 project(s) overshoot their size bounds, lowering Project Cohesion to 8.8/10. The most over is `packages/docs` (10511 LoC, 97 module-visible types across 20 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 19 of 142 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 142 of the 306 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/@stylexjs/eslint-plugin/src/stylex-no-nonstandard-styles.js, packages/@stylexjs/postcss-plugin/src/discovery.js, packages/@stylexjs/babel-plugin/src/shared/stylex-nested-utils.js, REDACTED, packages/@stylexjs/babel-plugin/src/visitors/visitor-utils.js, packages/@stylexjs/babel-plugin/src/visitors/stylex-view-transition-class.js, packages/@stylexjs/eslint-plugin/src/stylex-no-legacy-contextual-styles.js, packages/@stylexjs/postcss-plugin/src/plugin.js (and 11 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/@stylexjs/cli`, `packages/scripts`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:3 — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 6129 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code · Unused export 'getExpandedKeys' · ×1
  • Unused export 'getExpandedKeys' packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/index.js:22 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'flattenObject' · ×1
  • Unused export 'flattenObject' packages/@stylexjs/babel-plugin/src/shared/utils/object-utils.js:26 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'objValues' · ×1
  • Unused export 'objValues' packages/@stylexjs/babel-plugin/src/shared/utils/object-utils.js:57 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'DEFAULT_IMPORT' · ×1
  • Unused export 'DEFAULT_IMPORT' packages/@stylexjs/babel-plugin/src/utils/evaluation-errors.js:19 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'XStyleWithout' · ×1
  • Unused export 'XStyleWithout' packages/@stylexjs/stylex/src/types/StyleXTypes.js:60 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'inherit' · ×1
  • Unused export 'inherit' packages/style-value-parser/src/css-types/common-types.js:35 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'initial' · ×1
  • Unused export 'initial' packages/style-value-parser/src/css-types/common-types.js:39 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'unset' · ×1
  • Unused export 'unset' packages/style-value-parser/src/css-types/common-types.js:43 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'revert' · ×1
  • Unused export 'revert' packages/style-value-parser/src/css-types/common-types.js:47 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'auto' · ×1
  • Unused export 'auto' packages/style-value-parser/src/css-types/common-types.js:51 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'OtherComponent2' · ×1
  • Unused module-local declaration 'OtherComponent2' packages/typescript-tests/src/test1.tsx:34 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'Correct' · ×1
  • Unused module-local declaration 'Correct' packages/typescript-tests/src/theming1.tsx:138 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'Incorrect' · ×1
  • Unused module-local declaration 'Incorrect' packages/typescript-tests/src/theming1.tsx:141 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~0.3 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 11328 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/docs/src/components/Playground/index.tsx (2), packages/docs/src/waku.server.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 46 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×46
  • Outdated (npm): @babel/core — @babel/core is pinned at 7.28.5; registry.npmjs.org publishes 8.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/helper-module-imports — @babel/helper-module-imports is pinned at 7.27.1; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-syntax-flow — @babel/plugin-syntax-flow is pinned at 7.27.1; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-syntax-jsx — @babel/plugin-syntax-jsx is pinned at 7.27.1; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/plugin-syntax-typescript — @babel/plugin-syntax-typescript is pinned at 7.27.1; registry.npmjs.org publishes 8.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/standalone — @babel/standalone is pinned at 7.28.5; registry.npmjs.org publishes 8.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/traverse — @babel/traverse is pinned at 7.28.5; registry.npmjs.org publishes 8.0.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @babel/types — @babel/types is pinned at 7.29.0; registry.npmjs.org publishes 8.0.10 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): @clack/prompts — @clack/prompts is pinned at 0.11.0; registry.npmjs.org publishes 1.8.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @csstools/css-tokenizer — @csstools/css-tokenizer is pinned at 3.0.4; registry.npmjs.org publishes 4.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-collapsible — @radix-ui/react-collapsible is pinned at 1.1.12; registry.npmjs.org publishes 1.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-navigation-menu — @radix-ui/react-navigation-menu is pinned at 1.2.14; registry.npmjs.org publishes 1.4.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-popover — @radix-ui/react-popover is pinned at 1.1.15; registry.npmjs.org publishes 1.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @radix-ui/react-presence — @radix-ui/react-presence is pinned at 1.1.5; registry.npmjs.org publishes 1.1.11 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): @radix-ui/react-scroll-area — @radix-ui/react-scroll-area is pinned at 1.2.10; registry.npmjs.org publishes 1.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): @remix-run/node-fetch-server — @remix-run/node-fetch-server is pinned at 0.12.0; registry.npmjs.org publishes 1.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): algoliasearch — algoliasearch is pinned at 5.46.2; registry.npmjs.org publishes 5.61.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): ansis — ansis is pinned at 3.17.0; registry.npmjs.org publishes 4.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): browserslist — browserslist is pinned at 4.28.0; registry.npmjs.org publishes 4.29.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): capnweb — capnweb is pinned at 0.2.0; registry.npmjs.org publishes 0.12.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): express — express is pinned at 5.2.1; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): fb-watchman — fb-watchman is pinned at 2.0.2; registry.npmjs.org publishes 2.0.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): feed — feed is pinned at 4.2.2; registry.npmjs.org publishes 6.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): flow-api-translator — flow-api-translator is pinned at 0.36.1; registry.npmjs.org publishes 0.337.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): fs-extra — fs-extra is pinned at 11.3.2; registry.npmjs.org publishes 11.4.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.
  • + 21 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-970d21bb2d1248e29c9b5f45a1808c9d/history.json --exit-code 0 --source .2artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-970d21bb2d1248e29c9b5f45a1808c9d/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude flow-typed --exclude packages/@stylexjs/cli/__tests__/__mocks__/snapshot/components --exclude packages/@stylexjs/cli/__tests__/__mocks__/snapshot/pages --exclude packages/@stylexjs/cli/__tests__/__mocks__/snapshot2/components --exclude packages/@stylexjs/cli/__tests__/__mocks__/snapshot2/pages .87artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update71artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 86 file(s) — `REDACTED`, `packages/@stylexjs/babel-plugin/src/shared/common-types.js`, `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-ltr.js`, `packages/@stylexjs/babel-plugin/src/shared/physical-rtl/generate-rtl.js`, `packages/@stylexjs/babel-plugin/src/shared/preprocess-rules/PreRule.js`, … (+81 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a18acc-cb1c-7d10-881e-6b7f8296e536 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 73 · Warnings: 553 · Recommendations: 112 · Info: 46 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 30-10-2026 @ 03:13 UTC.

Downloadable artifacts

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

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