gatsby-core-utils 2.0.0
A collection of gatsby utils used in different gatsby packages
gatsby-core-utils@2.0.0 was published on 2021-03-02. Its manifest declares 8 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=12.13.0.
All gatsby-core-utils versions · Permanent reference to 2.0.0 · Latest release
Package specifications
| Version | 2.0.0 |
|---|---|
| License declaration | MIT |
| Published | 2021-03-02T10:41:05.586Z |
| Node.js requirement | >=12.13.0 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 8 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 52.33 KiB |
| Published file count | 36 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dist/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 38 |
| Repository stars | 55920 |
| Repository forks | 10091 |
Install gatsby-core-utils 2.0.0
npm install gatsby-core-utils@2.0.0 pnpm add gatsby-core-utils@2.0.0 yarn add gatsby-core-utils@2.0.0
Runtime dependencies
- tmp ^0.2.1
- ci-info 2.0.0
- fs-extra ^8.1.0
- file-type ^16.2.0
- configstore ^5.0.1
- xdg-basedir ^4.0.0
- proper-lockfile ^4.1.1
- node-object-hash ^2.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @tokenizer/token@0.3.0 — indirect
- abort-controller@3.0.0 — indirect
- base64-js@1.5.1 — indirect
- buffer@6.0.3 — indirect
- ci-info@2.0.0 — direct
- configstore@5.0.1 — direct
- crypto-random-string@2.0.0 — indirect
- dot-prop@5.3.0 — indirect
- event-target-shim@5.0.1 — indirect
- events@3.3.0 — indirect
- file-type@16.5.4 — direct
- fs-extra@8.1.0 — direct
- graceful-fs@4.2.11 — indirect
- ieee754@1.2.1 — indirect
- imurmurhash@0.1.4 — indirect
- is-obj@2.0.0 — indirect
- is-typedarray@1.0.0 — indirect
- jsonfile@4.0.0 — indirect
- make-dir@3.1.0 — indirect
- node-object-hash@2.3.10 — direct
- peek-readable@4.1.0 — indirect
- process@0.11.10 — indirect
- proper-lockfile@4.1.2 — direct
- readable-stream@4.8.0 — indirect
- readable-web-to-node-stream@3.0.4 — indirect
- retry@0.12.0 — indirect
- safe-buffer@5.2.1 — indirect
- semver@6.3.1 — indirect
- signal-exit@3.0.7 — indirect
- string_decoder@1.3.0 — indirect
- strtok3@6.3.0 — indirect
- tmp@0.2.7 — direct
- token-types@4.2.1 — indirect
- typedarray-to-buffer@3.1.5 — indirect
- unique-string@2.0.0 — indirect
- universalify@0.1.2 — indirect
- write-file-atomic@3.0.3 — indirect
- xdg-basedir@4.0.0 — direct
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-Review | 10/10 — all changesets reviewed |
|---|---|
| Maintained | 2/10 — 2 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 2 |
| Security-Policy | 10/10 — security policy file detected |
| Token-Permissions | 10/10 — GitHub workflow tokens follow principle of least privilege |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 10/10 — license file detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Branch-Protection | 5/10 — branch protection is not maximal on development and all release branches |
| Fuzzing | 0/10 — project is not fuzzed |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 9/10 — SAST tool is not run on all commits -- score normalized to 9 |
Evidence and freshness
- https://registry.npmjs.org/gatsby-core-utils/2.0.0 — retrieved 2026-10-30T19:22:02.052Z
- https://api.deps.dev/v3/projects/github.com%2Fgatsbyjs%2Fgatsby — retrieved 2026-10-30T16:03:09.567Z
- https://api.deps.dev/v3/systems/npm/packages/gatsby-core-utils/versions/2.0.0 — retrieved 2026-10-30T19:22:02.519Z
- https://api.deps.dev/v3/systems/npm/packages/gatsby-core-utils/versions/2.0.0:dependencies — retrieved 2026-10-30T19:22:02.536Z