gatsby-parcel-config

A minimal Parcel config for use in Gatsby

gatsby-parcel-config@1.16.0 was published on 2026-01-26. Its manifest declares 12 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All gatsby-parcel-config versions · Permanent reference to 1.16.0

Package specifications

Version1.16.0
License declarationMIT
Published2026-01-26T20:27:24.773Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count12
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.42 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entrylib/index.json
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies194
Repository stars55920
Repository forks10091

Install gatsby-parcel-config 1.16.0

npm install gatsby-parcel-config@1.16.0
pnpm add gatsby-parcel-config@1.16.0
yarn add gatsby-parcel-config@1.16.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Maintained2/10 — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2
Security-Policy10/10 — security policy file detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
License10/10 — license file detected
Binary-Artifacts10/10 — no binaries found in the repo
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
SAST9/10 — SAST tool is not run on all commits -- score normalized to 9

Evidence and freshness