gatsby-recipes
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:urql | AI (phantom-deps): Phantom deps in gatsby-recipes are referenced in config files and loaded dynamically per the recipe architecture; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Phantom deps in gatsby-recipes are referenced in config files and loaded dynamically per the recipe architecture; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): Phantom deps in gatsby-recipes are referenced in config files and loaded dynamically per the recipe architecture; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:acorn | AI (phantom-deps): Phantom deps in gatsby-recipes are referenced in config files and loaded dynamically per the recipe architecture; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Phantom deps in gatsby-recipes are referenced in config files and loaded dynamically per the recipe architecture; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:gatsby-telemetry | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:gatsby-core-utils | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:babel-plugin-remove-export-keywords | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| dependencies | unvetted-dep:babel-plugin-remove-export-keywords | AI (dependencies): babel-plugin-remove-export-keywords is a known Gatsby ecosystem Babel plugin used in the build pipeline; legitimate usage for this package. | ai | |
| phantom-deps | phantom-dep:yup | AI (phantom-deps): gatsby-recipes is a large build-tool package; phantom deps reflect indirect/convention-based usage patterns, not malicious signals. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): gatsby-recipes is a complex monorepo package that bundles many deps indirectly; phantom-dep findings reflect build/bundle patterns, not missing or malicious imports. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves a hardcoded relative path to .babelrc.js — standard monorepo Babel config pattern, not arbitrary module loading. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from wardpeet to lekoarts is a documented Gatsby team maintainer transition in 2021. lekoarts has strong track record (6255 approved packages) in the Gatsby ecosystem. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a framework-scoped transitive dependency in Gatsby/Babel ecosystems; not being directly imported is expected and stable for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() in step-renderer.js is an intentional DSL execution pattern for Gatsby Recipes, executing controlled recipe step code in a scoped environment — not arbitrary untrusted input. | ai | |
| dependencies | unvetted-dep:hicat | AI (dependencies): hicat is a legitimate syntax highlighter package; its use in a Gatsby recipes UI component is expected and benign. | ai | |
| dependencies | unvetted-dep:contentful-management | AI (dependencies): contentful-management is the official Contentful CMS SDK, a legitimate dependency for a Gatsby recipes tool that integrates with Contentful. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 59 / 24 | |
| 1.3.0 | 59 / 24 | |
| 1.2.0 | 59 / 24 | |
| 1.1.3 | 59 / 24 | |
| 1.1.2 | 59 / 24 | |
| 1.1.1 | 59 / 24 | |
| 1.1.0 | 59 / 24 | |
| 1.0.0 | 59 / 24 | |
| 0.25.0 | 59 / 24 | |
| 0.24.0 | 58 / 24 | |
| 0.23.0 | 58 / 24 | |
| 0.22.0 | 58 / 24 | |
| 0.21.0 | 58 / 24 | |
| 0.20.0 | 58 / 24 | |
| 0.19.0 | 58 / 24 | |
| 0.18.1 | 58 / 24 | |
| 0.18.0 | 58 / 24 | |
| 0.17.0 | 58 / 24 | |
| 0.16.0 | 58 / 24 | |
| 0.15.1 | 58 / 24 | |
| 0.15.0 | 58 / 24 | |
| 0.14.0 | 58 / 24 | |
| 0.13.0 | 58 / 24 | |
| 0.12.0 | 58 / 24 | |
| 0.11.0 | 58 / 24 | |
| 0.9.3 | 58 / 24 | |
| 0.9.2 | 58 / 24 | |
| 0.9.1 | 58 / 24 | |
| 0.9.0 | 58 / 24 | |
| 0.8.0 | 58 / 24 | |
| 0.7.1 | 58 / 24 | |
| 0.7.0 | 58 / 24 | |
| 0.6.1 | 58 / 24 | |
| 0.6.0 | 58 / 24 | |
| 0.5.1 | 58 / 24 | |
| 0.5.0 | 58 / 24 | |
| 0.4.1 | 58 / 24 | |
| 0.4.0 | 58 / 24 | |
| 0.3.1 | 58 / 24 | |
| 0.3.0 | 58 / 24 | |
| 0.2.38 | 59 / 24 | |
| 0.2.37 | 59 / 24 | |
| 0.2.36 | 59 / 24 | |
| 0.2.35 | 59 / 24 | |
| 0.2.34 | 59 / 24 | |
| 0.2.33 | 84 / 17 | |
| 0.2.28 | 84 / 17 | |
| 0.2.15 | 83 / 16 | |
| 0.2.5 | 80 / 16 | |
| 0.0.8 | 55 / 5 | |
| 0.0.4 | 0 / 0 |
v1.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 2021-12-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2021-11-16. 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.
v1.1.3
2 findingsThis version was published by a different npm account than previous versions on 2021-11-15. 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.
v1.1.2
2 findingsThis version was published by a different npm account than previous versions on 2021-11-11. 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.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2021-11-10. 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.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-11-02. 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.
v1.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 2021-10-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.25.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 2021-09-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-08-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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 2021-08-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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 2021-05-25. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-05-11. This could indicate a legitimate maintainer transition or an account compromise.
v0.15.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 2021-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.15.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 2021-04-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-04-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-03-30. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-03-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.3
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 2021-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.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 2021-02-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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 2021-02-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-01-19. This could indicate a legitimate maintainer transition or an account compromise.
v0.7.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 2021-01-13. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2021-01-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.6.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 2020-12-23. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2020-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.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 2020-12-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2020-12-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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 2020-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.38
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 2020-11-05. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.37
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 2020-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
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 2020-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.34
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 2020-10-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.33
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 2020-10-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.