Public report of gatsbyjs/gatsby, published 13 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 13 November 2026, 18:04 UTC · Survey ID cd_f75a183a9073455c8bacb4b61bda16b2
gatsbyjs/gatsby
Measured 13 November 2026, 18:01 UTC, at code version 0ac6c88
CAI scoreAt riskDown 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 129,104 lines of product code in 118 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Production Readiness, 30
Findings by how serious they are
452 critical1379 serious1240 minor
5 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 18:01 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
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. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
80of 80 dimensions measured by tools.
2730of 3071 findings point to an exact file and line, so you can open each one in the code. The other 341 concern the repository as a whole, such as missing documentation.
80dimensions across 7 lenses, read from 129,104 lines of product code in 118 projects.
gatsbyjs/gatsby is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies, and it has packages under a licence on your banned list. It scores 42 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step is replacing the 48 packages under a banned licence, worth about 10 points. Pinning the dependencies taken from a moving source comes next, worth about 6 points. Raising Production Readiness to 70 would lift the score to about 52.
323 known security holes in the packages the code depends on can be used by attackers. Forty-eight packages carry licence risk, and seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages, replacing or clearing the banned-licence packages and pinning each tool to an exact version would close these risks. The five passwords or keys in the code's history need replacing, with the old ones switched off. The four pipeline steps that run downloads without checking them need each download checked against a known checksum first. The 35 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 129,104 lines, about €180,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe 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.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 42 to about 52.
Code composition: what the lines of code are
Product code 63%Tests 37%
New since the last survey: 403 findings
These 403 critical or serious findings weren't in the previous survey, on 24 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 672 findings
These 672 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one. The first 100 are listed here.
€59,000 to €300,000, for 979 to 3,107 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 129,104 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 48 Banned license finding(s) in License Compliance — start with REDACTED (47), REDACTED.
Raises the score by about 10 points · Medium effort · License Compliance
2
Resolve the 93 Floating npm dependency finding(s) in Dependency Hygiene.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 3 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Production Readiness, at 30 (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 48 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for medium effort, because it clears the 48 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 15% on every change. The history of the code shows how much it changes: about 336 lines over the last 90 days, which is about 1,363 lines a year. At that pace, the extra work comes to an estimated 0.2 to 1.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
570 modules, with 388 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 530 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.
packages.gatsby-cli.src.reporter uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby-cli.src.reporter, while a change to packages.gatsby-cli.src.reporter can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby-cli.src.reporter uses a module listed above it, which is the healthy direction.
packages.gatsby-cli.src.reporter.redux.types uses packages.gatsby-cli.src.reporter.constants, so a change to packages.gatsby-cli.src.reporter.constants can break packages.gatsby-cli.src.reporter.redux.types, while a change to packages.gatsby-cli.src.reporter.redux.types can't break packages.gatsby-cli.src.reporter.constants.
Position
Below the diagonal: packages.gatsby-cli.src.reporter.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby-cli.src.reporter.redux.types uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby-cli.src.reporter.redux.types, while a change to packages.gatsby-cli.src.reporter.redux.types can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby-cli.src.reporter.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby-cli.src.reporter.reporter uses packages.gatsby-cli.src.reporter.constants, so a change to packages.gatsby-cli.src.reporter.constants can break packages.gatsby-cli.src.reporter.reporter, while a change to packages.gatsby-cli.src.reporter.reporter can't break packages.gatsby-cli.src.reporter.constants.
Position
Below the diagonal: packages.gatsby-cli.src.reporter.reporter uses a module listed above it, which is the healthy direction.
packages.gatsby-cli.src.reporter.reporter uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby-cli.src.reporter.reporter, while a change to packages.gatsby-cli.src.reporter.reporter can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby-cli.src.reporter.reporter uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-utils.src uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby-plugin-utils.src, while a change to packages.gatsby-plugin-utils.src can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby-plugin-utils.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-utils.src uses packages.gatsby-cli.src.reporter.constants, so a change to packages.gatsby-cli.src.reporter.constants can break packages.gatsby-plugin-utils.src, while a change to packages.gatsby-plugin-utils.src can't break packages.gatsby-cli.src.reporter.constants.
Position
Below the diagonal: packages.gatsby-plugin-utils.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-utils.src uses packages.gatsby-plugin-utils.src.types, so a change to packages.gatsby-plugin-utils.src.types can break packages.gatsby-plugin-utils.src, while a change to packages.gatsby-plugin-utils.src can't break packages.gatsby-plugin-utils.src.types.
Position
Below the diagonal: packages.gatsby-plugin-utils.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.gatsby-plugin-utils.src uses a type in packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type.
packages.gatsby-plugin-utils.src uses packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type, so a change to packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type can break packages.gatsby-plugin-utils.src, while a change to packages.gatsby-plugin-utils.src can't break packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type.
Position
Below the diagonal: packages.gatsby-plugin-utils.src uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a type in deprecated-packages.gatsby-telemetry.src.store.
packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql, while a change to packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a type in packages.gatsby-cli.src.reporter.constants.
packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses packages.gatsby-cli.src.reporter.constants, so a change to packages.gatsby-cli.src.reporter.constants can break packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql, while a change to packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql can't break packages.gatsby-cli.src.reporter.constants.
Position
Below the diagonal: packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a type in packages.gatsby-plugin-image.src.image-utils.
packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses packages.gatsby-plugin-image.src.image-utils, so a change to packages.gatsby-plugin-image.src.image-utils can break packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql, while a change to packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql can't break packages.gatsby-plugin-image.src.image-utils.
Position
Below the diagonal: packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a module listed above it, which is the healthy direction.
7 pairs of types, where a type in packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a type in packages.gatsby-plugin-utils.src.polyfill-remote-file.types.
packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses packages.gatsby-plugin-utils.src.polyfill-remote-file.types, so a change to packages.gatsby-plugin-utils.src.polyfill-remote-file.types can break packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql, while a change to packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql can't break packages.gatsby-plugin-utils.src.polyfill-remote-file.types.
Position
Below the diagonal: packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.gatsby.src.schema.types uses a type in packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type.
packages.gatsby.src.schema.types uses packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type, so a change to packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type can break packages.gatsby.src.schema.types, while a change to packages.gatsby.src.schema.types can't break packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type.
Position
Below the diagonal: packages.gatsby.src.schema.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.schema.types uses packages.gatsby.src.schema.type-definitions, so a change to packages.gatsby.src.schema.type-definitions can break packages.gatsby.src.schema.types, while a change to packages.gatsby.src.schema.types can't break packages.gatsby.src.schema.type-definitions.
Position
Below the diagonal: packages.gatsby.src.schema.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils.adapter.types uses packages.gatsby-page-utils.src.apply-trailing-slash-option, so a change to packages.gatsby-page-utils.src.apply-trailing-slash-option can break packages.gatsby.src.utils.adapter.types, while a change to packages.gatsby.src.utils.adapter.types can't break packages.gatsby-page-utils.src.apply-trailing-slash-option.
Position
Below the diagonal: packages.gatsby.src.utils.adapter.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils.cache uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.utils.cache, while a change to packages.gatsby.src.utils.cache can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.utils.cache uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-page-creator.src uses packages.gatsby-cli.src.reporter.constants, so a change to packages.gatsby-cli.src.reporter.constants can break packages.gatsby-plugin-page-creator.src, while a change to packages.gatsby-plugin-page-creator.src can't break packages.gatsby-cli.src.reporter.constants.
Position
Below the diagonal: packages.gatsby-plugin-page-creator.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-page-creator.src uses packages.gatsby-page-utils.src.apply-trailing-slash-option, so a change to packages.gatsby-page-utils.src.apply-trailing-slash-option can break packages.gatsby-plugin-page-creator.src, while a change to packages.gatsby-plugin-page-creator.src can't break packages.gatsby-page-utils.src.apply-trailing-slash-option.
Position
Below the diagonal: packages.gatsby-plugin-page-creator.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-page-creator.src uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby-plugin-page-creator.src, while a change to packages.gatsby-plugin-page-creator.src can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby-plugin-page-creator.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-sharp.src uses packages.gatsby-plugin-image.src.image-utils, so a change to packages.gatsby-plugin-image.src.image-utils can break packages.gatsby-plugin-sharp.src, while a change to packages.gatsby-plugin-sharp.src can't break packages.gatsby-plugin-image.src.image-utils.
Position
Below the diagonal: packages.gatsby-plugin-sharp.src uses a module listed above it, which is the healthy direction.
packages.gatsby-plugin-sharp.src uses packages.gatsby.src.utils.cache, so a change to packages.gatsby.src.utils.cache can break packages.gatsby-plugin-sharp.src, while a change to packages.gatsby-plugin-sharp.src can't break packages.gatsby.src.utils.cache.
Position
Below the diagonal: packages.gatsby-plugin-sharp.src uses a module listed above it, which is the healthy direction.
packages.gatsby-source-shopify.src uses packages.gatsby-plugin-image.src.components.gatsby-image_browser, so a change to packages.gatsby-plugin-image.src.components.gatsby-image_browser can break packages.gatsby-source-shopify.src, while a change to packages.gatsby-source-shopify.src can't break packages.gatsby-plugin-image.src.components.gatsby-image_browser.
Position
Below the diagonal: packages.gatsby-source-shopify.src uses a module listed above it, which is the healthy direction.
packages.gatsby-source-shopify.src uses packages.gatsby.src.utils.cache, so a change to packages.gatsby.src.utils.cache can break packages.gatsby-source-shopify.src, while a change to packages.gatsby-source-shopify.src can't break packages.gatsby.src.utils.cache.
Position
Below the diagonal: packages.gatsby-source-shopify.src uses a module listed above it, which is the healthy direction.
packages.gatsby.src.commands.types uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.commands.types, while a change to packages.gatsby.src.commands.types can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.commands.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.redux.types uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby.src.redux.types, while a change to packages.gatsby.src.redux.types can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby.src.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.redux.types uses packages.gatsby-page-utils.src.apply-trailing-slash-option, so a change to packages.gatsby-page-utils.src.apply-trailing-slash-option can break packages.gatsby.src.redux.types, while a change to packages.gatsby.src.redux.types can't break packages.gatsby-page-utils.src.apply-trailing-slash-option.
Position
Below the diagonal: packages.gatsby.src.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.redux.types uses packages.gatsby-cli.src.reporter.redux.types, so a change to packages.gatsby-cli.src.reporter.redux.types can break packages.gatsby.src.redux.types, while a change to packages.gatsby.src.redux.types can't break packages.gatsby-cli.src.reporter.redux.types.
Position
Below the diagonal: packages.gatsby.src.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.redux.types uses packages.gatsby.src.utils.adapter.types, so a change to packages.gatsby.src.utils.adapter.types can break packages.gatsby.src.redux.types, while a change to packages.gatsby.src.redux.types can't break packages.gatsby.src.utils.adapter.types.
Position
Below the diagonal: packages.gatsby.src.redux.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.bootstrap uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.bootstrap, while a change to packages.gatsby.src.bootstrap can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.bootstrap uses a module listed above it, which is the healthy direction.
packages.gatsby.src.bootstrap uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby.src.bootstrap, while a change to packages.gatsby.src.bootstrap can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby.src.bootstrap uses a module listed above it, which is the healthy direction.
packages.gatsby.src.bootstrap uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.bootstrap, while a change to packages.gatsby.src.bootstrap can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.bootstrap uses a module listed above it, which is the healthy direction.
packages.gatsby.src.bootstrap uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.bootstrap, while a change to packages.gatsby.src.bootstrap can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.bootstrap uses a module listed above it, which is the healthy direction.
packages.gatsby.src.commands uses packages.gatsby-cli.src.reporter.redux.types, so a change to packages.gatsby-cli.src.reporter.redux.types can break packages.gatsby.src.commands, while a change to packages.gatsby.src.commands can't break packages.gatsby-cli.src.reporter.redux.types.
Position
Below the diagonal: packages.gatsby.src.commands uses a module listed above it, which is the healthy direction.
packages.gatsby.src.commands uses packages.gatsby.src.commands.types, so a change to packages.gatsby.src.commands.types can break packages.gatsby.src.commands, while a change to packages.gatsby.src.commands can't break packages.gatsby.src.commands.types.
Position
Below the diagonal: packages.gatsby.src.commands uses a module listed above it, which is the healthy direction.
packages.gatsby.src.commands uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.commands, while a change to packages.gatsby.src.commands can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.commands uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.types uses packages.gatsby.src.datastore.common.iterable, so a change to packages.gatsby.src.datastore.common.iterable can break packages.gatsby.src.datastore.types, while a change to packages.gatsby.src.datastore.types can't break packages.gatsby.src.datastore.common.iterable.
Position
Below the diagonal: packages.gatsby.src.datastore.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.types uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.datastore.types, while a change to packages.gatsby.src.datastore.types can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.datastore.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.query.graphql-runner uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.query.graphql-runner, while a change to packages.gatsby.src.query.graphql-runner can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.query.graphql-runner uses a module listed above it, which is the healthy direction.
packages.gatsby.src.query.graphql-runner uses packages.gatsby.src.schema.type-definitions, so a change to packages.gatsby.src.schema.type-definitions can break packages.gatsby.src.query.graphql-runner, while a change to packages.gatsby.src.query.graphql-runner can't break packages.gatsby.src.schema.type-definitions.
Position
Below the diagonal: packages.gatsby.src.query.graphql-runner uses a module listed above it, which is the healthy direction.
packages.gatsby.src.query.graphql-runner uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.query.graphql-runner, while a change to packages.gatsby.src.query.graphql-runner can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.query.graphql-runner uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.in-memory uses packages.gatsby.src.datastore.common.iterable, so a change to packages.gatsby.src.datastore.common.iterable can break packages.gatsby.src.datastore.in-memory, while a change to packages.gatsby.src.datastore.in-memory can't break packages.gatsby.src.datastore.common.iterable.
Position
Below the diagonal: packages.gatsby.src.datastore.in-memory uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.in-memory uses packages.gatsby.src.datastore.common.query, so a change to packages.gatsby.src.datastore.common.query can break packages.gatsby.src.datastore.in-memory, while a change to packages.gatsby.src.datastore.in-memory can't break packages.gatsby.src.datastore.common.query.
Position
Below the diagonal: packages.gatsby.src.datastore.in-memory uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.in-memory uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.datastore.in-memory, while a change to packages.gatsby.src.datastore.in-memory can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.datastore.in-memory uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.in-memory uses packages.gatsby.src.datastore.types, so a change to packages.gatsby.src.datastore.types can break packages.gatsby.src.datastore.in-memory, while a change to packages.gatsby.src.datastore.in-memory can't break packages.gatsby.src.datastore.types.
Position
Below the diagonal: packages.gatsby.src.datastore.in-memory uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.lmdb.query uses packages.gatsby.src.datastore.common.iterable, so a change to packages.gatsby.src.datastore.common.iterable can break packages.gatsby.src.datastore.lmdb.query, while a change to packages.gatsby.src.datastore.lmdb.query can't break packages.gatsby.src.datastore.common.iterable.
Position
Below the diagonal: packages.gatsby.src.datastore.lmdb.query uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.lmdb.query uses packages.gatsby.src.datastore.common.query, so a change to packages.gatsby.src.datastore.common.query can break packages.gatsby.src.datastore.lmdb.query, while a change to packages.gatsby.src.datastore.lmdb.query can't break packages.gatsby.src.datastore.common.query.
Position
Below the diagonal: packages.gatsby.src.datastore.lmdb.query uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.lmdb.query uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.datastore.lmdb.query, while a change to packages.gatsby.src.datastore.lmdb.query can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.datastore.lmdb.query uses a module listed above it, which is the healthy direction.
packages.gatsby.src.datastore.lmdb.query uses packages.gatsby.src.datastore.types, so a change to packages.gatsby.src.datastore.types can break packages.gatsby.src.datastore.lmdb.query, while a change to packages.gatsby.src.datastore.lmdb.query can't break packages.gatsby.src.datastore.types.
Position
Below the diagonal: packages.gatsby.src.datastore.lmdb.query uses a module listed above it, which is the healthy direction.
packages.gatsby.src.query uses packages.gatsby.src.query.graphql-runner, so a change to packages.gatsby.src.query.graphql-runner can break packages.gatsby.src.query, while a change to packages.gatsby.src.query can't break packages.gatsby.src.query.graphql-runner.
Position
Below the diagonal: packages.gatsby.src.query uses a module listed above it, which is the healthy direction.
packages.gatsby.src.schema uses packages.gatsby.src.schema.type-definitions, so a change to packages.gatsby.src.schema.type-definitions can break packages.gatsby.src.schema, while a change to packages.gatsby.src.schema can't break packages.gatsby.src.schema.type-definitions.
Position
Below the diagonal: packages.gatsby.src.schema uses a module listed above it, which is the healthy direction.
packages.gatsby.src.schema uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.schema, while a change to packages.gatsby.src.schema can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.schema uses a module listed above it, which is the healthy direction.
packages.gatsby.src.schema uses packages.gatsby.src.datastore.types, so a change to packages.gatsby.src.datastore.types can break packages.gatsby.src.schema, while a change to packages.gatsby.src.schema can't break packages.gatsby.src.datastore.types.
Position
Below the diagonal: packages.gatsby.src.schema uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses packages.gatsby.src.commands.types, so a change to packages.gatsby.src.commands.types can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break packages.gatsby.src.commands.types.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.services.types uses packages.gatsby.src.query.graphql-runner, so a change to packages.gatsby.src.query.graphql-runner can break packages.gatsby.src.services.types, while a change to packages.gatsby.src.services.types can't break packages.gatsby.src.query.graphql-runner.
Position
Below the diagonal: packages.gatsby.src.services.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.data-layer.types uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.state-machines.data-layer.types, while a change to packages.gatsby.src.state-machines.data-layer.types can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.state-machines.data-layer.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.data-layer.types uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.state-machines.data-layer.types, while a change to packages.gatsby.src.state-machines.data-layer.types can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.state-machines.data-layer.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.data-layer.types uses packages.gatsby.src.commands.types, so a change to packages.gatsby.src.commands.types can break packages.gatsby.src.state-machines.data-layer.types, while a change to packages.gatsby.src.state-machines.data-layer.types can't break packages.gatsby.src.commands.types.
Position
Below the diagonal: packages.gatsby.src.state-machines.data-layer.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.data-layer.types uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.state-machines.data-layer.types, while a change to packages.gatsby.src.state-machines.data-layer.types can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.state-machines.data-layer.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.data-layer.types uses packages.gatsby.src.query.graphql-runner, so a change to packages.gatsby.src.query.graphql-runner can break packages.gatsby.src.state-machines.data-layer.types, while a change to packages.gatsby.src.state-machines.data-layer.types can't break packages.gatsby.src.query.graphql-runner.
Position
Below the diagonal: packages.gatsby.src.state-machines.data-layer.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses packages.gatsby.src.commands.types, so a change to packages.gatsby.src.commands.types can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break packages.gatsby.src.commands.types.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses packages.gatsby.src.query.graphql-runner, so a change to packages.gatsby.src.query.graphql-runner can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break packages.gatsby.src.query.graphql-runner.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.state-machines.query-running.types uses packages.gatsby.src.services.types, so a change to packages.gatsby.src.services.types can break packages.gatsby.src.state-machines.query-running.types, while a change to packages.gatsby.src.state-machines.query-running.types can't break packages.gatsby.src.services.types.
Position
Below the diagonal: packages.gatsby.src.state-machines.query-running.types uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses deprecated-packages.gatsby-telemetry.src.store, so a change to deprecated-packages.gatsby-telemetry.src.store can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break deprecated-packages.gatsby-telemetry.src.store.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby-cli.src.reporter.types, so a change to packages.gatsby-cli.src.reporter.types can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby-cli.src.reporter.types.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.datastore.common.iterable, so a change to packages.gatsby.src.datastore.common.iterable can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.datastore.common.iterable.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby-cli.src.reporter.reporter, so a change to packages.gatsby-cli.src.reporter.reporter can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby-cli.src.reporter.reporter.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.utils.adapter.types, so a change to packages.gatsby.src.utils.adapter.types can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.utils.adapter.types.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.utils.cache, so a change to packages.gatsby.src.utils.cache can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.utils.cache.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.commands.types, so a change to packages.gatsby.src.commands.types can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.commands.types.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.redux.types, so a change to packages.gatsby.src.redux.types can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.redux.types.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils uses packages.gatsby.src.services.types, so a change to packages.gatsby.src.services.types can break packages.gatsby.src.utils, while a change to packages.gatsby.src.utils can't break packages.gatsby.src.services.types.
Position
Below the diagonal: packages.gatsby.src.utils uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils.worker.child uses packages.gatsby.src.query.graphql-runner, so a change to packages.gatsby.src.query.graphql-runner can break packages.gatsby.src.utils.worker.child, while a change to packages.gatsby.src.utils.worker.child can't break packages.gatsby.src.query.graphql-runner.
Position
Below the diagonal: packages.gatsby.src.utils.worker.child uses a module listed above it, which is the healthy direction.
packages.gatsby.src.utils.worker.child uses packages.gatsby.src.services.types, so a change to packages.gatsby.src.services.types can break packages.gatsby.src.utils.worker.child, while a change to packages.gatsby.src.utils.worker.child can't break packages.gatsby.src.services.types.
Position
Below the diagonal: packages.gatsby.src.utils.worker.child uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 56% · Adequate · gated by D2 ·
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 category
Findings
Severity
A03:2025 — Software Supply Chain Failures
482
High / Critical
A05:2025 — Injection
61
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
A02:2025 — Security Misconfiguration
6
High / Critical
Roadmap
Top priorities: Resolve the 48 Banned license finding(s) in License Compliance — start with REDACTED (47), REDACTED; Resolve the 93 Floating npm dependency finding(s) in Dependency 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 48 Banned license finding(s) in License Compliance — start with REDACTED (47), REDACTED.
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.
Reconcile the README with reality: deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 1, but the manifest declares `gatsby` ^4.14.0; deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 2, but the manifest declares `gatsby` ^4.14.0; docs/docs/debugging-incremental-builds.md names Gatsby 3, but the manifest declares `gatsby` ^4.14.0; docs/docs/profiling-site-performance-with-react-profiler.md names React 16, but the manifest declares `react` ^17.0.2; docs/tutorial/building-a-theme.md names Gatsby 404, but the manifest declares `gatsby` ^4.14.0.
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
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 — 452
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 — 1379
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 — 1240
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 80 dimensions across the health lenses
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
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, 2730 of 3071 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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.
D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D31 IaC & Container Security — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/gatsby-plugin-utils/src/polyfill-remote-file/types.ts`, `packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts`, `packages/gatsby-source-shopify/src/create-resolvers.ts`, `packages/gatsby-source-shopify/types/interface.d.ts`, `packages/gatsby-source-wordpress/src/models/gatsby-api.ts`, … (+4 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (integration-tests/gatsby-source-wordpress/docker-compose.yml). compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get -o Acquire::Check-Valid-Until=false update && apt-get install unzip git -y && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100; runtime evidence skipped.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 22 further occurrence(s) are not listed individually; the score already reflects all 62.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
PF3 Async & latency hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 108 further occurrence(s) are not listed individually; the score already reflects all 148.
R11 Import Boundaries — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 168 further occurrence(s) are not listed individually; the score already reflects all 208.
R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 226 further occurrence(s) are not listed individually; the score already reflects all 266.
R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 220 further occurrence(s) are not listed individually; the score already reflects all 260.
R8 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 75 further occurrence(s) are not listed individually; the score already reflects all 115.
SC1 Supply-chain hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 118 further occurrence(s) are not listed individually; the score already reflects all 158.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index').
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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: 119 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
193 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was exports at 107. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being schema.createTypeComposerFromGatsbyType at 16 — they are counted neither in the figure above nor in this dimension's score.
+ 139 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with exports (cyclomatic 107), html.htmlReducer (cyclomatic 77), start-server.startServer (cyclomatic 74). — 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 5 together lifts Cyclomatic Complexity from 4.0 to about 5.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 194 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 17 bodies over 60 down to 60 or less in Cognitive Complexity — start with html.htmlReducer (cognitive 167), start-server.startServer (cognitive 139), exports (cognitive 130). — 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 17 together lifts Cognitive Complexity from 2.0 to about 4.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 44 FunctionTooLong finding(s) in God Classes — start with customize-schema.js (4), gatsby-node.ts (2), bundle-webpack.ts (2). — One of this dimension's main actionable groups (44 warning-level).
Resolve the 21 FileTooLong finding(s) in God Classes — start with types.ts, schema.js, error-map.ts. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 5 MethodTooLong finding(s) in God Classes — start with static-query-mapper.ts, loader.js, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
118 production modules (npm), 1 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 23 of the 118 (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).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with reporter.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 85.9%, branch coverage 70.9%. Measured from the JavaScript/TypeScript suite (jest in the repository root: not run; jest in .github/actions/high-priority-prs/: not run; jest via `yarn install --frozen-lockfile --ignore-scripts` in deprecated-packages/gatsby-recipes/).
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.5 / 10Stronggated by 93 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.
130 skipped (73 with a documented reason), 73 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3663 tests (2 harness-style project(s) excluded from the assertion penalty).
Skipped test: should download and transform an image · ×57packages/gatsby-plugin-utils/src/polyfill-remote-file/jobs/__tests__/gatsby-worker.ts:29
No assertions: %s · ×36packages/gatsby-worker/src/__tests__/task-queue.ts:212
Mock-dominated test: correctly creates nodes from XML · ×67packages/gatsby-transformer-xml/src/__tests__/gatsby-node.js:44
No direct assertions: Not changing plugin doesn't invalidate nodes created by it · ×37integration-tests/cache-resilience/__tests__/cache.js:181
Resolve the 67 Mock-dominated test finding(s) in Test Quality — start with gatsby-node.js (41), fetch.js (10), REDACTED (5). — One of this dimension's main actionable groups (67 recommendation-level).
Resolve the 57 Skipped test finding(s) in Test Quality — start with REDACTED (8), infer.js (6), run-query.js (6). — One of this dimension's main actionable groups (57 warning-level).
Resolve the 36 No assertions finding(s) in Test Quality — start with REDACTED (5), home-page-spec.js (5), ssr.cy.ts (4). — One of this dimension's main actionable groups (36 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in .github/actions/high-priority-prs/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in deprecated-packages/gatsby-recipes/ (17 tests)): measured (0 flaky).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
275 outdated direct production npm dependency(ies) of 382 graded, 115 pinning defect(s), across 272 REDACTED (158 of them the product) and 8 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 22 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 93 Floating npm dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (93 warning-level).
Resolve the 48 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (48). — One of this dimension's main actionable groups (48 warning-level).
Resolve the 22 One package at two majors across the workspace finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (22 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
48 of 2328 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 2332 package(s) this repository's committed lockfile installs for a consumer — its 382 production, optional and peer dependency(ies), across 158 product REDACTED manifest(s), and everything those install in turn. Its 1101 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 14 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. A further 4 package(s) the lockfile resolves are not published on the public registry at all — a private scope, a workspace-internal name or a git install — and are outside this verdict. This repository publishes itself under 0BSD / ISC / MIT, which is its own choice and is not judged here.
Resolve the 48 Banned license finding(s) in License Compliance — start with REDACTED (47), REDACTED. — One of this dimension's main actionable groups (48 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/gatsby/src/utils/page-ssr-module/lambda.ts. Counted over 404 of the 1109 production source files in this repository: 683 are under the ~2,400-byte size floor this dimension measures over, and the remaining 22 have no attributable history left to measure.
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.
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.
153 deducted task-comment markers across 73266 LoC (0.2/KLoC) → score 9.6. 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.
Resolve the 136 TodoComment finding(s) in Explicit Debt — start with indexing.ts (13), types.ts (9), queries.ts (7). — One of this dimension's main actionable groups (136 warning-level).
Resolve the 14 FixmeComment finding(s) in Explicit Debt — start with create-index.ts (3), lmdb-datastore.ts (2), errors.ts. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with scroll-handler.tsx, catch-exit-signals.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 2 documentation facets pass in full; short on: F2 example. 142 document(s) read across 122 unit(s).
Documentation: no build, run or usage example · ×7.github/actions/gatsby-site-showcase-validator/README.md:1
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundpackages/gatsby-plugin-preload-fonts/package.json:7
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
5 naming inconsistencies among 130 declarations measured against a convention their peers follow.
`updateURL` spells `URL` where 20 names in the project spell it `Url`packages/gatsby-graphiql-explorer/src/app.jsx:71
`newLinkURL` spells `URL` where 20 names in the project spell it `Url`packages/gatsby-remark-copy-linked-files/src/index.js:58
`wpActionUPDATE` spells `UPDATE` where 41 names in the project spell it `Update`packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:275
`locInGraphQlToLocInFile` spells `Ql` where 51 names in the project spell it `QL`packages/gatsby/src/query/error-parser.ts:176
`skipSsr` spells `Ssr` where 13 names in the project spell it `SSR`packages/gatsby/src/utils/dev-ssr/render-dev-html.ts:141
What to do
Resolve the 1 `updateURL` spells `URL` where 20 names in the project spell it `Url` finding(s) in Naming Consistency — start with app.jsx. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `newLinkURL` spells `URL` where 20 names in the project spell it `Url` finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `wpActionUPDATE` spells `UPDATE` where 41 names in the project spell it… finding(s) in Naming Consistency — start with update.js. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
31 domain type(s) cross context boundaries across 102 contexts; they are measured and withheld (not published, not scored). Contexts: babel-plugin-remove-graphql-queries, babel-preset-gatsby, babel-preset-gatsby-package, create-gatsby, gatsby, gatsby-adapter-netlify, gatsby-cli, gatsby-codemods, gatsby-core-utils, gatsby-cypress, gatsby-dev-cli, gatsby-graphiql-explorer and 90 more.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×9packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:24
What to do
Resolve the 48 redundant comment finding(s) in Comment Value — start with index.ts (4), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (48 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
19 % of calls cross a namespace and 1 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
5 finding(s): 0 critical, 5 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
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
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.
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).
61 finding(s): 0 critical, 20 high, 41 medium, 0 low. 3 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 10 file(s) — `packages/gatsby-plugin-utils/src/polyfill-remote-file/types.ts` (line 59), `packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts` (lines 540–545, line 2127, line 2132, …), `packages/gatsby-source-shopify/src/create-resolvers.ts` (line 42), `packages/gatsby-source-shopify/types/interface.d.ts` (line 155), `packages/gatsby-source-wordpress/src/models/gatsby-api.ts` (line 120), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 289 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (191), REDACTED (97), REDACTED. — One of this dimension's main actionable groups (289 issue-level).
Resolve the 25 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13), REDACTED (12). — One of this dimension's main actionable groups (25 issue-level).
Resolve the 9 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (9 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
315 of 426 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts. Counted over 426 of the 1109 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1
Concentrated knowledge decay
What to do
Resolve the 312 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (21), gatsby-node.js (18), index.ts (16). — One of this dimension's main actionable groups (312 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with plugin-options-schema-joi-type.ts, public.js, schema.js. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 97 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.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives4.5 / 10Weak✓ Tool-verified
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.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — deprecated-packages/gatsby-admin/src/components/navbar.tsx:82, deprecated-packages/gatsby-admin/src/components/navbar.tsx:99
This interactive image has no accessible name. Add a non-empty alt (or aria-label) describing its action/destination — alt="" does not name an image button or link. (×4) — packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:456, packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:522, packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:605, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels3.8 / 10Weak✓ Tool-verified
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.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:745, packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:809, packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:911
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — packages/gatsby-graphiql-explorer/src/index.html.ejs:2
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.
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.
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.
`.fa-spin` moves (`animation: fa-spin 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/using-javascript-transforms/src/static/fonts/fontawesome/style.css:120
`.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/using-javascript-transforms/src/static/fonts/fontawesome/style.css:125
`.message` moves (`animation: pulse-black 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — examples/functions-google-oauth/src/pages/auth-redirect.module.scss:10
`.astro` moves (`animation-name: float`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — e2e-tests/adapters/src/pages/index.css:23
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The projects babel-plugin-remove-graphql-queries → gatsby → babel-plugin-remove-graphql-queries (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — packages/babel-plugin-remove-graphql-queries/package.json:24
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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.
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.
`ObjectSchema` declares 20 required operations: `and`, `append`, `assert`, `instance`, `keys`, `length`, `max`, `min`, `nand`, `or`, `oxor`, `pattern`, `ref`, `regex`, `rename`, `schema`, `unknown`, `with`, `without`, `xor`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1570
`PluginOptionsSchemaJoi` declares 55 required operations: `ValidationError`, `any`, `array`, `bool`, `boolean`, `binary`, `date`, `func`, `function`, `number`, `object`, `string`, `symbol`, `alternatives`, `alternatives`, `alt`, `alt`, `link`, `assert`, `assert`, `attempt`, `attempt`, `compile`, `checkPreferences`, `custom`, `defaults`, `expression`, `extend`, `in`, `isError`, `isExpression`, `isRef`, `isSchema`, `ref`, `types`, `x`, `subPlugins`, `allow`, `valid`, `equal`, and 15 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 55 declarations carry 50 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 50 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1956
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — packages/babel-plugin-remove-graphql-queries/src/index.ts:256
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.
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.
`onPreInit` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:308
`onPreBootstrap` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:314
`onPreBuild` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:320
`createGraphQLNode` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-lever/src/normalize.js:14
`storedAuthSettings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/auth-handling.ts:5
`restoreAuthPluginOptions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/auth-handling.ts:19
`isWpGatsby` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:231
`customizeSchema` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js:15
`imageRoutes` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/image-routes.ts:4
`buildNonNodeQueries` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js:6
`logPostBuildWarnings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby-source-wordpress/src/steps/log-post-build-warnings.ts:5
`onCreateDevServer` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby/src/internal-plugins/partytown/gatsby-node.ts:36
`setQueryRunningFinished` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby/src/state-machines/develop/actions.ts:54
`userGetsSevenDayFeedback` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/gatsby/src/utils/feedback.ts:158
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×22) — packages/gatsby-link/src/__tests__/is-local-link.js:15, packages/gatsby-link/src/__tests__/is-local-link.js:20, packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:56, …
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×4) — packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1, packages/gatsby-transformer-sharp/src/fragments.js:1, packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1, …
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 1, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deprecated-packages/gatsby-plugin-netlify-cms/README.md:7
deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 2, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — deprecated-packages/gatsby-plugin-netlify-cms/README.md:9
docs/docs/debugging-incremental-builds.md names Gatsby 3, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/docs/debugging-incremental-builds.md:5
docs/docs/profiling-site-performance-with-react-profiler.md names React 16, but the manifest declares `react` ^17.0.2. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/docs/profiling-site-performance-with-react-profiler.md:9
docs/tutorial/building-a-theme.md names Gatsby 404, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/tutorial/building-a-theme.md:175
packages/gatsby-plugin-emotion/README.md names Emotion 8, but the manifest declares `emotion` ^11.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/gatsby-plugin-emotion/README.md:9
What to do
Reconcile the README with reality: deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 1, but the manifest declares `gatsby` ^4.14.0; deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 2, but the manifest declares `gatsby` ^4.14.0; docs/docs/debugging-incremental-builds.md names Gatsby 3, but the manifest declares `gatsby` ^4.14.0; docs/docs/profiling-site-performance-with-react-profiler.md names React 16, but the manifest declares `react` ^17.0.2; docs/tutorial/building-a-theme.md names Gatsby 404, but the manifest declares `gatsby` ^4.14.0.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.3 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/create-gatsby`, `packages/gatsby-cli`, `packages/gatsby-codemods`, `packages/gatsby-dev-cli`.
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:17
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:29
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:42
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:43
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:56
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 69 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:69
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:70
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 274 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:274
`packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 289 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/api-browser-docs.ts:289
`packages/gatsby/src/utils/nodes.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/nodes.ts:28
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:6
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:7
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:8
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:11
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:14
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:18
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:21
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:22
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:25
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:28
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:33
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:37
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:41
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:42
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:45
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:48
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:53
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 57 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:57
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 61 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:61
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:62
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:63
`packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/print-instructions.ts:66
`packages/gatsby/src/utils/source-nodes.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/source-nodes.ts:70
`packages/gatsby/src/utils/stack-trace-utils.ts` reports through `console.*` at line 99 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/stack-trace-utils.ts:99
`packages/gatsby/src/utils/webpack-plugins.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/webpack-plugins.ts:12
`packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts` reports through `console.*` at line 354 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:354
`packages/gatsby/src/utils/tracer/zipkin-local.ts` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/tracer/zipkin-local.ts:65
`packages/gatsby/src/utils/tracer/zipkin-local.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/tracer/zipkin-local.ts:70
`packages/gatsby/src/utils/page-ssr-module/lambda.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/gatsby/src/utils/page-ssr-module/lambda.ts:56
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 2 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` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — 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.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — packages/gatsby/cache-dir/fast-refresh-overlay/utils.js:18, packages/gatsby/src/utils/tracer/zipkin-local.ts:52
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.existsSync` in `maybeCreateGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/create-gatsby/src/init-starter.ts:56
`execSync` in `createInitialGitCommit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/create-gatsby/src/init-starter.ts:72, REDACTED:86
`existsSync` in `maybeCreateGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:64
`existsSync` in `copy` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:139
`existsSync` in `initStarter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:324
`fs.existsSync` in `remove` 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/gatsby-core-utils/src/page-html.ts:22
`fs.chmodSync` in `callback to fs.copy` 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/gatsby-dev-cli/src/watch.js:83
`fs.existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/gatsby-dev-cli/src/watch.js:203
`fs.existsSync` in `createImageNode` 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/gatsby-plugin-image/src/node-apis/image-processing.ts:34
`fs.existsSync` in `callback to 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/gatsby-plugin-image/src/node-apis/image-processing.ts:126
`existsSync` in `createPagesStatefully` 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/gatsby-plugin-page-creator/src/gatsby-node.ts:87
`fsExtra.existsSync` in `callback to Array.from` 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/gatsby-remark-copy-linked-files/src/index.js:301
`readFileSync` in `getImageBase64` 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/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:36
`fs.rmSync` in `writeQueriesToDisk` 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/gatsby-source-wordpress/src/steps/ingest-remote-schema/write-queries-to-disk.js:27
`fs.existsSync` in `copyFileToStaticAndReturnUrlPath` 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:398
`clipboardy.writeSync` in `handleFetchErrors` 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:546
`fs.readFileSync` in `resolve` 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/gatsby-transformer-sharp/src/customize-schema.js:597
`fs.existsSync` in `resolve` 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/gatsby-transformer-sharp/src/customize-schema.js:607
`fs.readFileSync` in `getPageData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:157
`fs.readFileSync` in `readSliceData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:290
`fs.readFileSync` in `loadPageDataSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:162
`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/gatsby/src/commands/build.ts:463
`fs.readFileSync` in `exports` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:159
`fs.utimesSync` in `ensureFunctionIsCompiled` 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:52
`fs.writeFileSync` in `createWebpackConfig` 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:220
`fs.readFileSync` in `createWebpackConfig` 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:241
`fs.existsSync` in `createInternalPackagesCacheDir` 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/gatsby/src/schema/graphql-engine/bundle-webpack.ts:72
`fs.existsSync` in `initialize` 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. (×3) — packages/gatsby/src/services/initialize.ts:257, packages/gatsby/src/services/initialize.ts:258, packages/gatsby/src/services/initialize.ts:259
`fs.readFileSync` in `isResolvedSSR` 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/gatsby/src/services/initialize.ts:570
`fs.writeFileSync` in `isResolvedSSR` 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/gatsby/src/services/initialize.ts:587, packages/gatsby/src/services/initialize.ts:592
`fs.readFileSync` in `absoluteOrDirectory` 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/gatsby/src/utils/get-ssl-cert.ts:69, packages/gatsby/src/utils/get-ssl-cert.ts:70
`fs.mkdtempSync` in `getSslCert` 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/gatsby/src/utils/get-ssl-cert.ts:86
`fs.existsSync` in `writeGraphQLConfig` 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/gatsby/src/utils/graphql-typegen/file-writes.ts:21
`fs.existsSync` in `removePageData` 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/gatsby/src/utils/page-data.ts:53
`fs.readFileSync` in `createPageSSRBundle` 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/gatsby/src/utils/page-ssr-module/bundle-webpack.ts:221
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.
Do you agree with this assessment?
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.
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.
44 duplicated blocks under packages/ have copies in at least two of the sibling directories babel-plugin-remove-graphql-queries, create-gatsby, gatsby, gatsby-codemods, gatsby-core-utils, gatsby-plugin-emotion (+25 more sibling(s) not listed) — 29 of them are reported below, and 15 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 44 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 44 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 44 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/gatsby-plugin-image/src/image-utils.ts:376
9 duplicated blocks under packages/gatsby/src/ have copies in at least two of the sibling directories bootstrap, commands, internal-plugins, query, schema, services (+2 more sibling(s) not listed) — 7 of them are reported below, and 2 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:358
packages/gatsby-plugin-image/src/image-utils.ts:376 · packages/gatsby-plugin-sharp/src/utils.js:17 — the two spans are one implementation copied and then locally edited — 974 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/gatsby-plugin-image/src/image-utils.ts:376
packages/gatsby-codemods/src/transforms/global-graphql-calls.js:4 · packages/gatsby-codemods/src/transforms/import-link.js:4 — the two spans are one implementation copied and then locally edited — 540 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/gatsby-codemods/src/transforms/global-graphql-calls.js:4
packages/gatsby-plugin-manifest/src/safe-sharp.js:12 · packages/gatsby-plugin-sharp/src/safe-sharp.js:12 · packages/gatsby-remark-images-contentful/src/safe-sharp.js:12 · packages/gatsby-transformer-sharp/src/safe-sharp.js:12 — these 4 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/gatsby-plugin-manifest/src/safe-sharp.js:12
packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:173 · packages/gatsby/src/query/transform-document.ts:3 — 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/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:173
packages/gatsby-plugin-sharp/src/utils.js:84 · packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:515 — the two spans are one implementation copied and then locally edited — 288 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/gatsby-plugin-sharp/src/utils.js:84
packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:243 · packages/gatsby/src/query/transform-document.ts:73 — 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/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:243
scripts/backport.js:7 · scripts/create-release-notes.js:9 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/backport.js:7
packages/gatsby-transformer-sharp/src/customize-schema.js:158 · packages/gatsby-transformer-sharp/src/customize-schema.js:320 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — packages/gatsby-transformer-sharp/src/customize-schema.js:158
packages/gatsby-cli/src/reporter/reporter-progress.ts:22 · packages/gatsby-cli/src/reporter/reporter-timer.ts:23 — the two spans are one implementation copied and then locally edited — 214 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/gatsby-cli/src/reporter/reporter-progress.ts:22
packages/gatsby-plugin-image/src/node-apis/parser.ts:10 · packages/gatsby/src/utils/babel-parse-to-ast.ts:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/gatsby-plugin-image/src/node-apis/parser.ts:10
packages/gatsby/src/datastore/in-memory/indexing.ts:296 · packages/gatsby/src/datastore/in-memory/indexing.ts:475 — 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/gatsby/src/datastore/in-memory/indexing.ts:296
packages/gatsby-remark-images-contentful/src/index.js:243 · packages/gatsby-remark-images/src/index.js:478 — the two spans are one implementation copied and then locally edited — 218 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/gatsby-remark-images-contentful/src/index.js:243
REDACTED:304 · REDACTED:285 — the two spans are one implementation copied and then locally edited — 195 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:304
packages/gatsby/cache-dir/loader.js:190 · packages/gatsby/cache-dir/loader.js:248 — 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/gatsby/cache-dir/loader.js:190
packages/gatsby-cli/src/reporter/loggers/ink/components/trees.tsx:159 · packages/gatsby-cli/src/reporter/loggers/yurnalist/index.ts:87 — the two spans are one implementation copied and then locally edited — 218 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/gatsby-cli/src/reporter/loggers/ink/components/trees.tsx:159
packages/gatsby/src/datastore/in-memory/indexing.ts:592 · packages/gatsby/src/datastore/in-memory/indexing.ts:627 — 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/gatsby/src/datastore/in-memory/indexing.ts:592
REDACTED:215 · REDACTED:265 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:215
packages/gatsby/src/schema/schema.js:633 · packages/gatsby/src/schema/schema.js:696 — 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/gatsby/src/schema/schema.js:633
packages/babel-plugin-remove-graphql-queries/src/index.ts:312 · packages/babel-plugin-remove-graphql-queries/src/index.ts:354 — the two spans are one implementation copied and then locally edited — 133 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/babel-plugin-remove-graphql-queries/src/index.ts:312
packages/gatsby-plugin-google-analytics/src/gatsby-browser.js:1 · packages/gatsby-plugin-google-tagmanager/src/gatsby-browser.js:1 — the two spans are one implementation copied and then locally edited — 157 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/gatsby-plugin-google-analytics/src/gatsby-browser.js:1
packages/gatsby-plugin-less/src/gatsby-node.js:16 · packages/gatsby-plugin-stylus/src/gatsby-node.js:35 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/gatsby-plugin-less/src/gatsby-node.js:16
packages/gatsby-transformer-sharp/src/customize-schema.js:95 · packages/gatsby-transformer-sharp/src/customize-schema.js:255 — 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/gatsby-transformer-sharp/src/customize-schema.js:95
scripts/gatsby-changelog-generator/cli.js:9 · scripts/gatsby-changelog-generator/cli.js:38 — 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. — scripts/gatsby-changelog-generator/cli.js:9
packages/gatsby-source-filesystem/src/extend-file-node.js:23 · packages/gatsby-transformer-sharp/src/customize-schema.js:599 — the two spans are one implementation copied and then locally edited — 87 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/gatsby-source-filesystem/src/extend-file-node.js:23
packages/gatsby-plugin-sharp/src/image-data.ts:319 · packages/gatsby-plugin-sharp/src/image-data.ts:348 — 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/gatsby-plugin-sharp/src/image-data.ts:319
packages/gatsby/cache-dir/loader.js:884 · packages/gatsby/cache-dir/loader.js:911 — 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/gatsby/cache-dir/loader.js:884
packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:50 · packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:50
packages/gatsby-plugin-sharp/src/index.js:542 · packages/gatsby-plugin-sharp/src/index.js:694 — 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/gatsby-plugin-sharp/src/index.js:542
packages/gatsby-source-wordpress/src/utils/cache.ts:50 · packages/gatsby/src/utils/cache.ts:40 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/gatsby-source-wordpress/src/utils/cache.ts:50
packages/gatsby/src/services/run-slice-queries.ts:6 · packages/gatsby/src/services/run-static-queries.ts:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/gatsby/src/services/run-slice-queries.ts:6
packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:86 · packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:51 — 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/gatsby-codemods/src/transforms/gatsby-plugin-image.js:86
packages/gatsby-plugin-image/src/image-utils.ts:535 · packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:601 — 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/gatsby-plugin-image/src/image-utils.ts:535
packages/gatsby/cache-dir/fast-refresh-overlay/components/graphql-errors.js:69 · packages/gatsby/cache-dir/fast-refresh-overlay/components/runtime-errors.js:108 — 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/gatsby/cache-dir/fast-refresh-overlay/components/graphql-errors.js:69
packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1684 · packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2082 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1684
packages/gatsby/src/datastore/in-memory/indexing.ts:833 · packages/gatsby/src/datastore/in-memory/indexing.ts:891 — 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/gatsby/src/datastore/in-memory/indexing.ts:833
packages/gatsby/src/datastore/in-memory/indexing.ts:949 · packages/gatsby/src/datastore/in-memory/indexing.ts:1007 — 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/gatsby/src/datastore/in-memory/indexing.ts:949
packages/gatsby/cache-dir/develop-static-entry.js:39 · REDACTED:103 — 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/gatsby/cache-dir/develop-static-entry.js:39
packages/gatsby-plugin-google-analytics/src/index.js:20 · packages/gatsby-plugin-google-gtag/src/index.js:7 — 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/gatsby-plugin-google-analytics/src/index.js:20
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.
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.
.jestSetup.js:22 reaches into another package with a relative path (./packages/gatsby/src/utils/worker/__tests__/test-helpers/ts-register.js) — import the package by name instead. — .jestSetup.js:22
.jestSetup.js:22 imports packages/gatsby/src/utils/worker/__tests__/test-helpers/ts-register.js, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — .jestSetup.js:22
packages/create-gatsby/src/utils/site-metadata.ts:7 imports gatsby-core-utils, 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/create-gatsby/src/utils/site-metadata.ts:7
packages/gatsby-plugin-offline/src/gatsby-node.js:174 imports idb-keyval/dist/, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/gatsby-plugin-offline/src/gatsby-node.js:174
packages/gatsby-source-drupal/src/utils.ts:12 imports gatsby-core-utils, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-drupal/src/utils.ts:12
packages/gatsby-source-shopify/src/create-operations.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/create-operations.ts:1
packages/gatsby-source-shopify/src/create-resolvers.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/create-resolvers.ts:1
packages/gatsby-source-shopify/src/create-schema-customization.ts:1 reaches into another package with a relative path (../../gatsby) — import the package by name instead. — packages/gatsby-source-shopify/src/create-schema-customization.ts:1
packages/gatsby-source-shopify/src/helpers.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/helpers.ts:1
packages/gatsby-source-shopify/src/plugin-options-schema.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/plugin-options-schema.ts:1
packages/gatsby-source-shopify/src/process-bulk-results.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/process-bulk-results.ts:1
packages/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:2 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:2
REDACTED:2 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — REDACTED:2
packages/gatsby-source-shopify/src/source-nodes.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/source-nodes.ts:1
packages/gatsby-source-shopify/src/update-cache.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies. — packages/gatsby-source-shopify/src/update-cache.ts:1
packages/gatsby-transformer-react-docgen/src/parse.js:2 imports react-docgen/dist/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/gatsby-transformer-react-docgen/src/parse.js:2
packages/gatsby-transformer-remark/src/__tests__/extend-node.js:83 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/schema-composer) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/extend-node.js:83
packages/gatsby-transformer-remark/src/__tests__/extend-node.js:87 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/add-inferred-fields) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/extend-node.js:87
packages/gatsby-transformer-remark/src/__tests__/extend-node.js:90 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/inference-metadata) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/extend-node.js:90
packages/gatsby-transformer-remark/src/__tests__/extend-node.js:93 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/build-example-data) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/extend-node.js:93
packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:124 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/schema-composer) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:124
packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:127 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/add-inferred-fields) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:127
packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:130 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/inference-metadata) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:130
packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:133 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/build-example-data) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:133
packages/gatsby-transformer-remark/src/code-handler.js:1 imports mdast-util-to-hast/lib/handlers/code, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/gatsby-transformer-remark/src/code-handler.js:1
packages/gatsby-transformer-screenshot/lambda/screenshot.js:4 imports gatsby-core-utils, 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/gatsby-transformer-screenshot/lambda/screenshot.js:4
packages/gatsby-transformer-screenshot/src/gatsby-node.js:3 imports gatsby-source-filesystem, 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/gatsby-transformer-screenshot/src/gatsby-node.js:3
packages/gatsby-transformer-screenshot/src/placeholder-file-node.js:2 imports gatsby-source-filesystem/create-file-node, 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/gatsby-transformer-screenshot/src/placeholder-file-node.js:2
packages/gatsby/src/commands/build-html.ts:306 imports gatsby-plugin-image/dist/gatsby-image.browser.modern, 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/gatsby/src/commands/build-html.ts:306
REDACTED:25 reaches into another package with a relative path (../internal-plugins/functions/middleware) — import the package by name instead. — REDACTED:25
REDACTED:26 reaches into another package with a relative path (../internal-plugins/partytown/proxy) — import the package by name instead. — REDACTED:26
packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:11 reaches into another package with a relative path (../../utils/webpack-error-utils) — import the package by name instead. — packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:11
packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:12 reaches into another package with a relative path (../../redux/actions) — import the package by name instead. — packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:12
packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:13 reaches into another package with a relative path (../../redux/types) — import the package by name instead. — packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:13
REDACTED:14 reaches into another package with a relative path (../../redux/types) — import the package by name instead. — REDACTED:14
packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:6 reaches into another package with a relative path (../../redux) — import the package by name instead. — packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:6
packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:7 reaches into another package with a relative path (../../redux/actions) — import the package by name instead. — packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:7
packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:8 reaches into another package with a relative path (../../datastore) — import the package by name instead. — packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:8
packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:11 reaches into another package with a relative path (../../utils/parcel/compile-gatsby-files) — import the package by name instead. — packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js:11
packages/gatsby/src/internal-plugins/load-babel-config/gatsby-node.js:5 reaches into another package with a relative path (../../utils/api-runner-node) — import the package by name instead. — packages/gatsby/src/internal-plugins/load-babel-config/gatsby-node.js:5
What to do
Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (39 rows); declare the workspace packages these files import in the importing package's own REDACTED dependencies (15 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; move the shared test helper into a source directory production code may depend on (1 row).
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.
isTabbableRules has cyclomatic complexity 94 and cognitive complexity 121; 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/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2366
isFocusRelevantRules has cyclomatic complexity 90 and cognitive complexity 91; 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/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1173
htmlReducer has cyclomatic complexity 76 and cognitive complexity 162; 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/gatsby/src/redux/reducers/html.ts:35
build has cyclomatic complexity 54 and cognitive complexity 70; 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/gatsby/src/commands/build.ts:72
(anonymous) has cyclomatic complexity 50 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/datastore/in-memory/indexing.ts:677
generateImageData has cyclomatic complexity 49 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/gatsby-plugin-sharp/src/image-data.ts:123
transformField has cyclomatic complexity 46 and cognitive complexity 42; 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/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:141
queriesReducer has cyclomatic complexity 45 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/redux/reducers/queries.ts:60
createPage has cyclomatic complexity 43 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/redux/actions/public.js:185
sourceNodes has cyclomatic complexity 40 and cognitive complexity 99; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-source-drupal/src/gatsby-node.ts:143
generateImagesAndUpdateNode has cyclomatic complexity 35 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-remark-images/src/index.js:139
initialize has cyclomatic complexity 35 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/services/initialize.ts:76
CallSiteToString has cyclomatic complexity 34 and cognitive complexity 46; 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/gatsby-cli/src/reporter/prepare-stack-trace.ts:158
identifyAndStoreIngestableFieldsAndTypes has cyclomatic complexity 33 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js:12
sourceNodes has cyclomatic complexity 33 and cognitive complexity 64; 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/gatsby-source-contentful/src/source-nodes.js:52
exports has cyclomatic complexity 32 and cognitive complexity 46; 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/gatsby/src/utils/webpack.config.js:46
fluid has cyclomatic complexity 32 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/gatsby-plugin-sharp/src/index.js:420
(anonymous) has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:324
resolveIndexFieldRanges has cyclomatic complexity 29 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:489
(anonymous) has cyclomatic complexity 28 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/gatsby-webpack-stats-extractor.ts:21
(anonymous) has cyclomatic complexity 27 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:91
(anonymous) has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:492
ExportNamedDeclaration has cyclomatic complexity 26 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/webpack/loaders/partial-hydration-reference-loader.ts:59
isFocusableRules has cyclomatic complexity 25 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/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2048
run has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/create-gatsby/src/index.ts:73
(anonymous) has cyclomatic complexity 23 and cognitive complexity 43; 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:381
generateImageData has cyclomatic complexity 23 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-plugin-image/src/image-utils.ts:218
(anonymous) has cyclomatic complexity 22 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/handle-flags.ts:17
compareKey has cyclomatic complexity 22 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/datastore/lmdb/query/common.ts:93
compileGatsbyFiles has cyclomatic complexity 22 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:81
findPageOwnedByNode has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/src/utils/node-manifest.ts:61
getNext has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-source-drupal/src/gatsby-node.ts:520
fetchFile has cyclomatic complexity 21 and cognitive complexity 25; 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/gatsby-core-utils/src/fetch-remote-file.ts:134
gatsbyImageResolver has cyclomatic complexity 21 and cognitive complexity 25; 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/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:80
getGatsbyImageCdnFields has cyclomatic complexity 21 and cognitive complexity 25; 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/gatsby-source-drupal/src/normalize.ts:26
isOnlyTabbableRules has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1916
(anonymous) has cyclomatic complexity 21 and cognitive complexity 22; 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/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:58
onRenderBody has cyclomatic complexity 21 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:28
checkIfSchemaHasChanged has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:19
(anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/create-gatsby/src/components/placeholder.js:21
Do you agree with this assessment?
R3 · Large Files7.8 / 10Strong✓ 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/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js has 3016 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/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1
packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts has 1947 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/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1
packages/gatsby/src/redux/types.ts has 1448 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/gatsby/src/redux/types.ts:1
packages/gatsby/src/redux/actions/public.js has 1375 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/gatsby/src/redux/actions/public.js:1
packages/gatsby/src/schema/schema.js has 1349 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/gatsby/src/schema/schema.js:1
packages/gatsby/src/datastore/in-memory/indexing.ts has 1096 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/gatsby/src/datastore/in-memory/indexing.ts:1
packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js has 1002 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/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:1
packages/gatsby-cli/src/structured-errors/error-map.ts has 970 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/gatsby-cli/src/structured-errors/error-map.ts:1
packages/gatsby/src/schema/node-model.js has 910 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/gatsby/src/schema/node-model.js:1
packages/gatsby-source-drupal/src/gatsby-node.ts has 891 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/gatsby-source-drupal/src/gatsby-node.ts:1
packages/gatsby/cache-dir/loader.js has 845 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/gatsby/cache-dir/loader.js:1
packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js has 842 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:1
packages/gatsby-source-contentful/src/normalize.js has 797 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/gatsby-source-contentful/src/normalize.js:1
packages/gatsby-transformer-sharp/src/customize-schema.js has 783 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/gatsby-transformer-sharp/src/customize-schema.js:1
packages/gatsby/src/commands/build-html.ts has 780 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/gatsby/src/commands/build-html.ts:1
REDACTED has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/gatsby/src/utils/webpack-utils.ts has 770 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/gatsby/src/utils/webpack-utils.ts:1
packages/gatsby-transformer-remark/src/extend-node-type.js 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. — packages/gatsby-transformer-remark/src/extend-node-type.js:1
packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts has 718 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:1
packages/gatsby/src/schema/resolvers.ts has 707 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/gatsby/src/schema/resolvers.ts:1
packages/gatsby-plugin-sharp/src/index.js has 691 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/gatsby-plugin-sharp/src/index.js:1
packages/gatsby/src/redux/actions/restricted.ts has 658 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/gatsby/src/redux/actions/restricted.ts:1
packages/gatsby/src/utils/worker/child/render-html.ts has 658 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/gatsby/src/utils/worker/child/render-html.ts:1
packages/gatsby/src/utils/api-runner-node.js has 655 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/gatsby/src/utils/api-runner-node.js:1
packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts has 637 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/gatsby/src/datastore/lmdb/query/filter-using-index.ts:1
packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js has 630 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/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:1
packages/gatsby/src/query/file-parser.js has 624 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/gatsby/src/query/file-parser.js:1
packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:1
packages/gatsby/src/utils/adapter/manager.ts has 604 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/gatsby/src/utils/adapter/manager.ts:1
packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts has 594 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/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:1
packages/gatsby/src/commands/build.ts has 576 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/gatsby/src/commands/build.ts:1
packages/babel-plugin-remove-graphql-queries/src/index.ts has 572 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/babel-plugin-remove-graphql-queries/src/index.ts:1
packages/gatsby-cli/src/create-cli.ts has 568 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/gatsby-cli/src/create-cli.ts:1
packages/gatsby/src/services/initialize.ts has 557 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/gatsby/src/services/initialize.ts:1
packages/gatsby-plugin-image/src/image-utils.ts has 554 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/gatsby-plugin-image/src/image-utils.ts:1
packages/gatsby-source-medium/src/gatsby-node.js has 553 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/gatsby-source-medium/src/gatsby-node.js:1
packages/gatsby-source-contentful/src/source-nodes.js has 524 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/gatsby-source-contentful/src/source-nodes.js:1
packages/gatsby/src/bootstrap/load-plugins/validate.ts has 523 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/gatsby/src/bootstrap/load-plugins/validate.ts:1
packages/gatsby/src/internal-plugins/functions/gatsby-node.ts has 523 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:1
packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage7.5 / 10Strong✓ 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/gatsby/src/schema/infer/__tests__/infer.js:433 imports '../infer', 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/gatsby/src/schema/infer/__tests__/infer.js:433
packages/gatsby/src/utils/__tests__/test-import-error.ts:8 imports './fixtures/module-does-not-exist.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/gatsby/src/utils/__tests__/test-import-error.ts:8
peril/tests/invite-collaborator.test.ts:6 imports '../rules/invite-collaborator', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — peril/tests/invite-collaborator.test.ts:6
peril/tests/validate-yaml/validate-yaml-authors.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — peril/tests/validate-yaml/validate-yaml-authors.test.ts:3
peril/tests/validate-yaml/validate-yaml-creators.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — peril/tests/validate-yaml/validate-yaml-creators.test.ts:3
peril/tests/validate-yaml/validate-yaml-sites.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — peril/tests/validate-yaml/validate-yaml-sites.test.ts:3
peril/tests/validate-yaml/validate-yaml-starters.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — peril/tests/validate-yaml/validate-yaml-starters.test.ts:3
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/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:1, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:1, packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
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/gatsby/src/schema/infer/__tests__/infer.js and 6 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/gatsby/src/schema/infer/__tests__/infer.js:433
Do you agree with this assessment?
R7 · Dead Code5.1 / 10Adequate✓ 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.
22 file(s) (~2385 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — deprecated-packages/gatsby-recipes
11 file(s) (~1004 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — e2e-tests/adapters
1 file(s) (~74 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. (×2) — e2e-tests/development-runtime, e2e-tests/production-runtime
2 file(s) (~245 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. — integration-tests/esm-in-gatsby-files
1 file(s) (~1 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. — integration-tests/functions/plugins/gatsby-plugin-cool
597 file(s) (~115040 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: packages/gatsby/index.d.ts imports './dist/utils/adapter/types', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — packages/gatsby
12 file(s) (~1693 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-codemods
5 file(s) (~205 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-canonical-urls
5 file(s) (~757 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-catch-links
4 file(s) (~69 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-cxs
2 file(s) (~174 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-emotion
4 file(s) (~211 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-facebook-analytics
6 file(s) (~660 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-feed
2 file(s) (~56 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-flow
2 file(s) (~76 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-fullstory
6 file(s) (~777 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-google-tagmanager
2 file(s) (~49 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-jss
4 file(s) (~142 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-less
1 file(s) (~43 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-lodash
13 file(s) (~2092 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-manifest
2 file(s) (~146 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-nprogress
23 file(s) (~2845 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-page-creator
3 file(s) (~217 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-postcss
2 file(s) (~33 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-react-css-modules
4 file(s) (~115 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-react-helmet
3 file(s) (~416 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-sass
8 file(s) (~912 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-sitemap
3 file(s) (~91 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-styled-components
2 file(s) (~26 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-styled-jsx
1 file(s) (~23 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-subfont
4 file(s) (~119 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-twitter
2 file(s) (~203 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-typescript
5 file(s) (~313 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-plugin-typography
2 file(s) (~69 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-source-faker
1 file(s) (~187 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/gatsby-source-hacker-news
2 file(s) (~667 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-source-medium
2 file(s) (~886 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-transformer-documentationjs
2 file(s) (~228 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/gatsby-transformer-excel
2 file(s) (~139 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/gatsby-transformer-hjson
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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. (×35) — scripts/check-ts.js:14, markdown.config.js:3, scripts/check-versions.js:5, …
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. (×5) — packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:4, packages/gatsby/src/utils/webpack-utils.ts:8, packages/gatsby-plugin-image/src/resolver-utils.ts:3, …
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
packages/gatsby-adapter-netlify/src/file-cdn-handler.ts → packages/gatsby-adapter-netlify/src/index.ts → packages/gatsby-adapter-netlify/src/file-cdn-handler.ts (one verified cycle inside a mutually-dependent group of 3 files) — packages/gatsby-adapter-netlify/src/file-cdn-handler.ts:4
packages/gatsby-cli/src/reporter/redux/index.ts → packages/gatsby-cli/src/reporter/redux/diagnostics.ts → packages/gatsby-cli/src/reporter/redux/utils.ts → packages/gatsby-cli/src/reporter/redux/index.ts (one verified cycle inside a mutually-dependent group of 10 files) — packages/gatsby-cli/src/reporter/redux/index.ts:6
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. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
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.
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:362
`server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:862
What to do
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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.
`forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. — packages/gatsby-source-drupal/src/utils.ts:177
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×4) — packages/gatsby-remark-images-contentful/src/index.js:245, packages/gatsby-remark-images/src/index.js:480, packages/gatsby/src/utils/dev-ssr/render-dev-html.ts:162, …
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.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.6 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`decorateBulkObject` is exported and takes `input: unknown` from its caller, and it calls itself at line 82 (`decorateBulkObject`) with a piece of `input` (and at line 89) — and nowhere in `decorateBulkObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decorateBulkObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby-source-shopify/src/helpers.ts:82
`recursiveAddFields` is exported and takes `ent: object` from its caller, and it calls itself at line 53 (`recursiveAddFields`) with a piece of `ent` (and at line 57) — and nowhere in `recursiveAddFields` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `recursiveAddFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby-source-lever/src/normalize.js:53
`getValueAt` is exported, takes a document from its caller (line 1) and hands it to `get`, which calls itself at line 17 (`get`) with a piece of `obj` — and nowhere in `get` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `get` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby/src/utils/get-value-at.ts:17
`compareKey` is exported and takes `a: unknown` from its caller, and it calls itself at line 112 (`compareKey`) with a piece of `a` (and at line 119) — and nowhere in `compareKey` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `compareKey` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby/src/datastore/lmdb/query/common.ts:112
`createDbQueriesFromObject` is exported, takes a document from its caller (line 79) and hands it to `createDbQueriesFromObjectNested`, which calls itself at line 92 (`createDbQueriesFromObjectNested`) with a piece of `filter` (and at line 112) — and nowhere in `createDbQueriesFromObjectNested` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `createDbQueriesFromObjectNested` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby/src/datastore/common/query.ts:92
`objectToDottedField` is exported and takes `obj: Record<string, unknown>` from its caller, and it calls itself at line 248 (`objectToDottedField`) with a piece of `obj` — and nowhere in `objectToDottedField` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `objectToDottedField` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby/src/datastore/common/query.ts:248
`processPlugin` is exported and takes `plugin: PluginRef` from its caller, and it calls itself at line 54 (`processPlugin`) with a piece of `plugin` — and nowhere in `processPlugin` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `processPlugin` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/gatsby/src/bootstrap/load-plugins/process-plugin.ts:54
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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.
`initialize` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `GATSBY_QUERY_ON_DEMAND` environment variable (set at line 222, cleared at line 228) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between — or by a promise that rejects at an `await`, and while this function is suspended at one every other callback the event loop runs sees the moved value too: the process then keeps the overwritten value for the rest of its life, and every later relative path, child-process launch or config read in ANY module resolves against it. That failure is silent and remote from its cause — the function that breaks is not the function that moved the directory. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — the `cwd` and `env` options of `child_process.spawn`/`exec`/`execSync` (or `Deno.Command`) scope both to the CHILD — or build absolute paths with `path.resolve`. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — packages/gatsby/src/services/initialize.ts:76
What to do
Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a working directory or an environment variable passed to the operation that needs it (the `cwd` and `env` options of `child_process`, or of `Deno.Command`) is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move, a `try`/`finally` is the least that makes the restore unconditional.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 2/22 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`createScreenshotNode` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`. — packages/gatsby-transformer-screenshot/src/gatsby-node.js:121
`blankGetRequest` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:197
`graphqlFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-source-shopify/src/clients.ts:14
`sourceFromOperation` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:22
`fetch` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`. — packages/gatsby-source-lever/src/fetch.js:8
`sourceNodes` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-source-lever/src/gatsby-node.js:37
`request` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-source-graphql/src/batching/dataloader-link.js:78
`validateContentfulAccess` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-source-contentful/src/gatsby-node.js:16
`generateImagesAndUpdateNode` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`. — packages/gatsby-remark-images-contentful/src/index.js:48
`getBase64Img` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`. — packages/gatsby-remark-images-contentful/src/utils/index.js:5
`graphQLIntrospection` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-graphiql-explorer/src/app.jsx:75
`fetchFragments` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-graphiql-explorer/src/utils.js:4
`createTicket` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-cli/src/login.ts:12
`getTicket` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-cli/src/login.ts:33
`getUsername` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby-cli/src/whoami.ts:5
`_fetchFile` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`. — packages/gatsby/src/utils/get-latest-gatsby-files.ts:27
`startServer` awaits `got.stream(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `got.stream(url, { signal })`. — REDACTED:67
`_processQueue` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/gatsby/src/utils/tracer/zipkin-local.ts:48
`fetchData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — packages/gatsby/cache-dir/fast-refresh-overlay/components/hooks.js:48, packages/gatsby/cache-dir/fast-refresh-overlay/components/hooks.js:84
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×38) — packages/gatsby-worker/src/index.ts:323, packages/gatsby-transformer-documentationjs/src/gatsby-node.js:213, packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:66, …
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — packages/gatsby-transformer-screenshot/src/gatsby-node.js:116
`.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/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:226
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
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.
21/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.0 `!` null assertions per 1k TypeScript source lines — 79 assertion(s) across the 82852 source line(s) of the 637 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/gatsby/src/datastore/in-memory/indexing.ts (18), packages/gatsby-source-drupal/src/plugin-options.ts (7), packages/gatsby/src/utils/jobs/manager.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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).
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.
Unscored — 5 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.
P12 CI test-gate honesty — 4 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'.
SC1 Supply-chain hygiene — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 6 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 — 43 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's PHP 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. PHP builds its object graph per request and shares none of it between requests. 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
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: process "/bin/sh -c apt-get -o Acquire::Check-Valid-Until=false update && apt-get install unzip git -y && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
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.
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.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.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.
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
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
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 10 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — Document value interpolated into markup unescaped could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
Banned license: @wordpress/a11y REDACTED:5304— `@wordpress/a11y` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/api-fetch REDACTED:5317— `@wordpress/api-fetch` 6.48.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/autop REDACTED:5330— `@wordpress/autop` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/blob REDACTED:5341— `@wordpress/blob` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/block-editor REDACTED:5352— `@wordpress/block-editor` 12.19.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/block-library starters/gatsby-starter-wordpress-blog/package.json:13— `@wordpress/block-library` 8.28.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is a production, optional or peer dependency this repository's committed lockfile resolves — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/block-serialization-default-parser REDACTED:5482— `@wordpress/block-serialization-default-parser` 4.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/blocks REDACTED:5493— `@wordpress/blocks` 12.28.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/commands REDACTED:5551— `@wordpress/commands` 0.22.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/components REDACTED:5576— `@wordpress/components` 26.0.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/compose REDACTED:5657— `@wordpress/compose` 6.28.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/core-data REDACTED:5683— `@wordpress/core-data` 6.28.1 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/data REDACTED:5731— `@wordpress/data` 9.21.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/date REDACTED:5759— `@wordpress/date` 4.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/deprecated REDACTED:5773— `@wordpress/deprecated` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/dom REDACTED:5785— `@wordpress/dom` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/dom-ready REDACTED:5797— `@wordpress/dom-ready` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/element REDACTED:5808— `@wordpress/element` 5.28.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/escape-html REDACTED:5826— `@wordpress/escape-html` 2.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/hooks REDACTED:5837— `@wordpress/hooks` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/html-entities REDACTED:5848— `@wordpress/html-entities` 3.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/i18n REDACTED:5859— `@wordpress/i18n` 4.51.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/icons REDACTED:5878— `@wordpress/icons` 9.42.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/interactivity REDACTED:5891— `@wordpress/interactivity` 5.0.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Banned license: @wordpress/interactivity-router REDACTED:5904— `@wordpress/interactivity-router` 1.1.0 is published on registry.npmjs.org under `GPL-2.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception.
Unlisted import 'remark' packages/gatsby-remark-autolink-headers/src/__tests__/index.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-code-repls/src/__tests__/index.js:9— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-custom-blocks/src/__tests__/index.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-embed-snippet/src/__tests__/index.js:9— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-images/src/__tests__/index.js:27— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-images-contentful/src/__tests__/index.js:93— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'remark' packages/gatsby-remark-smartypants/src/__tests__/index.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' packages/gatsby-plugin-canonical-urls/src/gatsby-ssr.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' REDACTED:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' packages/gatsby-plugin-layout/src/wrap-page.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' packages/gatsby-plugin-manifest/src/gatsby-ssr.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' packages/gatsby-plugin-preload-fonts/src/gatsby-ssr.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'react' packages/gatsby-source-contentful/src/__tests__/rich-text.js:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC1 · Text alternatives· <area> without a text alternative · ×4
<area> without a text alternative packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:456— This interactive image has no accessible name. Add a non-empty alt (or aria-label) describing its action/destination — alt="" does not name an image button or link.
<area> without a text alternative packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:522— This interactive image has no accessible name. Add a non-empty alt (or aria-label) describing its action/destination — alt="" does not name an image button or link.
<area> without a text alternative packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:605— This interactive image has no accessible name. Add a non-empty alt (or aria-label) describing its action/destination — alt="" does not name an image button or link.
<area> without a text alternative packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:724— This interactive image has no accessible name. Add a non-empty alt (or aria-label) describing its action/destination — alt="" does not name an image button or link.
AC2 · Forms & labels· <input> without a programmatic label · ×3
<input> without a programmatic label packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:745— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:809— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:911— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC1 · Text alternatives· <img> without a text alternative · ×2
<img> without a text alternative deprecated-packages/gatsby-admin/src/components/navbar.tsx:82— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative deprecated-packages/gatsby-admin/src/components/navbar.tsx:99— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
Unlisted import 'lodash' markdown.config.js:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'lodash' packages/gatsby-remark-custom-blocks/src/index.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@babel/types' packages/babel-preset-gatsby/src/optimize-hook-destructuring.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@babel/types' packages/gatsby-plugin-image/src/babel-helpers.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'sharp' packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:237— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'sharp' packages/gatsby-plugin-utils/src/polyfill-remote-file/types.ts:59— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'common-tags' REDACTED:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'common-tags' packages/gatsby-plugin-google-tagmanager/src/__tests__/gatsby-ssr.js:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'prop-types' packages/gatsby-plugin-google-analytics/src/index.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'prop-types' packages/gatsby-plugin-google-gtag/src/index.js:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/react' packages/gatsby-react-router-scroll/src/__tests__/use-scroll-restoration.tsx:12— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@testing-library/react' packages/gatsby-source-contentful/src/__tests__/rich-text.js:7— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'bluebird' packages/gatsby-remark-images/src/index.js:15— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'bluebird' packages/gatsby-remark-images-contentful/src/index.js:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Project dependency cycle packages/babel-plugin-remove-graphql-queries/package.json:24— The projects babel-plugin-remove-graphql-queries → gatsby → babel-plugin-remove-graphql-queries (one cycle inside a mutually-dependent group of 5 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
Unlisted import 'ansi-colors' packages/create-gatsby/src/components/form.js:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'configstore' packages/create-gatsby/src/utils/get-config-store.ts:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@parcel/types' packages/gatsby-parcel-namer-relative-to-cwd/src/index.ts:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import '@emotion/babel-plugin' packages/gatsby-plugin-emotion/src/gatsby-node.js:4— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'unist-util-visit' packages/gatsby-remark-embed-snippet/src/index.js:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'fastq' packages/gatsby-source-contentful/src/normalize.js:6— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
TodoComment packages/gatsby-worker/src/index.ts:245— // TODO: figure out IPC message order guarantees (or lack of them) - for now — 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/gatsby-source-wordpress/src/gatsby-browser.ts:72— // @ts-ignore - TODO: Fix me — 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/gatsby-source-wordpress/src/utils/cache.ts:311— // TODO: extend node type for wordpress? — 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/gatsby-source-wordpress/src/utils/cache.ts:346— // TODO: update gatsby types — 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/gatsby-source-shopify/src/clients.ts:6— // TODO Update logic for handling errors (500 specifically) and update the — 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/gatsby-source-drupal/src/plugin-options.ts:9— // TODO: type all options — 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/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1464— // TODO: support number and symbol index — 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/gatsby-plugin-utils/src/polyfill-remote-file/jobs/__tests__/gatsby-worker.ts:28— // TODO msw is failing on weird error during CI but not locally — 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/gatsby-plugin-page-creator/src/error-utils.ts:22— // TODO: Refactor to use contextual data instead of only context.sourceMessage — 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/gatsby-plugin-page-creator/src/extract-query.ts:18— // TODO: 'fields' possibly contains duplicate fields, e.g. field{name},field{description} that should be merged to field{name,description} — 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/gatsby-plugin-image/src/babel-plugin-parse-static-images.ts:45— // TODO: Add a shortlink to docs on the plugin — 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/gatsby-plugin-image/src/babel-plugin-parse-static-images.ts:74— // TODO add info about minimum Gatsby version once this is merged — 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/gatsby-core-utils/src/site-metadata.ts:35— // TODO(v5): Remove again - Necessary because of renaming in https://github.com/gatsbyjs/gatsby/pull/34094
TodoComment packages/gatsby-core-utils/src/remote-file-utils/fetch-file.ts:87— // TODO(v5): use dynamic import syntax - it's currently blocked because older v4 versions have V8-compile-cache — 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/gatsby-core-utils/src/remote-file-utils/fetch-file.ts:113— // TODO move to new Error type — 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/gatsby-core-utils/src/remote-file-utils/fetch-file.ts:260— // TODO move to new Error type — 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/gatsby-cli/src/index.ts:21— // @ts-ignore - TODO: Remove _CFLAGS_ again — 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/gatsby-cli/src/login.ts:51— // TODO: this will break if run from the CLI — 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/gatsby-cli/src/structured-errors/error-map.ts:378— // TODO: Make this a warning? Needs to be also changed where this error is called + tests — 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/gatsby-cli/src/structured-errors/error-map.ts:386— // TODO: Make this a warning? Needs to be also changed where this error is called + tests — 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/gatsby-cli/src/structured-errors/types.ts:93— // TODO(v6): Remove these types — 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/gatsby-cli/src/reporter/reporter.ts:196— // TODO: remove this once Error component can render this info — 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/gatsby-cli/src/reporter/start-logger.ts:25— // TODO move to dynamic imports — 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/gatsby-cli/src/reporter/start-logger.ts:30— // TODO move to dynamic imports — 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/gatsby-cli/src/reporter/start-logger.ts:33— // TODO move to dynamic imports — 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.
+ 111 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×116
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/adapters/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/contentful/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/development-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/mdx/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/path-prefix/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/production-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/themes/development-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/themes/gatsby-theme-about/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/themes/production-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/trailing-slash/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in e2e-tests/visual-regression/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/artifacts/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/esm-in-gatsby-files/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/functions/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `latest` in integration-tests/gatsby-pipeline/package.json, which names no releasable version: `latest` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/gatsby-source-wordpress/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/head-function-export/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/images/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/lmdb-regeneration/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/long-term-caching/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/ssr/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby — `gatsby` is declared as `next` in integration-tests/structured-logging/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby-adapter-netlify — `gatsby-adapter-netlify` is declared as `next` in e2e-tests/adapters/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby-cypress — `gatsby-cypress` is declared as `next` in e2e-tests/production-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Floating npm dependency: gatsby-image — `gatsby-image` is declared as `next` in e2e-tests/development-runtime/package.json, which names no releasable version: `next` is a moving dist-tag, not a version. A production dependency that cannot be resolved to one immutable release makes the build non-reproducible — two installs a day apart can ship different code — and leaves nothing for a vulnerability scanner to match against.
Skipped test: should download and transform an image packages/gatsby-plugin-utils/src/polyfill-remote-file/jobs/__tests__/gatsby-worker.ts:29— Skipped — switched off by it.skip
Skipped test: should process immediately when asked packages/gatsby-plugin-sharp/src/__tests__/index.js:124— Skipped — switched off by it.skip
Skipped test: checks if the user might be forcing navigation packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:56— Skipped — switched off by it.skip
Skipped test: checks if we clicked on an anchor packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:57— Skipped — switched off by it.skip
Skipped test: checks if the document author might be forcing navigation packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:58— Skipped — switched off by it.skip
Skipped test: checks if the destination/origin URLs have matching origins packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:59— Skipped — switched off by it.skip
Skipped test: checks if the destination/origin URLs have matching top level paths packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:60— Skipped — switched off by it.skip
Skipped test: checks if the destination URL wants to scroll the page with a hash anchor packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:61— Skipped — switched off by it.skip
Skipped test: handles pathPrefix if necessary packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:62— Skipped — switched off by it.skip
Skipped test: routes the destination href through gatsby packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:63— Skipped — switched off by it.skip
Skipped test: throws TypeError if input is undefined packages/gatsby-link/src/__tests__/is-local-link.js:15— Skipped — switched off by it.skip
Skipped test: throws TypeError if input is not a string packages/gatsby-link/src/__tests__/is-local-link.js:20— Skipped — switched off by it.skip
Skipped test: (unnamed test) packages/gatsby/src/utils/__tests__/node-manifest.ts:17— Skipped — switched off by xit
Skipped test: recovers from unknown output types packages/gatsby/src/schema/types/__tests__/sort-and-filter.js:394— Skipped — switched off by it.skip
Skipped test: Removes specific root fields packages/gatsby/src/schema/infer/__tests__/infer-input.js:227— Skipped — switched off by it.skip
Skipped test: Removes specific root fields packages/gatsby/src/schema/infer/__tests__/infer.js:432— Skipped — switched off by it.skip
Skipped test: Errors clearly when missing types packages/gatsby/src/schema/infer/__tests__/infer.js:1200— Skipped — switched off by it.skip
Skipped test: Uses a different type for the same child node types with a different key packages/gatsby/src/schema/infer/__tests__/infer.js:1277— Skipped — switched off by it.skip
Skipped test: Creates a new type after schema updates clear union types packages/gatsby/src/schema/infer/__tests__/infer.js:1306— Skipped — switched off by it.skip
Skipped test: Uses a reliable naming convention packages/gatsby/src/schema/infer/__tests__/infer.js:1310— Skipped — switched off by it.skip
Skipped test: does not warn about provided types packages/gatsby/src/schema/infer/__tests__/infer.js:1382— Skipped — switched off by it.skip
Skipped test: reports date and string conflicts packages/gatsby/src/schema/infer/__tests__/inference-metadata.ts:1023— Skipped — switched off by it.skip
Skipped test: validates non-existing extension options packages/gatsby/src/schema/extensions/__tests__/field-extensions.js:1005— Skipped — switched off by it.skip
Skipped test: merges user-defined type (graphql-js) with plugin-defined type packages/gatsby/src/schema/__tests__/build-schema.js:603— Skipped — switched off by it.skip
Skipped test: warns when merging plugin-defined type (graphql-js) with type defined by other plugin packages/gatsby/src/schema/__tests__/build-schema.js:850— Skipped — switched off by it.skip
Deprecated: rimraf deprecated-packages/gatsby-admin/package.json:52— rimraf 3.0.2, declared in deprecated-packages/gatsby-admin/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @hapi/hoek REDACTED:21— @hapi/hoek 8.5.1, declared in REDACTED, is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @hapi/joi REDACTED:22— @hapi/joi 15.1.1, declared in REDACTED, is marked deprecated by its publisher: "Switch to 'npm install joi'". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob REDACTED:36— glob 7.2.3, 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.
Deprecated: rimraf REDACTED:87— rimraf 3.0.2, declared in REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob deprecated-packages/gatsby-theme/package.json:22— glob 7.2.3, declared in deprecated-packages/gatsby-theme/package.json, 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.
Deprecated: glob integration-tests/cache-resilience/package.json:23— glob 7.2.3, declared in integration-tests/cache-resilience/package.json, 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.
Deprecated: rimraf integration-tests/gatsby-source-wordpress/package.json:29— rimraf 3.0.2, declared in integration-tests/gatsby-source-wordpress/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @lerna/prompt REDACTED:10— @lerna/prompt 3.18.5, declared in REDACTED, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:38— eslint 8.44.0, 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:48— glob 7.2.3, 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.
Deprecated: joi REDACTED:57— joi 14.3.1, declared in REDACTED, is marked deprecated by its publisher: "This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf REDACTED:66— rimraf 3.0.2, declared in REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator packages/babel-preset-gatsby-package/package.json:12— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6, declared in packages/babel-preset-gatsby-package/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-optional-chaining packages/babel-preset-gatsby-package/package.json:13— @babel/plugin-proposal-optional-chaining 7.20.7, declared in packages/babel-preset-gatsby-package/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @sigmacomputing/babel-plugin-lodash packages/babel-preset-gatsby-package/package.json:21— @sigmacomputing/babel-plugin-lodash 3.3.5, declared in packages/babel-preset-gatsby-package/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-class-properties packages/babel-preset-gatsby/package.json:12— @babel/plugin-proposal-class-properties 7.18.6, declared in packages/babel-preset-gatsby/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator packages/babel-preset-gatsby/package.json:13— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6, declared in packages/babel-preset-gatsby/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-optional-chaining packages/babel-preset-gatsby/package.json:14— @babel/plugin-proposal-optional-chaining 7.20.7, declared in packages/babel-preset-gatsby/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: yurnalist packages/gatsby-cli/package.json:52— yurnalist 2.1.0, declared in packages/gatsby-cli/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @sigmacomputing/babel-plugin-lodash packages/gatsby-cli/package.json:61— @sigmacomputing/babel-plugin-lodash 3.3.5, declared in packages/gatsby-cli/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: rimraf packages/gatsby-cli/package.json:70— rimraf 3.0.2, declared in packages/gatsby-cli/package.json, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-class-properties packages/gatsby-codemods/package.json:28— @babel/plugin-proposal-class-properties 7.18.6, declared in packages/gatsby-codemods/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: verdaccio packages/gatsby-dev-cli/package.json:24— verdaccio 5.25.0, declared in packages/gatsby-dev-cli/package.json, is marked deprecated by its publisher: "this version is deprecated, please migrate to 6.x versions". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-class-properties packages/gatsby-graphiql-explorer/package.json:37— @babel/plugin-proposal-class-properties 7.18.6, declared in packages/gatsby-graphiql-explorer/package.json, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
FunctionTooLong: declare-plugin-options-schema.pluginOptionsSchema packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:23— FunctionTooLong — pluginOptionsSchema runs 704 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 604 over it, 7.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.
FunctionTooLong: start-server.startServer REDACTED:67— FunctionTooLong — startServer runs 514 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 414 over it, 5.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: extend-node-type.remarkExtendNodeType packages/gatsby-transformer-remark/src/extend-node-type.js:88— FunctionTooLong — remarkExtendNodeType runs 460 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 360 over it, 4.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: gatsby-node.sourceNodes packages/gatsby-source-drupal/src/gatsby-node.ts:143— FunctionTooLong — sourceNodes runs 440 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 340 over it, 4.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: build.build packages/gatsby/src/commands/build.ts:72— FunctionTooLong — build runs 371 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 271 over it, 3.71× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: create-cli.buildLocalCommands packages/gatsby-cli/src/create-cli.ts:26— FunctionTooLong — buildLocalCommands runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: static-entry.staticPage REDACTED:114— FunctionTooLong — staticPage runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× 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: ssr-develop-static-entry.staticPage REDACTED:59— FunctionTooLong — staticPage runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: pluginOptionsSchema.pluginOptionSchema packages/gatsby-plugin-manifest/src/pluginOptionsSchema.js:1— FunctionTooLong — pluginOptionSchema runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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: html.htmlReducer packages/gatsby/src/redux/reducers/html.ts:35— FunctionTooLong — htmlReducer runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: public.actions.createPage packages/gatsby/src/redux/actions/public.js:185— FunctionTooLong — actions.createPage runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.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: image-data.generateImageData packages/gatsby-plugin-sharp/src/image-data.ts:123— FunctionTooLong — generateImageData runs 212 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 112 over it, 2.12× 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: lambda-handler.prepareFunction packages/gatsby-adapter-netlify/src/lambda-handler.ts:29— FunctionTooLong — prepareFunction runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: bundle-webpack.createGraphqlEngineBundle packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:336— FunctionTooLong — createGraphqlEngineBundle runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: serve.default REDACTED:96— FunctionTooLong — default runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.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: manager.getRoutesManifest packages/gatsby/src/utils/adapter/manager.ts:335— FunctionTooLong — getRoutesManifest runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.default packages/babel-plugin-remove-graphql-queries/src/index.ts:298— FunctionTooLong — default runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: gatsby-node.onCreateNode packages/gatsby-transformer-documentationjs/src/gatsby-node.js:204— FunctionTooLong — onCreateNode runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× 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: gatsby-node.createWebpackConfig packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:142— FunctionTooLong — createWebpackConfig runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: bundle-webpack.createPageSSRBundle packages/gatsby/src/utils/page-ssr-module/bundle-webpack.ts:65— FunctionTooLong — createPageSSRBundle runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: field-transformers.getFieldTransformers packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js:13— FunctionTooLong — getFieldTransformers runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js:116— FunctionTooLong — generateNodeQueriesFromIngestibleFields runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× 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: customize-schema.createFields packages/gatsby-transformer-sharp/src/customize-schema.js:563— FunctionTooLong — createFields runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.fluid packages/gatsby-plugin-sharp/src/index.js:420— FunctionTooLong — fluid runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: gatsby-layout-loader.gatsbyLayoutLoader packages/gatsby-plugin-mdx/src/gatsby-layout-loader.ts:26— FunctionTooLong — gatsbyLayoutLoader runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Sync-over-async blocking packages/create-gatsby/src/init-starter.ts:56— `fs.existsSync` in `maybeCreateGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/create-gatsby/src/init-starter.ts:72— `execSync` in `createInitialGitCommit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:64— `existsSync` in `maybeCreateGitIgnore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:86— `execSync` in `createInitialGitCommit` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:139— `existsSync` in `copy` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:324— `existsSync` in `initStarter` 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/gatsby-core-utils/src/page-html.ts:22— `fs.existsSync` in `remove` 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/gatsby-dev-cli/src/watch.js:83— `fs.chmodSync` in `callback to fs.copy` 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/gatsby-dev-cli/src/watch.js:203— `fs.existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/gatsby-plugin-image/src/node-apis/image-processing.ts:34— `fs.existsSync` in `createImageNode` 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/gatsby-plugin-image/src/node-apis/image-processing.ts:126— `fs.existsSync` in `callback to 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/gatsby-plugin-page-creator/src/gatsby-node.ts:87— `existsSync` in `createPagesStatefully` 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/gatsby-remark-copy-linked-files/src/index.js:301— `fsExtra.existsSync` in `callback to Array.from` 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/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:36— `readFileSync` in `getImageBase64` 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/gatsby-source-wordpress/src/steps/ingest-remote-schema/write-queries-to-disk.js:27— `fs.rmSync` in `writeQueriesToDisk` 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:398— `fs.existsSync` in `copyFileToStaticAndReturnUrlPath` 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:546— `clipboardy.writeSync` in `handleFetchErrors` 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/gatsby-transformer-sharp/src/customize-schema.js:597— `fs.readFileSync` in `resolve` 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/gatsby-transformer-sharp/src/customize-schema.js:607— `fs.existsSync` in `resolve` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:157— `fs.readFileSync` in `getPageData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:290— `fs.readFileSync` in `readSliceData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:162— `fs.readFileSync` in `loadPageDataSync` 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/gatsby/src/commands/build.ts:463— `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 REDACTED:159— `fs.readFileSync` in `exports` 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/gatsby/src/internal-plugins/functions/gatsby-node.ts:52— `fs.utimesSync` in `ensureFunctionIsCompiled` 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.
Boundary violation [package:relative-cross-package] .jestSetup.js:22— .jestSetup.js:22 reaches into another package with a relative path (./packages/gatsby/src/utils/worker/__tests__/test-helpers/ts-register.js) — import the package by name instead.
Boundary violation [package:test-suite-dependency] .jestSetup.js:22— .jestSetup.js:22 imports packages/gatsby/src/utils/worker/__tests__/test-helpers/ts-register.js, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
Boundary violation [package:undeclared-workspace-dep] packages/create-gatsby/src/utils/site-metadata.ts:7— packages/create-gatsby/src/utils/site-metadata.ts:7 imports gatsby-core-utils, 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:third-party-deep-import] packages/gatsby-plugin-offline/src/gatsby-node.js:174— packages/gatsby-plugin-offline/src/gatsby-node.js:174 imports idb-keyval/dist/, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-drupal/src/utils.ts:12— packages/gatsby-source-drupal/src/utils.ts:12 imports gatsby-core-utils, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/create-operations.ts:1— packages/gatsby-source-shopify/src/create-operations.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/create-resolvers.ts:1— packages/gatsby-source-shopify/src/create-resolvers.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:relative-cross-package] packages/gatsby-source-shopify/src/create-schema-customization.ts:1— packages/gatsby-source-shopify/src/create-schema-customization.ts:1 reaches into another package with a relative path (../../gatsby) — import the package by name instead.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/helpers.ts:1— packages/gatsby-source-shopify/src/helpers.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/plugin-options-schema.ts:1— packages/gatsby-source-shopify/src/plugin-options-schema.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/process-bulk-results.ts:1— packages/gatsby-source-shopify/src/process-bulk-results.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:2— packages/gatsby-source-shopify/src/resolve-gatsby-image-data.ts:2 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] REDACTED:2— REDACTED:2 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/source-nodes.ts:1— packages/gatsby-source-shopify/src/source-nodes.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:app-undeclared-workspace-dep] packages/gatsby-source-shopify/src/update-cache.ts:1— packages/gatsby-source-shopify/src/update-cache.ts:1 imports gatsby, a workspace package this repository defines, while this package's own REDACTED declares its OTHER workspace siblings and not this one — the import resolves only through the root install's hoisted link, so the manifest that is this package's record of what it depends on is incomplete, and nothing fails until the layout changes. Add it to this package's dependencies.
Boundary violation [package:third-party-deep-import] packages/gatsby-transformer-react-docgen/src/parse.js:2— packages/gatsby-transformer-react-docgen/src/parse.js:2 imports react-docgen/dist/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/extend-node.js:83— packages/gatsby-transformer-remark/src/__tests__/extend-node.js:83 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/schema-composer) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/extend-node.js:87— packages/gatsby-transformer-remark/src/__tests__/extend-node.js:87 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/add-inferred-fields) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/extend-node.js:90— packages/gatsby-transformer-remark/src/__tests__/extend-node.js:90 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/inference-metadata) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/extend-node.js:93— packages/gatsby-transformer-remark/src/__tests__/extend-node.js:93 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/build-example-data) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:124— packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:124 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/schema-composer) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:127— packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:127 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/add-inferred-fields) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:130— packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:130 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/inference-metadata) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:133— packages/gatsby-transformer-remark/src/__tests__/on-node-create.js:133 reaches past another workspace package's public entry into its internals with a relative path (../../../gatsby/src/schema/infer/build-example-data) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/gatsby-transformer-remark/src/code-handler.js:1— packages/gatsby-transformer-remark/src/code-handler.js:1 imports mdast-util-to-hast/lib/handlers/code, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
+ 15 more in this group — see findings.md.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×40
JavaScript dependencies are not locked .github/actions/format-stale-output/package.json:16— .github/actions/format-stale-output/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked .github/actions/gatsby-site-showcase-validator/package.json:6— .github/actions/gatsby-site-showcase-validator/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked .github/actions/high-priority-prs/package.json:9— .github/actions/high-priority-prs/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/create-pages/package.json:11— benchmarks/create-pages/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/docker-runner/package.json:31— benchmarks/docker-runner/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-csv-markdown/package.json:15— benchmarks/gabe-csv-markdown/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-csv-text/package.json:15— benchmarks/gabe-csv-text/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-fs-markdown-images/package.json:15— benchmarks/gabe-fs-markdown-images/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-fs-markdown-route-api/package.json:16— benchmarks/gabe-fs-markdown-route-api/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-fs-markdown/package.json:15— benchmarks/gabe-fs-markdown/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-fs-mdx/package.json:15— benchmarks/gabe-fs-mdx/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-fs-text/package.json:15— benchmarks/gabe-fs-text/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-json-text/package.json:15— benchmarks/gabe-json-text/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/gabe-yaml-text/package.json:15— benchmarks/gabe-yaml-text/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/image-processing/package.json:7— benchmarks/image-processing/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/markdown_id/package.json:7— benchmarks/markdown_id/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/markdown_slug/package.json:7— benchmarks/markdown_slug/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/markdown_table/package.json:13— benchmarks/markdown_table/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/md/package.json:18— benchmarks/md/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/mdx/package.json:18— benchmarks/mdx/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/plugin-manifest/package.json:14— benchmarks/plugin-manifest/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/query-filters-sort/package.json:11— benchmarks/query-filters-sort/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/query/package.json:11— benchmarks/query/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/source-agilitycms/package.json:17— benchmarks/source-agilitycms/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
JavaScript dependencies are not locked benchmarks/source-contentful/package.json:19— benchmarks/source-contentful/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Swallowed exception (empty catch) packages/gatsby-worker/src/index.ts:323— 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/gatsby-transformer-documentationjs/src/gatsby-node.js:213— 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:66— 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:79— 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:534— 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/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:226— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:280— 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:289— 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/gatsby-source-npm-package-search/src/gatsby-node.js:103— 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/gatsby-remark-copy-linked-files/src/index.js:230— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/gatsby-remark-copy-linked-files/src/index.js:263— 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/gatsby-dev-cli/src/index.js:114— 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/gatsby-core-utils/src/ci.ts:22— 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:47— 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/gatsby-cli/src/create-cli.ts:459— 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/gatsby-cli/src/create-cli.ts:524— 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/gatsby-cli/src/reporter/errors.ts:140— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/gatsby-cli/src/reporter/errors.ts:182— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/gatsby/src/utils/develop-preload-headers.ts:66— 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/gatsby/src/utils/ensure-file-content.ts:10— 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/gatsby/src/utils/feedback.ts:112— 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/gatsby/src/utils/find-page-by-path.ts:52— 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/gatsby/src/utils/gatsby-dependents.ts:57— 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/gatsby/src/utils/module-resolver.ts:16— 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/gatsby/src/utils/prepare-urls.ts:57— 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.
No assertions: %s packages/gatsby-worker/src/__tests__/task-queue.ts:212— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) packages/gatsby-transformer-remark/src/__tests__/extend-node.js:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Creates entities from object collections of entities packages/gatsby-source-lever/src/__tests__/normalize.js:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: creates a file node packages/gatsby-source-filesystem/src/__tests__/create-file-node.js:134— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should pass when gatsby-plugin-image is installed and configured packages/gatsby-source-contentful/src/__tests__/gatsby-node.js:452— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: does not crash when no pluginConfig is provided packages/gatsby-plugin-google-gtag/src/__tests__/gatsby-ssr.js:4— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: it can be instantiated packages/gatsby/src/utils/__tests__/cache-lmdb.ts:19— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) packages/gatsby/src/utils/__tests__/websocket-manager.ts:61— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${methodName} can filter out null value packages/gatsby/cache-dir/__tests__/static-entry.js:390— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${methodName} can filter out null values packages/gatsby/cache-dir/__tests__/static-entry.js:397— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${methodName} can filter out empty array packages/gatsby/cache-dir/__tests__/static-entry.js:407— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${methodName} can filter out empty arrays packages/gatsby/cache-dir/__tests__/static-entry.js:414— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: ${methodName} can flatten arrays packages/gatsby/cache-dir/__tests__/static-entry.js:421— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: contains a greeting examples/using-jest/src/pages/__tests__/index.js:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders siteTitle examples/using-jest/src/components/__tests__/header.js:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: successfully loads examples/gatsbygram/cypress/integration/about-page-spec.js:2— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: contains the title with an SVG icon and text "Gatsbygram" examples/gatsbygram/cypress/integration/about-page-spec.js:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: displays title of the page examples/gatsbygram/cypress/integration/about-page-spec.js:25— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: successfully loads examples/gatsbygram/cypress/integration/home-page-spec.js:4— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: contains the title with an SVG icon and text "Gatsbygram" examples/gatsbygram/cypress/integration/home-page-spec.js:8— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: renders user avatar and name examples/gatsbygram/cypress/integration/home-page-spec.js:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows user's posts and followers count examples/gatsbygram/cypress/integration/home-page-spec.js:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shows number of likes when hovered on a post examples/gatsbygram/cypress/integration/home-page-spec.js:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work correctly e2e-tests/adapters/cypress/e2e/dsg.cy.ts:4— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: direct visit no query params (${staticPath}) e2e-tests/adapters/cypress/e2e/ssr.cy.ts:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 11 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×33
No test reaches this file packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.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/gatsby-source-wordpress/src/utils/fetch-graphql.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.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/gatsby/src/schema/graphql-engine/bundle-webpack.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby/src/commands/build.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.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/gatsby/src/internal-plugins/functions/gatsby-node.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby/src/utils/page-ssr-module/lambda.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby/src/utils/page-ssr-module/entry.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-plugin-page-creator/src/gatsby-node.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/create-schema-customization/helpers.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/gatsby-source-wordpress/src/steps/preview/index.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-codemods/src/transforms/gatsby-plugin-image.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/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.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/gatsby-source-wordpress/src/utils/cache.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.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/gatsby-source-wordpress/src/models/gatsby-api.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-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/gatsby-design-tokens/src/theme-gatsbyjs-org.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/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/gatsby/cache-dir/production-app.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/gatsby/src/commands/develop.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 8 more in this group — see findings.md.
D12 · Dependency Hygiene· One package at two majors across the workspace · ×22
One package at two majors across the workspace: @graphql-tools/utils — `@graphql-tools/utils` is maintained at 2 different major versions inside this one repository — major 7 in REDACTED; major 8 in packages/gatsby-source-graphql/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: @sindresorhus/slugify — `@sindresorhus/slugify` is maintained at 2 different major versions inside this one repository — major 1 in packages/gatsby-plugin-page-creator/package.json; major 2 in e2e-tests/mdx/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: cache-manager — `cache-manager` is maintained at 2 different major versions inside this one repository — major 2 in REDACTED; major 3 in packages/gatsby-source-wordpress/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: fs-extra — `fs-extra` is maintained at 2 different major versions inside this one repository — major 10 in deprecated-packages/gatsby-plugin-graphql-config/package.json, REDACTED; major 11 in deprecated-packages/gatsby-plugin-gatsby-cloud/package.json, deprecated-packages/gatsby-telemetry/package.json, e2e-tests/mdx/package.json (+19 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: gatsby — `gatsby` is maintained at 3 different major versions inside this one repository — major 3 in integration-tests/gatsby-cli/gatsby-sites/gatsby-build-errors/package.json, integration-tests/gatsby-cli/gatsby-sites/gatsby-build-ssr-errors/package.json, integration-tests/gatsby-cli/gatsby-sites/gatsby-build/package.json (+3 more); major 4 in integration-tests/cache-resilience/package.json; major 5 in e2e-tests/react-19/package.json, starters/blog/package.json, starters/default/package.json (+4 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: gatsby-core-utils — `gatsby-core-utils` is maintained at 2 different major versions inside this one repository — major 3 in REDACTED; major 4 in deprecated-packages/gatsby-plugin-gatsby-cloud/package.json, deprecated-packages/gatsby-telemetry/package.json, packages/babel-plugin-remove-graphql-queries/package.json (+24 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: gatsby-source-filesystem — `gatsby-source-filesystem` is maintained at 2 different major versions inside this one repository — major 2 in integration-tests/gatsby-cli/gatsby-sites/gatsby-plugin/package.json; major 5 in packages/gatsby-source-contentful/package.json, packages/gatsby-source-drupal/package.json, packages/gatsby-source-shopify/package.json (+3 more). Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: globby — `globby` is maintained at 2 different major versions inside this one repository — major 10 in deprecated-packages/gatsby-theme/package.json; major 11 in packages/gatsby-plugin-page-creator/package.json, REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: graphql — `graphql` is maintained at 2 different major versions inside this one repository — major 15 in REDACTED; major 16 in packages/gatsby-codemods/package.json, REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: graphql-compose — `graphql-compose` is maintained at 2 different major versions inside this one repository — major 7 in REDACTED; major 9 in packages/gatsby-plugin-utils/package.json, REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: mdast-util-toc — `mdast-util-toc` is maintained at 2 different major versions inside this one repository — major 5 in REDACTED; major 6 in packages/gatsby-plugin-mdx/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: node-fetch — `node-fetch` is maintained at 2 different major versions inside this one repository — major 2 in REDACTED, packages/gatsby-cli/package.json, packages/gatsby-plugin-benchmark-reporting/package.json (+6 more); major 3 in e2e-tests/development-runtime/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: postcss-loader — `postcss-loader` is maintained at 2 different major versions inside this one repository — major 5 in REDACTED; major 7 in packages/gatsby-plugin-postcss/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react — `react` is maintained at 2 different major versions inside this one repository — major 18 in e2e-tests/adapters/package.json, e2e-tests/contentful/package.json, e2e-tests/development-runtime/package.json (+31 more); major 19 in e2e-tests/react-19/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-dom — `react-dom` is maintained at 2 different major versions inside this one repository — major 18 in e2e-tests/adapters/package.json, e2e-tests/contentful/package.json, e2e-tests/development-runtime/package.json (+31 more); major 19 in e2e-tests/react-19/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: react-helmet — `react-helmet` is maintained at 2 different major versions inside this one repository — major 5 in integration-tests/gatsby-cli/gatsby-sites/gatsby-build-errors/package.json, integration-tests/gatsby-cli/gatsby-sites/gatsby-build-ssr-errors/package.json, integration-tests/gatsby-cli/gatsby-sites/gatsby-build/package.json (+3 more); major 6 in integration-tests/gatsby-pipeline/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: remark-gfm — `remark-gfm` is maintained at 2 different major versions inside this one repository — major 1 in REDACTED; major 3 in e2e-tests/mdx/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: remark-parse — `remark-parse` is maintained at 2 different major versions inside this one repository — major 6 in REDACTED; major 9 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: remark-stringify — `remark-stringify` is maintained at 2 different major versions inside this one repository — major 8 in REDACTED; major 9 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: unified — `unified` is maintained at 3 different major versions inside this one repository — major 8 in REDACTED; major 9 in packages/gatsby-remark-katex/package.json, REDACTED; major 10 in packages/gatsby-plugin-mdx/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: unist-util-visit — `unist-util-visit` is maintained at 2 different major versions inside this one repository — major 2 in REDACTED, packages/gatsby-remark-autolink-headers/package.json, packages/gatsby-remark-copy-linked-files/package.json (+6 more); major 4 in packages/gatsby-plugin-mdx/package.json. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
One package at two majors across the workspace: uuid — `uuid` is maintained at 2 different major versions inside this one repository — major 3 in REDACTED; major 8 in REDACTED. Every major carries its own breaking changes, advisories and upgrade path, so the cost of keeping current is paid more than once; and where the packages are installed together, the resolver cannot dedupe them, so both copies ship.
FileTooLong: redux/types.ts packages/gatsby/src/redux/types.ts— FileTooLong — 973 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 473 over it, 1.95× 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: schema/schema.js packages/gatsby/src/schema/schema.js— FileTooLong — 966 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 466 over it, 1.93× 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: structured-errors/error-map.ts packages/gatsby-cli/src/structured-errors/error-map.ts— FileTooLong — 835 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: errors (23-981). The bar is 500 significant lines; this is 335 over it, 1.67× 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: actions/public.js packages/gatsby/src/redux/actions/public.js— FileTooLong — 740 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 240 over it, 1.48× 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: steps/declare-plugin-options-schema.js packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js— FileTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: pluginOptionsSchema (23-1007). The bar is 500 significant lines; this is 220 over it, 1.44× 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: in-memory/indexing.ts packages/gatsby/src/datastore/in-memory/indexing.ts— FileTooLong — 655 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 155 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: src/gatsby-node.ts packages/gatsby-source-drupal/src/gatsby-node.ts— FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 145 over it, 1.29× 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: utils/plugin-options-schema-joi-type.ts packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/customize-schema.js packages/gatsby-transformer-sharp/src/customize-schema.js— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 99 over it, 1.20× 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: create-nodes/process-node.js packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js— FileTooLong — 586 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 86 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/build-html.ts packages/gatsby/src/commands/build-html.ts— FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 84 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: schema/node-model.js packages/gatsby/src/schema/node-model.js— FileTooLong — 575 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 75 over it, 1.15× 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 — 572 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: startServer (67-887). The bar is 500 significant lines; this is 72 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/normalize.js packages/gatsby-source-contentful/src/normalize.js— FileTooLong — 558 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 58 over it, 1.12× 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: utils/fetch-graphql.ts packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: cache-dir/loader.js packages/gatsby/cache-dir/loader.js— FileTooLong — 539 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 74% of them inside a single declaration: BaseLoader (111-834). The bar is 500 significant lines; this is 39 over it, 1.08× 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/webpack-utils.ts packages/gatsby/src/utils/webpack-utils.ts— FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: createWebpackUtils (176-853). The bar is 500 significant lines; this is 35 over it, 1.07× 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: schema/resolvers.ts packages/gatsby/src/schema/resolvers.ts— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× 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: child/render-html.ts packages/gatsby/src/utils/worker/child/render-html.ts— FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 22 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/extend-node-type.js packages/gatsby-transformer-remark/src/extend-node-type.js— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED packages/gatsby-plugin-sharp/src/index.js— FileTooLong — 515 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 15 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
X2 · Cancellation propagation· Async function without AbortSignal · ×20
Async function without AbortSignal: createScreenshotNode packages/gatsby-transformer-screenshot/src/gatsby-node.js:121— `createScreenshotNode` awaits `axios.post(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.post(url, { signal })`.
Async function without AbortSignal: blankGetRequest packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:197— `blankGetRequest` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: graphqlFetch packages/gatsby-source-shopify/src/clients.ts:14— `graphqlFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sourceFromOperation REDACTED:22— `sourceFromOperation` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetch packages/gatsby-source-lever/src/fetch.js:8— `fetch` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`.
Async function without AbortSignal: sourceNodes packages/gatsby-source-lever/src/gatsby-node.js:37— `sourceNodes` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: request packages/gatsby-source-graphql/src/batching/dataloader-link.js:78— `request` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: validateContentfulAccess packages/gatsby-source-contentful/src/gatsby-node.js:16— `validateContentfulAccess` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: generateImagesAndUpdateNode packages/gatsby-remark-images-contentful/src/index.js:48— `generateImagesAndUpdateNode` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`.
Async function without AbortSignal: getBase64Img packages/gatsby-remark-images-contentful/src/utils/index.js:5— `getBase64Img` awaits `axios(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios(url, { signal })`.
Async function without AbortSignal: graphQLIntrospection packages/gatsby-graphiql-explorer/src/app.jsx:75— `graphQLIntrospection` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchFragments packages/gatsby-graphiql-explorer/src/utils.js:4— `fetchFragments` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: createTicket packages/gatsby-cli/src/login.ts:12— `createTicket` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getTicket packages/gatsby-cli/src/login.ts:33— `getTicket` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: getUsername packages/gatsby-cli/src/whoami.ts:5— `getUsername` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: _fetchFile packages/gatsby/src/utils/get-latest-gatsby-files.ts:27— `_fetchFile` awaits `axios.get(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `axios.get(url, { signal })`.
Async function without AbortSignal: startServer REDACTED:67— `startServer` awaits `got.stream(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `got.stream(url, { signal })`.
Async function without AbortSignal: _processQueue packages/gatsby/src/utils/tracer/zipkin-local.ts:48— `_processQueue` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchData packages/gatsby/cache-dir/fast-refresh-overlay/components/hooks.js:48— `fetchData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchData packages/gatsby/cache-dir/fast-refresh-overlay/components/hooks.js:84— `fetchData` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
FixmeComment packages/gatsby-cli/src/reporter/errors.ts:127— // FIXME: when https://github.com/AriaMinaei/pretty-error/pull/49 is merged
FixmeComment packages/gatsby-cli/src/reporter/start-logger.ts:21— // FIXME: disable IPC logger when inside worker. IPC messages crash jest-worker. — 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.
FixmeComment packages/gatsby/src/state-machines/query-running/index.ts:44— // FIXME: this has to be fixed properly by not leaving "extractingQueries" state — 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.
FixmeComment packages/gatsby/src/schema/infer/inference-metadata.ts:231— // FIXME: this will produce false positives as this node can be — 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.
FixmeComment packages/gatsby/src/schema/infer/is-file.ts:77— // FIXME: Do we need all of this? — 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.
FixmeComment packages/gatsby/src/redux/types.ts:1056— // FIXME: figure out why payload can be undefined here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment packages/gatsby/src/redux/reducers/__tests__/queries.ts:278— // FIXME: probably we shouldn't invalidate query text if it didn't actually change — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts:105— // FIXME: sharedStructuresKey breaks tests - probably need some cleanup for it on DELETE_CACHE — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts:202— // FIXME: add -1 when restoring shared structures key — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/query/common.ts:92— // FIXME: replace with an import in v4 — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/query/create-index.ts:116— // FIXME — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/query/create-index.ts:195— // FIXME — 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.
FixmeComment packages/gatsby/src/datastore/lmdb/query/create-index.ts:299— // FIXME: not sure if we want this but there are tests for this :/ — 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.
FixmeComment packages/gatsby/src/commands/build-utils.ts:161— // FIXME: checking pages state here because pages are not persisted — 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.
Fake-async — async method never awaits packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:308— `onPreInit` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:314— `onPreBootstrap` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js:320— `onPreBuild` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-lever/src/normalize.js:14— `createGraphQLNode` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/auth-handling.ts:5— `storedAuthSettings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/auth-handling.ts:19— `restoreAuthPluginOptions` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:231— `isWpGatsby` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js:15— `customizeSchema` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/image-routes.ts:4— `imageRoutes` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js:6— `buildNonNodeQueries` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby-source-wordpress/src/steps/log-post-build-warnings.ts:5— `logPostBuildWarnings` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby/src/internal-plugins/partytown/gatsby-node.ts:36— `onCreateDevServer` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby/src/state-machines/develop/actions.ts:54— `setQueryRunningFinished` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/gatsby/src/utils/feedback.ts:158— `userGetsSevenDayFeedback` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Off the main sequence: create-gatsby — create-gatsby: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: gatsby-sharp — gatsby-sharp: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: gatsby-core-utils — gatsby-core-utils: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: gatsby — gatsby: abstractness 0.06, instability 0.16, distance 0.78 — zone of pain — concrete and depended on by 85 project(s), so it's rigid to change.
Off the main sequence: gatsby-page-utils — gatsby-page-utils: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: gatsby-react-router-scroll — gatsby-react-router-scroll: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: gatsby-worker — gatsby-worker: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
R4 · Test Coverage· This test file cannot be loaded · ×7
This test file cannot be loaded packages/gatsby/src/schema/infer/__tests__/infer.js:433— packages/gatsby/src/schema/infer/__tests__/infer.js:433 imports '../infer', 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/gatsby/src/utils/__tests__/test-import-error.ts:8— packages/gatsby/src/utils/__tests__/test-import-error.ts:8 imports './fixtures/module-does-not-exist.js', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded peril/tests/invite-collaborator.test.ts:6— peril/tests/invite-collaborator.test.ts:6 imports '../rules/invite-collaborator', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded peril/tests/validate-yaml/validate-yaml-authors.test.ts:3— peril/tests/validate-yaml/validate-yaml-authors.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded peril/tests/validate-yaml/validate-yaml-creators.test.ts:3— peril/tests/validate-yaml/validate-yaml-creators.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded peril/tests/validate-yaml/validate-yaml-sites.test.ts:3— peril/tests/validate-yaml/validate-yaml-sites.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded peril/tests/validate-yaml/validate-yaml-starters.test.ts:3— peril/tests/validate-yaml/validate-yaml-starters.test.ts:3 imports '../../rules/validate-yaml', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×7
Recursive walk over a caller-supplied document has no depth cap packages/gatsby-source-shopify/src/helpers.ts:82— `decorateBulkObject` is exported and takes `input: unknown` from its caller, and it calls itself at line 82 (`decorateBulkObject`) with a piece of `input` (and at line 89) — and nowhere in `decorateBulkObject` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decorateBulkObject` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby-source-lever/src/normalize.js:53— `recursiveAddFields` is exported and takes `ent: object` from its caller, and it calls itself at line 53 (`recursiveAddFields`) with a piece of `ent` (and at line 57) — and nowhere in `recursiveAddFields` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `recursiveAddFields` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby/src/utils/get-value-at.ts:17— `getValueAt` is exported, takes a document from its caller (line 1) and hands it to `get`, which calls itself at line 17 (`get`) with a piece of `obj` — and nowhere in `get` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `get` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby/src/datastore/lmdb/query/common.ts:112— `compareKey` is exported and takes `a: unknown` from its caller, and it calls itself at line 112 (`compareKey`) with a piece of `a` (and at line 119) — and nowhere in `compareKey` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `compareKey` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby/src/datastore/common/query.ts:92— `createDbQueriesFromObject` is exported, takes a document from its caller (line 79) and hands it to `createDbQueriesFromObjectNested`, which calls itself at line 92 (`createDbQueriesFromObjectNested`) with a piece of `filter` (and at line 112) — and nowhere in `createDbQueriesFromObjectNested` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `createDbQueriesFromObjectNested` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby/src/datastore/common/query.ts:248— `objectToDottedField` is exported and takes `obj: Record<string, unknown>` from its caller, and it calls itself at line 248 (`objectToDottedField`) with a piece of `obj` — and nowhere in `objectToDottedField` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `objectToDottedField` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap packages/gatsby/src/bootstrap/load-plugins/process-plugin.ts:54— `processPlugin` is exported and takes `plugin: PluginRef` from its caller, and it calls itself at line 54 (`processPlugin`) with a piece of `plugin` — and nowhere in `processPlugin` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `processPlugin` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
MethodTooLong: StaticQueryMapper.apply packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:71— MethodTooLong — apply 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.
MethodTooLong: BaseLoader.loadPage packages/gatsby/cache-dir/loader.js:349— MethodTooLong — loadPage runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dev404Page.render REDACTED:87— MethodTooLong — render runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FileParser.parseFile packages/gatsby/src/query/file-parser.js:486— MethodTooLong — parseFile 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.
MethodTooLong: WorkerPool.startAll packages/gatsby-worker/src/index.ts:178— MethodTooLong — startAll runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.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.
Duplicated block (24 lines × 2 locations) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:86— packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:86 · packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:51 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (24 lines × 2 locations) packages/gatsby-plugin-image/src/image-utils.ts:535— packages/gatsby-plugin-image/src/image-utils.ts:535 · packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:601 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (24 lines × 2 locations) packages/gatsby/cache-dir/fast-refresh-overlay/components/graphql-errors.js:69— packages/gatsby/cache-dir/fast-refresh-overlay/components/graphql-errors.js:69 · packages/gatsby/cache-dir/fast-refresh-overlay/components/runtime-errors.js:108 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (24 lines × 2 locations) packages/gatsby/src/datastore/in-memory/indexing.ts:833— packages/gatsby/src/datastore/in-memory/indexing.ts:833 · packages/gatsby/src/datastore/in-memory/indexing.ts:891 — 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 (24 lines × 2 locations) packages/gatsby/src/datastore/in-memory/indexing.ts:949— packages/gatsby/src/datastore/in-memory/indexing.ts:949 · packages/gatsby/src/datastore/in-memory/indexing.ts:1007 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard examples/using-javascript-transforms/src/static/fonts/fontawesome/style.css:120— `.fa-spin` moves (`animation: fa-spin 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/using-javascript-transforms/src/static/fonts/fontawesome/style.css:125— `.fa-pulse` moves (`animation: fa-spin 1s infinite steps(8)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard examples/functions-google-oauth/src/pages/auth-redirect.module.scss:10— `.message` moves (`animation: pulse-black 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard e2e-tests/adapters/src/pages/index.css:23— `.astro` moves (`animation-name: float`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
P12 · CI test-gate honesty· Runner config excludes tests no gate runs · ×4
Runner config excludes tests no gate runs integration-tests/esm-in-gatsby-files/jest.config.js:6— `/__tests__/fixtures/` removes 6 test(s) in 6 file(s) (e.g. `integration-tests/esm-in-gatsby-files/__tests__/fixtures/gatsby-config.js`, `integration-tests/esm-in-gatsby-files/__tests__/fixtures/gatsby-config.mjs`) 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 integration-tests/functions/jest.config.js:8— `__tests__/fixtures` removes 1 test(s) in 1 file(s) (e.g. `integration-tests/functions/__tests__/fixtures/function-a.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 integration-tests/functions/jest.config.js:11— `src/api` removes 2 test(s) in 2 file(s) (e.g. `integration-tests/functions/src/api/ignore/hello.test.js`, `integration-tests/functions/src/api/ignore/__tests__/hello.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 integration-tests/ssr/jest.config.js:10— `__tests__/fixtures` removes 2 test(s) in 2 file(s) (e.g. `integration-tests/ssr/__tests__/fixtures/bad-page.js`, `integration-tests/ssr/__tests__/fixtures/bad-ssr.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.
Duplicated block (25 lines × 2 locations) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:50— packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:50 · packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (25 lines × 2 locations) packages/gatsby-plugin-sharp/src/index.js:542— packages/gatsby-plugin-sharp/src/index.js:542 · packages/gatsby-plugin-sharp/src/index.js:694 — 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 (25 lines × 2 locations) packages/gatsby-source-wordpress/src/utils/cache.ts:50— packages/gatsby-source-wordpress/src/utils/cache.ts:50 · packages/gatsby/src/utils/cache.ts:40 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (25 lines × 2 locations) packages/gatsby/src/services/run-slice-queries.ts:6— packages/gatsby/src/services/run-slice-queries.ts:6 · packages/gatsby/src/services/run-static-queries.ts:6 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
`async` Promise executor packages/gatsby-remark-images-contentful/src/index.js:245— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/gatsby-remark-images/src/index.js:480— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/gatsby/src/utils/dev-ssr/render-dev-html.ts:162— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:453— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
Duplicated block (28 lines × 2 locations) packages/gatsby-plugin-less/src/gatsby-node.js:16— packages/gatsby-plugin-less/src/gatsby-node.js:16 · packages/gatsby-plugin-stylus/src/gatsby-node.js:35 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (28 lines × 2 locations) packages/gatsby-transformer-sharp/src/customize-schema.js:95— packages/gatsby-transformer-sharp/src/customize-schema.js:95 · packages/gatsby-transformer-sharp/src/customize-schema.js:255 — 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 (28 lines × 2 locations) scripts/gatsby-changelog-generator/cli.js:9— scripts/gatsby-changelog-generator/cli.js:9 · scripts/gatsby-changelog-generator/cli.js:38 — 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.
HackComment packages/gatsby-react-router-scroll/src/scroll-handler.tsx:129— // Hack to allow accessing this._stateStorage. — 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.
HackComment packages/gatsby-cli/src/reporter/catch-exit-signals.ts:25— // hack so at least one activity is surely failed, so — 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.
index.default::generateImagesAndUpdateNode (cognitive 40) packages/gatsby-remark-images/src/index.js:139— index.default::generateImagesAndUpdateNode has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 9, ternaries 6 (9 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (index.default::getImageCaption::getCaptionString) 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.
index.default::getImageCaption::getCaptionString (cognitive 26) packages/gatsby-remark-images/src/index.js:95— index.default::getImageCaption::getCaptionString has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 1 (3 pts), ternaries 2 (3 pts), loops 1 (2 pts), boolean chains 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. This shape REPEATS in the file: one other method here (index.default::generateImagesAndUpdateNode) 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.
exports::generateImagesAndUpdateNode (cognitive 37) packages/gatsby-remark-images/src/index.js:139— exports::generateImagesAndUpdateNode has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (20 pts), boolean chains 8, ternaries 7, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
exports::getImageCaption::getCaptionString (cognitive 25) packages/gatsby-remark-images/src/index.js:95— exports::getImageCaption::getCaptionString has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 1 (3 pts), loops 1 (2 pts), ternaries 2, boolean chains 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.
index.default (cognitive 26) REDACTED:41— index.default has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 4 (12 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 101, verifyFile, getFilePath, …). 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.
index.default (cognitive 26) packages/gatsby-remark-images-contentful/src/index.js:18— index.default has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (20 pts), error handling 2, ternaries 2, boolean chains 1, loops 1 (nesting depth added 5). None of this is in the body itself: all 26 points belong to 4 function items inside it that branch (generateImagesAndUpdateNode, a function literal at line 245, a function literal at line 221, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports (cognitive 26) REDACTED:41— exports has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 4 (12 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 101, verifyFile, getFilePath, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports (cognitive 26) packages/gatsby-remark-prismjs/src/index.js:11— exports has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 10, ternaries 4 (nesting depth added 3). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 37, a function literal at line 138, normalizeLanguage). 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.
Outbound HTTP without resilience packages/gatsby/cache-dir/fast-refresh-overlay/utils.js:18— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience packages/gatsby/src/utils/tracer/zipkin-local.ts:52— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (46 lines × 2 locations) packages/gatsby-plugin-image/src/node-apis/parser.ts:10— packages/gatsby-plugin-image/src/node-apis/parser.ts:10 · packages/gatsby/src/utils/babel-parse-to-ast.ts:4 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (46 lines × 2 locations) packages/gatsby/src/datastore/in-memory/indexing.ts:296— packages/gatsby/src/datastore/in-memory/indexing.ts:296 · packages/gatsby/src/datastore/in-memory/indexing.ts:475 — 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 (30 lines × 2 locations) REDACTED:215— REDACTED:215 · REDACTED:265 — 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 (30 lines × 2 locations) packages/gatsby/src/schema/schema.js:633— packages/gatsby/src/schema/schema.js:633 · packages/gatsby/src/schema/schema.js:696 — 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 (26 lines × 2 locations) packages/gatsby-plugin-sharp/src/image-data.ts:319— packages/gatsby-plugin-sharp/src/image-data.ts:319 · packages/gatsby-plugin-sharp/src/image-data.ts:348 — 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 (26 lines × 2 locations) packages/gatsby/cache-dir/loader.js:884— packages/gatsby/cache-dir/loader.js:884 · packages/gatsby/cache-dir/loader.js:911 — 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark packages/gatsby-graphiql-explorer/src/index.html.ejs:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
exports (cyclomatic 107) packages/gatsby/src/utils/webpack.config.js:46— exports has cyclomatic complexity 107 (threshold 15). Of this number, 32 points are the body's own statements and 75 belong to 35 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.
html.htmlReducer (cyclomatic 77) packages/gatsby/src/redux/reducers/html.ts:35— html.htmlReducer has cyclomatic complexity 77 (threshold 15). Of this number, 76 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.
start-server.startServer (cyclomatic 74) REDACTED:67— start-server.startServer has cyclomatic complexity 74 (threshold 15). Most of this is not in the body itself: 10 of the 74 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 381, a function literal at line 283, a function literal at line 648, …). 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.
gatsby-node.sourceNodes (cyclomatic 70) packages/gatsby-source-drupal/src/gatsby-node.ts:143— gatsby-node.sourceNodes has cyclomatic complexity 70 (threshold 15). Of this number, 47 points are the body's own statements and 23 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
extend-node-type.remarkExtendNodeType (cyclomatic 68) packages/gatsby-transformer-remark/src/extend-node-type.js:88— extend-node-type.remarkExtendNodeType has cyclomatic complexity 68 (threshold 15). Most of this is not in the body itself: 3 of the 68 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 107, 256, 520, …). 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.
build.build (cyclomatic 55) packages/gatsby/src/commands/build.ts:72— build.build has cyclomatic complexity 55 (threshold 15). Of this number, 54 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
sourceNodes (cyclomatic 54) packages/gatsby-source-contentful/src/source-nodes.js:52— sourceNodes has cyclomatic complexity 54 (threshold 15). Of this number, 33 points are the body's own statements and 21 belong to 18 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.
image-data.generateImageData (cyclomatic 52) packages/gatsby-plugin-sharp/src/image-data.ts:123— image-data.generateImageData has cyclomatic complexity 52 (threshold 15). Of this number, 49 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
indexing.getNodesFromCacheByValue (cyclomatic 50) packages/gatsby/src/datastore/in-memory/indexing.ts:672— indexing.getNodesFromCacheByValue has cyclomatic complexity 50 (threshold 15). Of this number, 48 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.
initialize.initialize (cyclomatic 47) packages/gatsby/src/services/initialize.ts:76— initialize.initialize has cyclomatic complexity 47 (threshold 15). Of this number, 34 points are the body's own statements and 13 belong to 4 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.
recursively-transform-fields.transformField (cyclomatic 46) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:141— recursively-transform-fields.transformField has cyclomatic complexity 46 (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.
queries.queriesReducer (cyclomatic 45) packages/gatsby/src/redux/reducers/queries.ts:60— queries.queriesReducer has cyclomatic complexity 45 (threshold 15). Of this number, 43 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.
handle-flags.handleFlags (cyclomatic 45) packages/gatsby/src/utils/handle-flags.ts:8— handle-flags.handleFlags has cyclomatic complexity 45 (threshold 15). Of this number, 24 points are the body's own statements and 21 belong to 7 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
createPage (cyclomatic 44) packages/gatsby/src/redux/actions/public.js:185— createPage has cyclomatic complexity 44 (threshold 15). Of this number, 43 points are the body's own statements and 1 belongs 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.
normalize.createNodesForContentType (cyclomatic 43) packages/gatsby-source-contentful/src/normalize.js:409— normalize.createNodesForContentType has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 2 of the 43 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 640, 523, 684, …). 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.
replaceNodeHtmlImages (cyclomatic 43) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:455— replaceNodeHtmlImages has cyclomatic complexity 43 (threshold 15). Of this number, 17 points are the body's own statements and 26 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.
index.fluid (cyclomatic 41) packages/gatsby-plugin-sharp/src/index.js:420— index.fluid has cyclomatic complexity 41 (threshold 15). Of this number, 32 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
partial-hydration-reference-loader.partialHydrationReferenceLoader (cyclomatic 40) packages/gatsby/src/utils/webpack/loaders/partial-hydration-reference-loader.ts:38— partial-hydration-reference-loader.partialHydrationReferenceLoader has cyclomatic complexity 40 (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.
serve.default (cyclomatic 39) REDACTED:96— serve.default has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 15 of the 39 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 208, a function literal at line 262, a function literal at line 362, …). 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.
getFieldTransformers (cyclomatic 39) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js:13— getFieldTransformers has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 41 function items inside it that branch (test, test, test, …). 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.
index.default (cyclomatic 37) packages/babel-plugin-remove-graphql-queries/src/index.ts:298— index.default has cyclomatic complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes (cyclomatic 37) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js:12— identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes has cyclomatic complexity 37 (threshold 15). Of this number, 33 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.default::generateImagesAndUpdateNode (cyclomatic 36) packages/gatsby-remark-images/src/index.js:139— index.default::generateImagesAndUpdateNode has cyclomatic complexity 36 (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.
babel-plugin-remove-api.removeApiCalls (cyclomatic 36) packages/gatsby/src/utils/babel/babel-plugin-remove-api.ts:9— babel-plugin-remove-api.removeApiCalls has cyclomatic complexity 36 (threshold 15). Of this number, 22 points are the body's own statements and 14 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
index.default (cyclomatic 35) packages/gatsby-remark-copy-linked-files/src/index.js:77— index.default has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 12 function items inside it that branch (generateImagesAndUpdateNode, visitor, a function literal at line 189, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports::generateImagesAndUpdateNode (cyclomatic 35) packages/gatsby-remark-images/src/index.js:139— exports::generateImagesAndUpdateNode has cyclomatic complexity 35 (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.
exports (cyclomatic 35) packages/gatsby-remark-copy-linked-files/src/index.js:77— exports has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 2 of the 35 points are its own statements and the rest belongs to 15 function items inside it that branch (generateImagesAndUpdateNode, visitor, a function literal at line 189, …). 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.
prepare-stack-trace.CallSiteToString (cyclomatic 34) packages/gatsby-cli/src/reporter/prepare-stack-trace.ts:158— prepare-stack-trace.CallSiteToString 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.
gatsby-node.onCreateNode (cyclomatic 34) packages/gatsby-transformer-documentationjs/src/gatsby-node.js:204— gatsby-node.onCreateNode has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (prepareNodeForDocs, tryToAddTypeDef, getNodeIDForType, …). 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.
print.printTypeDefinitions (cyclomatic 34) REDACTED:314— print.printTypeDefinitions has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 8 function items inside it that branch (shouldIncludeType, addWithFieldTypes, isInternalType, …). 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.
StaticQueryMapper.apply (cyclomatic 34) packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:71— StaticQueryMapper.apply has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 91, 211, 79). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
production-app.apiRunnerAsync("onClientEntry").then() (cyclomatic 34) packages/gatsby/cache-dir/production-app.js:48— production-app.apiRunnerAsync("onClientEntry").then() has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 207, a function literal at line 129, a function literal at line 271, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 34) packages/gatsby/cache-dir/production-app.js:48— (anonymous) has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 207, a function literal at line 129, a function literal at line 271, …). 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.
create-cli.buildLocalCommands (cyclomatic 33) packages/gatsby-cli/src/create-cli.ts:26— create-cli.buildLocalCommands has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 8 of the 33 points are its own statements and the rest belongs to 9 function items inside it that branch (resolveLocalCommand, a function literal at line 110, a function literal at line 140, …). 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.
filter-using-index.resolveIndexFieldRanges (cyclomatic 33) packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:489— filter-using-index.resolveIndexFieldRanges has cyclomatic complexity 33 (threshold 15). Of this number, 25 points are the body's own statements and 8 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.
image-utils.generateImageData (cyclomatic 32) packages/gatsby-plugin-image/src/image-utils.ts:218— image-utils.generateImageData has cyclomatic complexity 32 (threshold 15). Of this number, 23 points are the body's own statements and 9 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
page-data.flush (cyclomatic 32) packages/gatsby/src/utils/page-data.ts:198— page-data.flush has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 13 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 259). 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.
loadPage (cyclomatic 32) packages/gatsby/cache-dir/loader.js:349— loadPage has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 8 of the 32 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 459, a function literal at line 430, a function literal at line 378, …). 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.
watch.watch (cyclomatic 31) packages/gatsby-dev-cli/src/watch.js:30— watch.watch has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 9 of the 31 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 220, 58, 333, …). 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.
resolve-module-exports.staticallyAnalyzeExports (cyclomatic 31) packages/gatsby/src/bootstrap/resolve-module-exports.ts:12— resolve-module-exports.staticallyAnalyzeExports has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 125, 103, 61, …). 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.
fetch-graphql.handleFetchErrors (cyclomatic 30) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:312— fetch-graphql.handleFetchErrors 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.
validate.validatePluginsOptions (cyclomatic 29) packages/gatsby/src/bootstrap/load-plugins/validate.ts:203— validate.validatePluginsOptions has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 212, 300, 247, …). 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.
GatsbyWebpackStatsExtractor.apply (cyclomatic 29) packages/gatsby/src/utils/gatsby-webpack-stats-extractor.ts:20— GatsbyWebpackStatsExtractor.apply has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 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.
apiRunnerNode (cyclomatic 29) packages/gatsby/src/utils/api-runner-node.js:516— apiRunnerNode has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 539, a function literal at line 632, a function literal at line 711, …). 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.
index.run (cyclomatic 27) packages/create-gatsby/src/index.ts:73— index.run has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong 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.
gatsby-image-resolver.gatsbyImageResolver (cyclomatic 26) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:80— gatsby-image-resolver.gatsbyImageResolver has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
entry.getData (cyclomatic 25) packages/gatsby/src/utils/page-ssr-module/entry.ts:114— entry.getData has cyclomatic complexity 25 (threshold 15). Of this number, 19 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.default (cyclomatic 24) packages/gatsby-remark-prismjs/src/index.js:11— index.default has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 37, a function literal at line 138, normalizeLanguage). 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.
fetch-nodes-paginated.paginatedWpNodeFetch (cyclomatic 24) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:27— fetch-nodes-paginated.paginatedWpNodeFetch has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 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.
client-assets-for-template.getScriptsAndStylesForTemplate (cyclomatic 24) packages/gatsby/src/utils/client-assets-for-template.ts:30— client-assets-for-template.getScriptsAndStylesForTemplate has cyclomatic complexity 24 (threshold 15). Of this number, 17 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
exports (cyclomatic 24) packages/gatsby-remark-prismjs/src/index.js:11— exports has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 37, a function literal at line 138, normalizeLanguage). 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.
normalize.getGatsbyImageCdnFields (cyclomatic 23) packages/gatsby-source-drupal/src/normalize.ts:26— normalize.getGatsbyImageCdnFields has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PartialHydrationPlugin._generateManifest (cyclomatic 23) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:43— PartialHydrationPlugin._generateManifest has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 143, recordModuleExports, recordModule, …). 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.
bundle-webpack.createGraphqlEngineBundle (cyclomatic 23) packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:336— bundle-webpack.createGraphqlEngineBundle has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 581, 582, 599, …). 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.
index.initializeYurnalistLogger (cyclomatic 22) packages/gatsby-cli/src/reporter/loggers/yurnalist/index.ts:197— index.initializeYurnalistLogger has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 217). 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.
fetch-file.requestRemoteNode (cyclomatic 22) packages/gatsby-core-utils/src/remote-file-utils/fetch-file.ts:80— fetch-file.requestRemoteNode 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 7 function literals inside it that branch (lines 157, 137, 235, …). 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.
gatsby-ssr.onRenderBody (cyclomatic 22) REDACTED:28— gatsby-ssr.onRenderBody has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.fixed (cyclomatic 22) packages/gatsby-plugin-sharp/src/index.js:638— index.fixed has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
index.default (cyclomatic 22) packages/gatsby-remark-images-contentful/src/index.js:18— index.default 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 4 function items inside it that branch (generateImagesAndUpdateNode, a function literal at line 245, a function literal at line 221, …). 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.
compile-gatsby-files.compileGatsbyFiles (cyclomatic 22) packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:81— compile-gatsby-files.compileGatsbyFiles 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.
common.compareKey (cyclomatic 22) packages/gatsby/src/datastore/lmdb/query/common.ts:93— common.compareKey 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.
file-parser.findGraphQLTags (cyclomatic 22) packages/gatsby/src/query/file-parser.js:235— file-parser.findGraphQLTags 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, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
exports (cyclomatic 22) packages/gatsby-remark-images-contentful/src/index.js:18— exports 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 10 function items inside it that branch (generateImagesAndUpdateNode, a function literal at line 245, a function literal at line 221, …). 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.
placeholder.default (cyclomatic 21) packages/create-gatsby/src/components/placeholder.js:21— placeholder.default has cyclomatic complexity 21 (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.
fetch-graphql.handleGraphQLErrors (cyclomatic 21) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:142— fetch-graphql.handleGraphQLErrors 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.
check-plugin-requirements.areRemotePluginVersionsSatisfied (cyclomatic 21) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:50— check-plugin-requirements.areRemotePluginVersionsSatisfied has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
diff-schemas.checkIfSchemaHasChanged (cyclomatic 21) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:19— diff-schemas.checkIfSchemaHasChanged has cyclomatic complexity 21 (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.
node-manifest.findPageOwnedByNode (cyclomatic 21) packages/gatsby/src/utils/node-manifest.ts:61— node-manifest.findPageOwnedByNode 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.
route-handler.processRoutesManifest (cyclomatic 20) packages/gatsby-adapter-netlify/src/route-handler.ts:141— route-handler.processRoutesManifest 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.
fetch-remote-file.fetchFile (cyclomatic 20) packages/gatsby-core-utils/src/fetch-remote-file.ts:134— fetch-remote-file.fetchFile 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.
check-deps-changes.checkDepsChanges (cyclomatic 20) packages/gatsby-dev-cli/src/utils/check-deps-changes.js:30— check-deps-changes.checkDepsChanges has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, 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.
gatsby-node.createPagesStatefully (cyclomatic 20) packages/gatsby-plugin-page-creator/src/gatsby-node.ts:49— gatsby-node.createPagesStatefully has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 174, 126, 236, …). 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.
normalize.buildForeignReferenceMap (cyclomatic 20) packages/gatsby-source-contentful/src/normalize.js:131— normalize.buildForeignReferenceMap has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 169, 182, 153). 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.
inference-metadata.incrementalReducer (cyclomatic 20) packages/gatsby/src/redux/reducers/inference-metadata.ts:22— inference-metadata.incrementalReducer has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
build-html.renderHTMLQueue (cyclomatic 20) packages/gatsby/src/commands/build-html.ts:342— build-html.renderHTMLQueue has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 371, 386). 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.
api-runner-node.runAPI (cyclomatic 20) packages/gatsby/src/utils/api-runner-node.js:316— api-runner-node.runAPI has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
schema.addConvenienceChildrenFields (cyclomatic 20) packages/gatsby/src/schema/schema.js:1029— schema.addConvenienceChildrenFields has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 1034, 1086, 1109, …). 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.
ssr-develop-static-entry.staticPage (cyclomatic 20) REDACTED:59— ssr-develop-static-entry.staticPage has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (generateBodyHTML, a function literal at line 173, generateBodyHTML::getPageDataPath, …). 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.
makeManifest (cyclomatic 20) packages/gatsby-plugin-manifest/src/gatsby-node.js:133— makeManifest has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 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.
image-utils.setDefaultDimensions (cyclomatic 19) packages/gatsby-plugin-image/src/image-utils.ts:151— image-utils.setDefaultDimensions 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.
utils.handleReferences (cyclomatic 19) packages/gatsby-source-drupal/src/utils.ts:23— utils.handleReferences has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 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.
create-local-file-node.errorPanicker (cyclomatic 19) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:46— create-local-file-node.errorPanicker has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
create-local-file-node.createLocalFileNode (cyclomatic 19) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:199— create-local-file-node.createLocalFileNode has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
inference-metadata.updateValueDescriptor (cyclomatic 19) packages/gatsby/src/schema/infer/inference-metadata.ts:252— inference-metadata.updateValueDescriptor has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
node-model.getQueryFields (cyclomatic 19) packages/gatsby/src/schema/node-model.js:703— node-model.getQueryFields has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
manager.initAdapterManager (cyclomatic 19) packages/gatsby/src/utils/adapter/manager.ts:123— manager.initAdapterManager has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 185, 254, 153, …). 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.
manager.getRoutesManifest (cyclomatic 19) packages/gatsby/src/utils/adapter/manager.ts:335— manager.getRoutesManifest has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
static-entry.staticPage (cyclomatic 19) REDACTED:114— static-entry.staticPage has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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.
bundle-webpack.createPageSSRBundle (cyclomatic 19) packages/gatsby/src/utils/page-ssr-module/bundle-webpack.ts:65— bundle-webpack.createPageSSRBundle has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong 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.
FormInput.renderChoice (cyclomatic 18) packages/create-gatsby/src/components/form.js:6— FormInput.renderChoice 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.
gatsby-plugin-image.updateImport (cyclomatic 18) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:111— gatsby-plugin-image.updateImport 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.
process-file.processFile (cyclomatic 18) packages/gatsby-plugin-sharp/src/process-file.ts:30— process-file.processFile has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 49). 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.
index.default (cyclomatic 18) REDACTED:41— index.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 101, verifyFile, getFilePath, …). 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.
process-bulk-results.processBulkResults (cyclomatic 18) packages/gatsby-source-shopify/src/process-bulk-results.ts:24— process-bulk-results.processBulkResults 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.
update.wpActionUPDATE (cyclomatic 18) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:275— update.wpActionUPDATE has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
add-inferred-fields.getSimpleFieldConfig (cyclomatic 18) packages/gatsby/src/schema/infer/add-inferred-fields.js:283— add-inferred-fields.getSimpleFieldConfig 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.
schema.mergeTypes (cyclomatic 18) packages/gatsby/src/schema/schema.js:349— schema.mergeTypes 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.
schema.addExtensions (cyclomatic 18) packages/gatsby/src/schema/schema.js:495— schema.addExtensions has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 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.
public.createNode (cyclomatic 18) packages/gatsby/src/redux/actions/public.js:677— public.createNode 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.
FileParser.parseFile (cyclomatic 18) packages/gatsby/src/query/file-parser.js:486— FileParser.parseFile 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.
resolvers.link (cyclomatic 18) packages/gatsby/src/schema/resolvers.ts:355— resolvers.link 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 3 function items inside it that branch (linkResolverValue, a function literal at line 373, linkResolverQueryResult). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports (cyclomatic 18) REDACTED:41— exports has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 101, verifyFile, getFilePath, …). 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.
index.OutboundLink (cyclomatic 17) packages/gatsby-plugin-google-analytics/src/index.js:16— index.OutboundLink has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 21, 46). 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.
prism-show-invisibles.default (cyclomatic 17) packages/gatsby-remark-prismjs/src/plugins/prism-show-invisibles.js:12— prism-show-invisibles.default has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (addInvisibles, handleToken). 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.
fetch.fetchContent (cyclomatic 17) packages/gatsby-source-contentful/src/fetch.js:236— fetch.fetchContent 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.
update.fetchAndCreateSingleNode (cyclomatic 17) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:24— update.fetchAndCreateSingleNode has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
fetch-graphql.fetchGraphql (cyclomatic 17) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:696— fetch-graphql.fetchGraphql 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, 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.
generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields (cyclomatic 17) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js:116— generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields 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.
node-model.resolveRecursive (cyclomatic 17) packages/gatsby/src/schema/node-model.js:780— node-model.resolveRecursive 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, 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.
PartialHydrationPlugin.addClientModuleEntries (cyclomatic 17) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:208— PartialHydrationPlugin.addClientModuleEntries has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PartialHydrationPlugin.apply (cyclomatic 17) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:360— PartialHydrationPlugin.apply has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 422, 362, 452, …). 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.
validate-component.validateComponent (cyclomatic 17) packages/gatsby/src/utils/validate-component.ts:25— validate-component.validateComponent 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.
common.matchesFilter (cyclomatic 17) packages/gatsby/src/datastore/lmdb/query/common.ts:41— common.matchesFilter has cyclomatic complexity 17 (threshold 15). 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, 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.
query-compiler.processDefinitions (cyclomatic 17) packages/gatsby/src/query/query-compiler.js:321— query-compiler.processDefinitions 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.
query-runner.queryRunner (cyclomatic 17) packages/gatsby/src/query/query-runner.ts:119— query-runner.queryRunner has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
app.apiRunnerAsync("onClientEntry").then() (cyclomatic 17) packages/gatsby/cache-dir/app.js:105— app.apiRunnerAsync("onClientEntry").then() has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 156, 183, 186, …). 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.
getValidHeadNodesAndAttributes (cyclomatic 17) packages/gatsby/cache-dir/head/utils.js:115— getValidHeadNodesAndAttributes 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.
(anonymous) (cyclomatic 17) packages/gatsby/cache-dir/app.js:105— (anonymous) has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 11 function items inside it that branch (dismissLoadingIndicator, a function literal at line 183, (anonymous)::onHydrated, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports (cyclomatic 17) packages/gatsby-remark-prismjs/src/plugins/prism-show-invisibles.js:12— exports has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (addInvisibles, handleToken, a function literal at line 106). 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.
index.preset (cyclomatic 16) packages/babel-preset-gatsby/src/index.js:32— index.preset has cyclomatic complexity 16 (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.
gatsby-image.browser.GatsbyImageHydrator (cyclomatic 16) REDACTED:63— gatsby-image.browser.GatsbyImageHydrator has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 99, 162, 193, …). 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.
plugin-options.enhanceMdxOptions (cyclomatic 16) packages/gatsby-plugin-mdx/src/plugin-options.ts:49— plugin-options.enhanceMdxOptions 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.
create-pages-from-changed-nodes.createPagesFromChangedNodes (cyclomatic 16) packages/gatsby-plugin-page-creator/src/create-pages-from-changed-nodes.ts:5— create-pages-from-changed-nodes.createPagesFromChangedNodes 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.
index.generateBase64 (cyclomatic 16) packages/gatsby-plugin-sharp/src/index.js:255— index.generateBase64 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.
parse-options.default (cyclomatic 16) packages/gatsby-remark-prismjs/src/parse-options.js:3— parse-options.default has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 17). 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.
gatsby-script.injectScript (cyclomatic 16) REDACTED:133— gatsby-script.injectScript 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.
fetch.createContentfulErrorMessage (cyclomatic 16) packages/gatsby-source-contentful/src/fetch.js:13— fetch.createContentfulErrorMessage 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.
image-helpers.createUrl (cyclomatic 16) packages/gatsby-source-contentful/src/image-helpers.js:27— image-helpers.createUrl has cyclomatic complexity 16 (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.
process-node.replaceFileLinks (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:726— process-node.replaceFileLinks has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 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.
recursively-transform-fields.transformInlineFragments (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:14— recursively-transform-fields.transformInlineFragments 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 52). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
recursively-transform-fields.transformFields (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:517— recursively-transform-fields.transformFields has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 550, 536). 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.
introspect-remote-schema.introspectAndStoreRemoteSchema (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/introspect-remote-schema.js:53— introspect-remote-schema.introspectAndStoreRemoteSchema 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 3 function literals inside it that branch (lines 88, 105, 114). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WorkerPool.startAll::workerProcessMessageHandler (cyclomatic 16) packages/gatsby-worker/src/index.ts:230— WorkerPool.startAll::workerProcessMessageHandler 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.
build-html.buildHTMLPagesAndDeleteStaleArtifacts (cyclomatic 16) packages/gatsby/src/commands/build-html.ts:612— build-html.buildHTMLPagesAndDeleteStaleArtifacts 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.
build-example-data.buildExampleValue (cyclomatic 16) packages/gatsby/src/schema/infer/build-example-data.ts:32— build-example-data.buildExampleValue has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
webpack-utils.createWebpackUtils (cyclomatic 16) packages/gatsby/src/utils/webpack-utils.ts:176— webpack-utils.createWebpackUtils has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 265, a function literal at line 291, a function literal at line 341, …). 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.
start-webpack-server.startWebpackServer (cyclomatic 16) packages/gatsby/src/services/start-webpack-server.ts:24— start-webpack-server.startWebpackServer has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 69, 40, 50). 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.
resolvers.getProjectedField (cyclomatic 16) packages/gatsby/src/schema/resolvers.ts:564— resolvers.getProjectedField has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
entry.renderHTML (cyclomatic 16) packages/gatsby/src/utils/page-ssr-module/entry.ts:402— entry.renderHTML 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.
develop.default (cyclomatic 16) packages/gatsby/src/commands/develop.ts:162— develop.default has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
lambda.setupFsWrapper (cyclomatic 16) packages/gatsby/src/utils/page-ssr-module/lambda.ts:33— lambda.setupFsWrapper has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 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.
createTypeComposerFromGatsbyType (cyclomatic 16) packages/gatsby/src/schema/schema.js:626— createTypeComposerFromGatsbyType has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 8 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
requestRemoteNode (cyclomatic 16) REDACTED:159— requestRemoteNode has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 8 function items inside it that branch (processRemoteNode, (anonymous)::handleTimeout, (anonymous)::resetTimeout, …). 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.
transformFields (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js:105— transformFields has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 128, 123, 155, …). 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.
XxxComment packages/gatsby/src/schema/types/sort.ts:85— // XXX(freiksenet): this is to preserve legacy behaviour, this probably doesn't actually sort — 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.
html.htmlReducer (cognitive 167) packages/gatsby/src/redux/reducers/html.ts:35— html.htmlReducer has cognitive complexity 167 (threshold 15). Drivers by points: if/else 42 (121 pts), loops 15 (42 pts), boolean chains 3, match/switch 1 (nesting depth added 106). Of this number, 162 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
start-server.startServer (cognitive 139) REDACTED:67— start-server.startServer has cognitive complexity 139 (threshold 15). Drivers by points: if/else 55 (95 pts), error handling 8 (19 pts), loops 4 (10 pts), ternaries 5 (8 pts), boolean chains 7 (nesting depth added 60). Most of this is not in the body itself: 10 of the 139 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 381, a function literal at line 283, a function literal at line 648, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
exports (cognitive 130) packages/gatsby/src/utils/webpack.config.js:46— exports has cognitive complexity 130 (threshold 15). Drivers by points: if/else 40 (71 pts), boolean chains 24, ternaries 12 (21 pts), match/switch 6, loops 2 (4 pts), error handling 2, other 2 (nesting depth added 42). Of this number, 46 points are the body's own statements and 84 belong to 35 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.
gatsby-node.sourceNodes (cognitive 113) packages/gatsby-source-drupal/src/gatsby-node.ts:143— gatsby-node.sourceNodes has cognitive complexity 113 (threshold 15). Drivers by points: if/else 26 (64 pts), loops 10 (29 pts), boolean chains 11, error handling 4 (9 pts) (nesting depth added 62). Of this number, 106 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
sourceNodes (cognitive 107) packages/gatsby-source-contentful/src/source-nodes.js:52— sourceNodes has cognitive complexity 107 (threshold 15). Drivers by points: if/else 30 (69 pts), loops 7 (17 pts), boolean chains 10, ternaries 5 (10 pts), other 1 (nesting depth added 54). Of this number, 64 points are the body's own statements and 43 belong to 18 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.
identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes (cognitive 90) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js:12— identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes has cognitive complexity 90 (threshold 15). Drivers by points: if/else 24 (67 pts), loops 5 (16 pts), boolean chains 7 (nesting depth added 54). Of this number, 84 points are the body's own statements and 6 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.
extend-node-type.remarkExtendNodeType (cognitive 90) packages/gatsby-transformer-remark/src/extend-node-type.js:88— extend-node-type.remarkExtendNodeType has cognitive complexity 90 (threshold 15). Drivers by points: if/else 47 (61 pts), boolean chains 16, loops 5 (8 pts), ternaries 2 (5 pts) (nesting depth added 20). Most of this is not in the body itself: 2 of the 90 points are its own statements and the rest belongs to 20 function literals inside it that branch (lines 107, 256, 184, …). 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.
indexing.getNodesFromCacheByValue (cognitive 88) packages/gatsby/src/datastore/in-memory/indexing.ts:672— indexing.getNodesFromCacheByValue has cognitive complexity 88 (threshold 15). Drivers by points: if/else 43 (78 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 39). Of this number, 85 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GatsbyWebpackStatsExtractor.apply (cognitive 83) packages/gatsby/src/utils/gatsby-webpack-stats-extractor.ts:20— GatsbyWebpackStatsExtractor.apply has cognitive complexity 83 (threshold 15). Drivers by points: if/else 15 (43 pts), loops 10 (36 pts), boolean chains 4 (nesting depth added 54). None of this is in the body itself: all 83 points belong 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.
createPage (cognitive 80) packages/gatsby/src/redux/actions/public.js:185— createPage has cognitive complexity 80 (threshold 15). Drivers by points: if/else 37 (63 pts), boolean chains 8, ternaries 2 (4 pts), error handling 1 (3 pts), other 2 (nesting depth added 30). Of this number, 75 points are the body's own statements and 5 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.build (cognitive 73) packages/gatsby/src/commands/build.ts:72— build.build has cognitive complexity 73 (threshold 15). Drivers by points: if/else 37 (47 pts), boolean chains 11, error handling 7 (10 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 15). Of this number, 70 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, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
serve.default (cognitive 73) REDACTED:96— serve.default has cognitive complexity 73 (threshold 15). Drivers by points: if/else 18 (38 pts), boolean chains 12, error handling 6 (12 pts), loops 2 (9 pts), ternaries 2 (nesting depth added 33). Most of this is not in the body itself: 15 of the 73 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 262, a function literal at line 208, a function literal at line 362, …). 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.
route-handler.processRoutesManifest (cognitive 69) packages/gatsby-adapter-netlify/src/route-handler.ts:141— route-handler.processRoutesManifest has cognitive complexity 69 (threshold 15). Drivers by points: if/else 14 (45 pts), ternaries 2 (12 pts), loops 3 (11 pts), boolean chains 1 (nesting depth added 49). 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.
handle-flags.handleFlags (cognitive 65) packages/gatsby/src/utils/handle-flags.ts:8— handle-flags.handleFlags has cognitive complexity 65 (threshold 15). Drivers by points: if/else 24 (47 pts), boolean chains 12, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 26). Of this number, 43 points are the body's own statements and 22 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
replaceNodeHtmlImages (cognitive 64) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:455— replaceNodeHtmlImages has cognitive complexity 64 (threshold 15). Drivers by points: if/else 15 (33 pts), boolean chains 14, ternaries 4 (9 pts), other 4, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 25). Of this number, 26 points are the body's own statements and 38 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.
resolvers.getProjectedField (cognitive 61) packages/gatsby/src/schema/resolvers.ts:564— resolvers.getProjectedField has cognitive complexity 61 (threshold 15). Drivers by points: if/else 13 (53 pts), loops 1 (6 pts), boolean chains 2 (nesting depth added 45). Most of this is not in the body itself: 14 of the 61 points are its own statements and the rest belongs to one function literal inside it that branches (line 590). 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.
partial-hydration-reference-loader.partialHydrationReferenceLoader (cognitive 61) packages/gatsby/src/utils/webpack/loaders/partial-hydration-reference-loader.ts:38— partial-hydration-reference-loader.partialHydrationReferenceLoader has cognitive complexity 61 (threshold 15). Drivers by points: if/else 17 (38 pts), loops 4 (12 pts), boolean chains 8, match/switch 2, ternaries 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createNodesForContentType (cognitive 60) packages/gatsby-source-contentful/src/normalize.js:409— createNodesForContentType has cognitive complexity 60 (threshold 15). Drivers by points: if/else 29 (45 pts), boolean chains 11, loops 1 (2 pts), ternaries 2 (nesting depth added 17). Most of this is not in the body itself: 2 of the 60 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 523, a function literal at line 640, (anonymous)::(anonymous)::(anonymous)::traverse, …). 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.
StaticQueryMapper.apply (cognitive 59) packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:71— StaticQueryMapper.apply has cognitive complexity 59 (threshold 15). Drivers by points: if/else 20 (39 pts), loops 11 (16 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 25). None of this is in the body itself: all 59 points belong to 3 function literals inside it that branch (lines 91, 211, 79). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
onCreateNode (cognitive 59) packages/gatsby-transformer-documentationjs/src/gatsby-node.js:204— onCreateNode has cognitive complexity 59 (threshold 15). Drivers by points: if/else 23 (48 pts), boolean chains 10, error handling 1 (nesting depth added 25). Most of this is not in the body itself: 4 of the 59 points are its own statements and the rest belongs to 15 function items inside it that branch (prepareNodeForDocs, tryToAddTypeDef, getNodeIDForType, …). 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.
getValidHeadNodesAndAttributes (cognitive 58) packages/gatsby/cache-dir/head/utils.js:115— getValidHeadNodesAndAttributes has cognitive complexity 58 (threshold 15). Drivers by points: if/else 15 (45 pts), ternaries 1 (6 pts), loops 2 (5 pts), boolean chains 1, other 1 (nesting depth added 38). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
page-data.flush (cognitive 55) packages/gatsby/src/utils/page-data.ts:198— page-data.flush has cognitive complexity 55 (threshold 15). Drivers by points: if/else 19 (39 pts), boolean chains 8, error handling 1 (4 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 24). Most of this is not in the body itself: 13 of the 55 points are its own statements and the rest belongs to one function literal inside it that branches (line 259). 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.
PartialHydrationPlugin._generateManifest (cognitive 54) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:43— PartialHydrationPlugin._generateManifest has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (40 pts), loops 8 (14 pts) (nesting depth added 30). Of this number, 20 points are the body's own statements and 34 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.
babel-plugin-remove-api.removeApiCalls (cognitive 54) packages/gatsby/src/utils/babel/babel-plugin-remove-api.ts:9— babel-plugin-remove-api.removeApiCalls has cognitive complexity 54 (threshold 15). Drivers by points: if/else 24 (43 pts), boolean chains 8, loops 2 (3 pts) (nesting depth added 20). Of this number, 24 points are the body's own statements and 30 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
filter-using-index.resolveIndexFieldRanges (cognitive 52) packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:489— filter-using-index.resolveIndexFieldRanges has cognitive complexity 52 (threshold 15). Drivers by points: if/else 12 (24 pts), ternaries 10 (22 pts), loops 2 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 26). Of this number, 34 points are the body's own statements and 18 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.
initialize.initialize (cognitive 51) packages/gatsby/src/services/initialize.ts:76— initialize.initialize has cognitive complexity 51 (threshold 15). Drivers by points: if/else 25 (29 pts), boolean chains 10, error handling 5 (7 pts), ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 8). Of this number, 35 points are the body's own statements and 16 belong to 4 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
queries.queriesReducer (cognitive 50) packages/gatsby/src/redux/reducers/queries.ts:60— queries.queriesReducer has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 6 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 27). Of this number, 46 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
image-data.generateImageData (cognitive 49) packages/gatsby-plugin-sharp/src/image-data.ts:123— image-data.generateImageData has cognitive complexity 49 (threshold 15). Drivers by points: if/else 25 (29 pts), boolean chains 17, ternaries 2, match/switch 1 (nesting depth added 4). Of this number, 44 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
utils.handleReferences (cognitive 47) packages/gatsby-source-drupal/src/utils.ts:23— utils.handleReferences has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (38 pts), ternaries 2 (4 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 28). Of this number, 28 points are the body's own statements and 19 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
prepare-stack-trace.CallSiteToString (cognitive 45) packages/gatsby-cli/src/reporter/prepare-stack-trace.ts:158— prepare-stack-trace.CallSiteToString has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 15, ternaries 5 (8 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.
index.default (cognitive 44) packages/babel-plugin-remove-graphql-queries/src/index.ts:298— index.default has cognitive complexity 44 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 11, ternaries 2 (4 pts), loops 1 (nesting depth added 10). Of this number, 39 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
watch.watch (cognitive 44) packages/gatsby-dev-cli/src/watch.js:30— watch.watch has cognitive complexity 44 (threshold 15). Drivers by points: if/else 28 (38 pts), error handling 1 (2 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 11). Most of this is not in the body itself: 11 of the 44 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 220, 58, 333, …). 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.
process-bulk-results.processBulkResults (cognitive 44) packages/gatsby-source-shopify/src/process-bulk-results.ts:24— process-bulk-results.processBulkResults has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 3 (9 pts), ternaries 1 (5 pts), boolean chains 4 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetch-graphql.handleFetchErrors (cognitive 44) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:312— fetch-graphql.handleFetchErrors has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (25 pts), ternaries 4 (8 pts), boolean chains 6, error handling 2 (5 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.
client-assets-for-template.getScriptsAndStylesForTemplate (cognitive 44) packages/gatsby/src/utils/client-assets-for-template.ts:30— client-assets-for-template.getScriptsAndStylesForTemplate has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (29 pts), loops 6 (10 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 20). Of this number, 37 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getValidHeadNodesAndAttributesSSR (cognitive 44) REDACTED:36— getValidHeadNodesAndAttributesSSR has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (35 pts), ternaries 1 (5 pts), boolean chains 2, loops 1, other 1 (nesting depth added 25). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PartialHydrationPlugin.addClientModuleEntries (cognitive 43) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:208— PartialHydrationPlugin.addClientModuleEntries has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (36 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 27). Of this number, 37 points are the body's own statements and 6 belong to one function item 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.
add-inferred-fields.getSimpleFieldConfig (cognitive 43) packages/gatsby/src/schema/infer/add-inferred-fields.js:283— add-inferred-fields.getSimpleFieldConfig has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (36 pts), loops 1 (4 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
loadPage (cognitive 42) packages/gatsby/cache-dir/loader.js:349— loadPage has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 6, loops 3 (4 pts), error handling 3, ternaries 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 10 of the 42 points are its own statements and the rest belongs to 21 function items inside it that branch (a function literal at line 459, a function literal at line 430, a function literal at line 378, …). 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.
transformField (cognitive 42) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:141— transformField has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 23, if/else 17 (19 pts) (nesting depth added 2). 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.
(anonymous) (cognitive 41) packages/gatsby/cache-dir/production-app.js:48— (anonymous) has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 14, ternaries 4 (6 pts), error handling 1 (nesting depth added 8). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 18 function items inside it that branch (a function literal at line 207, a function literal at line 129, a function literal at line 271, …). 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.
print.printTypeDefinitions (cognitive 40) REDACTED:314— print.printTypeDefinitions has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 14, error handling 2 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 8 of the 40 points are its own statements and the rest belongs to 8 function items inside it that branch (shouldIncludeType, addWithFieldTypes, a function literal at line 444, …). 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.
index.default (cognitive 39) packages/gatsby-remark-copy-linked-files/src/index.js:77— index.default has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 10, error handling 3 (4 pts), ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 12 function items inside it that branch (visitor, generateImagesAndUpdateNode, a function literal at line 189, …). 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.
update.wpActionUPDATE (cognitive 39) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:275— update.wpActionUPDATE has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (27 pts), boolean chains 5, loops 1 (4 pts), ternaries 1 (3 pts) (nesting depth added 23). Of this number, 37 points are the body's own statements and 2 belong to 2 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.
fluid (cognitive 39) packages/gatsby-plugin-sharp/src/index.js:420— fluid has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 10, ternaries 8, match/switch 1 (2 pts), error handling 1 (nesting depth added 5). Of this number, 26 points are the body's own statements and 13 belong to 7 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
exports (cognitive 39) packages/gatsby-remark-copy-linked-files/src/index.js:77— exports has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (22 pts), boolean chains 10, error handling 3 (4 pts), ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 15 function items inside it that branch (visitor, generateImagesAndUpdateNode, a function literal at line 189, …). 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.
common.compareKey (cognitive 38) packages/gatsby/src/datastore/lmdb/query/common.ts:93— common.compareKey has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 4 (10 pts), boolean chains 4, loops 1 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
compile-gatsby-files.compileGatsbyFiles (cognitive 37) packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:81— compile-gatsby-files.compileGatsbyFiles has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (24 pts), error handling 5 (10 pts), loops 2, boolean chains 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.
runAPI (cognitive 37) packages/gatsby/src/utils/api-runner-node.js:316— runAPI has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 6 (12 pts), boolean chains 5 (nesting depth added 16). Of this number, 29 points are the body's own statements and 8 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check-deps-changes.checkDepsChanges (cognitive 36) packages/gatsby-dev-cli/src/utils/check-deps-changes.js:30— check-deps-changes.checkDepsChanges has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (27 pts), ternaries 1 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 15). Of this number, 24 points are the body's own statements and 12 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.default (cognitive 36) packages/gatsby-remark-embed-snippet/src/index.js:38— index.default has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (31 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to one function literal inside it that branches (line 47). 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.
normalize.buildForeignReferenceMap (cognitive 36) packages/gatsby-source-contentful/src/normalize.js:131— normalize.buildForeignReferenceMap has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 5, loops 1 (nesting depth added 18). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 169, 182, 153). 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.
exports (cognitive 36) packages/gatsby-remark-embed-snippet/src/index.js:38— exports has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (31 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 18). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 47, 101). 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.
build-html.renderHTMLQueue (cognitive 35) packages/gatsby/src/commands/build-html.ts:342— build-html.renderHTMLQueue has cognitive complexity 35 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 8 (11 pts), ternaries 3 (6 pts), boolean chains 2, error handling 1 (nesting depth added 15). Most of this is not in the body itself: 15 of the 35 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 371, 386). 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.
production-app.apiRunnerAsync("onClientEntry").then() (cognitive 35) packages/gatsby/cache-dir/production-app.js:48— production-app.apiRunnerAsync("onClientEntry").then() has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 12, ternaries 2, error handling 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 35 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 207, a function literal at line 129, a function literal at line 271, …). 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.
bundle-webpack.createGraphqlEngineBundle (cognitive 35) packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:336— bundle-webpack.createGraphqlEngineBundle has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (28 pts), loops 2 (3 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 11). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 581, 599, 582, …). 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.
addCustomResolveFunctions (cognitive 35) packages/gatsby/src/schema/schema.js:888— addCustomResolveFunctions has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (28 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 20). None of this is in the body itself: all 35 points belong to 4 function items inside it that branch (a function literal at line 898, a function literal at line 894, createResolvers::(anonymous)::(anonymous)::resolve, …). 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.
apiRunnerNode (cognitive 35) packages/gatsby/src/utils/api-runner-node.js:516— apiRunnerNode has cognitive complexity 35 (threshold 15). Drivers by points: if/else 23 (25 pts), boolean chains 4, error handling 2 (4 pts), ternaries 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 14 function items inside it that branch (a function literal at line 539, a function literal at line 632, a function literal at line 655, …). 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.
getFieldTransformers (cognitive 35) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js:13— getFieldTransformers has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 22, if/else 7, other 4, ternaries 2. None of this is in the body itself: all 35 points belong to 41 function items inside it that branch (transform::resolve, test, test, …). 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.
LocalNodeModel.findRootNodeAncestor (cognitive 34) packages/gatsby/src/schema/node-model.js:520— LocalNodeModel.findRootNodeAncestor has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
install-packages.installPackages (cognitive 33) packages/gatsby-dev-cli/src/local-npm-registry/install-packages.js:7— install-packages.installPackages has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (26 pts), error handling 3 (7 pts) (nesting depth added 17). Of this number, 25 points are the body's own statements and 8 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.
gatsby-image-resolver.gatsbyImageResolver (cognitive 33) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:80— gatsby-image-resolver.gatsbyImageResolver has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). Of this number, 25 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
makeManifest (cognitive 33) packages/gatsby-plugin-manifest/src/gatsby-node.js:133— makeManifest has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (6 pts), ternaries 2 (3 pts), boolean chains 1, other 1 (nesting depth added 14). Of this number, 18 points are the body's own statements and 15 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
paginatedWpNodeFetch (cognitive 33) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:27— paginatedWpNodeFetch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 10 (nesting depth added 10). Of this number, 17 points are the body's own statements and 16 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.
index.run (cognitive 32) packages/create-gatsby/src/index.ts:73— index.run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 10, ternaries 2 (3 pts) (nesting depth added 4). Of this number, 28 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
index.initializeYurnalistLogger (cognitive 32) packages/gatsby-cli/src/reporter/loggers/yurnalist/index.ts:197— index.initializeYurnalistLogger has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 3, match/switch 1 (nesting depth added 16). None of this is in the body itself: all 32 points belong to one function literal inside it that branches (line 217). 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.
entry.getData (cognitive 32) packages/gatsby/src/utils/page-ssr-module/entry.ts:114— entry.getData has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (nesting depth added 7). Of this number, 22 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
create-cli.buildLocalCommands (cognitive 31) packages/gatsby-cli/src/create-cli.ts:26— create-cli.buildLocalCommands has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 14, if/else 10, ternaries 5, error handling 2. Most of this is not in the body itself: 7 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (resolveLocalCommand, a function literal at line 140, a function literal at line 204, …). 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.
create-pages-from-changed-nodes.createPagesFromChangedNodes (cognitive 31) packages/gatsby-plugin-page-creator/src/create-pages-from-changed-nodes.ts:5— create-pages-from-changed-nodes.createPagesFromChangedNodes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 5 (9 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.getExtendedFileNodeData (cognitive 31) packages/gatsby-source-drupal/src/utils.ts:480— utils.getExtendedFileNodeData has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (20 pts), loops 2 (4 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 18). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 501, 488). 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.
validate.validatePluginsOptions (cognitive 31) packages/gatsby/src/bootstrap/load-plugins/validate.ts:203— validate.validatePluginsOptions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 7, error handling 3, ternaries 2 (3 pts) (nesting depth added 6). None of this is in the body itself: all 31 points belong to 4 function literals inside it that branch (lines 212, 260, 247, …). 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.
resolve-module-exports.staticallyAnalyzeExports (cognitive 30) packages/gatsby/src/bootstrap/resolve-module-exports.ts:12— resolve-module-exports.staticallyAnalyzeExports has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 8, error handling 2, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 125, 103, 61, …). 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.
middleware.createSetContextFunctionMiddleware.executeFunction (cognitive 30) REDACTED:81— middleware.createSetContextFunctionMiddleware.executeFunction has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 16). Of this number, 21 points are the body's own statements and 9 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.
createTypeComposerFromGatsbyType (cognitive 30) packages/gatsby/src/schema/schema.js:626— createTypeComposerFromGatsbyType has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (29 pts), match/switch 1 (nesting depth added 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 642, a function literal at line 705, interfaces, …). 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.
resolveRecursive (cognitive 30) packages/gatsby/src/schema/node-model.js:780— resolveRecursive has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 3 (12 pts), if/else 5 (10 pts), boolean chains 6, loops 2 (nesting depth added 14). Of this number, 22 points are the body's own statements and 8 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.
exports (cognitive 30) packages/gatsby-remark-images-contentful/src/index.js:18— exports has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (20 pts), ternaries 4 (6 pts), error handling 2, boolean chains 1, loops 1 (nesting depth added 7). None of this is in the body itself: all 30 points belong to 10 function items inside it that branch (generateImagesAndUpdateNode, a function literal at line 245, a function literal at line 221, …). 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.
introspectAndStoreRemoteSchema (cognitive 30) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/introspect-remote-schema.js:53— introspectAndStoreRemoteSchema has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 6 (11 pts), boolean chains 5 (nesting depth added 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 88, 105, 114, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
utils.handleDeletedNode (cognitive 29) packages/gatsby-source-drupal/src/utils.ts:139— utils.handleDeletedNode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 17). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 177, 193). 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.
generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields (cognitive 29) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js:116— generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 4, error handling 1 (3 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plugin-options.enhanceMdxOptions (cognitive 28) packages/gatsby-plugin-mdx/src/plugin-options.ts:49— plugin-options.enhanceMdxOptions has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (6 pts), boolean chains 4 (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.
file-parser.findGraphQLTags (cognitive 28) packages/gatsby/src/query/file-parser.js:235— file-parser.findGraphQLTags has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3, ternaries 1 (nesting depth added 7). Of this number, 23 points are the body's own statements and 5 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.
fetch-file.requestRemoteNode (cognitive 27) packages/gatsby-core-utils/src/remote-file-utils/fetch-file.ts:80— fetch-file.requestRemoteNode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 4). None of this is in the body itself: all 27 points belong to 7 function literals inside it that branch (lines 157, 137, 235, …). 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.
image-utils.generateImageData (cognitive 27) packages/gatsby-plugin-image/src/image-utils.ts:218— image-utils.generateImageData has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 10, match/switch 1 (nesting depth added 2). Of this number, 19 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
fetch-graphql.handleGraphQLErrors (cognitive 27) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:142— fetch-graphql.handleGraphQLErrors has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (9 pts), boolean chains 4, loops 1 (nesting depth added 10). Of this number, 24 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
node-manifest.findPageOwnedByNode (cognitive 27) packages/gatsby/src/utils/node-manifest.ts:61— node-manifest.findPageOwnedByNode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 7, ternaries 2 (3 pts), 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.
ForceCssHMRForEdgeCases.apply (cognitive 27) packages/gatsby/src/utils/webpack/plugins/force-css-hmr-for-edge-cases.ts:26— ForceCssHMRForEdgeCases.apply has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 14). None of this is in the body itself: all 27 points belong to 2 function literals inside it that branch (lines 28, 47). 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.
query-compiler.processDefinitions (cognitive 27) packages/gatsby/src/query/query-compiler.js:321— query-compiler.processDefinitions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (7 pts), boolean chains 5 (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.
static-entry.staticPage (cognitive 27) REDACTED:114— static-entry.staticPage has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 3 (4 pts), loops 1 (3 pts), ternaries 3, boolean chains 1 (nesting depth added 7). Of this number, 22 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
lambda.setupFsWrapper (cognitive 27) packages/gatsby/src/utils/page-ssr-module/lambda.ts:33— lambda.setupFsWrapper has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 4, loops 2 (4 pts), error handling 1 (nesting depth added 13). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (mapPathUsingRewrites, applyRename, LinkedWriteStream, …). 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.
diagnostics.createStructuredLoggingDiagnosticsMiddleware.diagnosticMiddleware (cognitive 26) packages/gatsby-cli/src/reporter/redux/diagnostics.ts:121— diagnostics.createStructuredLoggingDiagnosticsMiddleware.diagnosticMiddleware has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), ternaries 1 (4 pts) (nesting depth added 16). Of this number, 22 points are the body's own statements and 4 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.
normalize.getGatsbyImageCdnFields (cognitive 26) packages/gatsby-source-drupal/src/normalize.ts:26— normalize.getGatsbyImageCdnFields has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 7, error handling 1, ternaries 1 (nesting depth added 6). Of this number, 25 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.
WorkerPool.startAll::workerProcessMessageHandler (cognitive 26) packages/gatsby-worker/src/index.ts:230— WorkerPool.startAll::workerProcessMessageHandler has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2 (5 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 26) packages/gatsby/cache-dir/app.js:105— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 5 (nesting depth added 7). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 11 function items inside it that branch (dismissLoadingIndicator, a function literal at line 183, (anonymous)::onHydrated, …). 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.
schema.addConvenienceChildrenFields (cognitive 25) packages/gatsby/src/schema/schema.js:1029— schema.addConvenienceChildrenFields has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 8 (nesting depth added 6). None of this is in the body itself: all 25 points belong to 7 function literals inside it that branch (lines 1034, 1086, 1109, …). 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.
manager.initAdapterManager (cognitive 25) packages/gatsby/src/utils/adapter/manager.ts:123— manager.initAdapterManager has cognitive complexity 25 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 185, 254, 153, …). 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.
addExtensions (cognitive 25) packages/gatsby/src/schema/schema.js:495— addExtensions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6, error handling 2 (4 pts), ternaries 2 (3 pts) (nesting depth added 8). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 552, 528, 567, …). 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.
staticPage (cognitive 25) REDACTED:59— staticPage has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (5 pts), boolean chains 4, error handling 2 (3 pts), ternaries 3 (nesting depth added 6). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 31 function items inside it that branch (generateBodyHTML, a function literal at line 173, generateBodyHTML::getPageDataPath, …). 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.
fetch-remote-file.fetchFile (cognitive 24) packages/gatsby-core-utils/src/fetch-remote-file.ts:134— fetch-remote-file.fetchFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 5, ternaries 3 (4 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.
index.default (cognitive 24) packages/gatsby-remark-prismjs/src/index.js:11— index.default has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 9, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 37, a function literal at line 138, normalizeLanguage). 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.
gatsby-script.injectScript (cognitive 24) REDACTED:133— gatsby-script.injectScript has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 3 (5 pts), boolean chains 4 (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.
backreferences.getExistingCachedNodes (cognitive 24) packages/gatsby-source-contentful/src/backreferences.js:16— backreferences.getExistingCachedNodes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 2 (5 pts), boolean chains 2 (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.
source-from-operation.makeSourceFromOperation.sourceFromOperation (cognitive 24) REDACTED:22— source-from-operation.makeSourceFromOperation.sourceFromOperation has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (3 pts), error handling 1, loops 1 (nesting depth added 10). Of this number, 22 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.
PartialHydrationPlugin.apply (cognitive 24) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:360— PartialHydrationPlugin.apply has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 5 (7 pts), boolean chains 2, error handling 1 (nesting depth added 7). None of this is in the body itself: all 24 points belong to 6 function literals inside it that branch (lines 422, 452, 362, …). 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.
sanitize-node.sanitizeNode (cognitive 24) packages/gatsby/src/utils/sanitize-node.ts:56— sanitize-node.sanitizeNode has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 10). 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.
query-compiler.extractOperations (cognitive 24) packages/gatsby/src/query/query-compiler.js:198— query-compiler.extractOperations has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 2, loops 1 (nesting depth added 13). Of this number, 14 points are the body's own statements and 10 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.
inference-metadata.getType (cognitive 23) packages/gatsby/src/schema/infer/inference-metadata.ts:131— inference-metadata.getType has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (7 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
stitching.stitchSlices (cognitive 23) packages/gatsby/src/utils/slices/stitching.ts:21— stitching.stitchSlices has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build-html.buildHTMLPagesAndDeleteStaleArtifacts (cognitive 23) packages/gatsby/src/commands/build-html.ts:612— build-html.buildHTMLPagesAndDeleteStaleArtifacts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 3 (7 pts), boolean chains 5 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
public.createNode (cognitive 23) packages/gatsby/src/redux/actions/public.js:677— public.createNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
manager.getRoutesManifest (cognitive 23) packages/gatsby/src/utils/adapter/manager.ts:335— manager.getRoutesManifest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 8, boolean chains 1, ternaries 1 (nesting depth added 5). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exports (cognitive 23) packages/gatsby-remark-prismjs/src/highlight-code.js:10— exports has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 4 (7 pts), error handling 2 (4 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 11). Of this number, 21 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.
gatsby-ssr.onRenderBody (cognitive 22) REDACTED:28— gatsby-ssr.onRenderBody has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11, if/else 5 (6 pts), boolean chains 4, loops 1 (nesting depth added 1). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
image-utils.setDefaultDimensions (cognitive 22) packages/gatsby-plugin-image/src/image-utils.ts:151— image-utils.setDefaultDimensions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
check-plugin-requirements.areRemotePluginVersionsSatisfied (cognitive 22) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:50— check-plugin-requirements.areRemotePluginVersionsSatisfied has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8, ternaries 4, error handling 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.
indexing.getGatsbyNodePartial (cognitive 22) packages/gatsby/src/datastore/in-memory/indexing.ts:52— indexing.getGatsbyNodePartial has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 2, boolean chains 1, loops 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.
build-utils.calcDirtyHtmlFiles (cognitive 22) packages/gatsby/src/commands/build-utils.ts:93— build-utils.calcDirtyHtmlFiles has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 3 (nesting depth added 7). 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 items inside it that branch (markActionForPage, a function literal at line 158). 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.
process-plugin.processPlugin (cognitive 22) packages/gatsby/src/bootstrap/load-plugins/process-plugin.ts:6— process-plugin.processPlugin has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (8 pts), boolean chains 4, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
createContentfulErrorMessage (cognitive 22) packages/gatsby-source-contentful/src/fetch.js:13— createContentfulErrorMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, error handling 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.
createLocalFileNode (cognitive 22) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:199— createLocalFileNode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, error handling 2 (4 pts), ternaries 2 (3 pts) (nesting depth added 4). Of this number, 17 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
prism-show-invisibles.default (cognitive 21) packages/gatsby-remark-prismjs/src/plugins/prism-show-invisibles.js:12— prism-show-invisibles.default has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 3 (4 pts), match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (addInvisibles, handleToken). 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.
create-local-file-node.errorPanicker (cognitive 21) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js:46— create-local-file-node.errorPanicker has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 6, if/else 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
indexing.unionNodesByCounter (cognitive 21) packages/gatsby/src/datastore/in-memory/indexing.ts:1145— indexing.unionNodesByCounter has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 3, 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.
query-runner.queryRunner (cognitive 21) packages/gatsby/src/query/query-runner.ts:119— query-runner.queryRunner has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
exports (cognitive 21) packages/gatsby-remark-prismjs/src/plugins/prism-show-invisibles.js:12— exports has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 3 (4 pts), match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 3 function items inside it that branch (addInvisibles, handleToken, a function literal at line 106). 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.
create-cli.createCli (cognitive 20) packages/gatsby-cli/src/create-cli.ts:484— create-cli.createCli has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, ternaries 2, error handling 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 583, 532). 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.
gatsby-plugin-image.updateImport (cognitive 20) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:111— gatsby-plugin-image.updateImport has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 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.
gatsby-image-resolver.calculateFixedImageSizes (cognitive 20) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:468— gatsby-image-resolver.calculateFixedImageSizes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetch.fetchContent (cognitive 20) packages/gatsby-source-contentful/src/fetch.js:236— fetch.fetchContent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 4 (6 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
process-node.replaceFileLinks (cognitive 20) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:726— process-node.replaceFileLinks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 5). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 785, 764). 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.
gatsby-node.onPreBootstrap (cognitive 20) packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:426— gatsby-node.onPreBootstrap has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 460, 453, 519). 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.
parseFile (cognitive 20) packages/gatsby/src/query/file-parser.js:486— parseFile has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 7 (8 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exports (cognitive 20) packages/gatsby-remark-autolink-headers/src/index.js:16— exports has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 6). None of this is in the body itself: all 20 points belong to one function literal inside it that branches (line 30). 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.
image-processing.writeImages (cognitive 19) packages/gatsby-plugin-image/src/node-apis/image-processing.ts:63— image-processing.writeImages has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 3 (6 pts), boolean chains 4 (nesting depth added 5). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 85). 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.
gatsby-node.onCreateNode (cognitive 19) packages/gatsby-transformer-csv/src/gatsby-node.js:18— gatsby-node.onCreateNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 5). Of this number, 14 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
init.getAdapterInit (cognitive 19) packages/gatsby/src/utils/adapter/init.ts:127— init.getAdapterInit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
start-webpack-server.startWebpackServer (cognitive 19) packages/gatsby/src/services/start-webpack-server.ts:24— start-webpack-server.startWebpackServer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 69, 40, 50). 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.
resolvers.link (cognitive 19) packages/gatsby/src/schema/resolvers.ts:355— resolvers.link has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 3 function items inside it that branch (linkResolverValue, a function literal at line 373, linkResolverQueryResult). 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.
entry.renderHTML (cognitive 19) packages/gatsby/src/utils/page-ssr-module/entry.ts:402— entry.renderHTML has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
bundle-webpack.createPageSSRBundle (cognitive 19) packages/gatsby/src/utils/page-ssr-module/bundle-webpack.ts:65— bundle-webpack.createPageSSRBundle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), loops 5 (6 pts), ternaries 3, boolean chains 2 (nesting depth added 2). Of this number, 15 points are the body's own statements and 4 belong 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.
develop.default (cognitive 19) packages/gatsby/src/commands/develop.ts:162— develop.default has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getDimensionsAndAspectRatio (cognitive 19) packages/gatsby-plugin-sharp/src/utils.js:225— getDimensionsAndAspectRatio has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 2 (4 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.
process-file.processFile (cognitive 18) packages/gatsby-plugin-sharp/src/process-file.ts:30— process-file.processFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, error handling 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 49). 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.
index.default (cognitive 18) packages/gatsby-remark-autolink-headers/src/index.js:16— index.default has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 30). 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.
parse-options.default (cognitive 18) packages/gatsby-remark-prismjs/src/parse-options.js:3— parse-options.default has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 6 (nesting depth added 5). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 17). 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.
normalize.recursiveAddFields (cognitive 18) packages/gatsby-source-lever/src/normalize.js:45— normalize.recursiveAddFields has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
diff-schemas.checkIfSchemaHasChanged (cognitive 18) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:19— diff-schemas.checkIfSchemaHasChanged has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8 (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.
inference-metadata.incrementalReducer (cognitive 18) packages/gatsby/src/redux/reducers/inference-metadata.ts:22— inference-metadata.incrementalReducer has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 3 (6 pts), ternaries 2 (5 pts), match/switch 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
indexing.postIndexingMetaSetupLtLteGtGte (cognitive 18) packages/gatsby/src/datastore/in-memory/indexing.ts:209— indexing.postIndexingMetaSetupLtLteGtGte has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 4, if/else 4 (nesting depth added 6). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 244, 247). 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.
node-model.getQueryFields (cognitive 18) packages/gatsby/src/schema/node-model.js:703— node-model.getQueryFields has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, boolean chains 7, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
mergeTypes (cognitive 18) packages/gatsby/src/schema/schema.js:349— mergeTypes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
requestRemoteNode (cognitive 18) REDACTED:159— requestRemoteNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 2 (nesting depth added 1). None of this is in the body itself: all 18 points belong to 8 function items inside it that branch (processRemoteNode, (anonymous)::handleTimeout, (anonymous)::resetTimeout, …). 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.
fetchAndCreateSingleNode (cognitive 18) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:24— fetchAndCreateSingleNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7, ternaries 2 (nesting depth added 2). Of this number, 15 points are the body's own statements and 3 belong to one function item 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.
applyPropDoclets (cognitive 18) packages/gatsby-transformer-react-docgen/src/doclets.js:87— applyPropDoclets has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (6 pts), boolean chains 4 (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 3 function literals inside it that branch (lines 88, 108, 105). 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.
createFileNode (cognitive 18) packages/gatsby-source-filesystem/src/create-file-node.js:8— createFileNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.generateBase64 (cognitive 17) packages/gatsby-plugin-sharp/src/index.js:255— index.generateBase64 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, error handling 2 (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.
index.fixed (cognitive 17) packages/gatsby-plugin-sharp/src/index.js:638— index.fixed has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), match/switch 1, ternaries 1 (nesting depth added 1). Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
highlight-code.default (cognitive 17) packages/gatsby-remark-prismjs/src/highlight-code.js:10— highlight-code.default has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 2 (4 pts), match/switch 1 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocalNodeModel._query (cognitive 17) packages/gatsby/src/schema/node-model.js:199— LocalNodeModel._query has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (5 pts), boolean chains 2, loops 1 (nesting depth added 4). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate-component.validateComponent (cognitive 17) packages/gatsby/src/utils/validate-component.ts:25— validate-component.validateComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
filter-using-index.narrowResultsIfPossible (cognitive 17) packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:286— filter-using-index.narrowResultsIfPossible has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 1 (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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
manager.setAdapter (cognitive 17) packages/gatsby/src/utils/adapter/manager.ts:49— manager.setAdapter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (4 pts), boolean chains 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.
transformFields (cognitive 17) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js:105— transformFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 128, 123, 155, …). 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.
index.preset (cognitive 16) packages/babel-preset-gatsby/src/index.js:32— index.preset has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (5 pts), ternaries 2 (nesting depth added 1). 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.
FormInput.renderChoice (cognitive 16) packages/create-gatsby/src/components/form.js:6— FormInput.renderChoice has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 4, ternaries 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
route-handler.injectEntries (cognitive 16) packages/gatsby-adapter-netlify/src/route-handler.ts:32— route-handler.injectEntries has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, error handling 2, loops 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (getContentToAdd). 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.
CLI.render (cognitive 16) packages/gatsby-cli/src/reporter/loggers/ink/cli.tsx:40— CLI.render has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 7, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 65, 103, 83). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
gatsby-plugin-image.processImportUsage (cognitive 16) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js:219— gatsby-plugin-image.processImportUsage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
sort-and-aggr-graphql.updateSortAndAggrField (cognitive 16) packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:91— sort-and-aggr-graphql.updateSortAndAggrField has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
sort-and-aggr-graphql.processGraphQLQuery (cognitive 16) packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:243— sort-and-aggr-graphql.processGraphQLQuery has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), error handling 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.OutboundLink (cognitive 16) packages/gatsby-plugin-google-analytics/src/index.js:16— index.OutboundLink has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 3). None of this is in the body itself: all 16 points belong to 2 function literals inside it that branch (lines 21, 46). 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.
image-utils.fixedImageSizes (cognitive 16) packages/gatsby-plugin-image/src/image-utils.ts:410— image-utils.fixedImageSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
image-utils.responsiveImageSizes (cognitive 16) packages/gatsby-plugin-image/src/image-utils.ts:483— image-utils.responsiveImageSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7 (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.
gatsby-image.browser.GatsbyImageHydrator (cognitive 16) REDACTED:63— gatsby-image.browser.GatsbyImageHydrator has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 99, 162, 193, …). 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.
remark-infer-toc-meta.remarkInferTocMeta (cognitive 16) packages/gatsby-plugin-mdx/src/remark-infer-toc-meta.ts:30— remark-infer-toc-meta.remarkInferTocMeta has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 7). None of this is in the body itself: all 16 points belong to 2 function items inside it that branch (processToC, a function literal at line 48). 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.
utils.responsiveImageSizes (cognitive 16) packages/gatsby-plugin-sharp/src/utils.js:120— utils.responsiveImageSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7 (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.
plugin-options.healOptions (cognitive 16) packages/gatsby-plugin-sharp/src/plugin-options.ts:161— plugin-options.healOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (nesting depth added 2). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: 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.
gatsby-image-resolver.calculateResponsiveImageSizes (cognitive 16) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:553— gatsby-image-resolver.calculateResponsiveImageSizes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
gatsby-node.createPages (cognitive 16) packages/gatsby-remark-code-repls/src/gatsby-node.js:13— gatsby-node.createPages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 47). 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.
image-helpers.createUrl (cognitive 16) packages/gatsby-source-contentful/src/image-helpers.js:27— image-helpers.createUrl has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 2 (3 pts), ternaries 3, loops 1 (nesting depth added 1). 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.
run-steps.runSteps (cognitive 16) packages/gatsby-source-wordpress/src/utils/run-steps.ts:15— run-steps.runSteps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (5 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
recursively-transform-fields.transformInlineFragments (cognitive 16) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:14— recursively-transform-fields.transformInlineFragments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 52). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
gatsby-node.onCreateNode (cognitive 16) packages/gatsby-transformer-javascript-frontmatter/src/gatsby-node.js:12— gatsby-node.onCreateNode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 84, parseData, a function literal at line 74). 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.
babelrc.babelrcReducer (cognitive 16) packages/gatsby/src/redux/reducers/babelrc.ts:5— babelrc.babelrcReducer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 46, 74, 101). 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.
transform-document.processGraphQLQuery (cognitive 16) packages/gatsby/src/query/transform-document.ts:73— transform-document.processGraphQLQuery has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), error handling 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build-html.runWebpack (cognitive 16) packages/gatsby/src/commands/build-html.ts:140— build-html.runWebpack has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 167, 151, 194). 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.
render-html.renderPartialHydrationProd (cognitive 16) packages/gatsby/src/utils/worker/child/render-html.ts:506— render-html.renderPartialHydrationProd has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (8 pts), if/else 3 (5 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). 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.
build-example-data.buildExampleValue (cognitive 16) packages/gatsby/src/schema/infer/build-example-data.ts:32— build-example-data.buildExampleValue has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 3 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
node-manifest.processNodeManifest (cognitive 16) packages/gatsby/src/utils/node-manifest.ts:252— node-manifest.processNodeManifest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CacheFolderResolver.constructor (cognitive 16) packages/gatsby/src/utils/webpack/plugins/cache-folder-resolver.ts:33— CacheFolderResolver.constructor has cognitive complexity 16 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 4 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
express-middlewares.configureTrailingSlash.<returned closure> (cognitive 16) packages/gatsby/src/utils/express-middlewares.ts:8— express-middlewares.configureTrailingSlash.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
redirects-writer.writeRedirects (cognitive 16) packages/gatsby/src/bootstrap/redirects-writer.ts:11— redirects-writer.writeRedirects has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (6 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.fieldPathNeedToResolve (cognitive 16) packages/gatsby/src/schema/utils.ts:86— utils.fieldPathNeedToResolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
limited-exports-page-templates.isApiExport (cognitive 16) packages/gatsby/src/utils/eslint-rules/limited-exports-page-templates.ts:21— limited-exports-page-templates.isApiExport has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transformFields (cognitive 16) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:517— transformFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6 (nesting depth added 3). None of this is in the body itself: all 16 points belong to 6 function literals inside it that branch (lines 550, 536, 583, …). 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.
constructor (cognitive 16) packages/gatsby/cache-dir/slice.js:69— constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Low cohesion: Reporter (LCOM4 9) packages/gatsby-cli/src/reporter/reporter.ts:52— Reporter's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplication concentrated across 31 sibling directories (44 clone groups) packages/gatsby-plugin-image/src/image-utils.ts:376— 44 duplicated blocks under packages/ have copies in at least two of the sibling directories babel-plugin-remove-graphql-queries, create-gatsby, gatsby, gatsby-codemods, gatsby-core-utils, gatsby-plugin-emotion (+25 more sibling(s) not listed) — 29 of them are reported below, and 15 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 44 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 44 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 44 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.
Duplication concentrated across 8 sibling directories (9 clone groups) packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:358— 9 duplicated blocks under packages/gatsby/src/ have copies in at least two of the sibling directories bootstrap, commands, internal-plugins, query, schema, services (+2 more sibling(s) not listed) — 7 of them are reported below, and 2 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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 (194 matched lines × 2 locations) · ×1
Duplicated block with local edits (194 matched lines × 2 locations) packages/gatsby-plugin-image/src/image-utils.ts:376— packages/gatsby-plugin-image/src/image-utils.ts:376 · packages/gatsby-plugin-sharp/src/utils.js:17 — the two spans are one implementation copied and then locally edited — 974 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 (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) packages/gatsby-codemods/src/transforms/global-graphql-calls.js:4— packages/gatsby-codemods/src/transforms/global-graphql-calls.js:4 · packages/gatsby-codemods/src/transforms/import-link.js:4 — the two spans are one implementation copied and then locally edited — 540 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.
Wholesale file copy (65 identical lines × 4 files) packages/gatsby-plugin-manifest/src/safe-sharp.js:12— packages/gatsby-plugin-manifest/src/safe-sharp.js:12 · packages/gatsby-plugin-sharp/src/safe-sharp.js:12 · packages/gatsby-remark-images-contentful/src/safe-sharp.js:12 · packages/gatsby-transformer-sharp/src/safe-sharp.js:12 — these 4 files are line-for-line copies of one another — 65 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (62 lines × 2 locations) packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:173— packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:173 · packages/gatsby/src/query/transform-document.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (60 matched lines × 2 locations) · ×1
Duplicated block with local edits (60 matched lines × 2 locations) packages/gatsby-plugin-sharp/src/utils.js:84— packages/gatsby-plugin-sharp/src/utils.js:84 · packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:515 — the two spans are one implementation copied and then locally edited — 288 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (55 lines × 2 locations) packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:243— packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:243 · packages/gatsby/src/query/transform-document.ts:73 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) scripts/backport.js:7— scripts/backport.js:7 · scripts/create-release-notes.js:9 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (50 lines × 2 locations) packages/gatsby-transformer-sharp/src/customize-schema.js:158— packages/gatsby-transformer-sharp/src/customize-schema.js:158 · packages/gatsby-transformer-sharp/src/customize-schema.js:320 — all 2 copies are in the same file, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
R10 · Code Duplication· Duplicated block with local edits (46 matched lines × 2 locations) · ×1
Duplicated block with local edits (46 matched lines × 2 locations) packages/gatsby-cli/src/reporter/reporter-progress.ts:22— packages/gatsby-cli/src/reporter/reporter-progress.ts:22 · packages/gatsby-cli/src/reporter/reporter-timer.ts:23 — the two spans are one implementation copied and then locally edited — 214 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 (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) packages/gatsby-remark-images-contentful/src/index.js:243— packages/gatsby-remark-images-contentful/src/index.js:243 · packages/gatsby-remark-images/src/index.js:478 — the two spans are one implementation copied and then locally edited — 218 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 (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) REDACTED:304— REDACTED:304 · REDACTED:285 — the two spans are one implementation copied and then locally edited — 195 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (37 lines × 2 locations) packages/gatsby/cache-dir/loader.js:190— packages/gatsby/cache-dir/loader.js:190 · packages/gatsby/cache-dir/loader.js:248 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) packages/gatsby-cli/src/reporter/loggers/ink/components/trees.tsx:159— packages/gatsby-cli/src/reporter/loggers/ink/components/trees.tsx:159 · packages/gatsby-cli/src/reporter/loggers/yurnalist/index.ts:87 — the two spans are one implementation copied and then locally edited — 218 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (32 lines × 2 locations) packages/gatsby/src/datastore/in-memory/indexing.ts:592— packages/gatsby/src/datastore/in-memory/indexing.ts:592 · packages/gatsby/src/datastore/in-memory/indexing.ts:627 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) packages/babel-plugin-remove-graphql-queries/src/index.ts:312— packages/babel-plugin-remove-graphql-queries/src/index.ts:312 · packages/babel-plugin-remove-graphql-queries/src/index.ts:354 — the two spans are one implementation copied and then locally edited — 133 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (28 matched lines × 2 locations) · ×1
Duplicated block with local edits (28 matched lines × 2 locations) packages/gatsby-plugin-google-analytics/src/gatsby-browser.js:1— packages/gatsby-plugin-google-analytics/src/gatsby-browser.js:1 · packages/gatsby-plugin-google-tagmanager/src/gatsby-browser.js:1 — the two spans are one implementation copied and then locally edited — 157 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 (27 matched lines × 2 locations) · ×1
Duplicated block with local edits (27 matched lines × 2 locations) packages/gatsby-source-filesystem/src/extend-file-node.js:23— packages/gatsby-source-filesystem/src/extend-file-node.js:23 · packages/gatsby-transformer-sharp/src/customize-schema.js:599 — the two spans are one implementation copied and then locally edited — 87 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 (24 matched lines × 2 locations) · ×1
Duplicated block with local edits (24 matched lines × 2 locations) packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1684— packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1684 · packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2082 — the two spans are one implementation copied and then locally edited — 111 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (23 lines × 2 locations) packages/gatsby/cache-dir/develop-static-entry.js:39— packages/gatsby/cache-dir/develop-static-entry.js:39 · REDACTED:103 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (22 lines × 2 locations) packages/gatsby-plugin-google-analytics/src/index.js:20— packages/gatsby-plugin-google-analytics/src/index.js:20 · packages/gatsby-plugin-google-gtag/src/index.js:7 — 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.
Complex function isTabbableRules (cyclomatic 94, cognitive 121) packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2366— isTabbableRules has cyclomatic complexity 94 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isFocusRelevantRules (cyclomatic 90, cognitive 91) packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1173— isFocusRelevantRules has cyclomatic complexity 90 and cognitive complexity 91; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function htmlReducer (cyclomatic 76, cognitive 162) packages/gatsby/src/redux/reducers/html.ts:35— htmlReducer has cyclomatic complexity 76 and cognitive complexity 162; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function build (cyclomatic 54, cognitive 70) packages/gatsby/src/commands/build.ts:72— build has cyclomatic complexity 54 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 50, cognitive 87) packages/gatsby/src/datastore/in-memory/indexing.ts:677— (anonymous) has cyclomatic complexity 50 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateImageData (cyclomatic 49, cognitive 45) packages/gatsby-plugin-sharp/src/image-data.ts:123— generateImageData has cyclomatic complexity 49 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Complex function transformField (cyclomatic 46, cognitive 42) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:141— transformField has cyclomatic complexity 46 and cognitive complexity 42; 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.
Complex function queriesReducer (cyclomatic 45, cognitive 54) packages/gatsby/src/redux/reducers/queries.ts:60— queriesReducer has cyclomatic complexity 45 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createPage (cyclomatic 43, cognitive 75) packages/gatsby/src/redux/actions/public.js:185— createPage has cyclomatic complexity 43 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sourceNodes (cyclomatic 40, cognitive 99) packages/gatsby-source-drupal/src/gatsby-node.ts:143— sourceNodes has cyclomatic complexity 40 and cognitive complexity 99; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateImagesAndUpdateNode (cyclomatic 35, cognitive 37) packages/gatsby-remark-images/src/index.js:139— generateImagesAndUpdateNode has cyclomatic complexity 35 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function initialize (cyclomatic 35, cognitive 37) packages/gatsby/src/services/initialize.ts:76— initialize has cyclomatic complexity 35 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CallSiteToString (cyclomatic 34, cognitive 46) packages/gatsby-cli/src/reporter/prepare-stack-trace.ts:158— CallSiteToString has cyclomatic complexity 34 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function identifyAndStoreIngestableFieldsAndTypes (cyclomatic 33, cognitive 84) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js:12— identifyAndStoreIngestableFieldsAndTypes has cyclomatic complexity 33 and cognitive complexity 84; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sourceNodes (cyclomatic 33, cognitive 64) packages/gatsby-source-contentful/src/source-nodes.js:52— sourceNodes has cyclomatic complexity 33 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function exports (cyclomatic 32, cognitive 46) packages/gatsby/src/utils/webpack.config.js:46— exports has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fluid (cyclomatic 32, cognitive 26) packages/gatsby-plugin-sharp/src/index.js:420— fluid has cyclomatic complexity 32 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Complex function (anonymous) (cyclomatic 31, cognitive 45) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:324— (anonymous) has cyclomatic complexity 31 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveIndexFieldRanges (cyclomatic 29, cognitive 38) packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:489— resolveIndexFieldRanges has cyclomatic complexity 29 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.
Complex function (anonymous) (cyclomatic 28, cognitive 82) packages/gatsby/src/utils/gatsby-webpack-stats-extractor.ts:21— (anonymous) has cyclomatic complexity 28 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 49) packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:91— (anonymous) has cyclomatic complexity 27 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 26) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:492— (anonymous) has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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.
Complex function ExportNamedDeclaration (cyclomatic 26, cognitive 51) packages/gatsby/src/utils/webpack/loaders/partial-hydration-reference-loader.ts:59— ExportNamedDeclaration has cyclomatic complexity 26 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isFocusableRules (cyclomatic 25, cognitive 30) packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:2048— isFocusableRules has cyclomatic complexity 25 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 run (cyclomatic 24, cognitive 28) · ×1
Complex function run (cyclomatic 24, cognitive 28) packages/create-gatsby/src/index.ts:73— run has cyclomatic complexity 24 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 23, cognitive 43) REDACTED:381— (anonymous) has cyclomatic complexity 23 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateImageData (cyclomatic 23, cognitive 18) packages/gatsby-plugin-image/src/image-utils.ts:218— generateImageData has cyclomatic complexity 23 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 22, cognitive 45) packages/gatsby/src/utils/handle-flags.ts:17— (anonymous) has cyclomatic complexity 22 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compareKey (cyclomatic 22, cognitive 38) packages/gatsby/src/datastore/lmdb/query/common.ts:93— compareKey has cyclomatic complexity 22 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.
Complex function compileGatsbyFiles (cyclomatic 22, cognitive 37) packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:81— compileGatsbyFiles has cyclomatic complexity 22 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function findPageOwnedByNode (cyclomatic 21, cognitive 31) packages/gatsby/src/utils/node-manifest.ts:61— findPageOwnedByNode has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getNext (cyclomatic 21, cognitive 26) packages/gatsby-source-drupal/src/gatsby-node.ts:520— getNext has cyclomatic complexity 21 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchFile (cyclomatic 21, cognitive 25) packages/gatsby-core-utils/src/fetch-remote-file.ts:134— fetchFile has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function gatsbyImageResolver (cyclomatic 21, cognitive 25) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:80— gatsbyImageResolver has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getGatsbyImageCdnFields (cyclomatic 21, cognitive 25) packages/gatsby-source-drupal/src/normalize.ts:26— getGatsbyImageCdnFields has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isOnlyTabbableRules (cyclomatic 21, cognitive 24) packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1916— isOnlyTabbableRules has cyclomatic complexity 21 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 22) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts:58— (anonymous) has cyclomatic complexity 21 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onRenderBody (cyclomatic 21, cognitive 21) REDACTED:28— onRenderBody has cyclomatic complexity 21 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function checkIfSchemaHasChanged (cyclomatic 21, cognitive 18) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:19— checkIfSchemaHasChanged has cyclomatic complexity 21 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 16) packages/create-gatsby/src/components/placeholder.js:21— (anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js · ×1
packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js: 3016 lines of code packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1— packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js has 3016 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/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts · ×1
packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts: 1947 lines of code packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1— packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts has 1947 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/gatsby/src/redux/types.ts · ×1
packages/gatsby/src/redux/types.ts: 1448 lines of code packages/gatsby/src/redux/types.ts:1— packages/gatsby/src/redux/types.ts has 1448 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/gatsby/src/redux/actions/public.js · ×1
packages/gatsby/src/redux/actions/public.js: 1375 lines of code packages/gatsby/src/redux/actions/public.js:1— packages/gatsby/src/redux/actions/public.js has 1375 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/gatsby/src/schema/schema.js · ×1
packages/gatsby/src/schema/schema.js: 1349 lines of code packages/gatsby/src/schema/schema.js:1— packages/gatsby/src/schema/schema.js has 1349 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/gatsby/src/datastore/in-memory/indexing.ts · ×1
packages/gatsby/src/datastore/in-memory/indexing.ts: 1096 lines of code packages/gatsby/src/datastore/in-memory/indexing.ts:1— packages/gatsby/src/datastore/in-memory/indexing.ts has 1096 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/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js · ×1
packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js: 1002 lines of code packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:1— packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js has 1002 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/gatsby-cli/src/structured-errors/error-map.ts · ×1
packages/gatsby-cli/src/structured-errors/error-map.ts: 970 lines of code packages/gatsby-cli/src/structured-errors/error-map.ts:1— packages/gatsby-cli/src/structured-errors/error-map.ts has 970 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/gatsby/src/schema/node-model.js · ×1
packages/gatsby/src/schema/node-model.js: 910 lines of code packages/gatsby/src/schema/node-model.js:1— packages/gatsby/src/schema/node-model.js has 910 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/gatsby-source-drupal/src/gatsby-node.ts · ×1
packages/gatsby-source-drupal/src/gatsby-node.ts: 891 lines of code packages/gatsby-source-drupal/src/gatsby-node.ts:1— packages/gatsby-source-drupal/src/gatsby-node.ts has 891 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/gatsby/cache-dir/loader.js · ×1
packages/gatsby/cache-dir/loader.js: 845 lines of code packages/gatsby/cache-dir/loader.js:1— packages/gatsby/cache-dir/loader.js has 845 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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js · ×1
packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js: 842 lines of code packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:1— packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js has 842 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/gatsby-source-contentful/src/normalize.js · ×1
packages/gatsby-source-contentful/src/normalize.js: 797 lines of code packages/gatsby-source-contentful/src/normalize.js:1— packages/gatsby-source-contentful/src/normalize.js has 797 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/gatsby-transformer-sharp/src/customize-schema.js · ×1
packages/gatsby-transformer-sharp/src/customize-schema.js: 783 lines of code packages/gatsby-transformer-sharp/src/customize-schema.js:1— packages/gatsby-transformer-sharp/src/customize-schema.js has 783 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/gatsby/src/commands/build-html.ts · ×1
packages/gatsby/src/commands/build-html.ts: 780 lines of code packages/gatsby/src/commands/build-html.ts:1— packages/gatsby/src/commands/build-html.ts has 780 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: 778 lines of code REDACTED:1— REDACTED has 778 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/gatsby/src/utils/webpack-utils.ts · ×1
packages/gatsby/src/utils/webpack-utils.ts: 770 lines of code packages/gatsby/src/utils/webpack-utils.ts:1— packages/gatsby/src/utils/webpack-utils.ts has 770 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/gatsby-transformer-remark/src/extend-node-type.js · ×1
packages/gatsby-transformer-remark/src/extend-node-type.js: 731 lines of code packages/gatsby-transformer-remark/src/extend-node-type.js:1— packages/gatsby-transformer-remark/src/extend-node-type.js 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/gatsby-source-wordpress/src/utils/fetch-graphql.ts · ×1
packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts: 718 lines of code packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:1— packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts has 718 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/gatsby/src/schema/resolvers.ts · ×1
packages/gatsby/src/schema/resolvers.ts: 707 lines of code packages/gatsby/src/schema/resolvers.ts:1— packages/gatsby/src/schema/resolvers.ts has 707 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/gatsby-plugin-sharp/src/index.js · ×1
packages/gatsby-plugin-sharp/src/index.js: 691 lines of code packages/gatsby-plugin-sharp/src/index.js:1— packages/gatsby-plugin-sharp/src/index.js has 691 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/gatsby/src/redux/actions/restricted.ts · ×1
packages/gatsby/src/redux/actions/restricted.ts: 658 lines of code packages/gatsby/src/redux/actions/restricted.ts:1— packages/gatsby/src/redux/actions/restricted.ts has 658 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/gatsby/src/utils/worker/child/render-html.ts · ×1
packages/gatsby/src/utils/worker/child/render-html.ts: 658 lines of code packages/gatsby/src/utils/worker/child/render-html.ts:1— packages/gatsby/src/utils/worker/child/render-html.ts has 658 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/gatsby/src/utils/api-runner-node.js · ×1
packages/gatsby/src/utils/api-runner-node.js: 655 lines of code packages/gatsby/src/utils/api-runner-node.js:1— packages/gatsby/src/utils/api-runner-node.js has 655 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/gatsby/src/datastore/lmdb/query/filter-using-index.ts · ×1
packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts: 637 lines of code packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:1— packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts has 637 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/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js · ×1
packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js: 630 lines of code packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:1— packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js has 630 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/gatsby/src/query/file-parser.js · ×1
packages/gatsby/src/query/file-parser.js: 624 lines of code packages/gatsby/src/query/file-parser.js:1— packages/gatsby/src/query/file-parser.js has 624 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/gatsby/src/schema/graphql-engine/bundle-webpack.ts · ×1
packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts: 616 lines of code packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:1— packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts has 616 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/gatsby/src/utils/adapter/manager.ts · ×1
packages/gatsby/src/utils/adapter/manager.ts: 604 lines of code packages/gatsby/src/utils/adapter/manager.ts:1— packages/gatsby/src/utils/adapter/manager.ts has 604 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/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts · ×1
packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts: 594 lines of code packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts:1— packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts has 594 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/gatsby/src/commands/build.ts · ×1
packages/gatsby/src/commands/build.ts: 576 lines of code packages/gatsby/src/commands/build.ts:1— packages/gatsby/src/commands/build.ts has 576 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/babel-plugin-remove-graphql-queries/src/index.ts · ×1
packages/babel-plugin-remove-graphql-queries/src/index.ts: 572 lines of code packages/babel-plugin-remove-graphql-queries/src/index.ts:1— packages/babel-plugin-remove-graphql-queries/src/index.ts has 572 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/gatsby-cli/src/create-cli.ts · ×1
packages/gatsby-cli/src/create-cli.ts: 568 lines of code packages/gatsby-cli/src/create-cli.ts:1— packages/gatsby-cli/src/create-cli.ts has 568 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/gatsby/src/services/initialize.ts · ×1
packages/gatsby/src/services/initialize.ts: 557 lines of code packages/gatsby/src/services/initialize.ts:1— packages/gatsby/src/services/initialize.ts has 557 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/gatsby-plugin-image/src/image-utils.ts · ×1
packages/gatsby-plugin-image/src/image-utils.ts: 554 lines of code packages/gatsby-plugin-image/src/image-utils.ts:1— packages/gatsby-plugin-image/src/image-utils.ts has 554 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/gatsby-source-medium/src/gatsby-node.js · ×1
packages/gatsby-source-medium/src/gatsby-node.js: 553 lines of code packages/gatsby-source-medium/src/gatsby-node.js:1— packages/gatsby-source-medium/src/gatsby-node.js has 553 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/gatsby-source-contentful/src/source-nodes.js · ×1
packages/gatsby-source-contentful/src/source-nodes.js: 524 lines of code packages/gatsby-source-contentful/src/source-nodes.js:1— packages/gatsby-source-contentful/src/source-nodes.js has 524 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/gatsby/src/bootstrap/load-plugins/validate.ts · ×1
packages/gatsby/src/bootstrap/load-plugins/validate.ts: 523 lines of code packages/gatsby/src/bootstrap/load-plugins/validate.ts:1— packages/gatsby/src/bootstrap/load-plugins/validate.ts has 523 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/gatsby/src/internal-plugins/functions/gatsby-node.ts · ×1
packages/gatsby/src/internal-plugins/functions/gatsby-node.ts: 523 lines of code packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:1— packages/gatsby/src/internal-plugins/functions/gatsby-node.ts has 523 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/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js · ×1
packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js: 518 lines of code packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js:1— packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
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/gatsby/src/schema/infer/__tests__/infer.js:433— This repository declares test tooling, and the ✓ above records that declaration — but packages/gatsby/src/schema/infer/__tests__/infer.js and 6 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.
Unlisted import '@parcel/diagnostic' packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:4— 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.
Unlisted import 'terser' packages/gatsby/src/utils/webpack-utils.ts:8— 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.
Unlisted import 'graphql-compose' packages/gatsby-plugin-image/src/resolver-utils.ts:3— 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.
Unlisted import 'express' REDACTED:10— 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.
Unlisted import 'got' packages/gatsby-plugin-utils/src/polyfill-remote-file/utils/get-request-headers-for-url.ts:3— 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.
`async` callback passed to `forEach` packages/gatsby-source-drupal/src/utils.ts:177— `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
X19 · Unrestored process-global state· Process-global state is restored only on the happy path · ×1
Process-global state is restored only on the happy path packages/gatsby/src/services/initialize.ts:76— `initialize` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `GATSBY_QUERY_ON_DEMAND` environment variable (set at line 222, cleared at line 228) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between — or by a promise that rejects at an `await`, and while this function is suspended at one every other callback the event loop runs sees the moved value too: the process then keeps the overwritten value for the rest of its life, and every later relative path, child-process launch or config read in ANY module resolves against it. That failure is silent and remote from its cause — the function that breaks is not the function that moved the directory. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — the `cwd` and `env` options of `child_process.spawn`/`exec`/`execSync` (or `Deno.Command`) scope both to the CHILD — or build absolute paths with `path.resolve`. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
Swallowed exception (caught, then discarded) packages/gatsby-transformer-screenshot/src/gatsby-node.js:116— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Orphaned file packages/gatsby/src/redux/types.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/gatsby/src/datastore/in-memory/indexing.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/gatsby-cli/src/structured-errors/error-map.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/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.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/gatsby-source-drupal/src/gatsby-node.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/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.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/gatsby/cache-dir/loader.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/gatsby/src/schema/node-model.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/gatsby-source-contentful/src/normalize.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/gatsby-source-wordpress/src/utils/fetch-graphql.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/gatsby-transformer-sharp/src/customize-schema.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/gatsby/src/utils/webpack-utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/gatsby/src/redux/actions/restricted.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/babel-plugin-remove-graphql-queries/src/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/gatsby-cli/src/create-cli.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/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.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/gatsby/src/utils/adapter/manager.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/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.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/gatsby/src/query/file-parser.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/gatsby/src/utils/api-node-docs.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/gatsby-source-contentful/src/source-nodes.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/gatsby/src/internal-plugins/functions/gatsby-node.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/gatsby-plugin-image/src/image-utils.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.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.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:612— @babel/plugin-proposal-async-generator-functions 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:622— @babel/plugin-proposal-class-properties 7.12.1 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-static-block REDACTED:638— @babel/plugin-proposal-class-static-block 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:647— @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:655— @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:663— @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:671— @babel/plugin-proposal-logical-assignment-operators 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:695— @babel/plugin-proposal-object-rest-spread 7.12.1 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:704— @babel/plugin-proposal-object-rest-spread 7.20.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:715— @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:740— @babel/plugin-proposal-private-property-in-object 7.20.5 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-unicode-property-regex REDACTED:750— @babel/plugin-proposal-unicode-property-regex 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/polyfill REDACTED:1219— @babel/polyfill 7.6.0 is resolved in REDACTED and is marked deprecated by its publisher: "🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @evocateur/libnpmaccess REDACTED:1568— @evocateur/libnpmaccess 3.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @evocateur/libnpmpublish REDACTED:1579— @evocateur/libnpmpublish 1.2.2 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @evocateur/npm-registry-fetch REDACTED:1594— @evocateur/npm-registry-fetch 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @evocateur/pacote REDACTED:1607— @evocateur/pacote 9.6.5 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @hapi/address REDACTED:2034— @hapi/address 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Moved to 'npm install @sideway/address'". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @hapi/bourne REDACTED:2039— @hapi/bourne 1.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @hapi/hoek REDACTED:2044— @hapi/hoek 6.2.4 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @hapi/topo REDACTED:2069— @hapi/topo 3.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated and is no longer supported or maintained". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:2090— @humanwhocodes/config-array 0.11.10 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/config-array REDACTED:2099— @humanwhocodes/config-array 0.5.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:2113— @humanwhocodes/object-schema 1.2.1 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: @lerna/add REDACTED:2399— @lerna/add 3.21.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Outdated (npm): @graphql-codegen/add REDACTED:25— @graphql-codegen/add is pinned at 3.2.3; 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): @graphql-codegen/core REDACTED:26— @graphql-codegen/core is pinned at 2.6.8; registry.npmjs.org publishes 7.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/plugin-helpers REDACTED:27— @graphql-codegen/plugin-helpers is pinned at 2.7.2; 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): @graphql-codegen/typescript REDACTED:28— @graphql-codegen/typescript is pinned at 2.8.8; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-codegen/typescript-operations REDACTED:29— @graphql-codegen/typescript-operations is pinned at 2.5.13; registry.npmjs.org publishes 7.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-tools/links packages/gatsby-source-graphql/package.json:12— @graphql-tools/links is pinned at 8.3.36; registry.npmjs.org publishes 11.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @graphql-tools/utils REDACTED:20— @graphql-tools/utils is pinned at 8.13.1; registry.npmjs.org publishes 13.2.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): @graphql-tools/wrap packages/gatsby-source-graphql/package.json:14— @graphql-tools/wrap is pinned at 8.5.1; registry.npmjs.org publishes 11.2.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @hapi/hoek REDACTED:21— @hapi/hoek is pinned at 8.5.1; registry.npmjs.org publishes 11.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sindresorhus/slugify e2e-tests/mdx/package.json:8— @sindresorhus/slugify is pinned at 1.1.2; registry.npmjs.org publishes 4.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): @typescript-eslint/eslint-plugin deprecated-packages/gatsby-admin/package.json:28— @typescript-eslint/eslint-plugin is pinned at 5.60.1; registry.npmjs.org publishes 8.72.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): @typescript-eslint/parser deprecated-packages/gatsby-admin/package.json:29— @typescript-eslint/parser is pinned at 5.60.1; registry.npmjs.org publishes 8.72.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): @wordpress/block-library starters/gatsby-starter-wordpress-blog/package.json:13— @wordpress/block-library is pinned at 8.28.1; registry.npmjs.org publishes 12.1.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): boxen packages/gatsby-cli/package.json:24— boxen is pinned at 5.1.2; registry.npmjs.org publishes 9.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): cache-manager packages/gatsby-source-wordpress/package.json:18— cache-manager is pinned at 3.6.3; registry.npmjs.org publishes 7.2.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cache-manager-fs-hash packages/gatsby-source-wordpress/package.json:19— cache-manager-fs-hash is pinned at 0.0.9; registry.npmjs.org publishes 3.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): camelcase packages/gatsby-plugin-image/package.json:91— camelcase is pinned at 6.3.0; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): chokidar REDACTED:24— chokidar is pinned at 3.6.0; 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): coffee-loader packages/gatsby-plugin-coffeescript/package.json:14— coffee-loader is pinned at 0.9.0; registry.npmjs.org publishes 5.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): configstore packages/gatsby-core-utils/package.json:66— configstore is pinned at 5.0.1; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): css-minimizer-webpack-plugin REDACTED:67— css-minimizer-webpack-plugin is pinned at 2.0.0; 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): del packages/gatsby-dev-cli/package.json:16— del is pinned at 6.1.1; registry.npmjs.org publishes 9.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): diff packages/gatsby-source-wordpress/package.json:23— diff is pinned at 5.2.2; registry.npmjs.org publishes 9.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): dotenv benchmarks/md/package.json:21— dotenv is pinned at 8.6.0; registry.npmjs.org publishes 18.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): escape-string-regexp packages/gatsby-plugin-catch-links/package.json:11— escape-string-regexp is pinned at 1.0.5; registry.npmjs.org publishes 5.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.
Mock-dominated test: correctly creates nodes from XML packages/gatsby-transformer-xml/src/__tests__/gatsby-node.js:44— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: Correctly creates nodes from TOML test file packages/gatsby-transformer-toml/src/__tests__/gatsby-node.js:18— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates an ImageSharp node from a file image node packages/gatsby-transformer-sharp/src/__tests__/gatsby-node.js:4— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: doesn't create an ImageSharp node for a .gif file packages/gatsby-transformer-sharp/src/__tests__/gatsby-node.js:35— 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: doesn't create an ImageSharp node if parent is not a File packages/gatsby-transformer-sharp/src/__tests__/gatsby-node.js:65— 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: should only process javascript, jsx, and typescript nodes packages/gatsby-transformer-react-docgen/src/__tests__/on-node-create.js:72— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should do nothing if file extension is not pdf packages/gatsby-transformer-pdf/src/__tests__/gatsby-node.js:26— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should create node base on pdf data packages/gatsby-transformer-pdf/src/__tests__/gatsby-node.js:44— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates nodes from JSON which is an array of objects packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:63— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates a node from JSON which is a single object packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:81— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: creates a jsonId key if id was given packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:96— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly sets node type for array of objects packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:111— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: correctly sets node type for single object packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:159— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates nodes from JSON which is an array of objects and doesn't come from fs packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:195— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates a node from JSON which is a single object and doesn't come from fs packages/gatsby-transformer-json/src/__tests__/gatsby-node.js:213— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not loadNodeContent for not javascript file packages/gatsby-transformer-javascript-frontmatter/src/__tests__/gatsby-node.js:68— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should load frontmatter data with exported object packages/gatsby-transformer-javascript-frontmatter/src/__tests__/gatsby-node.js:90— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) 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: should load frontmatter data from named export packages/gatsby-transformer-javascript-frontmatter/src/__tests__/gatsby-node.js:105— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should pass fileAbsolutePath to node if file type is "File" packages/gatsby-transformer-javascript-frontmatter/src/__tests__/gatsby-node.js:130— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates nodes from HJSON which is an array of objects packages/gatsby-transformer-hjson/src/__tests__/gatsby-node.js:23— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates a node from HJSON which is a single object packages/gatsby-transformer-hjson/src/__tests__/gatsby-node.js:51— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates nodes from JSON which is an array of objects packages/gatsby-transformer-excel/src/__tests__/gatsby-node.js:22— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should correctly create nodes from JSON with raw option false packages/gatsby-transformer-excel/src/__tests__/gatsby-node.js:53— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should correctly create nodes from JSON with legacy rawOutput option false packages/gatsby-transformer-excel/src/__tests__/gatsby-node.js:87— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: correctly creates nodes from JSON which is an array of objects packages/gatsby-transformer-csv/src/__tests__/gatsby-node.js:24— This test sets up 4 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
redundant comment packages/babel-plugin-remove-graphql-queries/src/index.ts:369— "Remove imports to useStaticQuery" repeats the code it sits on: 4 of its 5 words (imports, use, static, query) are already in `const importPath = (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/babel-plugin-remove-graphql-queries/src/index.ts:431— "Replace the query with the hash of the query." repeats the code it sits on: 3 of its 3 words (replace, query, hash) are already in `templatePath.replaceWith(t.StringLiteral(queryHash))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/create-gatsby/src/init-starter.ts:76— "Remove git support if initial commit fails" repeats the code it sits on: 5 of its 6 words (git, support, initial, commit, fails) are already in `reporter.info(`Initial git commit failed - removing git support\n`)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/create-gatsby/src/utils/is-truthy.ts:9— "Return false if null or undefined" repeats the code it sits on: 4 of its 4 words (return, false, null, undefined) are already in `if (value === undefined || value === null) return false`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-adapter-netlify/src/allowed-remote-urls.ts:23— "test if url pattern already passes one of the regexes in netlify.toml" repeats the code it sits on: 7 of its 8 words (test, url, pattern, already, regexes, netlify, toml) are already in `const isAlreadyAllowed = allowedUrlsInNetlifyTomlRegexes.some(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:90— "Remove git support if initial commit fails" repeats the code it sits on: 5 of its 6 words (git, support, initial, commit, fails) are already in `report.info(`Initial git commit failed - removing git support\n`)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-core-utils/src/is-truthy.ts:7— "Return false if null or undefined" repeats the code it sits on: 4 of its 4 words (return, false, null, undefined) are already in `if (value === undefined || value === null) return false`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-link/src/index.js:21— "Set up IntersectionObserver" repeats the code it sits on: 3 of its 3 words (set, intersection, observer) are already in `const createIntersectionObserver = (el, cb) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-plugin-image/src/components/hooks.ts:60— "This checks both for gatsbyImageData and gatsbyImage" repeats the code it sits on: 4 of its 4 words (checks, gatsby, image, data) are already in `if (isGatsbyImageData(node))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-plugin-manifest/src/gatsby-node.js:187— "Check if the icon exists" repeats the code it sits on: 3 of its 3 words (check, icon, exists) are already in `if (!doesIconExist(icon))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-plugin-page-creator/src/path-utils.ts:21— "Remove the file extension from the end of a path" repeats the code it sits on: 4 of its 5 words (remove, file, extension, path) are already in `export function removeFileExtension(absolutePath: string): string`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-plugin-preact/src/gatsby-node.js:52— "add webpack-hot-middleware/client to the commons entry" repeats the code it sits on: 6 of its 7 words (webpack, hot, middleware, client, commons, entry) are already in `webpackConfig.entry.commons.unshift(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-remark-copy-linked-files/src/index.js:235— "extracts all elements that have the provided url attribute" repeats the code it sits on: 4 of its 5 words (extracts, elements, url, attribute) are already in `function extractUrlAttributeAndElement(selection, attribute)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-contentful/src/__tests__/normalize.js:37— "Counts the created nodes per node type" repeats the code it sits on: 5 of its 5 words (counts, created, nodes, node, type) are already in `function countCreatedNodeTypesFromMock(mock)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-contentful/src/normalize.js:443— "Create a node for the content type" repeats the code it sits on: 4 of its 4 words (create, node, content, type) are already in `const contentTypeNode = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-drupal/src/__tests__/index.js:565— 5 comments in this file only repeat the code they sit on (lines 565, 629, 653, 678, 737), for example "Call onPreBootstrap to set options". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-drupal/src/gatsby-node.ts:642— "Construct URL with new pageOffset." repeats the code it sits on: 4 of its 5 words (url, new, page, offset) are already in `newUrl.searchParams.set(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-filesystem/src/create-file-node-from-buffer.js:85— "Create the file node." repeats the code it sits on: 3 of its 3 words (create, file, node) are already in `const fileNode = await createFileNode(filename, createNodeId, {})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-filesystem/src/create-file-path.js:35— "Find the File node" repeats the code it sits on: 3 of its 3 words (find, file, node) are already in `const fileNode = findFileNode({ node, getNode })`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-filesystem/src/create-remote-file-node.js:65— "Create the file node." repeats the code it sits on: 3 of its 3 words (create, file, node) are already in `const fileNode = await createFileNode(filename, createNodeId, {})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js:15— "recursively transform fields" repeats the code it sits on: 3 of its 3 words (recursively, transform, fields) are already in `const transformedFields = recursivelyTransformFields({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js:307— "if we have either inlineFragments or fields" repeats the code it sits on: 3 of its 3 words (inline, fragments, fields) are already in `return {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-wordpress/src/steps/persist-cached-images.ts:10— "get all existing media item nodes" repeats the code it sits on: 4 of its 5 words (get, media, item, nodes) are already in `const mediaItemNodes = helpers.getNodesByType(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment packages/gatsby-source-wordpress/src/steps/source-nodes/before-change-node/menu.js:24— "delete child menu items" repeats the code it sits on: 4 of its 4 words (delete, child, menu, items) are already in `return deleteMenuNodeChildMenuItems(api.remoteNode)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:319— "Create the file node." repeats the code it sits on: 3 of its 3 words (create, file, node) are already in `const fileNode = await createFileNode(filename, createNodeId, {})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate packages/gatsby/src/state-machines/develop/index.ts:271— `!!pendingQueryRuns && pendingQueryRuns.size > 0` appears character-identically in 2 files — packages/gatsby/src/state-machines/develop/index.ts, packages/gatsby/src/state-machines/query-running/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-codemods/src/transforms/global-graphql-calls.js:19— `!!template && template.value.raw === MODULE_NAME` appears character-identically in 2 files — packages/gatsby-codemods/src/transforms/global-graphql-calls.js, packages/gatsby-codemods/src/transforms/import-link.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/gatsby-plugin-manifest/src/safe-sharp.js:66— `!acc.latestVersion || semver.gt(sharpVersion, acc.latestVersion)` appears character-identically in 4 files — packages/gatsby-plugin-manifest/src/safe-sharp.js, packages/gatsby-plugin-sharp/src/safe-sharp.js, packages/gatsby-remark-images-contentful/src/safe-sharp.js, packages/gatsby-transformer-sharp/src/safe-sharp.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 deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.js:377— `!plugin.key && plugin.name !== pluginOrThemeName` appears character-identically in 2 files — deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.js, packages/gatsby-cli/src/handlers/plugin-babel-utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts:197— `!props || typeof props !== `object` || Array.isArray(props)` appears character-identically in 2 files — packages/gatsby-codemods/src/transforms/sort-and-aggr-graphql.ts, packages/gatsby/src/query/transform-document.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/is-default-export.js:10— `!t.isIdentifier(object) || object.name !== `module`` appears character-identically in 2 files — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/is-default-export.js, packages/gatsby-cli/src/handlers/plugin-babel-utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/is-default-export.js:11— `!t.isIdentifier(property) || property.name !== `exports`` appears character-identically in 2 files — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/is-default-export.js, packages/gatsby-cli/src/handlers/plugin-babel-utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.js:51— `!t.isObjectExpression(node) && !t.isLogicalExpression(node)` appears character-identically in 2 files — deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.js, packages/gatsby-cli/src/handlers/plugin-babel-utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby/src/commands/build-html.ts:604— `(process.env.GATSBY_PARTIAL_HYDRATION === `true` || process.env.GATSBY_PARTIAL_HYDRATION === `1`) && _CFLAGS_.GATSBY_MAJOR === `5`` appears character-identically in 3 files — packages/gatsby/src/commands/build-html.ts, packages/gatsby/src/commands/build.ts, packages/gatsby/src/utils/webpack.config.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/gatsby/src/services/initialize.ts:66— `(reason as Error) || `Unhandled rejection`` appears character-identically in 2 files — packages/gatsby/src/services/initialize.ts, packages/gatsby/src/utils/worker/reporter.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-source-contentful/src/normalize.js:17— `(typeof getGatsbyVersion === `function` && getGatsbyVersion()) || `0.0.0`` appears character-identically in 2 files — packages/gatsby-source-contentful/src/normalize.js, packages/gatsby-source-drupal/src/utils.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-source-graphql/src/batching/dataloader-link.js:22— `Number(process.env.GATSBY_EXPERIMENTAL_QUERY_CONCURRENCY) || 4` appears character-identically in 2 files — packages/gatsby-source-graphql/src/batching/dataloader-link.js, packages/gatsby/src/query/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate deprecated-packages/gatsby-recipes/src/providers/gatsby/page.js:98— `REQUIRES_KEYS.includes(resource.name) && !resource.key` appears character-identically in 2 files — deprecated-packages/gatsby-recipes/src/providers/gatsby/page.js, deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.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/gatsby/src/commands/build-html.ts:431— `_CFLAGS_.GATSBY_MAJOR === `5` && process.env.GATSBY_SLICES` appears character-identically in 8 files — packages/gatsby/src/commands/build-html.ts, packages/gatsby/src/commands/build.ts, packages/gatsby/src/redux/actions/restricted.ts, packages/gatsby/src/redux/reducers/html.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby/cache-dir/navigation.js:113— ``serviceWorker` in navigator && navigator.serviceWorker.controller !== null && navigator.serviceWorker.controller.state === `activated`` appears character-identically in 2 files — packages/gatsby/cache-dir/navigation.js, packages/gatsby/cache-dir/production-app.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/gatsby-cli/src/reporter/loggers/ipc/index.ts:24— ``statusText` in copiedAction.payload && copiedAction.payload.statusText` appears character-identically in 2 files — packages/gatsby-cli/src/reporter/loggers/ipc/index.ts, packages/gatsby-cli/src/reporter/loggers/json/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-cli/src/reporter/loggers/ipc/index.ts:21— ``text` in copiedAction.payload && copiedAction.payload.text` appears character-identically in 2 files — packages/gatsby-cli/src/reporter/loggers/ipc/index.ts, packages/gatsby-cli/src/reporter/loggers/json/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/gatsby-codemods/src/transforms/__testfixtures__/gatsby-plugin-image/no-change.input.js:14— `content[idx - 1] && content[idx - 1].componentName === `Heading`` appears character-identically in 2 files — packages/gatsby-codemods/src/transforms/__testfixtures__/gatsby-plugin-image/no-change.input.js, packages/gatsby-codemods/src/transforms/__testfixtures__/gatsby-plugin-image/no-change.output.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/gatsby/src/state-machines/develop/actions.ts:186— `context.pendingQueryRuns || new Set<string>()` appears character-identically in 2 files — packages/gatsby/src/state-machines/develop/actions.ts, packages/gatsby/src/state-machines/query-running/actions.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate starters/blog/src/pages/index.js:9— `data.site.siteMetadata?.title || `Title`` appears character-identically in 2 files — starters/blog/src/pages/index.js, starters/default/src/components/layout.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 deprecated-packages/gatsby-telemetry/src/index.ts:73— `data.sort()[Math.floor((data.length - 1) / 2)] || 0` appears character-identically in 2 files — deprecated-packages/gatsby-telemetry/src/index.ts, deprecated-packages/gatsby-telemetry/src/telemetry.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate deprecated-packages/gatsby-transformer-javascript-static-exports/src/gatsby-node.js:100— `dataVariableDeclarator && dataVariableDeclarator.init` appears character-identically in 2 files — deprecated-packages/gatsby-transformer-javascript-static-exports/src/gatsby-node.js, packages/gatsby-transformer-javascript-frontmatter/src/gatsby-node.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 deprecated-packages/gatsby-transformer-javascript-static-exports/src/gatsby-node.js:94— `declaration && declaration.type === `VariableDeclaration`` appears character-identically in 2 files — deprecated-packages/gatsby-transformer-javascript-static-exports/src/gatsby-node.js, packages/gatsby-transformer-javascript-frontmatter/src/gatsby-node.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 starters/blog/src/components/seo.js:28— `description || site.siteMetadata.description` appears character-identically in 2 files — starters/blog/src/components/seo.js, starters/default/src/components/seo.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/gatsby/cache-dir/app.js:231— `doc.readyState === `complete` || (doc.readyState !== `loading` && !doc.documentElement.doScroll)` appears character-identically in 2 files — packages/gatsby/cache-dir/app.js, packages/gatsby/cache-dir/production-app.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.
+ 15 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:17— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 17 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:29— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:42— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:43— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:56— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:69— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 69 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:70— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 70 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:274— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 274 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/api-browser-docs.ts:289— `packages/gatsby/src/utils/api-browser-docs.ts` reports through `console.*` at line 289 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/nodes.ts:28— `packages/gatsby/src/utils/nodes.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:6— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 6 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:7— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 7 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:8— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 8 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:11— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:14— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:18— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:21— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:22— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:25— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:28— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:33— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:37— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:41— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:42— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/gatsby/src/utils/print-instructions.ts:45— `packages/gatsby/src/utils/print-instructions.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
No direct assertions: Not changing plugin doesn't invalidate nodes created by it integration-tests/cache-resilience/__tests__/cache.js:181— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding plugin adds new node integration-tests/cache-resilience/__tests__/cache.js:190— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing plugin clears nodes owned by it integration-tests/cache-resilience/__tests__/cache.js:199— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing plugin clears nodes owned by it and recreate nodes integration-tests/cache-resilience/__tests__/cache.js:208— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding source plugin cause transformers to create child nodes integration-tests/cache-resilience/__tests__/cache.js:220— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing source plugin invalidate nodes owned by it and all children nodes integration-tests/cache-resilience/__tests__/cache.js:229— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing source plugin invalidate nodes owned by it and all children nodes and recreates all nodes integration-tests/cache-resilience/__tests__/cache.js:238— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding transformer adds child nodes to existing nodes integration-tests/cache-resilience/__tests__/cache.js:249— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing transformer clear nodes owned by it and remove children from parent nodes integration-tests/cache-resilience/__tests__/cache.js:258— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing transformer clears and recreates nodes owned by it integration-tests/cache-resilience/__tests__/cache.js:267— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding source plugin creates a node with fields integration-tests/cache-resilience/__tests__/cache.js:280— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing source plugin clears and recreates nodes owned by it integration-tests/cache-resilience/__tests__/cache.js:289— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding transformer adds fields to node created by source plugin integration-tests/cache-resilience/__tests__/cache.js:300— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing transformer removes fields from node created by source plugin integration-tests/cache-resilience/__tests__/cache.js:309— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing transformer removes fields from node created by source plugin and recreate fields integration-tests/cache-resilience/__tests__/cache.js:318— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Preserve disk cache if owner plugin did not changed integration-tests/cache-resilience/__tests__/cache.js:331— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing owner plugin clears disk cache integration-tests/cache-resilience/__tests__/cache.js:342— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding owner plugin creates disk cache integration-tests/cache-resilience/__tests__/cache.js:353— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing owner plugin clears disk cache and recreates it integration-tests/cache-resilience/__tests__/cache.js:364— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Not changing plugin doesn't change query results integration-tests/cache-resilience/__tests__/cache.js:401— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding plugin adds a type to schema integration-tests/cache-resilience/__tests__/cache.js:408— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing plugin removes a type from schema integration-tests/cache-resilience/__tests__/cache.js:415— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Changing plugin invalidates query results integration-tests/cache-resilience/__tests__/cache.js:422— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Adding source plugin creates parent and child types in schema and they are queryable on second run integration-tests/cache-resilience/__tests__/cache.js:432— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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: Removing source plugin removes parent and child types from schema and they are queryable on first run integration-tests/cache-resilience/__tests__/cache.js:439— No conventional assertion call was detected, and 34 of 39 tests in `integration-tests/cache-resilience` 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.
Disabled test packages/gatsby-link/src/__tests__/is-local-link.js:15— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/gatsby-link/src/__tests__/is-local-link.js:20— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:56— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:57— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:58— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:59— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:60— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:61— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:62— 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/gatsby-plugin-catch-links/src/__tests__/catch-links.js:63— 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/gatsby-plugin-sharp/src/__tests__/index.js:124— 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/gatsby-plugin-utils/src/polyfill-remote-file/jobs/__tests__/gatsby-worker.ts:29— 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/gatsby-remark-custom-blocks/src/__tests__/index.js:6— 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/gatsby/src/redux/reducers/__tests__/queries.ts:305— 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/gatsby/src/redux/reducers/__tests__/queries.ts:430— 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/gatsby/src/redux/reducers/__tests__/queries.ts:543— 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/gatsby/src/schema/__tests__/build-schema.js:603— 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/gatsby/src/schema/__tests__/build-schema.js:850— 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/gatsby/src/schema/__tests__/connection-filter-on-linked-nodes.js:305— 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/gatsby/src/schema/__tests__/connection-filter-on-linked-nodes.js:309— 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/gatsby/src/schema/__tests__/node-model.js:445— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test packages/gatsby/src/schema/__tests__/rebuild-schema.js:289— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Documentation: no build, run or usage example .github/actions/gatsby-site-showcase-validator/README.md:1— `gatsby-site-showcase-validator` is runnable (a `start` script in `REDACTED`) and neither `.github/actions/gatsby-site-showcase-validator/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-graphiql-explorer/README.md:1— `gatsby-graphiql-explorer` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-graphiql-explorer/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-legacy-polyfills/README.md:1— `gatsby-legacy-polyfills` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-legacy-polyfills/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-link/README.md:1— `gatsby-link` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-link/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-parcel-config/README.md:1— `gatsby-parcel-config` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-parcel-config/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-react-router-scroll/README.md:1— `gatsby-react-router-scroll` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-react-router-scroll/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example packages/gatsby-source-wordpress/README.md:1— `gatsby-source-wordpress` is a published package (`REDACTED` without `"private": true`) and neither `packages/gatsby-source-wordpress/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
README/code drift deprecated-packages/gatsby-plugin-netlify-cms/README.md:7— deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 1, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift deprecated-packages/gatsby-plugin-netlify-cms/README.md:9— deprecated-packages/gatsby-plugin-netlify-cms/README.md names Gatsby 2, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/docs/debugging-incremental-builds.md:5— docs/docs/debugging-incremental-builds.md names Gatsby 3, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/docs/profiling-site-performance-with-react-profiler.md:9— docs/docs/profiling-site-performance-with-react-profiler.md names React 16, but the manifest declares `react` ^17.0.2. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/tutorial/building-a-theme.md:175— docs/tutorial/building-a-theme.md names Gatsby 404, but the manifest declares `gatsby` ^4.14.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/gatsby-plugin-emotion/README.md:9— packages/gatsby-plugin-emotion/README.md names Emotion 8, but the manifest declares `emotion` ^11.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Silent fallback default in catch deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.js:171— `getReadmeForPlugin` swallows every exception into `return ``` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch deprecated-packages/gatsby-telemetry/src/event-storage.ts:58— `getUserAgent` swallows every exception into `return `Gatsby Telemetry`` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/gatsby-core-utils/src/get-gatsby-version.ts:11— `getGatsbyVersion` swallows every exception into `return ``` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/gatsby-transformer-screenshot/lambda/screenshot.js:40— `getFile` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/gatsby/src/redux/index.ts:77— `readState` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/gatsby/src/utils/flags.ts:17— `satisfiesSemvers.result` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Blanket warning suppression packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/gatsby-transformer-sharp/src/fragments.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression packages/gatsby/cache-dir/fast-refresh-overlay/helpers/focus-trap.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression REDACTED:247— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file packages/gatsby/src/redux/actions/public.js:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file packages/gatsby/src/schema/schema.js:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Fat interface: ObjectSchema (20 required operations) packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1570— `ObjectSchema` declares 20 required operations: `and`, `append`, `assert`, `instance`, `keys`, `length`, `max`, `min`, `nand`, `or`, `oxor`, `pattern`, `ref`, `regex`, `rename`, `schema`, `unknown`, `with`, `without`, `xor`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: PluginOptionsSchemaJoi (55 required operations) packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:1956— `PluginOptionsSchemaJoi` declares 55 required operations: `ValidationError`, `any`, `array`, `bool`, `boolean`, `binary`, `date`, `func`, `function`, `number`, `object`, `string`, `symbol`, `alternatives`, `alternatives`, `alt`, `alt`, `link`, `assert`, `assert`, `attempt`, `attempt`, `compile`, `checkPreferences`, `custom`, `defaults`, `expression`, `extend`, `in`, `isError`, `isExpression`, `isRef`, `isSchema`, `ref`, `types`, `x`, `subPlugins`, `allow`, `valid`, `equal`, and 15 more. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 55 declarations carry 50 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 50 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
No app-layer HTTPS enforcement detected REDACTED:362— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected REDACTED:862— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies packages/babel-plugin-remove-graphql-queries/src/index.ts:256— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 7 significant file(s) lose their only recent owner: packages/gatsby/src/utils/page-ssr-module/lambda.ts, packages/gatsby-adapter-netlify/src/lambda-handler.ts, packages/gatsby/src/utils/adapter/init.ts, packages/gatsby/src/bootstrap/load-themes/index.ts, packages/gatsby-dev-cli/src/local-npm-registry/publish-package.js, packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts, packages/gatsby-dev-cli/src/utils/traverse-package-deps.js. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (8 single-owned of 404 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; 404 of the 1109 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/gatsby-plugin-manifest/src/pluginOptionsSchema.js.
No ADRs found packages/gatsby-plugin-preload-fonts/package.json:7— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/gatsby-plugin-preload-fonts/package.json` makes this repository a deployable product (line 7).
D21 · Naming Consistency· `updateURL` spells `URL` where 20 names in the project spell it `Url` · ×1
`updateURL` spells `URL` where 20 names in the project spell it `Url` packages/gatsby-graphiql-explorer/src/app.jsx:71— 20 of 22 names in project repository spell the token `Url` (20 of 22; unit: names in project repository containing `Url`). Peers: resolve-recipe.resolveRecipe(pathOrUrl) (deprecated-packages/gatsby-recipes/src/resolve-recipe.js:14); [...imageUrl].ImageUrl (examples/route-api/src/pages/image/[...imageUrl].js:4); body-parser-urlencoded-limit.bodyParserUrlUncodedLimit (integration-tests/functions/src/api/config/body-parser-urlencoded-limit.js:3); internals.resolveSiteUrl (packages/gatsby-plugin-sitemap/src/internals.js:33); image-helpers.createUrl (packages/gatsby-source-contentful/src/image-helpers.js:27). Rename to `updateUrl`. [rule N6]
D21 · Naming Consistency· `newLinkURL` spells `URL` where 20 names in the project spell it `Url` · ×1
`newLinkURL` spells `URL` where 20 names in the project spell it `Url` packages/gatsby-remark-copy-linked-files/src/index.js:58— 20 of 22 names in project repository spell the token `Url` (20 of 22; unit: names in project repository containing `Url`). Peers: resolve-recipe.resolveRecipe(pathOrUrl) (deprecated-packages/gatsby-recipes/src/resolve-recipe.js:14); [...imageUrl].ImageUrl (examples/route-api/src/pages/image/[...imageUrl].js:4); body-parser-urlencoded-limit.bodyParserUrlUncodedLimit (integration-tests/functions/src/api/config/body-parser-urlencoded-limit.js:3); internals.resolveSiteUrl (packages/gatsby-plugin-sitemap/src/internals.js:33); image-helpers.createUrl (packages/gatsby-source-contentful/src/image-helpers.js:27). Rename to `newLinkUrl`. [rule N6]
D21 · Naming Consistency· `wpActionUPDATE` spells `UPDATE` where 41 names in the project spell it `Update` · ×1
`wpActionUPDATE` spells `UPDATE` where 41 names in the project spell it `Update` packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:275— 41 of 42 names in project repository spell the token `Update` (41 of 42; unit: names in project repository containing `Update`). Peers: update.runUpdate (benchmarks/source-agilitycms/bin/update.js:19); site.runDataUpdate (benchmarks/source-contentful/bin/site.js:362); gatsby-browser.onRouteUpdate (deprecated-packages/gatsby-plugin-guess-js/src/gatsby-browser.js:7); server.emitUpdate (deprecated-packages/gatsby-recipes/src/graphql-server/server.js:49); gatsby-browser.onPreRouteUpdate (e2e-tests/development-runtime/gatsby-browser.js:16). Rename to `wpActionUpdate`. [rule N6]
D21 · Naming Consistency· `locInGraphQlToLocInFile` spells `Ql` where 51 names in the project spell it `QL` · ×1
`locInGraphQlToLocInFile` spells `Ql` where 51 names in the project spell it `QL` packages/gatsby/src/query/error-parser.ts:176— 51 of 52 names in project repository spell the token `QL` (51 of 52; unit: names in project repository containing `QL`). Peers: providers.GraphQLProvider (deprecated-packages/gatsby-admin/src/components/providers.tsx:136); gatsby-node.cacheGraphQLConfig (deprecated-packages/gatsby-plugin-graphql-config/src/gatsby-node.ts:7); graphql-typegen.GraphQLTypegen (e2e-tests/development-runtime/src/pages/graphql-typegen.tsx:4); packages.babel-plugin-remove-graphql-queries.src.IGraphQLTag (packages/babel-plugin-remove-graphql-queries/src/index.ts:37); packages.babel-plugin-remove-graphql-queries.src.EmptyGraphQLTagError (packages/babel-plugin-remove-graphql-queries/src/index.ts:76). Rename to `locInGraphQLToLocInFile`. [rule N6]
D21 · Naming Consistency· `skipSsr` spells `Ssr` where 13 names in the project spell it `SSR` · ×1
`skipSsr` spells `Ssr` where 13 names in the project spell it `SSR` packages/gatsby/src/utils/dev-ssr/render-dev-html.ts:141— 13 of 14 names in project repository spell the token `SSR` (13 of 14; unit: names in project repository containing `SSR`). Peers: IFlattenedPlugin.skipSSR (packages/gatsby-plugin-utils/src/types.ts:48); IFlattenedPlugin.skipSSR (packages/gatsby/src/bootstrap/load-plugins/types.ts:44); build-html.devSSRWillInvalidate (packages/gatsby/src/commands/build-html.ts:61); build-html.getDevSSRWebpack (packages/gatsby/src/commands/build-html.ts:71); packages.gatsby.src.redux.types.ISetSSRGlobalSharedWebpackCompilationHashAction (packages/gatsby/src/redux/types.ts:974). Rename to `skipSSR`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 118 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. The most over is `packages/gatsby` (54151 LoC, 639 module-visible types across 59 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
Concentrated knowledge decay — 315 of 426 significant files have no living knowledge, while the repository is still being changed at a low rate (10 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 315 separate risks. Counted over 426 of the 1109 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
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.
Logging is not universal — Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/create-gatsby`, `packages/gatsby-cli`, `packages/gatsby-codemods`, `packages/gatsby-dev-cli`.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 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.
No dependency-update automation REDACTED:3— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 2/22 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 21/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~1.0 `!` null assertions per 1k TypeScript source lines — 79 assertion(s) across the 82852 source line(s) of the 637 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/gatsby/src/datastore/in-memory/indexing.ts (18), packages/gatsby-source-drupal/src/plugin-options.ts (7), packages/gatsby/src/utils/jobs/manager.ts (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Hand-rolled JSON/XML parsing via regex packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js:69— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Outdated (npm): @apollo/client — @apollo/client is pinned at 3.7.16; registry.npmjs.org publishes 4.3.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/code-frame — @babel/code-frame is pinned at 7.29.0; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/core — @babel/core is pinned at 7.20.12; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/eslint-parser — @babel/eslint-parser is pinned at 7.21.8; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/generator — @babel/generator is pinned at 7.20.14; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/helper-plugin-utils — @babel/helper-plugin-utils is pinned at 7.20.2; 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/parser — @babel/parser is pinned at 7.20.13; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-proposal-optional-chaining — @babel/plugin-proposal-optional-chaining is pinned at 7.20.7; registry.npmjs.org publishes 7.21.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-jsx — @babel/plugin-syntax-jsx is pinned at 7.18.6; 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.20.0; registry.npmjs.org publishes 8.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-classes — @babel/plugin-transform-classes is pinned at 7.20.7; registry.npmjs.org publishes 8.1.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-transform-runtime — @babel/plugin-transform-runtime is pinned at 7.19.6; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-spread — @babel/plugin-transform-spread is pinned at 7.20.7; registry.npmjs.org publishes 8.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-typescript — @babel/plugin-transform-typescript is pinned at 7.20.13; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-env — @babel/preset-env is pinned at 7.20.2; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-flow — @babel/preset-flow is pinned at 7.18.6; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-react — @babel/preset-react is pinned at 7.18.6; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-typescript — @babel/preset-typescript is pinned at 7.18.6; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/runtime — @babel/runtime is pinned at 7.23.7; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/template — @babel/template is pinned at 7.20.7; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/traverse — @babel/traverse is pinned at 7.20.13; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/types — @babel/types is pinned at 7.20.7; registry.npmjs.org publishes 8.1.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @builder.io/partytown — @builder.io/partytown is pinned at 0.7.5; registry.npmjs.org publishes 0.10.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): @contentful/rich-text-react-renderer — @contentful/rich-text-react-renderer is pinned at 15.22.11; registry.npmjs.org publishes 16.2.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): @emotion/babel-preset-css-prop — @emotion/babel-preset-css-prop is pinned at 11.11.0; registry.npmjs.org publishes 11.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.
Skipped (documented): (unnamed test) packages/gatsby-transformer-remark/src/__tests__/extend-node.js:154— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:25— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:28— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:31— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:34— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:37— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:40— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:43— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:46— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:49— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:52— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:55— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:58— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:61— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:64— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:68— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:71— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:74— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:77— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:81— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:84— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:87— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:90— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:93— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/gatsby/src/utils/eslint-rules/__tests__/limited-exports-page-templates.ts:96— Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
doc comments repeat the names packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:24— 0 of 0 documented parameters and 1 of 4 summaries in `functions` only repeat the member or parameter name (e.g. "The glob pattern *" for `globPattern`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby/cache-dir/find-path.js:62— 16 of 105 documented parameters and 5 of 379 summaries in `gatsby` only repeat the member or parameter name (e.g. "A raw pathname" for `rawPathname`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-core-utils/src/path.ts:75— 1 of 11 documented parameters and 0 of 21 summaries in `gatsby-core-utils` only repeat the member or parameter name (e.g. "File name" for `fileName`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-plugin-sharp/src/plugin-options.ts:111— 0 of 0 documented parameters and 1 of 4 summaries in `gatsby-plugin-sharp` only repeat the member or parameter name (e.g. "Creates a transform object" for `createTransformObject`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts:753— 2 of 52 documented parameters and 2 of 304 summaries in `gatsby-plugin-utils` only repeat the member or parameter name (e.g. "Get value from given flag." for `$_getFlag`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-source-contentful/src/fetch.js:377— 0 of 2 documented parameters and 1 of 7 summaries in `gatsby-source-contentful` only repeat the member or parameter name (e.g. "Fetches: * Content types" for `fetchContentTypes`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-source-lever/src/normalize.js:8— 0 of 0 documented parameters and 1 of 5 summaries in `gatsby-source-lever` only repeat the member or parameter name (e.g. "Create the Graph QL Node" for `createGraphQLNode`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-source-shopify/src/update-cache.ts:12— 1 of 4 documented parameters and 0 of 3 summaries in `gatsby-source-shopify` only repeat the member or parameter name (e.g. "Plugin Options Object" for `pluginOptions`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names packages/gatsby-transformer-sharp/src/fragments.js:31— 0 of 0 documented parameters and 2 of 14 summaries in `gatsby-transformer-sharp` only repeat the member or parameter name (e.g. "Traced SVG fixed images" for `GatsbyImageSharpFixed_tracedSVG`). Delete the restating tags, or add what the name does not say.
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.
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 9 file(s) — `packages/gatsby-plugin-utils/src/polyfill-remote-file/types.ts`, `packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts`, `packages/gatsby-source-shopify/src/create-resolvers.ts`, `packages/gatsby-source-shopify/types/interface.d.ts`, `packages/gatsby-source-wordpress/src/models/gatsby-api.ts`, … (+4 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
Run 01a1d612-22ce-780f-b2ab-97a63284f626 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 452 · Warnings: 1379 · Recommendations: 953 · Info: 287 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 18:01 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.