gatsby — Watchdog Audit

Executive summary

⚠ A critical security finding caps this grade — resolve it before relying on the score below; see the Security lens.

This large-scale asset, representing approximately €210,000 in rebuild value, is currently at risk with an overall health score of 49%. While the codebase is substantial, its operational fragility threatens delivery speed and reliability. The primary concern is not the size of the system, but the significant gap between its maturity and its readiness for production. This imbalance creates a high-stakes environment where minor changes can trigger disproportionate costs and delays.

The most critical vulnerability lies in Production Readiness, which scores a mere 43%. For a system of this magnitude, low readiness means that changes are likely to introduce defects, cause outages, or expose security gaps because the safety nets of testing and observability are insufficient. This weakness acts as a drag on every release, increasing the time and effort required to ship features. The risk is not theoretical; it directly impacts the team’s ability to respond to market needs without breaking existing functionality.

Compounding this is a Velocity Tax driven by poor code quality. The average complexity and cohesion scores suggest that every modification costs 13–28% more than it should. This inefficiency compounds over time, meaning the team is paying a hidden premium for every line of code they touch. While the architecture is moderately sound, the lack of clean, maintainable code ensures that future enhancements will become increasingly expensive and slow, eroding competitive advantage.

However, the situation is not hopeless. The system has a solid foundation in maturity, and the path to improvement is clear and cost-effective. The highest-leverage action is to integrate static application security testing into the continuous integration pipeline. This single step costs only a few engineer-days to implement but prevents recurring security regressions, paying for itself within months. By securing the build process first, the organization can stabilize the system and reduce the velocity tax, turning a fragile asset into a reliable one.

Code Health 66% Adequate · gated by D1, D2 Architecture 60% Adequate · gated by R9 Maturity 73% Adequate · gated by D34 Readiness 43% Weak · gated by R8, P3 Security 48% Weak · gated by D28, D29, D30, D36 Accessibility 58% Adequate · gated by AC2

How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.

Readiness 43% · 46% weightSecurity 48% · 25% weightAccessibility 58% · 14% weightArchitecture 60% · 8% weightCode Health 66% · 4% weightMaturity 73% · 2% weight

Raise Readiness 43 → 70 (the Healthy floor) ⇒ headline 49 → ~55.

Code composition — where the lines go

Tests 100%

New since the last scan (100+)

1126 finding(s) are new versus the previous scan (2026-08-06) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.

D1 · exports (cyclomatic 107) packages/gatsby/src/utils/webpack.config.js
D1 · html.htmlReducer (cyclomatic 77) packages/gatsby/src/redux/reducers/html.ts
D1 · start-server.startServer (cyclomatic 74) REDACTED
D1 · gatsby-node.sourceNodes (cyclomatic 70) packages/gatsby-source-drupal/src/gatsby-node.ts
D1 · index.default (cyclomatic 68) packages/gatsby-remark-images/src/index.js
D1 · extend-node-type.remarkExtendNodeType (cyclomatic 68) packages/gatsby-transformer-remark/src/extend-node-type.js
D1 · build.build (cyclomatic 55) packages/gatsby/src/commands/build.ts
D1 · sourceNodes (cyclomatic 54) packages/gatsby-source-contentful/src/source-nodes.js
D1 · image-data.generateImageData (cyclomatic 52) packages/gatsby-plugin-sharp/src/image-data.ts
D1 · handle-flags.handleFlags (cyclomatic 51) packages/gatsby/src/utils/handle-flags.ts
D1 · indexing.getNodesFromCacheByValue (cyclomatic 50) packages/gatsby/src/datastore/in-memory/indexing.ts
D1 · initialize.initialize (cyclomatic 47) packages/gatsby/src/services/initialize.ts
D1 · recursively-transform-fields.transformField (cyclomatic 46) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js
D1 · queries.queriesReducer (cyclomatic 45) packages/gatsby/src/redux/reducers/queries.ts
D1 · createPage (cyclomatic 44) packages/gatsby/src/redux/actions/public.js
D1 · normalize.createNodesForContentType (cyclomatic 43) packages/gatsby-source-contentful/src/normalize.js
D1 · replaceNodeHtmlImages (cyclomatic 43) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js
D1 · index.fluid (cyclomatic 41) packages/gatsby-plugin-sharp/src/index.js
D1 · partial-hydration-reference-loader.partialHydrationReferenceLoader (cyclomatic 40) packages/gatsby/src/utils/webpack/loaders/partial-hydration-reference-loader.ts
D1 · serve.default (cyclomatic 39) packages/gatsby/src/commands/serve.ts
D1 · getFieldTransformers (cyclomatic 39) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js
D1 · index.default (cyclomatic 37) packages/babel-plugin-remove-graphql-queries/src/index.ts
D1 · identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes (cyclomatic 37) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js
D1 · babel-plugin-remove-api.removeApiCalls (cyclomatic 36) packages/gatsby/src/utils/babel/babel-plugin-remove-api.ts
D1 · index.default (cyclomatic 35) packages/gatsby-remark-copy-linked-files/src/index.js
D1 · exports::generateImagesAndUpdateNode (cyclomatic 35) packages/gatsby-remark-images/src/index.js
D1 · exports (cyclomatic 35) packages/gatsby-remark-copy-linked-files/src/index.js
D1 · prepare-stack-trace.CallSiteToString (cyclomatic 34) packages/gatsby-cli/src/reporter/prepare-stack-trace.ts
D1 · gatsby-node.onCreateNode (cyclomatic 34) packages/gatsby-transformer-documentationjs/src/gatsby-node.js
D1 · print.printTypeDefinitions (cyclomatic 34) packages/gatsby/src/schema/print.ts
D1 · StaticQueryMapper.apply (cyclomatic 34) packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts
D1 · (anonymous) (cyclomatic 34) packages/gatsby/cache-dir/production-app.js
D1 · create-cli.buildLocalCommands (cyclomatic 33) packages/gatsby-cli/src/create-cli.ts
D1 · filter-using-index.resolveIndexFieldRanges (cyclomatic 33) packages/gatsby/src/datastore/lmdb/query/filter-using-index.ts
D1 · image-utils.generateImageData (cyclomatic 32) packages/gatsby-plugin-image/src/image-utils.ts
D1 · page-data.flush (cyclomatic 32) packages/gatsby/src/utils/page-data.ts
D1 · loadPage (cyclomatic 32) packages/gatsby/cache-dir/loader.js
D1 · watch.watch (cyclomatic 31) packages/gatsby-dev-cli/src/watch.js
D1 · resolve-module-exports.staticallyAnalyzeExports (cyclomatic 31) packages/gatsby/src/bootstrap/resolve-module-exports.ts
D1 · fetch-graphql.handleFetchErrors (cyclomatic 30) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts
D1 · validate.validatePluginsOptions (cyclomatic 29) packages/gatsby/src/bootstrap/load-plugins/validate.ts
D1 · manager.getRoutesManifest (cyclomatic 29) packages/gatsby/src/utils/adapter/manager.ts
D1 · GatsbyWebpackStatsExtractor.apply (cyclomatic 29) packages/gatsby/src/utils/gatsby-webpack-stats-extractor.ts
D1 · index.run (cyclomatic 27) packages/create-gatsby/src/index.ts
D1 · gatsby-image-resolver.gatsbyImageResolver (cyclomatic 26) packages/gatsby-plugin-utils/src/polyfill-remote-file/graphql/gatsby-image-resolver.ts
D1 · WorkerPool.startAll (cyclomatic 26) packages/gatsby-worker/src/index.ts
D1 · entry.getData (cyclomatic 25) packages/gatsby/src/utils/page-ssr-module/entry.ts
D1 · index.default (cyclomatic 24) packages/gatsby-remark-prismjs/src/index.js
D1 · fetch-nodes-paginated.paginatedWpNodeFetch (cyclomatic 24) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js
D1 · client-assets-for-template.getScriptsAndStylesForTemplate (cyclomatic 24) packages/gatsby/src/utils/client-assets-for-template.ts
D1 · exports (cyclomatic 24) packages/gatsby-remark-prismjs/src/index.js
D1 · normalize.getGatsbyImageCdnFields (cyclomatic 23) packages/gatsby-source-drupal/src/normalize.ts
D1 · PartialHydrationPlugin._generateManifest (cyclomatic 23) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts
D1 · bundle-webpack.createGraphqlEngineBundle (cyclomatic 23) packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts
D1 · index.initializeYurnalistLogger (cyclomatic 22) packages/gatsby-cli/src/reporter/loggers/yurnalist/index.ts
D1 · fetch-file.requestRemoteNode (cyclomatic 22) packages/gatsby-core-utils/src/remote-file-utils/fetch-file.ts
D1 · gatsby-ssr.onRenderBody (cyclomatic 22) REDACTED
D1 · index.fixed (cyclomatic 22) packages/gatsby-plugin-sharp/src/index.js
D1 · index.default (cyclomatic 22) packages/gatsby-remark-images-contentful/src/index.js
D1 · compile-gatsby-files.compileGatsbyFiles (cyclomatic 22) packages/gatsby/src/utils/parcel/compile-gatsby-files.ts
D1 · common.compareKey (cyclomatic 22) packages/gatsby/src/datastore/lmdb/query/common.ts
D1 · exports (cyclomatic 22) packages/gatsby-remark-images-contentful/src/index.js
D1 · placeholder.default (cyclomatic 21) packages/create-gatsby/src/components/placeholder.js
D1 · fetch-graphql.handleGraphQLErrors (cyclomatic 21) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts
D1 · check-plugin-requirements.areRemotePluginVersionsSatisfied (cyclomatic 21) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts
D1 · diff-schemas.checkIfSchemaHasChanged (cyclomatic 21) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js
D1 · node-manifest.findPageOwnedByNode (cyclomatic 21) packages/gatsby/src/utils/node-manifest.ts
D1 · route-handler.processRoutesManifest (cyclomatic 20) packages/gatsby-adapter-netlify/src/route-handler.ts
D1 · fetch-remote-file.fetchFile (cyclomatic 20) packages/gatsby-core-utils/src/fetch-remote-file.ts
D1 · check-deps-changes.checkDepsChanges (cyclomatic 20) packages/gatsby-dev-cli/src/utils/check-deps-changes.js
D1 · gatsby-node.createPagesStatefully (cyclomatic 20) packages/gatsby-plugin-page-creator/src/gatsby-node.ts
D1 · normalize.buildForeignReferenceMap (cyclomatic 20) packages/gatsby-source-contentful/src/normalize.js
D1 · inference-metadata.incrementalReducer (cyclomatic 20) packages/gatsby/src/redux/reducers/inference-metadata.ts
D1 · build-html.renderHTMLQueue (cyclomatic 20) packages/gatsby/src/commands/build-html.ts
D1 · schema.addConvenienceChildrenFields (cyclomatic 20) packages/gatsby/src/schema/schema.js
D1 · ssr-develop-static-entry.staticPage (cyclomatic 20) REDACTED
D1 · makeManifest (cyclomatic 20) packages/gatsby-plugin-manifest/src/gatsby-node.js
D1 · image-utils.setDefaultDimensions (cyclomatic 19) packages/gatsby-plugin-image/src/image-utils.ts
D1 · utils.handleReferences (cyclomatic 19) packages/gatsby-source-drupal/src/utils.ts
D1 · create-local-file-node.errorPanicker (cyclomatic 19) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js
D1 · create-local-file-node.createLocalFileNode (cyclomatic 19) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js
D1 · inference-metadata.updateValueDescriptor (cyclomatic 19) packages/gatsby/src/schema/infer/inference-metadata.ts
D1 · node-model.getQueryFields (cyclomatic 19) packages/gatsby/src/schema/node-model.js
D1 · manager.initAdapterManager (cyclomatic 19) packages/gatsby/src/utils/adapter/manager.ts
D1 · static-entry.staticPage (cyclomatic 19) REDACTED
D1 · bundle-webpack.createPageSSRBundle (cyclomatic 19) packages/gatsby/src/utils/page-ssr-module/bundle-webpack.ts
D1 · FormInput.renderChoice (cyclomatic 18) packages/create-gatsby/src/components/form.js
D1 · index.createNetlifyAdapter (cyclomatic 18) packages/gatsby-adapter-netlify/src/index.ts
D1 · gatsby-plugin-image.updateImport (cyclomatic 18) packages/gatsby-codemods/src/transforms/gatsby-plugin-image.js
D1 · process-file.processFile (cyclomatic 18) packages/gatsby-plugin-sharp/src/process-file.ts
D1 · index.default (cyclomatic 18) packages/gatsby-remark-code-repls/src/index.js
D1 · process-bulk-results.processBulkResults (cyclomatic 18) packages/gatsby-source-shopify/src/process-bulk-results.ts
D1 · update.wpActionUPDATE (cyclomatic 18) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js
D1 · add-inferred-fields.getSimpleFieldConfig (cyclomatic 18) packages/gatsby/src/schema/infer/add-inferred-fields.js
D1 · schema.mergeTypes (cyclomatic 18) packages/gatsby/src/schema/schema.js
D1 · schema.addExtensions (cyclomatic 18) packages/gatsby/src/schema/schema.js
D1 · public.createNode (cyclomatic 18) packages/gatsby/src/redux/actions/public.js
D1 · resolvers.link (cyclomatic 18) packages/gatsby/src/schema/resolvers.ts
D1 · exports (cyclomatic 18) packages/gatsby-remark-code-repls/src/index.js
D1 · index.OutboundLink (cyclomatic 17) packages/gatsby-plugin-google-analytics/src/index.js

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Rebuild cost & value ~ Modeled — €71,000–€350,000

Cost to rebuild	€71,000–€350,000 (0.7–2.2 person-years (1,175–3,728 h), ~1–3 engineers)
Domain complexity	Standard — harder problems cost more per line
Quality factor	0.7× (at 49% quality) — the last 20% of quality is most of the work
Size & shape	Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~1.5 person-years of build effort (about ~€210,000 to rebuild). Its weakest lens is Readiness at 43% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.1) — vertical slice × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 1 Banned license finding(s) in License Compliance.

+3.6 pts · Low effort · License Compliance

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.

+6.5 pts · REDACTED effort · Security & performance tooling

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

+6.5 pts · REDACTED effort · Dependency Hygiene

Diagnosis — what's actually going on

Value concentrated against a weak lens · REDACTED · Value at risk

This is a Large asset (~1.5 person-years to rebuild), and its weakest lens is Readiness at 43%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: Large, ~1.5 person-years rebuild (130,330 LoC) · weakest lens: Readiness 43%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

A velocity tax on every change · REDACTED · Economics

The code-quality signals (complexity, duplication, cohesion) average 3.0/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 13–28% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)

Evidence: D1/D2 code quality: averaging 3.0/10 across the code-quality signals actually measured

→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.

The top fix pays for itself · REDACTED · Economics

The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 0.4–2.5 engineer-days every year, paid as drag on the ~1,342 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 5–85 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 13–28% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.

Evidence: D15 churn: 331 line(s) changed over a 90-day window ⇒ ~1,342/year · D1/D2 code quality: averaging 3.0/10 ⇒ a 13–28% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)

→ Do the top-ranked fix now if this code will still be yours in 85 months.

Highest-leverage move · REDACTED · Leverage

Of everything flagged, the best return on effort is: 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. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

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

Architecture — module dependency matrix

Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)

1333 modules, 383 dependencies. Every dependency points down the layering — no cycles.

Showing the 40 most-connected modules; 1293 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 benchmarks.gabe-csv-markdown.src.components.layout	2 deprecated-packages.gatsby-telemetry.src.store	4 packages.gatsby-cli.src.reporter.constants	5 packages.gatsby-cli.src.reporter.types	6 packages.gatsby-page-utils.src.apply-trailing-slash-option	7 packages.gatsby-plugin-utils.src.types	8 packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type	10 packages.gatsby.src.datastore.common.iterable	11 packages.gatsby.src.datastore.common.query	12 packages.gatsby.src.schema.type-definitions	13 packages.gatsby-cli.src.reporter.redux.types	14 packages.gatsby-cli.src.reporter.reporter	15 packages.gatsby-plugin-image.src.components.gatsby-image_browser	16 packages.gatsby-plugin-image.src.image-utils	20 packages.gatsby.src.utils.cache	21 packages.gatsby-plugin-image.src.components.hooks	25 packages.gatsby.src.commands.types	26 packages.gatsby.src.redux.types	30 packages.gatsby.src.datastore.types	31 packages.gatsby.src.query.graphql-runner	36 packages.gatsby.src.services.types
1 benchmarks.gabe-csv-markdown.src.components.layout
2 deprecated-packages.gatsby-telemetry.src.store
3 packages.gatsby-cli.src.reporter
4 packages.gatsby-cli.src.reporter.constants
5 packages.gatsby-cli.src.reporter.types
6 packages.gatsby-page-utils.src.apply-trailing-slash-option
7 packages.gatsby-plugin-utils.src.types
8 packages.gatsby-plugin-utils.src.utils.plugin-options-schema-joi-type
9 packages.gatsby-source-shopify.src.query-builders.bulk-query
10 packages.gatsby.src.datastore.common.iterable
11 packages.gatsby.src.datastore.common.query
12 packages.gatsby.src.schema.type-definitions
13 packages.gatsby-cli.src.reporter.redux.types			2	1
14 packages.gatsby-cli.src.reporter.reporter			1	2
15 packages.gatsby-plugin-image.src.components.gatsby-image_browser	1
16 packages.gatsby-plugin-image.src.image-utils	3
17 packages.gatsby-plugin-utils.src		1	1			2	1
18 packages.gatsby-source-wordpress.src.utils							1
19 packages.gatsby.src.schema.types							1			1
20 packages.gatsby.src.utils.cache		2
21 packages.gatsby-plugin-image.src.components.hooks	1												1	2
22 packages.gatsby-plugin-page-creator.src			3		2							5
23 packages.gatsby-plugin-sharp.src														2	1
24 packages.gatsby-plugin-utils.src.polyfill-remote-file.graphql		3	3											2
25 packages.gatsby.src.commands.types												1
26 packages.gatsby.src.redux.types				7	1						2
27 packages.gatsby-source-shopify.src													1		1	1
28 packages.gatsby.src.bootstrap		1		2								1						2
29 packages.gatsby.src.commands											1						7	1
30 packages.gatsby.src.datastore.types								2										3
31 packages.gatsby.src.query.graphql-runner		1								1								1
32 packages.gatsby.src.datastore.in-memory								1	6									2	3
33 packages.gatsby.src.datastore.lmdb.query								2	7									2	1
34 packages.gatsby.src.query																				1
35 packages.gatsby.src.schema										4								1	1
36 packages.gatsby.src.services.types		1		1								1					1	1		1
37 packages.gatsby.src.state-machines.data-layer.types		1										1					1	1		1
38 packages.gatsby.src.state-machines.query-running.types		1										1					1	1		1	1
39 packages.gatsby.src.utils		2		5				1				1			1		4	9			1
40 packages.gatsby.src.utils.worker.child																				1	1

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

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

The Good

D17 · JavaScript Explicit Debt 9.6 R1 · React / TS Type Safety 10.0 R10 · React / TS Code Duplication 9.5 R2 · React / TS Cyclomatic Complexity 8.0 R3 · React / TS Large Files 7.8

The Bad

D3 · JavaScript God Classes 6.5 R7 · React / TS Dead Code 5.1

The Ugly

D1 · JavaScript Cyclomatic Complexity 3.9 D2 · JavaScript Cognitive Complexity 2.0

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

The Good

D35 · JavaScript Change Coupling 10.0 AX10 · Repo Code composition 9.8 AX5 · Repo Architecture & structure 10.0 AX7 · Repo Slice cohesion 10.0

The Bad

R11 · React / TS Import Boundaries 6.0

The Ugly

R9 · React / TS Circular Imports 0.0

At a glance — Maturity · 73% · Adequate · gated by D34 ·

The Good

D15 · JavaScript Churn × Complexity Hotspots 9.8 D16 · JavaScript Bus Factor 9.8 D19 · JavaScript Documentation Quality 8.8 D21 · JavaScript Naming Consistency 10.0 M1 · Repo Documentation (README) 7.5 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M2 · Repo Architecture documentation 5.0

The Ugly

D20 · JavaScript ADR Quality 0.0 D34 · JavaScript Knowledge Freshness 2.7

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

The Good

D9 · JavaScript Test Distribution 9.7 D10 · JavaScript Test Quality 9.8 D11 · JavaScript Test Reliability 10.0 D13 · JavaScript REDACTED Scanning 10.0 D14 · JavaScript License Compliance 8.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 7.4 R5 · React / TS Dependency Freshness 9.7 R6 · React / TS Tooling 10.0

The Bad

D12 · JavaScript Dependency Hygiene 6.0

The Ugly

P3 · Repo Security & performance tooling 0.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 48% · Weak · gated by D28, D29, D30, D36 ·

The Good

D31 · JavaScript IaC & Container Security 9.0 D37 · JavaScript Vulnerability-disclosure Policy 10.0 D43 · JavaScript Malicious Dependencies 10.0

The Ugly

D28 · JavaScript Secrets (history) 2.0 D29 · JavaScript Static Analysis (SAST) 0.1 D30 · JavaScript Dependency Vulnerabilities 0.0 D36 · JavaScript Supply-chain Provenance & Signing 2.5

At a glance — Accessibility · 58% · Adequate · gated by AC2 ·

The Good

AC5 · Repo ARIA correctness 10.0 AC6 · Repo Visual & motion safety 10.0 AC7 · Repo A11y enforcement 8.0

The Bad

AC3 · Repo Page structure 5.2

The Ugly

AC1 · Repo Text alternatives 4.5 AC2 · Repo Forms & labels 3.8

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A06:2021 — Vulnerable & Outdated Components	187	REDACTED / Critical
A03:2021 — Injection	43	REDACTED / Critical
A02:2021 — Cryptographic Failures	9	REDACTED / Critical
A05:2021 — Security Misconfiguration	6	REDACTED / Critical

Roadmap

First, integrate static analysis into the CI pipeline to block security regressions before they land. Next, clean up the dependency tree by removing unused packages, explicitly declaring imports, and resolving floating version warnings. Then, expand test coverage to include currently unreached production modules. Finally, implement a draft release or manual gate to prevent bad builds from reaching users.

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

Do this	Helps	Effort	Dimension
Resolve the 1 Banned license finding(s) in License Compliance.	+3.6 pts	Low	License Compliance
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.	+6.5 pts	REDACTED	Security & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+6.5 pts	REDACTED	Dependency Hygiene
Resolve the 93 Floating npm dependency finding(s) in Dependency Hygiene.	+5.9 pts	REDACTED	Dependency Hygiene
Add tests that import the unreached modules (directly or through their public entry).	+5.7 pts	REDACTED	Test Coverage
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.	+5.3 pts	REDACTED	Deployment & Rollback
Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED.	+2.5 pts	Low	Secrets (history)
Resolve the 22 One package at two majors across the workspace finding(s) in Dependency Hygiene.	+3.0 pts	REDACTED	Dependency Hygiene

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	1.1	Slop	Dependency Vulnerabilities: REDACTED CVE: REDACTED
REDACTED	2.1	Slop	Dependency Vulnerabilities: REDACTED CVE: REDACTED
REDACTED	4.0	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.1	Mixed	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.8	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	4.8	Mixed	Dependency Vulnerabilities: REDACTED CVE: REDACTED
REDACTED	5.0	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: REDACTED IaC: REDACTED
REDACTED	5.1	Mixed	IaC & Container Security: REDACTED IaC: REDACTED
REDACTED	5.3	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	5.4	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	5.7	Mixed	Static Analysis (SAST): REDACTED: REDACTED
REDACTED	5.7	Mixed	Static Analysis (SAST): REDACTED: REDACTED

How the grades work

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

Critical — 195

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

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

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

Could not be resolved — 48

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

Methodology & how to trust this report

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

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

What we checked — 52 dimensions across the health lenses

D1D2D3D9D10D11D12D13D14D15D16D17D19D20D21D28D29D30D31D34D35D36D37D43AC1AC2AC3AC5AC6AC7AX10AX5AX7M1M2M3M4P1P3P4P6R1R10R11R2R3R4R5R6R7R8R9

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, 1232 of 1634 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0d84b-62fc-7fd0-9be4-488c567e87a2.

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

Run transparency — what happened this run

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

D4 Code Duplication — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.php) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load. Duplication in .ts, .tsx is measured by R10 Code Duplication and is not part of this gap.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .ts, and our analyzer cannot run the .ts test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 85.9% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. In the meantime, produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures and real coverage will be read. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then both halves are read on the next scan.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: D22 has no public-API collector for any other ecosystem, and the remedy is to write one — no change to the scan image can close it.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/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.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a REDACTED) is simply not read here yet.
AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM1 Aggregate boundaries — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: a class holding another class reads the same whether the inner type is an aggregate or a value object, so this cannot be decided from source without guessing — reported as guidance rather than measured.
DM2 Strongly-typed ids — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: branded ids (`type Id = string & { __brand }`) are an uncommon idiom, so a bare-string id is not on its own evidence of a missing typed id — reported as guidance rather than measured.
DM3 Integration-event coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: a domain type used across packages is indistinguishable in source from a deliberate shared-kernel package, so this is reported as guidance rather than measured.
DM4 Rich vs anemic model — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: telling a rich domain entity from an anemic data holder needs the behaviour a source-only read cannot always attribute (components, DTOs and readonly value objects are all legitimately data-shaped), so this is reported as guidance rather than measured.
DM5 Encapsulated state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: the language already steers state behind #private/private/readonly, so a mutable public field is rare enough that we report this as guidance rather than measuring it.
DM7 Repository granularity — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored for TypeScript: deciding whether a repository belongs to an aggregate root needs the aggregate structure, which source alone does not state — reported as guidance rather than measured.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 104 further occurrence(s) are not listed individually; the score already reflects all 144.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 284 further occurrence(s) are not listed individually; the score already reflects all 324.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 166 further occurrence(s) are not listed individually; the score already reflects all 206.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

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

Dimensions

D1 · Cyclomatic Complexity3.9 / 10Weak✓ Tool-verified

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

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

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

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

exports (cyclomatic 107)packages/gatsby/src/utils/webpack.config.js:46

html.htmlReducer (cyclomatic 77)packages/gatsby/src/redux/reducers/html.ts:35

start-server.startServer (cyclomatic 74)REDACTED:67

gatsby-node.sourceNodes (cyclomatic 70)packages/gatsby-source-drupal/src/gatsby-node.ts:143

index.default (cyclomatic 68)packages/gatsby-remark-images/src/index.js:37

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

What to do

Resolve the 1 exports (cyclomatic 107) finding(s) in Cyclomatic Complexity — start with webpack.config.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 html.htmlReducer (cyclomatic 77) finding(s) in Cyclomatic Complexity — start with html.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 start-server.startServer (cyclomatic 74) finding(s) in Cyclomatic Complexity — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

258 method(s) exceeded the cognitive complexity threshold of 15; the worst was html.htmlReducer at 167.

exports::generateImagesAndUpdateNode (cognitive 37) · ×2packages/gatsby-remark-images/src/index.js:139

index.default (cognitive 26) · ×2packages/gatsby-remark-code-repls/src/index.js:41

exports (cognitive 26) · ×2packages/gatsby-remark-code-repls/src/index.js:41

html.htmlReducer (cognitive 167)packages/gatsby/src/redux/reducers/html.ts:35

start-server.startServer (cognitive 139)REDACTED:67

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

What to do

Resolve the 2 exports finding(s) in Cognitive Complexity — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 index.default (cognitive 26) finding(s) in Cognitive Complexity — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 exports (cognitive 26) finding(s) in Cognitive Complexity — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes6.5 / 10Adequate✓ Tool-verified

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

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

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

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

FunctionTooLong: declare-plugin-options-schema.pluginOptionsSchema · ×34packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js:23

FileTooLong: redux/types.ts · ×21packages/gatsby/src/redux/types.ts

MethodTooLong: StaticQueryMapper.apply · ×4packages/gatsby/src/utils/webpack/plugins/static-query-mapper.ts:71

What to do

Resolve the 34 FunctionTooLong finding(s) in God Classes — start with index.ts (2), bundle-webpack.ts (2), manager.ts (2). — One of this dimension's main actionable groups (34 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 4 MethodTooLong finding(s) in God Classes — start with static-query-mapper.ts, loader.js, raw_dev-404-page.js. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution9.7 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.8 / 10Stronggated by 38 serious findings✓ Tool-verified

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

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

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

130 skipped (130 with a documented reason), 75 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3661 tests (2 harness-style project(s) excluded from the assertion penalty).

No assertions: e2e plugin resource test · ×38deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js:37

No direct assertions: Visits the index page and navigates · ×37examples/using-cypress/cypress/e2e/smoke.cy.ts:2

Skipped (documented): validate returns a syntax error · ×130deprecated-packages/gatsby-recipes/src/parser/validate.test.js:14

What to do

Resolve the 38 No assertions finding(s) in Test Quality — start with home-page-spec.js (5), REDACTED (5), trailing-slash.cy.ts (4). — One of this dimension's main actionable groups (38 warning-level).
Resolve the 37 No direct assertions finding(s) in Test Quality — start with cache.js (34), accessibility.cy.ts (2), smoke.cy.ts. — One of this dimension's main actionable groups (37 recommendation-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene6.0 / 10Adequate✓ Tool-verified

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

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

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

272 outdated direct production npm dependency(ies) of 382 graded, 115 pinning defect(s), across 272 package.json (158 of them the product) and 8 committed lockfile(s). Development dependencies are deliberately not graded: this dimension grades what SHIPS. Whether any of these packages is DEPRECATED or UNMAINTAINED is not graded — registry.npmjs.org's latest-version answer carries neither, and release age does not stand in for a maintenance status. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Floating npm dependency: gatsby · ×93

One package at two majors across the workspace: @graphql-tools/utils · ×22

Outdated (npm): @apollo/client · ×272

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 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).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

1 of 382 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 382 production dependency(ies) this repository's committed lockfile resolves, across 158 product package.json manifest(s). Its 1101 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 4 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. This repository publishes itself under 0BSD / ISC / MIT, which is its own choice and is not judged here.

Banned license: @wordpress/block-library

What to do

Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

Top hotspots: packages/gatsby/src/utils/page-ssr-module/lambda.ts (2×16=32)

Hotspot: packages/gatsby/src/utils/page-ssr-module/lambda.tspackages/gatsby/src/utils/page-ssr-module/lambda.ts:33

What to do

Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with lambda.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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: 685 are under the ~2,400-byte size floor this dimension measures over, and the remaining 20 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.

Do you agree with this assessment?

D17 · Explicit Debt9.6 / 10Stronggated by 153 serious findings✓ Tool-verified

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

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

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

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.

TodoComment · ×136packages/gatsby-adapter-netlify/src/route-handler.ts:177

FixmeComment · ×14packages/gatsby-cli/src/reporter/start-logger.ts:21

HackComment · ×2packages/gatsby-cli/src/reporter/catch-exit-signals.ts:25

XxxCommentpackages/gatsby/src/schema/types/sort.ts:85

What to do

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), start-logger.ts. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with catch-exit-signals.ts, scroll-handler.tsx. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

Gatsby's documentation is clear and complete for a framework. The README gives an excellent overview (what it does, the Gatsby logo, license badge, PRs welcome), links to quickstart, tutorial, plugins, starters, showcase, and release notes; architecture/Docs markdown files cover the monorepo changelog generator, gatsby-worker utility, YAML, XML, TOML, and SQIP plugins with full usage, options, and troubleshooting. The README is clipped mid-document but the outline lists every visible section. The documentation is excellent for Gatsby plugin transformers covering the core use cases of parsing Markdown (remark), JSON (json), HJSON (hjson), Excel (excel), CSV (csv), and a dedicated Documentation.js extractor. Each file provides install, usage examples, options, a parsing algorithm explanation, and queries with live demo links, while architecture/design docs are kept separate for the transformer libraries. The internal jargon is consistent across all files. The documentation is clear and complete for the gatsby-source-*** plugins (each README has install, usage examples, a Getting started section with Configure/Install/Retrieving API Information from Shopify sub-sections, and an outline of all the documented topics), but it lacks an overview of what each plugin does and no architecture/design docs. The READMEs are well written for consumers.

Documentation: no installation or build instructions · ×2README.md

What to do

Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).

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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)2.0 / 10Critical✓ Tool-verified

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 REDACTED. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED

What to do

Resolve the 8 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 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.

Do you agree with this assessment?

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

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

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

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

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

43 finding(s): 0 critical, 23 high, 20 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

What to do

Resolve the 20 REDACTED finding(s) charged to Static Analysis (SAST) — the other 3 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (23 issue-level, 20 of them charged here).
Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (20 warning-level).

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

Do you agree with this assessment?

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

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/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, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

187 finding(s): 13 critical, 110 high, 47 medium, 17 low.

REDACTED

What to do

Resolve the 107 REDACTED CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (77), REDACTED (30). — One of this dimension's main actionable groups (107 issue-level).
Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11), REDACTED (2). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 3 REDACTED vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security9.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

Resolve the 2 REDACTED 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 REDACTED 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.

Do you agree with this assessment?

D34 · Knowledge Freshness2.7 / 10Weak✓ Tool-verified

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

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

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

310 of 424 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 424 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

Concentrated knowledge decay

What to do

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.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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.

Do you agree with this assessment?

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

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

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

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

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — deprecated-packages/gatsby-admin/src/components/layout.tsx:15, 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.

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

AC7 · A11y enforcement8.0 / 10Strong✓ Tool-verified

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

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

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

Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 35 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Accessibility linting is already configured — run the suite that already asserts accessibility in CI so a regression blocks the merge.

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX7 · Slice cohesion10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

Do you agree with this assessment?

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

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 90 of 355 project(s) that lack one — worth up to 0.5 pts.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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

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

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

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

What to do

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

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.

Do you agree with this assessment?

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

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

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

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.

Do you agree with this assessment?

R10 · Code Duplication9.5 / 10Exemplary✓ Tool-verified

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

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

43 duplicated blocks under packages/ have copies in at least two of the sibling directories create-gatsby, gatsby, gatsby-codemods, gatsby-core-utils, gatsby-plugin-emotion, gatsby-plugin-google-analytics (+24 more sibling(s) not listed) — 28 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 43 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 43 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 43 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
8 duplicated blocks under packages/gatsby/src/ have copies in at least two of the sibling directories bootstrap, commands, internal-plugins, schema, services, state-machines (+1 more sibling(s) not listed) — 6 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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
packages/gatsby/src/commands/serve.ts:215 · packages/gatsby/src/commands/serve.ts: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. — packages/gatsby/src/commands/serve.ts: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.

Do you agree with this assessment?

R11 · Import Boundaries6.0 / 10Adequate✓ Tool-verified

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

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

.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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — packages/gatsby/src/commands/build-html.ts:306
packages/gatsby/src/commands/serve.ts:25 reaches into another package with a relative path (../internal-plugins/functions/middleware) — import the package by name instead. — packages/gatsby/src/commands/serve.ts:25
packages/gatsby/src/commands/serve.ts:26 reaches into another package with a relative path (../internal-plugins/partytown/proxy) — import the package by name instead. — packages/gatsby/src/commands/serve.ts: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
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
packages/gatsby/src/internal-plugins/load-babel-config/gatsby-node.js:6 reaches into another package with a relative path (../../utils/path) — import the package by name instead. — packages/gatsby/src/internal-plugins/load-babel-config/gatsby-node.js:6

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 (38 rows); declare the workspace packages these files import in the importing package's own package.json 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).

Do you agree with this assessment?

R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

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

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

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

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

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.

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

deprecated-packages/gatsby-recipes/src/create-types.test.js:1 imports './create-types', 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. — deprecated-packages/gatsby-recipes/src/create-types.test.js
deprecated-packages/gatsby-recipes/src/parser/validate.test.js:1 imports './validate', 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. — deprecated-packages/gatsby-recipes/src/parser/validate.test.js
deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js:1 imports './directory', 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. — deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js
deprecated-packages/gatsby-recipes/src/providers/fs/file.test.js:2 imports '../resource-schema', 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. — deprecated-packages/gatsby-recipes/src/providers/fs/file.test.js
deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.test.js:4 imports '../resource-schema', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (3 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. — deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.test.js
deprecated-packages/gatsby-recipes/src/providers/gatsby/shadow-file.test.js:4 imports '../../test-helper', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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. — deprecated-packages/gatsby-recipes/src/providers/gatsby/shadow-file.test.js
deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js:5 imports './site-metadata', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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. — deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js
deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/build-plugin-node.test.js:3 imports './build-plugin-node', 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. — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/build-plugin-node.test.js
deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/get-object-from-node.test.js:3 imports './get-object-from-node', 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. — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/get-object-from-node.test.js
deprecated-packages/gatsby-recipes/src/providers/git/ignore.test.js:2 imports './ignore', 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. — deprecated-packages/gatsby-recipes/src/providers/git/ignore.test.js
deprecated-packages/gatsby-recipes/src/providers/npm/package-json.test.js:3 imports './package-json', 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. — deprecated-packages/gatsby-recipes/src/providers/npm/package-json.test.js
deprecated-packages/gatsby-recipes/src/providers/npm/package.test.js:6 imports './package', 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. — deprecated-packages/gatsby-recipes/src/providers/npm/package.test.js
deprecated-packages/gatsby-recipes/src/providers/npm/script.test.js:3 imports './script', 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. — deprecated-packages/gatsby-recipes/src/providers/npm/script.test.js
deprecated-packages/gatsby-recipes/src/providers/utils/get-diff.test.js:1 imports './get-diff', 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. — deprecated-packages/gatsby-recipes/src/providers/utils/get-diff.test.js
deprecated-packages/gatsby-recipes/src/providers/utils/get-graphql-fields.test.js:1 imports './get-graphql-fields', 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. — deprecated-packages/gatsby-recipes/src/providers/utils/get-graphql-fields.test.js
deprecated-packages/gatsby-recipes/src/renderer/index.test.js:2 imports '../parser', 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. — deprecated-packages/gatsby-recipes/src/renderer/index.test.js
deprecated-packages/gatsby-recipes/src/renderer/render.test.js:3 imports './render', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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. — deprecated-packages/gatsby-recipes/src/renderer/render.test.js
deprecated-packages/gatsby-recipes/src/renderer/transform-to-plan-structure.test.js:1 imports './transform-to-plan-structure', 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. — deprecated-packages/gatsby-recipes/src/renderer/transform-to-plan-structure.test.js
deprecated-packages/gatsby-recipes/src/validate-recipe.test.js:1 imports './validate-recipe', 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. — deprecated-packages/gatsby-recipes/src/validate-recipe.test.js
e2e-tests/adapters/cypress/e2e-netlify/cdn-caching.cy.ts:1 imports '../../utils', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e-tests/adapters/cypress/e2e-netlify/cdn-caching.cy.ts
e2e-tests/adapters/cypress/e2e/basics.cy.ts:1 imports '../../constants', 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. — e2e-tests/adapters/cypress/e2e/basics.cy.ts
e2e-tests/adapters/cypress/e2e/dsg.cy.ts:1 imports '../../constants', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e-tests/adapters/cypress/e2e/dsg.cy.ts
e2e-tests/adapters/cypress/e2e/headers.cy.ts:1 imports '../../utils', 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. — e2e-tests/adapters/cypress/e2e/headers.cy.ts
e2e-tests/adapters/cypress/e2e/redirects.cy.ts:1 imports '../../utils', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e-tests/adapters/cypress/e2e/redirects.cy.ts
e2e-tests/adapters/cypress/e2e/slices.cy.ts:1 imports '../../constants', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — e2e-tests/adapters/cypress/e2e/slices.cy.ts
e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts:1 imports '../utils/assert-page-visits', 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. — e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts
packages/gatsby-remark-prismjs/src/__tests__/directives.js:3 imports './fixtures', 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-remark-prismjs/src/__tests__/directives.js
packages/gatsby-source-wordpress/__tests__/docs-generation.test.js:1 imports '../generate-plugin-options-docs', 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-source-wordpress/__tests__/docs-generation.test.js
packages/gatsby-source-wordpress/__tests__/process-node.test.js:86 imports './fixtures/media', 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-source-wordpress/__tests__/process-node.test.js
packages/gatsby-worker/src/__tests__/integration.ts:4 imports './fixtures/test-child', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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-worker/src/__tests__/integration.ts
packages/gatsby/src/bootstrap/load-plugins/__tests__/load-plugins.ts:548 imports './fixtures/local-plugin', 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/bootstrap/load-plugins/__tests__/load-plugins.ts
packages/gatsby/src/bootstrap/load-themes/__tests__/index.js:27 imports './fixtures/resolve-from-config-location/gatsby-config', 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/bootstrap/load-themes/__tests__/index.js
packages/gatsby/src/schema/__tests__/build-schema.js:34 imports './fixtures/node-model', 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/schema/__tests__/build-schema.js
packages/gatsby/src/schema/__tests__/node-model.js:7 imports './fixtures/node-model', 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/schema/__tests__/node-model.js
packages/gatsby/src/schema/__tests__/queries.js:23 imports './fixtures/queries', 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/schema/__tests__/queries.js
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
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
packages/gatsby/src/utils/adapter/__tests__/manager.ts:7 imports './fixtures/state', 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/adapter/__tests__/manager.ts
packages/gatsby/src/utils/parcel/__tests__/compile-gatsby-files.ts:9 imports './fixtures/utils/site-metadata', 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/utils/parcel/__tests__/compile-gatsby-files.ts
peril/tests/emptybody.test.ts:5 imports '../rules/emptybody', 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/emptybody.test.ts

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness9.7 / 10Exemplary✓ Tool-verified

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

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

What to do

Bump outdated dependencies to current versions to limit upgrade debt.

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 package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

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

This repository declares test tooling, and the ✓ above records that declaration — but deprecated-packages/gatsby-recipes/src/create-types.test.js and 46 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. — deprecated-packages/gatsby-recipes/src/create-types.test.js

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. — e2e-tests/development-runtime
Unreachable from the 269 application, 49 tooling and 471 test entry point(s) detected in this repo. Gate removals on `yarn run typecheck` — an undetected custom entry would make these reachable.
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js, packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/content-update-interval.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 13 in-repo import(s) from 13 other file(s) do name it (packages/gatsby-source-wordpress/src/hooks/node-filters.ts, packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js and 10 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/gatsby-source-wordpress/src/models/image-nodes.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×9) — packages/gatsby/src/internal-plugins/functions/gatsby-node.ts, packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js, packages/gatsby-plugin-sharp/src/gatsby-node.js, …
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 27 in-repo import(s) from 21 other file(s) do name it (packages/gatsby-source-wordpress/src/models/remoteSchema.ts, packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js and 18 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/create-schema-customization/helpers.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/gatsby-source-wordpress/src/models/develop.ts, packages/gatsby-source-wordpress/src/models/gatsby-api.ts, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/transform-object.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/preview/index.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/transform-object.js, packages/gatsby-source-wordpress/src/steps/preview/index.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 14 in-repo import(s) from 14 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/cache-fetched-types.js and 11 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/utils/cache.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/models/gatsby-api.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (packages/gatsby-source-wordpress/src/models/index.ts, packages/gatsby-source-wordpress/src/models/logger.ts, packages/gatsby-source-wordpress/src/steps/auth-handling.ts and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/models/gatsby-api.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-node-queries.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-query-on-field-name.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/fetch-and-create-non-node-root-fields.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/set-gatsby-api-to-state.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/process-and-validate-plugin-options.ts
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/preview/index.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js, packages/gatsby-source-wordpress/src/steps/preview/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/introspect-remote-schema.js
no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/models/index.ts, packages/gatsby-source-wordpress/src/steps/preview/cleanup.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/gatsby-source-wordpress/src/models/preview.ts

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×20) — packages/babel-preset-gatsby/src/optimize-hook-destructuring.ts:2, packages/create-gatsby/src/components/form.js:3, packages/create-gatsby/src/utils/get-config-store.ts:1, …
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. (×5) — 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, …
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
Every import is type-only — move it to devDependencies. — packages/gatsby/src/utils/graphql-typegen/ts-codegen.ts:5
Only test files import it — move it to devDependencies. — deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js:3

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports0.0 / 10Critical✓ Tool-verified

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

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

packages/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
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
packages/gatsby-plugin-image/src/node-apis/image-processing.ts → packages/gatsby-plugin-image/src/node-apis/watcher.ts → packages/gatsby-plugin-image/src/node-apis/image-processing.ts — packages/gatsby-plugin-image/src/node-apis/image-processing.ts
packages/gatsby-plugin-sharp/src/image-data.ts → packages/gatsby-plugin-sharp/src/index.js → packages/gatsby-plugin-sharp/src/image-data.ts — packages/gatsby-plugin-sharp/src/image-data.ts
packages/gatsby-source-wordpress/src/models/develop.ts → packages/gatsby-source-wordpress/src/models/index.ts → packages/gatsby-source-wordpress/src/models/develop.ts (one verified cycle inside a mutually-dependent group of 31 files) — packages/gatsby-source-wordpress/src/models/develop.ts
packages/gatsby/cache-dir/gatsby-browser-entry.js → packages/gatsby/cache-dir/public-page-renderer.js → packages/gatsby/cache-dir/public-page-renderer-dev.js → packages/gatsby/cache-dir/query-result-store.js → packages/gatsby/cache-dir/gatsby-browser-entry.js (one verified cycle inside a mutually-dependent group of 7 files) — packages/gatsby/cache-dir/gatsby-browser-entry.js
packages/gatsby/src/datastore/index.ts → packages/gatsby/src/datastore/datastore.ts → packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts → packages/gatsby/src/datastore/in-memory/run-fast-filters.ts → packages/gatsby/src/datastore/in-memory/indexing.ts → packages/gatsby/src/datastore/index.ts (one verified cycle inside a mutually-dependent group of 113 files) — packages/gatsby/src/datastore/index.ts
packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts → packages/gatsby/src/bootstrap/load-plugins/validate.ts → packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts — packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts
packages/gatsby/src/utils/parcel/compile-gatsby-files.ts → packages/gatsby/src/utils/parcel/compile-gatsby-files.ts — packages/gatsby/src/utils/parcel/compile-gatsby-files.ts

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

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

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	66%	Adequate — gated by D1, D2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	60%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	73%	Adequate — gated by D34	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	43%	Weak — gated by R8, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	48%	Weak — gated by D28, D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	58%	Adequate — gated by AC2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not evidenced — 4 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.

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 77 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 — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
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.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — Production source is present (.php, .ts, .tsx) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — 9 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — Duplication not measured — .php not exposed to the token comparison
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is .php, .ts, .tsx, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Aggregate boundaries — not scored for TypeScript: a class holding another class reads the same whether the inner type is an aggregate or a value object, so this cannot be decided from source without guessing — reported as guidance rather than measured
DM2 Strongly-typed ids — not scored for TypeScript: branded ids (`type Id = string & { __brand }`) are an uncommon idiom, so a bare-string id is not on its own evidence of a missing typed id — reported as guidance rather than measured
DM3 Integration-event coupling — not scored for TypeScript: a domain type used across packages is indistinguishable in source from a deliberate shared-kernel package, so this is reported as guidance rather than measured
DM4 Rich vs anemic model — not scored for TypeScript: telling a rich domain entity from an anemic data holder needs the behaviour a source-only read cannot always attribute (components, DTOs and readonly value objects are all legitimately data-shaped), so this is reported as guidance rather than measured
DM5 Encapsulated state — not scored for TypeScript: the language already steers state behind #private/private/readonly, so a mutable public field is rare enough that we report this as guidance rather than measuring it
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not scored for TypeScript: deciding whether a repository belongs to an aggregate root needs the aggregate structure, which source alone does not state — reported as guidance rather than measured
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — 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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
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 — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — 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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 195 finding(s)

D30 · Dependency Vulnerabilities · REDACTED CVE · ×107

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 82 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED · ×23

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×13

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import 'react' · ×5

Unlisted import 'react' packages/gatsby-plugin-canonical-urls/src/gatsby-ssr.js:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react' REDACTED:1 — Imported but not declared in any reachable package.json — 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 package.json — 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 package.json — 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 package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (2 files) · ×5

Import cycle (2 files) packages/gatsby-adapter-netlify/src/file-cdn-handler.ts — 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)
Import cycle (2 files) packages/gatsby-plugin-image/src/node-apis/image-processing.ts — packages/gatsby-plugin-image/src/node-apis/image-processing.ts → packages/gatsby-plugin-image/src/node-apis/watcher.ts → packages/gatsby-plugin-image/src/node-apis/image-processing.ts
Import cycle (2 files) packages/gatsby-plugin-sharp/src/image-data.ts — packages/gatsby-plugin-sharp/src/image-data.ts → packages/gatsby-plugin-sharp/src/index.js → packages/gatsby-plugin-sharp/src/image-data.ts
Import cycle (2 files) packages/gatsby-source-wordpress/src/models/develop.ts — packages/gatsby-source-wordpress/src/models/develop.ts → packages/gatsby-source-wordpress/src/models/index.ts → packages/gatsby-source-wordpress/src/models/develop.ts (one verified cycle inside a mutually-dependent group of 31 files)
Import cycle (2 files) packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts — packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts → packages/gatsby/src/bootstrap/load-plugins/validate.ts → packages/gatsby/src/bootstrap/load-plugins/resolve-plugin.ts

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.

D30 · Dependency Vulnerabilities · REDACTED vulnerability · ×3

REDACTED
REDACTED
REDACTED

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.

D31 · IaC & Container Security · REDACTED IaC · ×2

REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import '@babel/types' · ×2

Unlisted import '@babel/types' packages/babel-preset-gatsby/src/optimize-hook-destructuring.ts:2 — Imported but not declared in any reachable package.json — 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 package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'sharp' · ×2

Unlisted import 'sharp' packages/gatsby/src/schema/graphql-engine/bundle-webpack.ts:237 — Imported but not declared in any reachable package.json — 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 package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'common-tags' · ×2

Unlisted import 'common-tags' REDACTED:2 — Imported but not declared in any reachable package.json — 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 package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'prop-types' · ×2

Unlisted import 'prop-types' packages/gatsby-plugin-google-analytics/src/index.js:2 — Imported but not declared in any reachable package.json — 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 package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'remark' · ×2

Unlisted import 'remark' packages/gatsby-remark-autolink-headers/src/__tests__/index.js:1 — Imported but not declared in any reachable package.json — 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 package.json — installs work only by hoisting accident.

D14 · License Compliance · Banned license · ×1

Banned license: @wordpress/block-library — `@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 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 record an accepted exception.

R8 · Dependency Hygiene · Unlisted import 'ansi-colors' · ×1

Unlisted import 'ansi-colors' packages/create-gatsby/src/components/form.js:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'configstore' · ×1

Unlisted import 'configstore' packages/create-gatsby/src/utils/get-config-store.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@parcel/types' · ×1

Unlisted import '@parcel/types' packages/gatsby-parcel-namer-relative-to-cwd/src/index.ts:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@emotion/babel-plugin' · ×1

Unlisted import '@emotion/babel-plugin' packages/gatsby-plugin-emotion/src/gatsby-node.js:4 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@testing-library/react' · ×1

Unlisted import '@testing-library/react' packages/gatsby-react-router-scroll/src/__tests__/use-scroll-restoration.tsx:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (3 files) · ×1

Import cycle (3 files) packages/gatsby-cli/src/reporter/redux/index.ts — 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)

R9 · Circular Imports · Import cycle (4 files) · ×1

Import cycle (4 files) packages/gatsby/cache-dir/gatsby-browser-entry.js — packages/gatsby/cache-dir/gatsby-browser-entry.js → packages/gatsby/cache-dir/public-page-renderer.js → packages/gatsby/cache-dir/public-page-renderer-dev.js → packages/gatsby/cache-dir/query-result-store.js → packages/gatsby/cache-dir/gatsby-browser-entry.js (one verified cycle inside a mutually-dependent group of 7 files)

R9 · Circular Imports · Import cycle (5 files) · ×1

Import cycle (5 files) packages/gatsby/src/datastore/index.ts — packages/gatsby/src/datastore/index.ts → packages/gatsby/src/datastore/datastore.ts → packages/gatsby/src/datastore/lmdb/lmdb-datastore.ts → packages/gatsby/src/datastore/in-memory/run-fast-filters.ts → packages/gatsby/src/datastore/in-memory/indexing.ts → packages/gatsby/src/datastore/index.ts (one verified cycle inside a mutually-dependent group of 113 files)

R9 · Circular Imports · Import cycle (1 files) · ×1

Import cycle (1 files) packages/gatsby/src/utils/parcel/compile-gatsby-files.ts — packages/gatsby/src/utils/parcel/compile-gatsby-files.ts → packages/gatsby/src/utils/parcel/compile-gatsby-files.ts

Serious — 965 finding(s)

D17 · Explicit Debt · TodoComment · ×136

TodoComment packages/gatsby-adapter-netlify/src/route-handler.ts:177 — // TODO: add headers handling — 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/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/reporter/types.ts:2 — // TODO: This needs to be implemented when redux/acitons is converted to TS — 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.
TodoComment packages/gatsby-cli/src/reporter/start-logger.ts:36 — // 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/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/__tests__/index.ts:5 — // TODO: report.error now DOES return something. Get rid of this spying mocking stuff — 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/__tests__/errors.ts:5 — // TODO: Add tests for sourcemap mapping in prepareStackTrace[] — 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/loggers/ink/components/error.tsx:36 — // TODO: when there's no specific docsUrl, add helpful message describing how — 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/loggers/yurnalist/index.ts:245 — // TODO: I'm not convinced that this is ever called with a text property. — 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/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-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-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-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-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-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.
+ 111 more in this group — see findings.md.

D12 · Dependency Hygiene · Floating npm dependency · ×93

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.
+ 68 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · REDACTED CVE · ×47

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 22 more in this group — see findings.md.

R11 · Import Boundaries · Boundary violation [package · ×40

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 package.json does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:third-party-deep-import] packages/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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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 package.json 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.

R4 · Test Coverage · This test file cannot be loaded · ×40

This test file cannot be loaded deprecated-packages/gatsby-recipes/src/create-types.test.js — deprecated-packages/gatsby-recipes/src/create-types.test.js:1 imports './create-types', 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 deprecated-packages/gatsby-recipes/src/parser/validate.test.js — deprecated-packages/gatsby-recipes/src/parser/validate.test.js:1 imports './validate', 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 deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js — deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js:1 imports './directory', 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 deprecated-packages/gatsby-recipes/src/providers/fs/file.test.js — deprecated-packages/gatsby-recipes/src/providers/fs/file.test.js:2 imports '../resource-schema', 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 deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.test.js — deprecated-packages/gatsby-recipes/src/providers/gatsby/plugin.test.js:4 imports '../resource-schema', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (3 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 deprecated-packages/gatsby-recipes/src/providers/gatsby/shadow-file.test.js — deprecated-packages/gatsby-recipes/src/providers/gatsby/shadow-file.test.js:4 imports '../../test-helper', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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 deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js — deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js:5 imports './site-metadata', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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 deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/build-plugin-node.test.js — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/build-plugin-node.test.js:3 imports './build-plugin-node', 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 deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/get-object-from-node.test.js — deprecated-packages/gatsby-recipes/src/providers/gatsby/utils/get-object-from-node.test.js:3 imports './get-object-from-node', 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 deprecated-packages/gatsby-recipes/src/providers/git/ignore.test.js — deprecated-packages/gatsby-recipes/src/providers/git/ignore.test.js:2 imports './ignore', 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 deprecated-packages/gatsby-recipes/src/providers/npm/package-json.test.js — deprecated-packages/gatsby-recipes/src/providers/npm/package-json.test.js:3 imports './package-json', 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 deprecated-packages/gatsby-recipes/src/providers/npm/package.test.js — deprecated-packages/gatsby-recipes/src/providers/npm/package.test.js:6 imports './package', 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 deprecated-packages/gatsby-recipes/src/providers/npm/script.test.js — deprecated-packages/gatsby-recipes/src/providers/npm/script.test.js:3 imports './script', 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 deprecated-packages/gatsby-recipes/src/providers/utils/get-diff.test.js — deprecated-packages/gatsby-recipes/src/providers/utils/get-diff.test.js:1 imports './get-diff', 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 deprecated-packages/gatsby-recipes/src/providers/utils/get-graphql-fields.test.js — deprecated-packages/gatsby-recipes/src/providers/utils/get-graphql-fields.test.js:1 imports './get-graphql-fields', 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 deprecated-packages/gatsby-recipes/src/renderer/index.test.js — deprecated-packages/gatsby-recipes/src/renderer/index.test.js:2 imports '../parser', 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 deprecated-packages/gatsby-recipes/src/renderer/render.test.js — deprecated-packages/gatsby-recipes/src/renderer/render.test.js:3 imports './render', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (2 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 deprecated-packages/gatsby-recipes/src/renderer/transform-to-plan-structure.test.js — deprecated-packages/gatsby-recipes/src/renderer/transform-to-plan-structure.test.js:1 imports './transform-to-plan-structure', 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 deprecated-packages/gatsby-recipes/src/validate-recipe.test.js — deprecated-packages/gatsby-recipes/src/validate-recipe.test.js:1 imports './validate-recipe', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded e2e-tests/adapters/cypress/e2e-netlify/cdn-caching.cy.ts — e2e-tests/adapters/cypress/e2e-netlify/cdn-caching.cy.ts:1 imports '../../utils', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded e2e-tests/adapters/cypress/e2e/basics.cy.ts — e2e-tests/adapters/cypress/e2e/basics.cy.ts:1 imports '../../constants', 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 e2e-tests/adapters/cypress/e2e/dsg.cy.ts — e2e-tests/adapters/cypress/e2e/dsg.cy.ts:1 imports '../../constants', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded e2e-tests/adapters/cypress/e2e/headers.cy.ts — e2e-tests/adapters/cypress/e2e/headers.cy.ts:1 imports '../../utils', 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 e2e-tests/adapters/cypress/e2e/redirects.cy.ts — e2e-tests/adapters/cypress/e2e/redirects.cy.ts:1 imports '../../utils', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded e2e-tests/adapters/cypress/e2e/slices.cy.ts — e2e-tests/adapters/cypress/e2e/slices.cy.ts:1 imports '../../constants', 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.
+ 15 more in this group — see findings.md.

D10 · Test Quality · No assertions · ×38

No assertions: e2e plugin resource test deprecated-packages/gatsby-recipes/src/providers/gatsby/site-metadata.test.js:37 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: e2e shadow file resource test deprecated-packages/gatsby-recipes/src/providers/gatsby/shadow-file.test.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: e2e test deprecated-packages/gatsby-recipes/src/providers/git/ignore.test.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: e2e script resource test deprecated-packages/gatsby-recipes/src/providers/npm/script.test.js:9 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: e2e npm package resource test deprecated-packages/gatsby-recipes/src/providers/npm/package.test.js:20 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: e2e package resource test deprecated-packages/gatsby-recipes/src/providers/npm/package-json.test.js:27 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when using Gatsby Link (without slash) e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts:14 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work when using Gatsby Link (with slash) e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work on direct visit (with other setting) e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work on direct visit (with current setting) e2e-tests/adapters/cypress/e2e/trailing-slash.cy.ts:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: direct visit with query params (${staticPath}) e2e-tests/adapters/cypress/e2e/ssr.cy.ts:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: direct visit no query params (${paramPath}) e2e-tests/adapters/cypress/e2e/ssr.cy.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: direct visit with query params (${paramPath}) e2e-tests/adapters/cypress/e2e/ssr.cy.ts: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should work 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 13 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×34

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: webpack-utils.createWebpackUtils packages/gatsby/src/utils/webpack-utils.ts:176 — FunctionTooLong — createWebpackUtils runs 404 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 304 over it, 4.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: 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: index.getGraphqlTypegenConfig packages/gatsby/src/state-machines/develop/index.ts:17 — FunctionTooLong — getGraphqlTypegenConfig runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: 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 packages/gatsby/src/commands/serve.ts: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: indexing.getNodesFromCacheByValue packages/gatsby/src/datastore/in-memory/indexing.ts:672 — FunctionTooLong — getNodesFromCacheByValue runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× 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: 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: queries.queriesReducer packages/gatsby/src/redux/reducers/queries.ts:60 — FunctionTooLong — queriesReducer runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js:12 — FunctionTooLong — identifyAndStoreIngestableFieldsAndTypes runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: validate.validatePluginsOptions packages/gatsby/src/bootstrap/load-plugins/validate.ts:203 — FunctionTooLong — validatePluginsOptions 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.
+ 9 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 deprecated-packages/gatsby-recipes/package.json; 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 packages/gatsby/package.json; 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, deprecated-packages/gatsby-recipes/package.json; 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 deprecated-packages/gatsby-recipes/package.json; 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, packages/gatsby/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: graphql — `graphql` is maintained at 2 different major versions inside this one repository — major 15 in deprecated-packages/gatsby-recipes/package.json; major 16 in packages/gatsby-codemods/package.json, packages/gatsby/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: graphql-compose — `graphql-compose` is maintained at 2 different major versions inside this one repository — major 7 in deprecated-packages/gatsby-recipes/package.json; major 9 in packages/gatsby-plugin-utils/package.json, packages/gatsby/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: mdast-util-toc — `mdast-util-toc` is maintained at 2 different major versions inside this one repository — major 5 in packages/gatsby-transformer-remark/package.json; 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 deprecated-packages/gatsby-recipes/package.json, 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 packages/gatsby/package.json; 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 packages/gatsby-transformer-remark/package.json; 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 deprecated-packages/gatsby-recipes/package.json; major 9 in packages/gatsby-transformer-remark/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-stringify — `remark-stringify` is maintained at 2 different major versions inside this one repository — major 8 in deprecated-packages/gatsby-recipes/package.json; major 9 in packages/gatsby-transformer-remark/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: unified — `unified` is maintained at 3 different major versions inside this one repository — major 8 in deprecated-packages/gatsby-recipes/package.json; major 9 in packages/gatsby-remark-katex/package.json, packages/gatsby-transformer-remark/package.json; 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 deprecated-packages/gatsby-recipes/package.json, 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 deprecated-packages/gatsby-recipes/package.json; major 8 in packages/gatsby/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.

D3 · God Classes · FileTooLong · ×21

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: src/index.js 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.

D29 · Static Analysis (SAST) · REDACTED · ×20

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · FixmeComment · ×14

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-cli/src/reporter/errors.ts:127 — // FIXME: when https://github.com/AriaMinaei/pretty-error/pull/49 is merged
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.
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/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/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/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/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/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/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.

R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×5

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.

D3 · God Classes · MethodTooLong · ×4

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 packages/gatsby/src/internal-plugins/dev-404-page/raw_dev-404-page.js: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: 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.

R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×4

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.

D31 · IaC & Container Security · REDACTED IaC · ×3

REDACTED
REDACTED
REDACTED

R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×3

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.

AC3 · Page structure · Page without a main landmark · ×2

Page without a main landmark deprecated-packages/gatsby-admin/src/components/layout.tsx:15 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark packages/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>.

D17 · Explicit Debt · HackComment · ×2

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

D2 · Cognitive Complexity · exports · ×2

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.

D2 · Cognitive Complexity · index.default (cognitive 26) · ×2

index.default (cognitive 26) packages/gatsby-remark-code-repls/src/index.js: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 literals inside it that branch (lines 101, 83, 59, …). 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.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). Most of this is not in the body itself: 0 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 48, 245, 221, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · exports (cognitive 26) · ×2

exports (cognitive 26) packages/gatsby-remark-code-repls/src/index.js: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 (verifyMultipleFiles::(anonymous), verifyFile, getFilePath, …). 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.
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 ((anonymous), (anonymous), normalizeLanguage). 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.

R10 · Code Duplication · Duplicated block (46 lines × 2 locations) · ×2

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.

R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×2

Duplicated block (30 lines × 2 locations) packages/gatsby/src/commands/serve.ts:215 — packages/gatsby/src/commands/serve.ts:215 · packages/gatsby/src/commands/serve.ts: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.

R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×2

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.

R7 · Dead Code · Dead file (~340 LoC) · ×2

Dead file (~340 LoC) packages/gatsby-plugin-benchmark-reporting/src/gatsby-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~340 LoC) packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

D1 · Cyclomatic Complexity · exports (cyclomatic 107) · ×1

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.

D1 · Cyclomatic Complexity · html.htmlReducer (cyclomatic 77) · ×1

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.

D1 · Cyclomatic Complexity · start-server.startServer (cyclomatic 74) · ×1

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 literals inside it that branch (lines 381, 283, 648, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · gatsby-node.sourceNodes (cyclomatic 70) · ×1

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.

D1 · Cyclomatic Complexity · index.default (cyclomatic 68) · ×1

index.default (cyclomatic 68) packages/gatsby-remark-images/src/index.js:37 — index.default has cyclomatic complexity 68 (threshold 15). Most of this is not in the body itself: 1 of the 68 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 139, 95, 480, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · extend-node-type.remarkExtendNodeType (cyclomatic 68) · ×1

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 5 function literals inside it that branch (lines 107, 624, 272, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · build.build (cyclomatic 55) · ×1

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.

D1 · Cyclomatic Complexity · sourceNodes (cyclomatic 54) · ×1

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.

D1 · Cyclomatic Complexity · image-data.generateImageData (cyclomatic 52) · ×1

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.

D1 · Cyclomatic Complexity · handle-flags.handleFlags (cyclomatic 51) · ×1

handle-flags.handleFlags (cyclomatic 51) packages/gatsby/src/utils/handle-flags.ts:8 — handle-flags.handleFlags has cyclomatic complexity 51 (threshold 15). Of this number, 24 points are the body's own statements and 27 belong to 10 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · indexing.getNodesFromCacheByValue (cyclomatic 50) · ×1

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.

D1 · Cyclomatic Complexity · initialize.initialize (cyclomatic 47) · ×1

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 literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · recursively-transform-fields.transformField (cyclomatic 46) · ×1

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.

D1 · Cyclomatic Complexity · queries.queriesReducer (cyclomatic 45) · ×1

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.

D1 · Cyclomatic Complexity · createPage (cyclomatic 44) · ×1

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.

D1 · Cyclomatic Complexity · normalize.createNodesForContentType (cyclomatic 43) · ×1

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.

D1 · Cyclomatic Complexity · replaceNodeHtmlImages (cyclomatic 43) · ×1

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.

D1 · Cyclomatic Complexity · index.fluid (cyclomatic 41) · ×1

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.

D1 · Cyclomatic Complexity · partial-hydration-reference-loader.partialHydrationReferenceLoader (cyclomatic 40) · ×1

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.

D1 · Cyclomatic Complexity · serve.default (cyclomatic 39) · ×1

serve.default (cyclomatic 39) packages/gatsby/src/commands/serve.ts:96 — serve.default has cyclomatic complexity 39 (threshold 15). Of this number, 16 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.

D1 · Cyclomatic Complexity · getFieldTransformers (cyclomatic 39) · ×1

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, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · index.default (cyclomatic 37) · ×1

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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes (cyclomatic 37) · ×1

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.

D1 · Cyclomatic Complexity · babel-plugin-remove-api.removeApiCalls (cyclomatic 36) · ×1

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.

D1 · Cyclomatic Complexity · index.default (cyclomatic 35) · ×1

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 literals inside it that branch (lines 120, 93, 189, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · exports · ×1

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.

D1 · Cyclomatic Complexity · exports (cyclomatic 35) · ×1

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, (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · prepare-stack-trace.CallSiteToString (cyclomatic 34) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-node.onCreateNode (cyclomatic 34) · ×1

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 literals inside it that branch (lines 279, 249, 222, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · print.printTypeDefinitions (cyclomatic 34) · ×1

print.printTypeDefinitions (cyclomatic 34) packages/gatsby/src/schema/print.ts: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 literals inside it that branch (lines 365, 407, 351, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · StaticQueryMapper.apply (cyclomatic 34) · ×1

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 2 function literals inside it that branch (lines 91, 79). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 34) · ×1

(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 ((anonymous), render::(anonymous), (anonymous)::App::(anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · create-cli.buildLocalCommands (cyclomatic 33) · ×1

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: 14 of the 33 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 110, 140, 204, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · filter-using-index.resolveIndexFieldRanges (cyclomatic 33) · ×1

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.

D1 · Cyclomatic Complexity · image-utils.generateImageData (cyclomatic 32) · ×1

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.

D1 · Cyclomatic Complexity · page-data.flush (cyclomatic 32) · ×1

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.

D1 · Cyclomatic Complexity · loadPage (cyclomatic 32) · ×1

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 ((anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous), (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · watch.watch (cyclomatic 31) · ×1

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.

D1 · Cyclomatic Complexity · resolve-module-exports.staticallyAnalyzeExports (cyclomatic 31) · ×1

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.

D1 · Cyclomatic Complexity · fetch-graphql.handleFetchErrors (cyclomatic 30) · ×1

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.

D1 · Cyclomatic Complexity · validate.validatePluginsOptions (cyclomatic 29) · ×1

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.

D1 · Cyclomatic Complexity · manager.getRoutesManifest (cyclomatic 29) · ×1

manager.getRoutesManifest (cyclomatic 29) packages/gatsby/src/utils/adapter/manager.ts:335 — manager.getRoutesManifest has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GatsbyWebpackStatsExtractor.apply (cyclomatic 29) · ×1

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.

D1 · Cyclomatic Complexity · index.run (cyclomatic 27) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-image-resolver.gatsbyImageResolver (cyclomatic 26) · ×1

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 literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WorkerPool.startAll (cyclomatic 26) · ×1

WorkerPool.startAll (cyclomatic 26) packages/gatsby-worker/src/index.ts:178 — WorkerPool.startAll has cyclomatic complexity 26 (threshold 15). 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 literals inside it that branch (lines 230, 313, 214, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · entry.getData (cyclomatic 25) · ×1

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.

D1 · Cyclomatic Complexity · index.default (cyclomatic 24) · ×1

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 literals inside it that branch (lines 37, 138, 29). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · fetch-nodes-paginated.paginatedWpNodeFetch (cyclomatic 24) · ×1

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.

D1 · Cyclomatic Complexity · client-assets-for-template.getScriptsAndStylesForTemplate (cyclomatic 24) · ×1

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). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · exports (cyclomatic 24) · ×1

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 ((anonymous), (anonymous), normalizeLanguage). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · normalize.getGatsbyImageCdnFields (cyclomatic 23) · ×1

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 literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PartialHydrationPlugin._generateManifest (cyclomatic 23) · ×1

PartialHydrationPlugin._generateManifest (cyclomatic 23) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:43 — PartialHydrationPlugin._generateManifest has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · bundle-webpack.createGraphqlEngineBundle (cyclomatic 23) · ×1

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 3 function literals inside it that branch (lines 581, 664, 431). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · index.initializeYurnalistLogger (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · fetch-file.requestRemoteNode (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-ssr.onRenderBody (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · index.fixed (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · index.default (cyclomatic 22) · ×1

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 literals inside it that branch (lines 48, 245, 221, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · compile-gatsby-files.compileGatsbyFiles (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · common.compareKey (cyclomatic 22) · ×1

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.

D1 · Cyclomatic Complexity · exports (cyclomatic 22) · ×1

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, (anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · placeholder.default (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · fetch-graphql.handleGraphQLErrors (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · check-plugin-requirements.areRemotePluginVersionsSatisfied (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · diff-schemas.checkIfSchemaHasChanged (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · node-manifest.findPageOwnedByNode (cyclomatic 21) · ×1

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.

D1 · Cyclomatic Complexity · route-handler.processRoutesManifest (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · fetch-remote-file.fetchFile (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · check-deps-changes.checkDepsChanges (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-node.createPagesStatefully (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · normalize.buildForeignReferenceMap (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · inference-metadata.incrementalReducer (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · build-html.renderHTMLQueue (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · schema.addConvenienceChildrenFields (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · ssr-develop-static-entry.staticPage (cyclomatic 20) · ×1

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 literals inside it that branch (lines 102, 173, 149, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · makeManifest (cyclomatic 20) · ×1

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.

D1 · Cyclomatic Complexity · image-utils.setDefaultDimensions (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · utils.handleReferences (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · create-local-file-node.errorPanicker (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · create-local-file-node.createLocalFileNode (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · inference-metadata.updateValueDescriptor (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · node-model.getQueryFields (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · manager.initAdapterManager (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · static-entry.staticPage (cyclomatic 19) · ×1

static-entry.staticPage (cyclomatic 19) REDACTED:114 — static-entry.staticPage has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · bundle-webpack.createPageSSRBundle (cyclomatic 19) · ×1

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.

D1 · Cyclomatic Complexity · FormInput.renderChoice (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · index.createNetlifyAdapter (cyclomatic 18) · ×1

index.createNetlifyAdapter (cyclomatic 18) packages/gatsby-adapter-netlify/src/index.ts:51 — index.createNetlifyAdapter has cyclomatic complexity 18 (threshold 15). Of this number, 9 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · gatsby-plugin-image.updateImport (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · process-file.processFile (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · index.default (cyclomatic 18) · ×1

index.default (cyclomatic 18) packages/gatsby-remark-code-repls/src/index.js: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 literals inside it that branch (lines 101, 83, 59, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · process-bulk-results.processBulkResults (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · update.wpActionUPDATE (cyclomatic 18) · ×1

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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · add-inferred-fields.getSimpleFieldConfig (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · schema.mergeTypes (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · schema.addExtensions (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · public.createNode (cyclomatic 18) · ×1

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.

D1 · Cyclomatic Complexity · resolvers.link (cyclomatic 18) · ×1

resolvers.link (cyclomatic 18) packages/gatsby/src/schema/resolvers.ts:355 — resolvers.link has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · exports (cyclomatic 18) · ×1

exports (cyclomatic 18) packages/gatsby-remark-code-repls/src/index.js: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 (verifyMultipleFiles::(anonymous), verifyFile, getFilePath, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · index.OutboundLink (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · prism-show-invisibles.default (cyclomatic 17) · ×1

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). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.

D1 · Cyclomatic Complexity · fetch.fetchContent (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · update.fetchAndCreateSingleNode (cyclomatic 17) · ×1

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). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · fetch-graphql.fetchGraphql (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · node-model.resolveRecursive (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · PartialHydrationPlugin.addClientModuleEntries (cyclomatic 17) · ×1

PartialHydrationPlugin.addClientModuleEntries (cyclomatic 17) packages/gatsby/src/utils/webpack/plugins/partial-hydration.ts:208 — PartialHydrationPlugin.addClientModuleEntries has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PartialHydrationPlugin.apply (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · validate-component.validateComponent (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · common.matchesFilter (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · query-compiler.processDefinitions (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · query-runner.queryRunner (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · getValidHeadNodesAndAttributes (cyclomatic 17) · ×1

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.

D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 17) · ×1

(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, (anonymous), (anonymous)::onHydrated, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · exports (cyclomatic 17) · ×1

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, (anonymous)). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · index.preset (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-image.browser.GatsbyImageHydrator (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · plugin-options.enhanceMdxOptions (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · create-pages-from-changed-nodes.createPagesFromChangedNodes (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · index.generateBase64 (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · parse-options.default (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · gatsby-script.injectScript (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · fetch.createContentfulErrorMessage (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · image-helpers.createUrl (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · create-operations.createOperations (cyclomatic 16) · ×1

create-operations.createOperations (cyclomatic 16) packages/gatsby-source-shopify/src/create-operations.ts:48 — create-operations.createOperations has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · process-node.replaceFileLinks (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · index.transformFields (cyclomatic 16) · ×1

index.transformFields (cyclomatic 16) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js:105 — index.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 one function literal inside it that branches (line 128). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · recursively-transform-fields.transformInlineFragments (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · recursively-transform-fields.transformFields (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · introspect-remote-schema.introspectAndStoreRemoteSchema (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · build-html.buildHTMLPagesAndDeleteStaleArtifacts (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · build-example-data.buildExampleValue (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · webpack-utils.createWebpackUtils (cyclomatic 16) · ×1

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 literals inside it that branch (lines 265, 291, 341, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · start-webpack-server.startWebpackServer (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · resolvers.getProjectedField (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · entry.renderHTML (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · develop.default (cyclomatic 16) · ×1

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 literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · lambda.setupFsWrapper (cyclomatic 16) · ×1

lambda.setupFsWrapper (cyclomatic 16) packages/gatsby/src/utils/page-ssr-module/lambda.ts:33 — lambda.setupFsWrapper has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · createTypeComposerFromGatsbyType (cyclomatic 16) · ×1

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.

D1 · Cyclomatic Complexity · requestRemoteNode (cyclomatic 16) · ×1

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, …). 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: packages/gatsby/src/utils/page-ssr-module/lambda.ts packages/gatsby/src/utils/page-ssr-module/lambda.ts:33 — packages/gatsby/src/utils/page-ssr-module/lambda.ts changed 2 times in last 90 days, max cyclomatic complexity 16 in lambda.setupFsWrapper at line 33. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-18..2026-09-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-18 22:28:40 +02:00' --until='2026-09-16 22:28:40 +02:00' --full-history --no-merges -- packages/gatsby/src/utils/page-ssr-module/lambda.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D17 · Explicit Debt · XxxComment · ×1

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.

D2 · Cognitive Complexity · html.htmlReducer (cognitive 167) · ×1

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.

D2 · Cognitive Complexity · start-server.startServer (cognitive 139) · ×1

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 literals inside it that branch (lines 381, 283, 648, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · exports (cognitive 130) · ×1

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.

D2 · Cognitive Complexity · gatsby-node.sourceNodes (cognitive 113) · ×1

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.

D2 · Cognitive Complexity · sourceNodes (cognitive 107) · ×1

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.

D2 · Cognitive Complexity · index.default (cognitive 98) · ×1

index.default (cognitive 98) packages/gatsby-remark-images/src/index.js:37 — index.default has cognitive complexity 98 (threshold 15). Drivers by points: if/else 36 (60 pts), boolean chains 16, ternaries 9 (14 pts), loops 3 (5 pts), match/switch 1 (3 pts) (nesting depth added 33). Most of this is not in the body itself: 0 of the 98 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 139, 95, 480, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · identify-and-store-ingestable-types.identifyAndStoreIngestableFieldsAndTypes (cognitive 90) · ×1

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.

D2 · Cognitive Complexity · extend-node-type.remarkExtendNodeType (cognitive 90) · ×1

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 5 function literals inside it that branch (lines 107, 624, 272, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · indexing.getNodesFromCacheByValue (cognitive 88) · ×1

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.

D2 · Cognitive Complexity · GatsbyWebpackStatsExtractor.apply (cognitive 83) · ×1

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). Most of this is not in the body itself: 0 of the 83 points are its own statements 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.

D2 · Cognitive Complexity · createPage (cognitive 80) · ×1

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.

D2 · Cognitive Complexity · handle-flags.handleFlags (cognitive 74) · ×1

handle-flags.handleFlags (cognitive 74) packages/gatsby/src/utils/handle-flags.ts:8 — handle-flags.handleFlags has cognitive complexity 74 (threshold 15). Drivers by points: if/else 29 (55 pts), boolean chains 13, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 29). Of this number, 43 points are the body's own statements and 31 belong to 10 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · build.build (cognitive 73) · ×1

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.

D2 · Cognitive Complexity · serve.default (cognitive 73) · ×1

serve.default (cognitive 73) packages/gatsby/src/commands/serve.ts: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). Of this number, 17 points are the body's own statements and 56 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · route-handler.processRoutesManifest (cognitive 69) · ×1

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.

D2 · Cognitive Complexity · replaceNodeHtmlImages (cognitive 64) · ×1

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.

D2 · Cognitive Complexity · resolvers.getProjectedField (cognitive 61) · ×1

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.

D2 · Cognitive Complexity · partial-hydration-reference-loader.partialHydrationReferenceLoader (cognitive 61) · ×1

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.

D2 · Cognitive Complexity · createNodesForContentType (cognitive 60) · ×1

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 ((anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous)::(anonymous)::traverse, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · StaticQueryMapper.apply (cognitive 59) · ×1

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). Most of this is not in the body itself: 0 of the 59 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 91, 79). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · onCreateNode (cognitive 59) · ×1

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, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · getValidHeadNodesAndAttributes (cognitive 58) · ×1

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.

D2 · Cognitive Complexity · WorkerPool.startAll (cognitive 56) · ×1

WorkerPool.startAll (cognitive 56) packages/gatsby-worker/src/index.ts:178 — WorkerPool.startAll has cognitive complexity 56 (threshold 15). Drivers by points: if/else 16 (34 pts), loops 4 (12 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 31). Most of this is not in the body itself: 2 of the 56 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 230, 313, 214, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · page-data.flush (cognitive 55) · ×1

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.

D2 · Cognitive Complexity · PartialHydrationPlugin._generateManifest (cognitive 54) · ×1

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, 30 points are the body's own statements and 24 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · babel-plugin-remove-api.removeApiCalls (cognitive 54) · ×1

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.

D2 · Cognitive Complexity · filter-using-index.resolveIndexFieldRanges (cognitive 52) · ×1

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.

D2 · Cognitive Complexity · initialize.initialize (cognitive 51) · ×1

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

D2 · Cognitive Complexity · queries.queriesReducer (cognitive 50) · ×1

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.

D2 · Cognitive Complexity · image-data.generateImageData (cognitive 49) · ×1

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.

D2 · Cognitive Complexity · utils.handleReferences (cognitive 47) · ×1

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.

D2 · Cognitive Complexity · prepare-stack-trace.CallSiteToString (cognitive 45) · ×1

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.

D2 · Cognitive Complexity · index.default (cognitive 44) · ×1

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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · watch.watch (cognitive 44) · ×1

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.

D2 · Cognitive Complexity · process-bulk-results.processBulkResults (cognitive 44) · ×1

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.

D2 · Cognitive Complexity · fetch-graphql.handleFetchErrors (cognitive 44) · ×1

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.

D2 · Cognitive Complexity · client-assets-for-template.getScriptsAndStylesForTemplate (cognitive 44) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · getValidHeadNodesAndAttributesSSR (cognitive 44) · ×1

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.

D2 · Cognitive Complexity · PartialHydrationPlugin.addClientModuleEntries (cognitive 43) · ×1

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). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · add-inferred-fields.getSimpleFieldConfig (cognitive 43) · ×1

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.

D2 · Cognitive Complexity · loadPage (cognitive 42) · ×1

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 ((anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous), (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · transformField (cognitive 42) · ×1

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.

D2 · Cognitive Complexity · (anonymous) (cognitive 41) · ×1

(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 ((anonymous), render::(anonymous), (anonymous)::App::(anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · print.printTypeDefinitions (cognitive 40) · ×1

print.printTypeDefinitions (cognitive 40) packages/gatsby/src/schema/print.ts: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 literals inside it that branch (lines 365, 407, 444, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · index.default (cognitive 39) · ×1

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 literals inside it that branch (lines 93, 120, 189, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · update.wpActionUPDATE (cognitive 39) · ×1

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 literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · fluid (cognitive 39) · ×1

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.

D2 · Cognitive Complexity · exports (cognitive 39) · ×1

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, (anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · common.compareKey (cognitive 38) · ×1

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.

D2 · Cognitive Complexity · compile-gatsby-files.compileGatsbyFiles (cognitive 37) · ×1

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.

D2 · Cognitive Complexity · manager.getRoutesManifest (cognitive 37) · ×1

manager.getRoutesManifest (cognitive 37) packages/gatsby/src/utils/adapter/manager.ts:335 — manager.getRoutesManifest has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (25 pts), loops 8, boolean chains 3, ternaries 1 (nesting depth added 8). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · check-deps-changes.checkDepsChanges (cognitive 36) · ×1

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.

D2 · Cognitive Complexity · index.default (cognitive 36) · ×1

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.

D2 · Cognitive Complexity · normalize.buildForeignReferenceMap (cognitive 36) · ×1

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.

D2 · Cognitive Complexity · exports (cognitive 36) · ×1

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.

D2 · Cognitive Complexity · build-html.renderHTMLQueue (cognitive 35) · ×1

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.

D2 · Cognitive Complexity · bundle-webpack.createGraphqlEngineBundle (cognitive 35) · ×1

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 3 function literals inside it that branch (lines 581, 431, 664). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · addCustomResolveFunctions (cognitive 35) · ×1

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). Most of this is not in the body itself: 0 of the 35 points are its own statements and the rest belongs to 4 function items inside it that branch (createResolvers::(anonymous)::(anonymous), createResolvers::(anonymous), createResolvers::(anonymous)::(anonymous)::resolve, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · getFieldTransformers (cognitive 35) · ×1

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. Most of this is not in the body itself: 0 of the 35 points are its own statements and the rest belongs to 41 function items inside it that branch (transform::resolve, test, test, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · LocalNodeModel.findRootNodeAncestor (cognitive 34) · ×1

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.

D2 · Cognitive Complexity · install-packages.installPackages (cognitive 33) · ×1

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 literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · gatsby-image-resolver.gatsbyImageResolver (cognitive 33) · ×1

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 literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · makeManifest (cognitive 33) · ×1

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.

D2 · Cognitive Complexity · paginatedWpNodeFetch (cognitive 33) · ×1

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.

D2 · Cognitive Complexity · index.run (cognitive 32) · ×1

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.

D2 · Cognitive Complexity · index.initializeYurnalistLogger (cognitive 32) · ×1

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). Most of this is not in the body itself: 0 of the 32 points are its own statements 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.

D2 · Cognitive Complexity · entry.getData (cognitive 32) · ×1

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.

D2 · Cognitive Complexity · create-cli.buildLocalCommands (cognitive 31) · ×1

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: 13 of the 31 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 140, 204, 110, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · create-pages-from-changed-nodes.createPagesFromChangedNodes (cognitive 31) · ×1

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.

D2 · Cognitive Complexity · utils.getExtendedFileNodeData (cognitive 31) · ×1

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.

D2 · Cognitive Complexity · validate.validatePluginsOptions (cognitive 31) · ×1

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). Most of this is not in the body itself: 0 of the 31 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · resolve-module-exports.staticallyAnalyzeExports (cognitive 30) · ×1

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.

D2 · Cognitive Complexity · middleware.createSetContextFunctionMiddleware (cognitive 30) · ×1

middleware.createSetContextFunctionMiddleware (cognitive 30) packages/gatsby/src/internal-plugins/functions/middleware.ts:76 — middleware.createSetContextFunctionMiddleware 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). Most of this is not in the body itself: 0 of the 30 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 81, 97). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · createTypeComposerFromGatsbyType (cognitive 30) · ×1

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 (interfaces::(anonymous), interfaces::(anonymous), interfaces, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · resolveRecursive (cognitive 30) · ×1

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.

D2 · Cognitive Complexity · exports (cognitive 30) · ×1

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). Most of this is not in the body itself: 0 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (generateImagesAndUpdateNode, (anonymous)::(anonymous)::(anonymous), (anonymous)::(anonymous), …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · introspectAndStoreRemoteSchema (cognitive 30) · ×1

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.

D2 · Cognitive Complexity · diagnostics.createStructuredLoggingDiagnosticsMiddleware (cognitive 29) · ×1

diagnostics.createStructuredLoggingDiagnosticsMiddleware (cognitive 29) packages/gatsby-cli/src/reporter/redux/diagnostics.ts:67 — diagnostics.createStructuredLoggingDiagnosticsMiddleware has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 16). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 121, 99, 142, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · utils.handleDeletedNode (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · generate-queries-from-ingestable-types.generateNodeQueriesFromIngestibleFields (cognitive 29) · ×1

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.

D2 · Cognitive Complexity · plugin-options.enhanceMdxOptions (cognitive 28) · ×1

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.

D2 · Cognitive Complexity · fetch-file.requestRemoteNode (cognitive 27) · ×1

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). Most of this is not in the body itself: 0 of the 27 points are its own statements 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.

D2 · Cognitive Complexity · image-utils.generateImageData (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · fetch-graphql.handleGraphQLErrors (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · node-manifest.findPageOwnedByNode (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · ForceCssHMRForEdgeCases.apply (cognitive 27) · ×1

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). Most of this is not in the body itself: 0 of the 27 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · query-compiler.processDefinitions (cognitive 27) · ×1

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.

D2 · Cognitive Complexity · static-entry.staticPage (cognitive 27) · ×1

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, 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: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · lambda.setupFsWrapper (cognitive 27) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · normalize.getGatsbyImageCdnFields (cognitive 26) · ×1

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 literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · (anonymous) (cognitive 26) · ×1

(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, (anonymous), (anonymous)::onHydrated, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · create-operations.createOperations (cognitive 25) · ×1

create-operations.createOperations (cognitive 25) packages/gatsby-source-shopify/src/create-operations.ts:48 — create-operations.createOperations has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · schema.addConvenienceChildrenFields (cognitive 25) · ×1

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). Most of this is not in the body itself: 0 of the 25 points are its own statements 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.

D2 · Cognitive Complexity · manager.initAdapterManager (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · addExtensions (cognitive 25) · ×1

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.

D2 · Cognitive Complexity · staticPage (cognitive 25) · ×1

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, generateBodyHTML::(anonymous), generateBodyHTML::getPageDataPath, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · fetch-remote-file.fetchFile (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · index.default (cognitive 24) · ×1

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 literals inside it that branch (lines 37, 138, 29). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · gatsby-script.injectScript (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · backreferences.getExistingCachedNodes (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · source-from-operation.makeSourceFromOperation (cognitive 24) · ×1

source-from-operation.makeSourceFromOperation (cognitive 24) REDACTED:14 — source-from-operation.makeSourceFromOperation 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). Most of this is not in the body itself: 0 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 22, 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.

D2 · Cognitive Complexity · PartialHydrationPlugin.apply (cognitive 24) · ×1

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). Most of this is not in the body itself: 0 of the 24 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · sanitize-node.sanitizeNode (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · query-compiler.extractOperations (cognitive 24) · ×1

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.

D2 · Cognitive Complexity · inference-metadata.getType (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · stitching.stitchSlices (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · build-html.buildHTMLPagesAndDeleteStaleArtifacts (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · public.createNode (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · exports (cognitive 23) · ×1

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.

D2 · Cognitive Complexity · gatsby-ssr.onRenderBody (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · image-utils.setDefaultDimensions (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · check-plugin-requirements.areRemotePluginVersionsSatisfied (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · indexing.getGatsbyNodePartial (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · build-utils.calcDirtyHtmlFiles (cognitive 22) · ×1

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). Of this number, 12 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.

D2 · Cognitive Complexity · process-plugin.processPlugin (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · createContentfulErrorMessage (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · createLocalFileNode (cognitive 22) · ×1

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.

D2 · Cognitive Complexity · prism-show-invisibles.default (cognitive 21) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · create-local-file-node.errorPanicker (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · indexing.unionNodesByCounter (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · query-runner.queryRunner (cognitive 21) · ×1

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.

D2 · Cognitive Complexity · exports (cognitive 21) · ×1

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, (anonymous)). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · create-cli.createCli (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · gatsby-plugin-image.updateImport (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · gatsby-image-resolver.calculateFixedImageSizes (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · fetch.fetchContent (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · process-node.replaceFileLinks (cognitive 20) · ×1

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.

D2 · Cognitive Complexity · gatsby-node.onPreBootstrap (cognitive 20) · ×1

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 2 function literals inside it that branch (lines 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.

D2 · Cognitive Complexity · exports (cognitive 20) · ×1

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). Most of this is not in the body itself: 0 of the 20 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · image-processing.writeImages (cognitive 19) · ×1

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). Most of this is not in the body itself: 0 of the 19 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · gatsby-node.onCreateNode (cognitive 19) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · init.getAdapterInit (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · create-headers.createHeadersMatcher (cognitive 19) · ×1

create-headers.createHeadersMatcher (cognitive 19) packages/gatsby/src/utils/adapter/create-headers.ts:14 — create-headers.createHeadersMatcher has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 5 (8 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 67, 59). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · start-webpack-server.startWebpackServer (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · resolvers.link (cognitive 19) · ×1

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). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · entry.renderHTML (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · bundle-webpack.createPageSSRBundle (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · develop.default (cognitive 19) · ×1

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 literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · getDimensionsAndAspectRatio (cognitive 19) · ×1

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.

D2 · Cognitive Complexity · index.createNetlifyAdapter (cognitive 18) · ×1

index.createNetlifyAdapter (cognitive 18) packages/gatsby-adapter-netlify/src/index.ts:51 — index.createNetlifyAdapter has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 5, ternaries 3, loops 1 (nesting depth added 1). Of this number, 9 points are the body's own statements and 9 belong 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.

D2 · Cognitive Complexity · process-file.processFile (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · index.default (cognitive 18) · ×1

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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · parse-options.default (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · normalize.recursiveAddFields (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · diff-schemas.checkIfSchemaHasChanged (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · inference-metadata.incrementalReducer (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · indexing.postIndexingMetaSetupLtLteGtGte (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · node-model.getQueryFields (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · mergeTypes (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · requestRemoteNode (cognitive 18) · ×1

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). Most of this is not in the body itself: 0 of the 18 points are its own statements and the rest belongs to 8 function items inside it that branch (processRemoteNode, (anonymous)::handleTimeout, (anonymous)::resetTimeout, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · fetchAndCreateSingleNode (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · applyPropDoclets (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · createFileNode (cognitive 18) · ×1

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.

D2 · Cognitive Complexity · remark-infer-toc-meta.remarkInferTocMeta (cognitive 17) · ×1

remark-infer-toc-meta.remarkInferTocMeta (cognitive 17) packages/gatsby-plugin-mdx/src/remark-infer-toc-meta.ts:30 — remark-infer-toc-meta.remarkInferTocMeta has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 7). Most of this is not in the body itself: 0 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 36, 48, 88). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · index.generateBase64 (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · index.fixed (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · highlight-code.default (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · LocalNodeModel._query (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · validate-component.validateComponent (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · filter-using-index.narrowResultsIfPossible (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · manager.setAdapter (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · generate.onNewVersion (cognitive 17) · ×1

generate.onNewVersion (cognitive 17) scripts/gatsby-changelog-generator/generate.js:316 — generate.onNewVersion has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (6 pts), if/else 3 (5 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · transformFields (cognitive 17) · ×1

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.

D2 · Cognitive Complexity · index.preset (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · FormInput.renderChoice (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · route-handler.injectEntries (cognitive 16) · ×1

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). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CLI.render (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · gatsby-plugin-image.processImportUsage (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · sort-and-aggr-graphql.updateSortAndAggrField (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · sort-and-aggr-graphql.processGraphQLQuery (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · index.OutboundLink (cognitive 16) · ×1

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). Most of this is not in the body itself: 0 of the 16 points are its own statements 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.

D2 · Cognitive Complexity · image-utils.fixedImageSizes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · image-utils.responsiveImageSizes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · gatsby-image.browser.GatsbyImageHydrator (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · utils.responsiveImageSizes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · plugin-options.healOptions (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · gatsby-image-resolver.calculateResponsiveImageSizes (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · gatsby-node.createPages (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · image-helpers.createUrl (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · run-steps.runSteps (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · recursively-transform-fields.transformInlineFragments (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · gatsby-node.onCreateNode (cognitive 16) · ×1

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 literals inside it that branch (lines 84, 50, 74). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · babelrc.babelrcReducer (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · transform-document.processGraphQLQuery (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · build-html.runWebpack (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · render-html.renderPartialHydrationProd (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · build-example-data.buildExampleValue (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · node-manifest.processNodeManifest (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · CacheFolderResolver.constructor (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · express-middlewares.configureTrailingSlash (cognitive 16) · ×1

express-middlewares.configureTrailingSlash (cognitive 16) packages/gatsby/src/utils/express-middlewares.ts:7 — express-middlewares.configureTrailingSlash has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 8). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · redirects-writer.writeRedirects (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · utils.fieldPathNeedToResolve (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · limited-exports-page-templates.isApiExport (cognitive 16) · ×1

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.

D2 · Cognitive Complexity · transformFields (cognitive 16) · ×1

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). Most of this is not in the body itself: 0 of the 16 points are its own statements and the rest belongs 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.

D2 · Cognitive Complexity · constructor (cognitive 16) · ×1

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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

R10 · Code Duplication · Duplication concentrated across 30 sibling directories (43 clone groups) · ×1

Duplication concentrated across 30 sibling directories (43 clone groups) packages/gatsby-plugin-image/src/image-utils.ts:376 — 43 duplicated blocks under packages/ have copies in at least two of the sibling directories create-gatsby, gatsby, gatsby-codemods, gatsby-core-utils, gatsby-plugin-emotion, gatsby-plugin-google-analytics (+24 more sibling(s) not listed) — 28 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 43 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 43 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 43 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 7 sibling directories (8 clone groups) · ×1

Duplication concentrated across 7 sibling directories (8 clone groups) packages/gatsby/src/internal-plugins/functions/gatsby-node.ts:358 — 8 duplicated blocks under packages/gatsby/src/ have copies in at least two of the sibling directories bootstrap, commands, internal-plugins, schema, services, state-machines (+1 more sibling(s) not listed) — 6 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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.

R10 · Code Duplication · Wholesale file copy (65 identical lines × 4 files) · ×1

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.

R10 · Code Duplication · Duplicated block (62 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (55 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (50 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1

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.

R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1

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.

R2 · Cyclomatic Complexity · Complex function isTabbableRules (cyclomatic 94, cognitive 121) · ×1

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.

R2 · Cyclomatic Complexity · Complex function isFocusRelevantRules (cyclomatic 90, cognitive 91) · ×1

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.

R2 · Cyclomatic Complexity · Complex function htmlReducer (cyclomatic 76, cognitive 162) · ×1

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.

R2 · Cyclomatic Complexity · Complex function build (cyclomatic 54, cognitive 70) · ×1

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 50, cognitive 87) · ×1

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.

R2 · Cyclomatic Complexity · Complex function generateImageData (cyclomatic 49, cognitive 45) · ×1

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.

R2 · Cyclomatic Complexity · Complex function transformField (cyclomatic 46, cognitive 42) · ×1

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.

R2 · Cyclomatic Complexity · Complex function queriesReducer (cyclomatic 45, cognitive 54) · ×1

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.

R2 · Cyclomatic Complexity · Complex function createPage (cyclomatic 43, cognitive 75) · ×1

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.

R2 · Cyclomatic Complexity · Complex function sourceNodes (cyclomatic 40, cognitive 99) · ×1

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.

R2 · Cyclomatic Complexity · Complex function generateImagesAndUpdateNode (cyclomatic 35, cognitive 37) · ×1

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.

R2 · Cyclomatic Complexity · Complex function initialize (cyclomatic 35, cognitive 37) · ×1

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.

R2 · Cyclomatic Complexity · Complex function CallSiteToString (cyclomatic 34, cognitive 46) · ×1

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.

R2 · Cyclomatic Complexity · Complex function identifyAndStoreIngestableFieldsAndTypes (cyclomatic 33, cognitive 84) · ×1

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.

R2 · Cyclomatic Complexity · Complex function sourceNodes (cyclomatic 33, cognitive 64) · ×1

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.

R2 · Cyclomatic Complexity · Complex function exports (cyclomatic 32, cognitive 46) · ×1

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.

R2 · Cyclomatic Complexity · Complex function fluid (cyclomatic 32, cognitive 26) · ×1

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 31, cognitive 45) · ×1

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.

R2 · Cyclomatic Complexity · Complex function resolveIndexFieldRanges (cyclomatic 29, cognitive 38) · ×1

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.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 28, cognitive 82) · ×1

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.

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

R7 · Dead Code · Dead file (~1011 LoC) · ×1

Dead file (~1011 LoC) packages/gatsby-source-wordpress/src/steps/declare-plugin-options-schema.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~999 LoC) · ×1

Dead file (~999 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/process-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~831 LoC) · ×1

Dead file (~831 LoC) packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 13 in-repo import(s) from 13 other file(s) do name it (packages/gatsby-source-wordpress/src/hooks/node-filters.ts, packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js and 10 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~732 LoC) · ×1

Dead file (~732 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~613 LoC) · ×1

Dead file (~613 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/gatsby-source-wordpress/src/models/image-nodes.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js, packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~589 LoC) · ×1

Dead file (~589 LoC) packages/gatsby/src/internal-plugins/functions/gatsby-node.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~466 LoC) · ×1

Dead file (~466 LoC) REDACTED — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~451 LoC) · ×1

Dead file (~451 LoC) packages/gatsby-source-wordpress/src/steps/create-schema-customization/helpers.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 27 in-repo import(s) from 21 other file(s) do name it (packages/gatsby-source-wordpress/src/models/remoteSchema.ts, packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js and 18 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~448 LoC) · ×1

Dead file (~448 LoC) packages/gatsby-source-wordpress/src/steps/preview/index.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 7 in-repo import(s) from 7 other file(s) do name it (packages/gatsby-source-wordpress/src/models/develop.ts, packages/gatsby-source-wordpress/src/models/gatsby-api.ts, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/transform-object.js and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~404 LoC) · ×1

Dead file (~404 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/transform-object.js, packages/gatsby-source-wordpress/src/steps/preview/index.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~379 LoC) · ×1

Dead file (~379 LoC) packages/gatsby-source-wordpress/src/utils/cache.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 14 in-repo import(s) from 14 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/check-plugin-requirements.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/cache-fetched-types.js and 11 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~373 LoC) · ×1

Dead file (~373 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-local-file-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/models/gatsby-api.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~369 LoC) · ×1

Dead file (~369 LoC) packages/gatsby-source-wordpress/src/models/gatsby-api.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 9 in-repo import(s) from 9 other file(s) do name it (packages/gatsby-source-wordpress/src/models/index.ts, packages/gatsby-source-wordpress/src/models/logger.ts, packages/gatsby-source-wordpress/src/steps/auth-handling.ts and 6 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~358 LoC) · ×1

Dead file (~358 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-node-queries.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~284 LoC) · ×1

Dead file (~284 LoC) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~264 LoC) · ×1

Dead file (~264 LoC) packages/gatsby-plugin-sharp/src/gatsby-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~262 LoC) · ×1

Dead file (~262 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~236 LoC) · ×1

Dead file (~236 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/field-transformers.js, packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~227 LoC) · ×1

Dead file (~227 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/build-query-on-field-name.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-and-store-ingestible-root-field-non-node-queries.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/generate-queries-from-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~225 LoC) · ×1

Dead file (~225 LoC) packages/gatsby-source-wordpress/src/steps/create-schema-customization/transform-fields/index.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/build-queries-from-introspection/recursively-transform-fields.js, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/identify-and-store-ingestable-types.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~213 LoC) · ×1

Dead file (~213 LoC) packages/gatsby/src/internal-plugins/internal-data-bridge/gatsby-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~192 LoC) · ×1

Dead file (~192 LoC) packages/gatsby-transformer-sharp/src/fragments.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~190 LoC) · ×1

Dead file (~190 LoC) packages/gatsby-graphiql-explorer/src/app.jsx — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~188 LoC) · ×1

Dead file (~188 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/create-nodes.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/source-nodes/create-nodes/fetch-and-create-non-node-root-fields.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~186 LoC) · ×1

Dead file (~186 LoC) packages/gatsby-transformer-screenshot/src/gatsby-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~174 LoC) · ×1

Dead file (~174 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts, packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~172 LoC) · ×1

Dead file (~172 LoC) packages/gatsby-source-wordpress/src/steps/process-and-validate-plugin-options.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/set-gatsby-api-to-state.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~167 LoC) · ×1

Dead file (~167 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/preview/index.ts, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-nodes.js, packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~166 LoC) · ×1

Dead file (~166 LoC) packages/gatsby-source-mongodb/src/gatsby-node.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~165 LoC) · ×1

Dead file (~165 LoC) packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/content-update-interval.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~144 LoC) · ×1

Dead file (~144 LoC) packages/gatsby-source-wordpress/src/steps/create-schema-customization/build-types.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/create-schema-customization/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~140 LoC) · ×1

Dead file (~140 LoC) scripts/create-release-notes.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~136 LoC) · ×1

Dead file (~136 LoC) packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/introspect-remote-schema.js — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/index.js, packages/gatsby-source-wordpress/src/steps/preview/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R7 · Dead Code · Dead file (~129 LoC) · ×1

Dead file (~129 LoC) packages/gatsby-source-wordpress/src/models/preview.ts — no import path from any entry point (269 application, 49 tooling, 471 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/gatsby-source-wordpress/src/models/index.ts, packages/gatsby-source-wordpress/src/steps/preview/cleanup.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

R8 · Dependency Hygiene · Unlisted import '@parcel/diagnostic' · ×1

Unlisted import '@parcel/diagnostic' packages/gatsby/src/utils/parcel/compile-gatsby-files.ts:4 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unlisted import 'terser' · ×1

Unlisted import 'terser' packages/gatsby/src/utils/webpack-utils.ts:8 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unlisted import 'graphql-compose' · ×1

Unlisted import 'graphql-compose' packages/gatsby-plugin-image/src/resolver-utils.ts:3 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unlisted import 'express' · ×1

Unlisted import 'express' REDACTED:10 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unlisted import 'got' · ×1

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 package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.

R8 · Dependency Hygiene · Unused dependency 'dictionary-en' · ×1

Unused dependency 'dictionary-en' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'markdown-magic' · ×1

Unused dependency 'markdown-magic' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'node-notifier' · ×1

Unused dependency 'node-notifier' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

Minor — 72 finding(s)

D10 · Test Quality · No direct assertions · ×37

No direct assertions: Visits the index page and navigates examples/using-cypress/cypress/e2e/smoke.cy.ts:2 — No conventional assertion call was detected, and 3 of 4 tests in `examples/using-cypress` 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: Has no detectable accessibility violations on load examples/using-cypress/cypress/e2e/accessibility.cy.ts:6 — No conventional assertion call was detected, and 3 of 4 tests in `examples/using-cypress` 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: Navigates to page 2 and checks for accessibility violations examples/using-cypress/cypress/e2e/accessibility.cy.ts:9 — No conventional assertion call was detected, and 3 of 4 tests in `examples/using-cypress` 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 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.
+ 12 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Low CVE · ×17

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Most significant orphaned file · ×3

Most significant orphaned file packages/gatsby-plugin-utils/src/utils/plugin-options-schema-joi-type.ts — 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 — 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 — 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.

D19 · Documentation Quality · Documentation · ×2

Documentation: no installation or build instructions README.md — The README is a single HTML page with no install/build or setup instructions. Add installation steps for the monorepo, including npx lerna bootstrap and any required packages.
Documentation: no architecture or design documentation packages/gatsby-transformer-screenshot/README.md — The screenshot plugin's Lambda setup and endpoint configuration are described but no architecture or design documentation exists in the set. Add an architecture doc covering how screenshots are generated, stored, and queried on AWS Lambda.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — Accessibility checks run in tests (Verified) but aren't gated in CI — run the suite that holds those checks in your pipeline so an accessibility regression blocks the merge (Prevented). What was searched, so you can tell an absence from a miss: the 35 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D16 · Bus Factor · Off-boarding risk · ×1

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 and example/demo 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.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D31 · IaC & Container Security · Low IaC · ×1

REDACTED

D34 · Knowledge Freshness · Concentrated knowledge decay · ×1

Concentrated knowledge decay — 310 of 424 significant files have no living knowledge, while the repository is still being changed at a low rate (9 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 310 separate risks. Counted over 424 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.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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

P3 · Security & performance tooling · No SAST · ×1

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

R8 · Dependency Hygiene · Type-only dependency '@graphql-codegen/plugin-helpers' in production deps · ×1

Type-only dependency '@graphql-codegen/plugin-helpers' in production deps packages/gatsby/src/utils/graphql-typegen/ts-codegen.ts:5 — Every import is type-only — move it to devDependencies.

R8 · Dependency Hygiene · Test-only dependency '@hapi/joi' in production deps · ×1

Test-only dependency '@hapi/joi' in production deps deprecated-packages/gatsby-recipes/src/providers/fs/directory.test.js:3 — Only test files import it — move it to devDependencies.

Minor — 402 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×272

Outdated (npm): @apollo/client — @apollo/client is pinned at 3.7.16; registry.npmjs.org publishes 4.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @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.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/eslint-parser — @babel/eslint-parser is pinned at 7.21.8; registry.npmjs.org publishes 7.29.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/generator — @babel/generator is pinned at 7.20.14; 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/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 7.29.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/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.0.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-runtime — @babel/plugin-transform-runtime is pinned at 7.19.6; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-spread — @babel/plugin-transform-spread is pinned at 7.20.7; registry.npmjs.org publishes 8.0.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-transform-typescript — @babel/plugin-transform-typescript is pinned at 7.20.13; registry.npmjs.org publishes 7.29.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-env — @babel/preset-env is pinned at 7.20.2; 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-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.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/runtime — @babel/runtime is pinned at 7.23.7; registry.npmjs.org publishes 8.0.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/template — @babel/template is pinned at 7.20.7; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/traverse — @babel/traverse 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/types — @babel/types is pinned at 7.20.7; registry.npmjs.org publishes 8.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @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.
+ 247 more in this group — see findings.md.

D10 · Test Quality · Skipped (documented) · ×130

Skipped (documented): validate returns a syntax error deprecated-packages/gatsby-recipes/src/parser/validate.test.js:14 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): fetches official recipes from unpkg deprecated-packages/gatsby-recipes/src/recipe-machine/index.test.js:81 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): should load successfully when navigating via Gatsby Link to a page with off-main-thread scripts e2e-tests/development-runtime/playwright/gatsby-script-off-main-thread.spec.ts:34 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): should load successfully when navigating via Gatsby Link between pages with off-main-thread scripts e2e-tests/development-runtime/playwright/gatsby-script-off-main-thread.spec.ts:55 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): should load successfully when navigating via Gatsby Link to a page with off-main-thread scripts e2e-tests/production-runtime/playwright/gatsby-script-off-main-thread.spec.ts:34 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): should load successfully when navigating via Gatsby Link between pages with off-main-thread scripts e2e-tests/production-runtime/playwright/gatsby-script-off-main-thread.spec.ts:55 — Skipped with a documented reason — a deferral, not lazy debt: switched off by test.skip
Skipped (documented): begins running the jest recipe integration-tests/gatsby-cli/__tests__/recipes.js:12 — Skipped with a documented reason — a deferral, not lazy debt: switched off by xit
Skipped (documented): starts a gatsby site on port 9000 with -p 9000 integration-tests/gatsby-cli/__tests__/develop.js:58 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): starts a gatsby site at a diffent host with -h integration-tests/gatsby-cli/__tests__/develop.js:59 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): starts a gatsby site with ssl using -S integration-tests/gatsby-cli/__tests__/develop.js:60 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): starts a gatsby site with cert file using -c integration-tests/gatsby-cli/__tests__/develop.js:61 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): starts a gatsby site with key file using -k integration-tests/gatsby-cli/__tests__/develop.js:62 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): starts a gatsby site with -open-tracing-config-file integration-tests/gatsby-cli/__tests__/develop.js:63 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): it emits just 2 SET_STATUS integration-tests/structured-logging/__tests__/to-do.js:213 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): assert that there are no jobs in progress integration-tests/structured-logging/__tests__/to-do.js:223 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): assert that there are no apis running integration-tests/structured-logging/__tests__/to-do.js:224 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): it emits just 2 SET_STATUS integration-tests/structured-logging/__tests__/to-do.js:236 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): asserts activities of bootstrap integration-tests/structured-logging/__tests__/to-do.js:258 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): asserts activities of bootstrap integration-tests/structured-logging/__tests__/to-do.js:531 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): emits actions with a timestamp integration-tests/structured-logging/__tests__/logs.js:41 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): Works correctly with the kitchen sink packages/babel-plugin-remove-graphql-queries/src/__tests__/index.ts:31 — Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Skipped (documented): throws TypeError if input is undefined packages/gatsby-link/src/__tests__/is-local-link.js:15 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): throws TypeError if input is not a string packages/gatsby-link/src/__tests__/is-local-link.js:20 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): checks if the user might be forcing navigation packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:56 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
Skipped (documented): checks if we clicked on an anchor packages/gatsby-plugin-catch-links/src/__tests__/catch-links.js:57 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skip
+ 105 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d2505c69ffd64d07beb32a84b4275a93/history.json --exit-code 0 --source .	104	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d2505c69ffd64d07beb32a84b4275a93/tree.json --exit-code 0 --source .	5	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	43	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	187	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	6	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 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.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a0d84b-62fc-7fd0-9be4-488c567e87a2 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Gatsbyjs/gatsby

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

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

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

At a glance — Maturity · 73% · Adequate · gated by D34 ·

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

At a glance — Security · 48% · Weak · gated by D28, D29, D30, D36 ·

At a glance — Accessibility · 58% · Adequate · gated by AC2 ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts