gatsby-plugin-emotion
Gatsby plugin to add support for Emotion
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): lekoarts is a well-established Gatsby ecosystem publisher with 6152 approved packages and 0 rejections; the transition from marvinjudehk is a legitimate Gatsby team maintainer change. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty main is a known artifact of Gatsby plugin build process (src/ compiled via prepare script). Mass-production flag reflects prior maintainer pieh's Gatsby monorepo ownership, not spam behavior. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (serhalp-netlify, mlgualtieri-gatsby) are Netlify-affiliated, consistent with Netlify's acquisition of Gatsby. Legitimate organizational transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect Netlify's consolidation of Gatsby package ownership post-acquisition. No hostile takeover indicators. | ai |
Versions (showing 100 of 142)
| Version | Deps | Published |
|---|---|---|
| 8.16.0 | 2 / 4 | |
| 8.15.0 | 2 / 4 | |
| 8.14.0 | 2 / 4 | |
| 8.13.1 | 2 / 4 | |
| 8.13.0 | 2 / 4 | |
| 8.12.0 | 2 / 4 | |
| 8.11.0 | 2 / 4 | |
| 8.10.0 | 2 / 4 | |
| 8.9.0 | 2 / 4 | |
| 8.8.0 | 2 / 4 | |
| 8.7.0 | 2 / 4 | |
| 8.6.0 | 2 / 4 | |
| 8.5.0 | 2 / 4 | |
| 8.4.0 | 2 / 4 | |
| 8.3.0 | 2 / 4 | |
| 8.2.0 | 2 / 4 | |
| 8.1.0 | 2 / 4 | |
| 8.0.0 | 2 / 4 | |
| 7.25.0 | 2 / 4 | |
| 7.24.0 | 2 / 4 | |
| 7.23.0 | 2 / 4 | |
| 7.22.0 | 2 / 4 | |
| 7.21.0 | 2 / 4 | |
| 7.20.0 | 2 / 4 | |
| 7.19.0 | 2 / 4 | |
| 7.18.0 | 2 / 4 | |
| 7.17.0 | 2 / 4 | |
| 7.16.0 | 2 / 4 | |
| 7.15.0 | 2 / 4 | |
| 7.14.0 | 2 / 4 | |
| 7.13.0 | 2 / 4 | |
| 7.12.1 | 2 / 4 | |
| 7.12.0 | 2 / 4 | |
| 7.11.0 | 2 / 4 | |
| 7.10.0 | 2 / 4 | |
| 7.9.0 | 2 / 4 | |
| 7.8.0 | 2 / 4 | |
| 7.7.0 | 2 / 4 | |
| 7.6.0 | 2 / 4 | |
| 7.5.0 | 2 / 4 | |
| 7.4.0 | 2 / 4 | |
| 7.3.0 | 2 / 4 | |
| 7.2.0 | 2 / 4 | |
| 7.1.0 | 2 / 4 | |
| 7.0.0 | 2 / 4 | |
| 6.15.0 | 2 / 4 | |
| 6.14.0 | 2 / 4 | |
| 6.13.0 | 2 / 4 | |
| 6.12.0 | 2 / 4 | |
| 6.11.0 | 2 / 4 | |
| 6.10.0 | 2 / 4 | |
| 6.9.0 | 2 / 4 | |
| 6.8.0 | 2 / 4 | |
| 6.7.1 | 2 / 4 | |
| 6.7.0 | 2 / 4 | |
| 6.6.0 | 2 / 4 | |
| 6.5.0 | 2 / 4 | |
| 6.4.0 | 2 / 4 | |
| 6.3.0 | 2 / 4 | |
| 6.2.0 | 2 / 4 | |
| 6.1.0 | 2 / 4 | |
| 6.0.0 | 2 / 4 | |
| 5.4.0 | 2 / 4 | |
| 5.3.0 | 2 / 4 | |
| 5.2.0 | 2 / 4 | |
| 5.1.0 | 2 / 4 | |
| 5.0.0 | 2 / 4 | |
| 4.5.0 | 2 / 4 | |
| 4.4.0 | 2 / 4 | |
| 4.3.15 | 2 / 4 | |
| 4.3.14 | 2 / 4 | |
| 4.3.13 | 2 / 4 | |
| 4.3.12 | 2 / 4 | |
| 4.3.11 | 2 / 4 | |
| 4.3.10 | 2 / 4 | |
| 4.3.9 | 2 / 4 | |
| 4.3.8 | 2 / 4 | |
| 4.3.6 | 2 / 4 | |
| 4.3.5 | 2 / 4 | |
| 4.3.4 | 2 / 4 | |
| 4.3.3 | 2 / 4 | |
| 4.3.2 | 2 / 4 | |
| 4.3.1 | 2 / 4 | |
| 4.3.0 | 2 / 4 | |
| 4.2.3 | 2 / 4 | |
| 4.2.2 | 2 / 4 | |
| 4.2.1 | 2 / 4 | |
| 4.2.0 | 2 / 4 | |
| 4.1.25 | 2 / 4 | |
| 4.1.24 | 2 / 4 | |
| 4.1.23 | 2 / 4 | |
| 4.1.22 | 2 / 4 | |
| 4.1.21 | 2 / 4 | |
| 4.1.20 | 2 / 4 | |
| 4.1.18 | 2 / 4 | |
| 4.1.16 | 2 / 4 | |
| 4.1.15 | 2 / 4 | |
| 4.1.14 | 2 / 4 | |
| 4.1.13 | 2 / 4 | |
| 4.1.12 | 2 / 4 |
v8.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.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.
v8.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.
v8.4.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.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.
v8.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.
v8.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.
v8.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.
v7.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.