gatsby-plugin-react-helmet
Manage document head data with react-helmet. Provides drop-in server rendering support for 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
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 long-standing Gatsby core maintainer (first seen 2871 days ago, 6227 approved packages); transition from lekoarts is a legitimate internal team handoff within the gatsbyjs org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Netlify acquired Gatsby; serhalp-netlify and mlgualtieri-gatsby are legitimate Netlify/Gatsby org maintainers. This transition is expected across all Gatsby packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Legacy Gatsby maintainers removed as part of Netlify acquisition transition. Expected across all Gatsby packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): pieh is the original Gatsby core maintainer; mass-produced templated Gatsby plugins are expected. Empty index.js is standard for Gatsby plugins built from src/. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard framework-scoped transitive dep in Gatsby plugins; not a real phantom dependency concern. | ai |
Versions (showing 100 of 147)
| Version | Deps | Published |
|---|---|---|
| 6.16.0 | 1 / 4 | |
| 6.15.0 | 1 / 4 | |
| 6.14.0 | 1 / 4 | |
| 6.13.1 | 1 / 4 | |
| 6.13.0 | 1 / 4 | |
| 6.12.0 | 1 / 4 | |
| 6.11.0 | 1 / 4 | |
| 6.10.0 | 1 / 4 | |
| 6.9.0 | 1 / 4 | |
| 6.8.0 | 1 / 4 | |
| 6.7.0 | 1 / 4 | |
| 6.6.0 | 1 / 4 | |
| 6.5.0 | 1 / 4 | |
| 6.4.0 | 1 / 4 | |
| 6.3.0 | 1 / 4 | |
| 6.2.0 | 1 / 4 | |
| 6.1.0 | 1 / 4 | |
| 6.0.0 | 1 / 4 | |
| 5.25.0 | 1 / 4 | |
| 5.24.0 | 1 / 4 | |
| 5.23.0 | 1 / 4 | |
| 5.22.0 | 1 / 4 | |
| 5.21.0 | 1 / 4 | |
| 5.20.0 | 1 / 4 | |
| 5.19.0 | 1 / 4 | |
| 5.18.0 | 1 / 4 | |
| 5.17.0 | 1 / 4 | |
| 5.16.0 | 1 / 4 | |
| 5.15.0 | 1 / 4 | |
| 5.14.0 | 1 / 4 | |
| 5.13.0 | 1 / 4 | |
| 5.12.1 | 1 / 4 | |
| 5.12.0 | 1 / 4 | |
| 5.11.0 | 1 / 4 | |
| 5.10.0 | 1 / 4 | |
| 5.9.0 | 1 / 4 | |
| 5.8.0 | 1 / 4 | |
| 5.7.0 | 1 / 4 | |
| 5.6.0 | 1 / 4 | |
| 5.5.0 | 1 / 4 | |
| 5.4.0 | 1 / 4 | |
| 5.3.0 | 1 / 4 | |
| 5.2.0 | 1 / 4 | |
| 5.1.0 | 1 / 4 | |
| 5.0.0 | 1 / 4 | |
| 4.15.0 | 1 / 4 | |
| 4.14.0 | 1 / 4 | |
| 4.13.0 | 1 / 4 | |
| 4.12.0 | 1 / 4 | |
| 4.11.0 | 1 / 4 | |
| 4.10.0 | 1 / 4 | |
| 4.9.0 | 1 / 4 | |
| 4.8.0 | 1 / 4 | |
| 4.7.1 | 1 / 4 | |
| 4.7.0 | 1 / 4 | |
| 4.6.0 | 1 / 4 | |
| 4.5.0 | 1 / 4 | |
| 4.4.0 | 1 / 4 | |
| 4.3.0 | 1 / 4 | |
| 4.2.0 | 1 / 4 | |
| 4.1.0 | 1 / 4 | |
| 4.0.0 | 1 / 4 | |
| 3.10.0 | 1 / 4 | |
| 3.9.0 | 1 / 4 | |
| 3.8.0 | 1 / 4 | |
| 3.7.0 | 1 / 4 | |
| 3.6.0 | 1 / 4 | |
| 3.5.0 | 1 / 4 | |
| 3.4.0 | 1 / 4 | |
| 3.3.14 | 1 / 4 | |
| 3.3.13 | 1 / 4 | |
| 3.3.12 | 1 / 4 | |
| 3.3.11 | 1 / 4 | |
| 3.3.10 | 1 / 4 | |
| 3.3.9 | 1 / 4 | |
| 3.3.8 | 1 / 4 | |
| 3.3.6 | 1 / 4 | |
| 3.3.5 | 1 / 4 | |
| 3.3.4 | 1 / 4 | |
| 3.3.3 | 1 / 4 | |
| 3.3.2 | 1 / 4 | |
| 3.3.1 | 1 / 4 | |
| 3.3.0 | 1 / 4 | |
| 3.2.5 | 1 / 4 | |
| 3.2.4 | 1 / 4 | |
| 3.2.3 | 1 / 4 | |
| 3.2.2 | 1 / 4 | |
| 3.2.1 | 1 / 4 | |
| 3.2.0 | 1 / 4 | |
| 3.1.24 | 1 / 4 | |
| 3.1.23 | 1 / 4 | |
| 3.1.22 | 1 / 4 | |
| 3.1.21 | 1 / 4 | |
| 3.1.20 | 1 / 4 | |
| 3.1.18 | 1 / 4 | |
| 3.1.16 | 1 / 4 | |
| 3.1.15 | 1 / 4 | |
| 3.1.14 | 1 / 4 | |
| 3.1.13 | 1 / 4 | |
| 3.1.12 | 1 / 4 |
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v6.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.
v5.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v5.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-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.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 2021-12-01. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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 2021-11-02. This could indicate a legitimate maintainer transition or an account compromise.
v5.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.