gatsby-plugin-utils
Gatsby utils that help creating plugins
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal of veryspry is consistent with the already-accepted 2022 publisher transition to lekoarts within the official Gatsby org. No takeover indicators. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best-practice recommendation; absence is not a security blocker for established packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@gatsbyjs/potrace, mini-svg-data-uri, svgo) are well-established, legitimate SVG/image processing packages consistent with Gatsby plugin utility expansion. No malicious indicators. | ai | |
| phantom-deps | phantom-dep:svgo | AI (phantom-deps): Phantom dep pattern is expected for this utility package; deps may be used conditionally or re-exported for plugin consumers. | ai | |
| phantom-deps | phantom-dep:mini-svg-data-uri | AI (phantom-deps): Phantom dep pattern is expected for this utility package; deps may be used conditionally or re-exported for plugin consumers. | ai | |
| phantom-deps | phantom-dep:@gatsbyjs/potrace | AI (phantom-deps): Phantom dep pattern is expected for this utility package; deps may be used conditionally or re-exported for plugin consumers. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): kathmbeck is a Gatsby team member; maintainer additions to this well-established Gatsby monorepo package reflect normal org activity, not a takeover risk. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a widely-used, well-known SVG optimization library; its use in a Gatsby utility package is expected and benign. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from lekoarts to pieh is a known transition between Gatsby core team members; both are long-standing trusted publishers. | ai | |
| email-domain | unclaimed-email:mxstbr | AI (email-domain): Author field '@mxstbr' is a social handle, not a real email. Max Stoiber is a known Gatsby contributor. False positive on domain parsing. | ai |
Versions (showing 51 of 95)
| Version | Deps | Published |
|---|---|---|
| 4.16.0 | 9 / 7 | |
| 4.15.0 | 9 / 7 | |
| 4.14.0 | 9 / 7 | |
| 4.13.1 | 9 / 7 | |
| 4.13.0 | 9 / 7 | |
| 4.12.3 | 9 / 7 | |
| 4.12.2 | 9 / 7 | |
| 4.12.1 | 9 / 7 | |
| 4.12.0 | 9 / 7 | |
| 4.11.0 | 9 / 7 | |
| 4.10.0 | 9 / 7 | |
| 4.9.0 | 9 / 7 | |
| 4.8.0 | 9 / 7 | |
| 4.7.0 | 9 / 7 | |
| 4.6.0 | 9 / 7 | |
| 4.5.0 | 9 / 7 | |
| 4.4.0 | 9 / 7 | |
| 4.3.1 | 9 / 7 | |
| 4.3.0 | 9 / 7 | |
| 4.2.0 | 9 / 7 | |
| 4.1.0 | 12 / 7 | |
| 4.0.0 | 12 / 7 | |
| 3.19.0 | 9 / 7 | |
| 3.18.0 | 12 / 7 | |
| 3.17.1 | 12 / 7 | |
| 3.17.0 | 12 / 7 | |
| 3.16.0 | 12 / 7 | |
| 3.15.0 | 12 / 7 | |
| 3.14.0 | 12 / 7 | |
| 3.13.0 | 11 / 7 | |
| 3.12.1 | 11 / 7 | |
| 3.12.0 | 11 / 7 | |
| 3.11.0 | 11 / 7 | |
| 3.10.0 | 11 / 7 | |
| 3.9.1 | 11 / 7 | |
| 3.9.0 | 11 / 7 | |
| 3.8.0 | 11 / 7 | |
| 3.7.0 | 11 / 7 | |
| 3.6.1 | 8 / 7 | |
| 3.6.0 | 8 / 7 | |
| 3.5.1 | 8 / 7 | |
| 3.5.0 | 8 / 7 | |
| 3.4.2 | 8 / 7 | |
| 3.4.1 | 8 / 7 | |
| 3.4.0 | 7 / 7 | |
| 3.3.0 | 2 / 6 | |
| 3.2.0 | 2 / 6 | |
| 3.1.0 | 2 / 6 | |
| 3.0.0 | 2 / 6 | |
| 2.5.0 | 2 / 6 | |
| 2.4.0 | 2 / 6 |
v4.16.0
2 findingsMaintainer email '@mxstbr' uses domain 'mxstbr' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.
v4.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.
v4.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.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
2 findings[Accepted risk] Package 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.
v3.17.1
2 findings[Accepted risk] Package 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-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.17.0
2 findings[Accepted risk] Package 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.
v3.16.0
2 findings[Accepted risk] Package 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.
v3.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-08-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.14.0
2 findings[Accepted risk] Package 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.
v3.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-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
2 findings[Accepted risk] Package 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.
v3.11.0
2 findings[Accepted risk] Package 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.
v3.10.0
2 findings[Accepted risk] Package 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.
v3.9.1
1 finding[Accepted risk] Package 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 2022-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.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-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.0
2 findings[Accepted risk] Package 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.
v3.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 2022-04-12. 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 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage 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 2022-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.