gatsby-plugin-react-helmet-async Apache-2.0 22 versions

gatsby-plugin-react-helmet-async

npm Repository Homepage

Use react-helmet-async with Gatsby

22

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

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

martinbrosenbergme4502

Keywords

gatsbygatsby-pluginreactreact-helmetreact-helmet-async

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from martinbrosenberg to me4502 is corroborated by the GitHub repo being under the Me4502 org; consistent with a legitimate ownership transfer.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): me4502 is an established npm account (22 approved packages) and the GitHub repo URL matches; this is a legitimate maintainer transition.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
1.2.3	0 / 21	2022-08-04
1.2.2	0 / 21	2022-06-15
1.2.1	0 / 14	2022-01-07
1.2.0	0 / 14	2021-03-09
1.1.1	0 / 16	2021-02-12
1.1.0	0 / 16	2020-08-26
1.0.16	0 / 16	2020-03-06
1.0.15	0 / 16	2020-01-29
1.0.14	0 / 16	2020-01-05
1.0.13	0 / 16	2019-12-08
1.0.12	0 / 17	2019-11-30
1.0.11	0 / 17	2019-11-19
1.0.10	0 / 17	2019-11-17
1.0.9	0 / 17	2019-11-13
1.0.8	0 / 17	2019-11-08
1.0.7	0 / 17	2019-11-06
1.0.6	0 / 17	2019-11-02
1.0.5	0 / 17	2019-10-31
1.0.4	0 / 17	2019-10-30
1.0.3	0 / 17	2019-10-28
1.0.2	0 / 17	2019-10-28
1.0.1	0 / 17	2019-10-28

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

2 findings

HIGH Publisher changed: martinbrosenberg → me4502 (on 2022-06-15) provenance

This version was published by a different npm account than previous versions on 2022-06-15. 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.

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.16

1 finding

LOW No provenance attestation provenance

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

v1.0.15

1 finding

LOW No provenance attestation provenance

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

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

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.