gatsby-parcel-config
A minimal Parcel config for use in Gatsby
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@parcel/transformer-react-refresh-wrap | AI (phantom-deps): Parcel config packages declare plugins/runtimes as deps but reference them in .parcelrc config, not code. This is the correct pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/runtime-browser-hmr | AI (phantom-deps): Parcel config packages declare plugins/runtimes as deps but reference them in .parcelrc config, not code. This is the correct pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/runtime-react-refresh | AI (phantom-deps): Parcel config packages declare plugins/runtimes as deps but reference them in .parcelrc config, not code. This is the correct pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/runtime-service-worker | AI (phantom-deps): Parcel config packages declare plugins/runtimes as deps but reference them in .parcelrc config, not code. This is the correct pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/transformer-raw | AI (phantom-deps): Parcel config packages declare plugins/runtimes as deps but reference them in .parcelrc config, not code. This is the correct pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Netlify/Gatsby org members, consistent with known acquisition and team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of lekoarts is part of the legitimate Gatsby→Netlify team transition. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate org transition from Gatsby to Netlify team; serhalp-netlify has strong track record (5583 approved, 0 rejected). | ai | |
| phantom-deps | phantom-dep:@parcel/resolver-default | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/transformer-json | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/runtime-js | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@gatsbyjs/parcel-namer-relative-to-cwd | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the official Gatsby monorepo; mass-production signal is from legitimate monorepo management by a core Gatsby contributor. README/keywords signals are cosmetic only. | ai | |
| phantom-deps | phantom-dep:@parcel/reporter-dev-server | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/packager-js | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/packager-raw | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/namer-default | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/compressor-raw | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/transformer-js | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/bundler-default | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@parcel/optimizer-terser | AI (phantom-deps): Parcel config packages declare plugins as deps referenced in JSON config, not JS imports. This is the correct design pattern; not a real phantom dep. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.16.0 | 12 / 0 | |
| 1.15.0 | 12 / 0 | |
| 1.14.0 | 12 / 0 | |
| 1.13.1 | 12 / 0 | |
| 1.13.0 | 12 / 0 | |
| 1.12.1 | 12 / 0 | |
| 1.12.0 | 12 / 0 | |
| 1.11.0 | 12 / 0 | |
| 1.10.0 | 12 / 0 | |
| 1.9.0 | 12 / 0 | |
| 1.8.0 | 12 / 0 | |
| 1.7.0 | 12 / 0 | |
| 1.6.0 | 12 / 0 | |
| 1.5.0 | 12 / 0 | |
| 1.4.0 | 12 / 0 | |
| 1.3.1 | 12 / 0 | |
| 1.3.0 | 12 / 0 | |
| 1.2.0 | 12 / 0 | |
| 1.1.0 | 12 / 0 | |
| 1.0.0 | 12 / 0 | |
| 0.16.0 | 12 / 0 | |
| 0.15.1 | 12 / 0 | |
| 0.15.0 | 11 / 0 | |
| 0.14.0 | 17 / 0 | |
| 0.13.0 | 17 / 0 | |
| 0.12.0 | 17 / 0 | |
| 0.11.0 | 17 / 0 | |
| 0.10.1 | 17 / 0 | |
| 0.10.0 | 17 / 0 | |
| 0.9.2 | 17 / 0 | |
| 0.9.1 | 17 / 0 | |
| 0.9.0 | 17 / 0 | |
| 0.8.0 | 17 / 0 | |
| 0.7.0 | 17 / 0 | |
| 0.6.0 | 17 / 0 | |
| 0.5.0 | 17 / 0 | |
| 0.4.0 | 17 / 0 | |
| 0.3.1 | 17 / 0 | |
| 0.3.0 | 17 / 0 | |
| 0.2.0 | 17 / 0 | |
| 0.1.0 | 17 / 0 | |
| 0.0.1 | 17 / 0 |
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
v1.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.
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 2023-01-10. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
v1.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.
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 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 2022-10-06. 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 2022-09-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 2022-09-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 2022-08-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 2022-08-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 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.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-07-12. This could indicate a legitimate maintainer transition or an account compromise.
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 2022-07-05. 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 2022-06-21. 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 2022-06-07. 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 2022-05-24. 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 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2022-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.3.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.
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 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.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-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.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-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.