create-gatsby
Create Gatsby apps in an interactive CLI experience that does the plumbing for you.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Both lekoarts and pieh are known Gatsby core team members; this is a routine internal maintainer rotation. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is declared in dependencies and consumed by the microbundle-compiled output; stable for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): CLI scaffolding tool passes env to child processes (npm/yarn install, git init); expected behavior for create-gatsby. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): create-gatsby is a CLI tool that spawns package managers and git; child_process is core functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Artifact of microbundle bundling TypeScript source into a single CJS file; standard for this build pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Publisher pieh is Gatsby core team; mass packages from gatsbyjs monorepo. No keywords is normal for this ecosystem. | ai |
Versions (showing 90 of 90)
| Version | Deps | Published |
|---|---|---|
| 3.16.0 | 1 / 17 | |
| 3.15.0 | 1 / 17 | |
| 3.14.0 | 1 / 17 | |
| 3.13.1 | 1 / 17 | |
| 3.13.0 | 1 / 17 | |
| 3.12.3 | 1 / 17 | |
| 3.12.2 | 1 / 17 | |
| 3.12.1 | 1 / 17 | |
| 3.12.0 | 1 / 17 | |
| 3.11.0 | 1 / 17 | |
| 3.10.0 | 1 / 17 | |
| 3.9.0 | 1 / 17 | |
| 3.8.0 | 1 / 17 | |
| 3.7.0 | 1 / 17 | |
| 3.6.0 | 1 / 17 | |
| 3.5.0 | 1 / 17 | |
| 3.4.0 | 1 / 17 | |
| 3.3.1 | 1 / 17 | |
| 3.3.0 | 1 / 17 | |
| 3.2.0 | 1 / 17 | |
| 3.1.0 | 1 / 17 | |
| 3.0.0 | 1 / 17 | |
| 2.25.0 | 1 / 17 | |
| 2.24.0 | 1 / 17 | |
| 2.23.1 | 1 / 17 | |
| 2.23.0 | 1 / 17 | |
| 2.22.1 | 1 / 17 | |
| 2.22.0 | 1 / 17 | |
| 2.21.0 | 1 / 19 | |
| 2.20.0 | 1 / 19 | |
| 2.19.0 | 1 / 19 | |
| 2.18.1 | 1 / 19 | |
| 2.18.0 | 1 / 19 | |
| 2.17.0 | 1 / 19 | |
| 2.16.0 | 1 / 19 | |
| 2.15.1 | 1 / 19 | |
| 2.15.0 | 1 / 19 | |
| 2.14.0 | 1 / 19 | |
| 2.13.0 | 1 / 19 | |
| 2.12.1 | 1 / 19 | |
| 2.12.0 | 1 / 19 | |
| 2.11.2 | 1 / 20 | |
| 2.11.1 | 1 / 20 | |
| 2.11.0 | 1 / 20 | |
| 2.10.2 | 1 / 20 | |
| 2.10.1 | 1 / 20 | |
| 2.10.0 | 1 / 20 | |
| 2.9.0 | 1 / 20 | |
| 2.8.0 | 1 / 20 | |
| 2.7.0 | 1 / 20 | |
| 2.6.1 | 1 / 20 | |
| 2.6.0 | 1 / 20 | |
| 2.5.1 | 1 / 20 | |
| 2.5.0 | 1 / 20 | |
| 2.4.0 | 1 / 20 | |
| 2.3.0 | 1 / 20 | |
| 2.2.0 | 1 / 20 | |
| 2.1.1 | 1 / 20 | |
| 2.1.0 | 1 / 20 | |
| 2.0.0 | 1 / 20 | |
| 1.15.0 | 1 / 20 | |
| 1.14.0 | 1 / 20 | |
| 1.13.0 | 0 / 20 | |
| 1.12.0 | 0 / 20 | |
| 1.11.0 | 0 / 20 | |
| 1.10.0 | 0 / 20 | |
| 1.9.0 | 0 / 21 | |
| 1.8.0 | 0 / 21 | |
| 1.7.1 | 0 / 21 | |
| 1.7.0 | 0 / 21 | |
| 1.6.0 | 0 / 21 | |
| 1.5.0 | 0 / 21 | |
| 1.4.0 | 0 / 21 | |
| 1.3.0 | 0 / 21 | |
| 1.2.0 | 0 / 21 | |
| 1.1.0 | 0 / 21 | |
| 1.0.0 | 0 / 21 | |
| 0.5.1 | 0 / 21 | |
| 0.5.0 | 0 / 21 | |
| 0.4.0 | 0 / 21 | |
| 0.3.0 | 0 / 21 | |
| 0.2.1 | 0 / 21 | |
| 0.2.0 | 0 / 21 | |
| 0.1.0 | 0 / 21 | |
| 0.0.2 | 0 / 21 | |
| 0.0.1 | 0 / 21 | |
| 3.17.0-react19.1 | 1 / 17 | |
| 3.17.0-react19.0 | 1 / 17 | |
| 3.17.0-next.0 | 1 / 17 | |
| 3.16.0-next.0 | 1 / 17 |
v3.16.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gatsbyjs/gatsby/blob/92d6c67dcf10b641adf5fcc81ebeec5f50b75e40/lib/index.js#L1 > 1 | var e=require("assert"),t=require("events"),i=require("readline"),s=require("child_process"),r=require("path"),n=require 2 | Configure the ${oo(e)} plugin. 3 | See ${ao(e)} for help.
Package 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
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 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-08-24. This could indicate a legitimate maintainer transition or an account compromise.
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 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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-09-08. 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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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 2022-05-24. 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.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-04-05. This could indicate a legitimate maintainer transition or an account compromise.
v2.11.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-03-31. This could indicate a legitimate maintainer transition or an account compromise.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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.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.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.