gatsby-script — Greenflagged

An enhanced script component for Gatsby sites with support for various loading strategies

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

piehkathmbeckserhalp-netlifymlgualtieri-gatsbyfktylerbarnesdaniellewgatsby

Keywords

gatsby

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/index.modern.mjs	AI (source-diff): Minified output from microbundle build tool, not obfuscation. Standard React component code visible in sample. Stable for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from pieh to serhalp-netlify reflects Gatsby's transition to Netlify stewardship; new publisher has strong track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are Netlify-affiliated, consistent with Gatsby's organizational transition to Netlify.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers are former Gatsby team members; removal aligns with known org transition.	ai	2026/04/24

Versions (showing 29 of 29)

Show 3 prereleases

Version	Deps	Published
2.16.0	0 / 7	2026-01-26
2.15.0	0 / 7	2025-08-27
2.14.0	0 / 7	2024-11-06
2.13.0	0 / 7	2023-12-18
2.12.0	0 / 7	2023-08-24
2.11.0	0 / 7	2023-06-15
2.10.0	0 / 7	2023-05-16
2.9.0	0 / 7	2023-04-18
2.8.0	0 / 7	2023-03-21
2.7.0	0 / 7	2023-02-21
2.6.0	0 / 7	2023-02-07
2.5.0	0 / 7	2023-01-24
2.4.0	0 / 7	2023-01-10
2.3.0	0 / 7	2022-12-13
2.2.0	0 / 7	2022-11-25
2.1.0	0 / 7	2022-11-22
2.0.0	0 / 7	2022-11-08
1.10.0	0 / 7	2022-12-07
1.9.0	0 / 7	2022-09-27
1.8.0	0 / 6	2022-09-13
1.7.0	0 / 5	2022-08-30
1.6.0	0 / 5	2022-08-16
1.5.0	0 / 5	2022-08-02
1.4.0	0 / 5	2022-07-19
1.3.0	0 / 8	2022-07-05
1.2.0	0 / 8	2022-06-21
1.1.0	0 / 8	2022-06-07
1.0.1	0 / 8	2022-06-01
1.0.0	0 / 8	2022-05-24

v2.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.0

2 findings

HIGH Publisher changed: pieh → serhalp-netlify (on 2024-11-06) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → pieh (on 2023-12-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-18. This could indicate a legitimate maintainer transition or an account compromise.

v2.12.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → pieh (on 2023-08-24) provenance

[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.

v2.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → lekoarts (on 2023-04-18) provenance

[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.

v2.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → pieh (on 2023-02-21) provenance

[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.

v2.6.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → lekoarts (on 2023-02-07) provenance

[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.

v2.5.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → pieh (on 2023-01-24) provenance

[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.

v2.4.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marvinjudehk → lekoarts (on 2023-01-10) provenance

[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.

v2.3.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → marvinjudehk (on 2022-12-13) provenance

[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.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → tyhopp (on 2022-11-22) provenance

[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.

v2.0.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marvinjudehk → pieh (on 2022-11-08) provenance

[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.

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tyhopp → marvinjudehk (on 2022-09-27) provenance

[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.

v1.8.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → tyhopp (on 2022-09-13) provenance

[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.

v1.7.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marvinjudehk → pieh (on 2022-08-30) provenance

[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.

v1.6.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → marvinjudehk (on 2022-08-16) provenance

[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.

v1.5.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: lekoarts → pieh (on 2022-08-02) provenance

[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.

v1.4.0

3 findings

HIGH New obfuscated file: dist/index.modern.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: j0sh77 → lekoarts (on 2022-07-19) provenance

[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.

v1.3.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tyhopp → j0sh77 (on 2022-07-05) provenance

[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.

v1.2.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: marvinjudehk → tyhopp (on 2022-06-21) provenance

[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.

v1.1.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pieh → marvinjudehk (on 2022-06-07) provenance

[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.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.