babel-preset-es2015
Babel preset for all es2015 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): sebmck → hzoo is a well-documented Babel project maintainer transition; hzoo is a core Babel team member with extensive track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tiny payload is expected for a preset aggregating plugins via deps. Mass-production signal reflects Babel monorepo structure, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2016, before Sigstore provenance existed. Not actionable for historical versions. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 24 / 2 | |
| 6.24.0 | 24 / 2 | |
| 6.22.0 | 24 / 2 | |
| 6.18.0 | 24 / 2 | |
| 6.16.0 | 24 / 2 | |
| 6.14.0 | 24 / 2 | |
| 6.13.2 | 24 / 2 | |
| 6.13.1 | 24 / 1 | |
| 6.13.0 | 24 / 1 | |
| 6.9.0 | 21 / 1 | |
| 6.6.0 | 21 / 1 | |
| 6.5.0 | 20 / 1 | |
| 6.3.13 | 20 / 1 | |
| 6.2.4 | 20 / 1 | |
| 6.1.18 | 20 / 1 | |
| 6.1.17 | 20 / 1 | |
| 6.1.4 | 20 / 1 | |
| 6.1.2 | 20 / 0 | |
| 6.0.15 | 20 / 0 | |
| 6.0.14 | 20 / 0 | |
| 6.0.12 | 20 / 0 | |
| 6.0.11 | 20 / 0 | |
| 6.0.8 | 19 / 0 | |
| 6.0.2 | 19 / 0 |
v6.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.2
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 2016-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v6.13.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 2016-08-05. This could indicate a legitimate maintainer transition or an account compromise.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.