babel-preset-stage-3 MIT 13 versions

babel-preset-stage-3

npm Repository Homepage

Babel preset for stage 3 plugins

13

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): The sebmck→hzoo transition is a well-documented legitimate Babel maintainer handoff in 2016; hzoo is a known Babel core maintainer. This is stable for this package.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Legitimate Babel core package from the official babel/babel monorepo. Spam-flagged maintainers are the actual Babel team; mass-production and tiny payload are expected for a preset package.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by years; no provenance is expected for this legacy Babel 6 release.	ai	2026/04/23

Versions (showing 13 of 13)

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

v6.24.1

2 findings

HIGH Low-value / spam package indicators (4 signals, score 8) bogus-package

Matched 4 signal(s), weighted score 8: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: amasad, jmm, sebmck, thejameskyle, hzoo, loganfsmyth. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_KEYWORDS] No keywords declared. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 3453 bytes total.

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

INFO No provenance attestation provenance

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

v6.17.0

1 finding

INFO No provenance attestation provenance

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

v6.16.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-09-28) provenance

This version was published by a different npm account than previous versions on 2016-09-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v6.11.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-06-27) provenance

This version was published by a different npm account than previous versions on 2016-06-27. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] 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.

INFO No provenance attestation provenance

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

v6.3.13

1 finding

INFO No provenance attestation provenance

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

v6.2.4

1 finding

INFO No provenance attestation provenance

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

v6.1.18

1 finding

INFO No provenance attestation provenance

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

v6.1.17

1 finding

INFO No provenance attestation provenance

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

v6.1.2

1 finding

INFO No provenance attestation provenance

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

v6.0.15

1 finding

INFO No provenance attestation provenance

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

v6.0.14

1 finding

INFO No provenance attestation provenance

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