gatsby-plugin-utils 1.7.1
Gatsby utils that help creating plugins
gatsby-plugin-utils@1.7.1 was published on 2021-06-10. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=12.13.0.
All gatsby-plugin-utils versions · Permanent reference to 1.7.1 · Latest release
Package specifications
| Version | 1.7.1 |
|---|---|
| License declaration | MIT |
| Published | 2021-06-10T16:49:03.322Z |
| Node.js requirement | >=12.13.0 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 165.08 KiB |
| Published file count | 26 |
| 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 | 6 |
| Repository stars | 55920 |
| Repository forks | 10091 |
Install gatsby-plugin-utils 1.7.1
npm install gatsby-plugin-utils@1.7.1 pnpm add gatsby-plugin-utils@1.7.1 yarn add gatsby-plugin-utils@1.7.1
Runtime dependencies
- joi ^17.2.1
Peer requirements
- gatsby ^3.0.0-next.0
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @hapi/hoek@9.3.0 — indirect
- @hapi/topo@5.1.0 — indirect
- @sideway/address@4.1.5 — indirect
- @sideway/formula@3.0.1 — indirect
- @sideway/pinpoint@2.0.0 — indirect
- joi@17.13.9 — 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-plugin-utils/1.7.1 — retrieved 2026-10-30T05:26:37.536Z
- https://api.deps.dev/v3/projects/github.com%2Fgatsbyjs%2Fgatsby — retrieved 2026-10-30T03:57:30.365Z
- https://api.deps.dev/v3/systems/npm/packages/gatsby-plugin-utils/versions/1.7.1 — retrieved 2026-10-30T05:26:38.061Z
- https://api.deps.dev/v3/systems/npm/packages/gatsby-plugin-utils/versions/1.7.1:dependencies — retrieved 2026-10-30T05:26:38.077Z