babel-preset-stage-1 MIT 12 versions

babel-preset-stage-1

npm Repository Homepage

Babel preset for stage 1 plugins

12

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amasadhzoojmmloganfsmythsebmck

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Known legitimate transition from sebmck (Babel creator) to hzoo (long-time Babel maintainer) in 2016.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Published in 2016, before Sigstore/provenance existed. Expected for legacy Babel packages.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
6.24.1	3 / 0	2017-04-07
6.22.0	3 / 0	2017-01-20
6.16.0	3 / 0	2016-09-28
6.13.0	3 / 0	2016-08-04
6.5.0	5 / 0	2016-02-07
6.3.13	5 / 0	2015-12-04
6.2.4	5 / 0	2015-11-25
6.1.18	5 / 0	2015-11-12
6.1.17	5 / 0	2015-11-12
6.1.2	5 / 0	2015-11-05
6.0.15	5 / 0	2015-11-01
6.0.14	5 / 0	2015-10-30

v6.24.1

1 finding

LOW No provenance attestation provenance

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

v6.22.0

1 finding

LOW No provenance attestation provenance

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

v6.16.0

1 finding

LOW No provenance attestation provenance

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

v6.13.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-08-04) provenance

This version was published by a different npm account than previous versions on 2016-08-04. 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.

v6.5.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

This version was published by a different npm account than previous versions on 2016-02-07. 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.

v6.3.13

1 finding

LOW No provenance attestation provenance

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

v6.2.4

1 finding

LOW No provenance attestation provenance

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

v6.1.18

1 finding

LOW No provenance attestation provenance

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

v6.1.17

1 finding

LOW No provenance attestation provenance

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

v6.1.2

1 finding

LOW No provenance attestation provenance

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

v6.0.15

1 finding

LOW No provenance attestation provenance

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

v6.0.14

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.