gatsby-page-utils
Gatsby library that helps creating pages
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): pieh is a known Gatsby core maintainer; the transition from lekoarts to pieh reflects an internal Gatsby team change, not a suspicious account takeover. Stable for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainer (fk) is consistent with the Gatsby/Netlify org transition; no evidence of hostile takeover. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Gatsby monorepo package; glob is a declared dependency used indirectly or via config. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash declared as dependency in Gatsby monorepo package; indirect usage pattern is expected. Stable false positive. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Netlify-affiliated maintainers (serhalp-netlify, mlgualtieri-gatsby) added as part of documented Gatsby/Netlify organizational transition. Strong track record, no malicious signals. | ai | |
| phantom-deps | phantom-dep:fs-exists-cached | AI (phantom-deps): fs-exists-cached declared as dependency; indirect usage in Gatsby monorepo context is expected. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel runtime; loaded by convention in Gatsby packages. Stable false positive. | ai | |
| phantom-deps | phantom-dep:bluebird | AI (phantom-deps): Bluebird declared as dependency; indirect usage in Gatsby monorepo context is expected. Stable false positive. | ai |
Versions (showing 100 of 165)
| Version | Deps | Published |
|---|---|---|
| 3.16.0 | 8 / 7 | |
| 3.15.0 | 8 / 7 | |
| 3.14.0 | 8 / 7 | |
| 3.13.1 | 8 / 7 | |
| 3.13.0 | 8 / 7 | |
| 3.12.1 | 8 / 7 | |
| 3.12.0 | 8 / 7 | |
| 3.11.0 | 8 / 7 | |
| 3.10.0 | 8 / 7 | |
| 3.9.0 | 8 / 7 | |
| 3.8.0 | 8 / 7 | |
| 3.7.0 | 8 / 7 | |
| 3.6.0 | 8 / 7 | |
| 3.5.0 | 8 / 7 | |
| 3.4.0 | 8 / 7 | |
| 3.3.1 | 8 / 7 | |
| 3.3.0 | 8 / 7 | |
| 3.2.0 | 8 / 7 | |
| 3.1.0 | 8 / 7 | |
| 3.0.0 | 8 / 7 | |
| 2.25.0 | 8 / 7 | |
| 2.24.1 | 8 / 7 | |
| 2.24.0 | 8 / 7 | |
| 2.23.0 | 8 / 7 | |
| 2.22.0 | 8 / 7 | |
| 2.21.0 | 8 / 7 | |
| 2.20.0 | 8 / 7 | |
| 2.19.0 | 8 / 7 | |
| 2.18.1 | 8 / 7 | |
| 2.18.0 | 8 / 7 | |
| 2.17.0 | 8 / 7 | |
| 2.16.0 | 8 / 7 | |
| 2.15.0 | 8 / 7 | |
| 2.14.1 | 8 / 7 | |
| 2.14.0 | 8 / 7 | |
| 2.13.0 | 8 / 7 | |
| 2.12.1 | 8 / 7 | |
| 2.12.0 | 8 / 7 | |
| 2.11.1 | 8 / 7 | |
| 2.11.0 | 8 / 7 | |
| 2.10.1 | 8 / 7 | |
| 2.10.0 | 8 / 7 | |
| 2.9.1 | 8 / 7 | |
| 2.9.0 | 8 / 7 | |
| 2.8.2 | 8 / 7 | |
| 2.8.1 | 8 / 7 | |
| 2.8.0 | 8 / 7 | |
| 2.7.0 | 8 / 7 | |
| 2.6.0 | 8 / 7 | |
| 2.5.2 | 8 / 7 | |
| 2.5.1 | 8 / 7 | |
| 2.5.0 | 8 / 7 | |
| 2.4.0 | 8 / 7 | |
| 2.3.0 | 8 / 7 | |
| 2.2.0 | 8 / 7 | |
| 2.1.3 | 8 / 7 | |
| 2.1.2 | 8 / 7 | |
| 2.1.1 | 8 / 7 | |
| 2.1.0 | 8 / 7 | |
| 2.0.0 | 8 / 7 | |
| 1.15.0 | 8 / 7 | |
| 1.14.0 | 8 / 7 | |
| 1.13.0 | 8 / 7 | |
| 1.12.0 | 8 / 7 | |
| 1.11.0 | 8 / 7 | |
| 1.10.0 | 8 / 7 | |
| 1.9.0 | 8 / 7 | |
| 1.8.0 | 8 / 7 | |
| 1.7.1 | 8 / 7 | |
| 1.7.0 | 8 / 7 | |
| 1.6.0 | 8 / 7 | |
| 1.5.0 | 8 / 7 | |
| 1.4.0 | 8 / 7 | |
| 1.3.0 | 8 / 7 | |
| 1.2.0 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.0 | 8 / 7 | |
| 0.9.1 | 8 / 7 | |
| 0.9.0 | 8 / 7 | |
| 0.8.0 | 8 / 7 | |
| 0.7.0 | 8 / 7 | |
| 0.6.1 | 8 / 7 | |
| 0.6.0 | 8 / 7 | |
| 0.5.0 | 8 / 5 | |
| 0.4.0 | 8 / 5 | |
| 0.3.0 | 8 / 5 | |
| 0.2.30 | 8 / 5 | |
| 0.2.29 | 8 / 5 | |
| 0.2.28 | 8 / 5 | |
| 0.2.27 | 8 / 5 | |
| 0.2.26 | 8 / 5 | |
| 0.2.25 | 8 / 5 | |
| 0.2.24 | 8 / 5 | |
| 0.2.23 | 8 / 5 | |
| 0.2.22 | 8 / 5 | |
| 0.2.21 | 8 / 5 | |
| 0.2.20 | 8 / 5 | |
| 0.2.19 | 8 / 5 | |
| 0.2.18 | 8 / 5 | |
| 0.2.17 | 8 / 5 |
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
2 findingsThis version was published by a different npm account than previous versions on 2023-08-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-18. This could indicate a legitimate maintainer transition or an account compromise.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-27. This could indicate a legitimate maintainer transition or an account compromise.
v2.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-30. This could indicate a legitimate maintainer transition or an account compromise.
v2.21.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.19.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-05. This could indicate a legitimate maintainer transition or an account compromise.
v2.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-21. This could indicate a legitimate maintainer transition or an account compromise.
v2.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.
v2.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.13.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v2.12.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v2.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-25. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-22. This could indicate a legitimate maintainer transition or an account compromise.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.