babel-plugin-transform-es2015-parameters
Compile ES2015 default and rest parameters to ES5
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from amasad to hzoo, both well-known Babel core maintainers. This is a documented team change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): amasad and thejameskyle are well-known Babel core team members; their addition is a legitimate team expansion, not a suspicious takeover. Stable for this package. | ai | |
| dependencies | unvetted-dep:babel-traverse | AI (dependencies): babel-traverse is a first-party Babel monorepo package published by the same team; not a third-party risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; no provenance is expected and consistent across all versions of this legacy Babel plugin. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 6 / 1 | |
| 6.23.0 | 6 / 1 | |
| 6.22.0 | 6 / 1 | |
| 6.21.0 | 6 / 1 | |
| 6.18.0 | 6 / 1 | |
| 6.17.0 | 6 / 1 | |
| 6.16.0 | 6 / 1 | |
| 6.11.4 | 6 / 1 | |
| 6.11.3 | 6 / 1 | |
| 6.8.0 | 6 / 1 | |
| 6.7.0 | 6 / 1 | |
| 6.6.5 | 6 / 1 | |
| 6.6.4 | 6 / 1 | |
| 6.6.0 | 6 / 1 | |
| 6.4.2 | 6 / 1 | |
| 6.4.0 | 6 / 1 | |
| 6.3.26 | 6 / 1 | |
| 6.3.21 | 6 / 1 | |
| 6.3.18 | 6 / 1 | |
| 6.3.13 | 6 / 1 | |
| 6.1.4 | 6 / 1 | |
| 6.0.14 | 6 / 0 | |
| 6.0.2 | 6 / 0 |
v6.24.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 2017-04-07. This could indicate a legitimate maintainer transition or an account compromise.
v6.23.0
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 2017-02-14. This could indicate a legitimate maintainer transition or an account compromise.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.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.17.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.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
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-05-02. This could indicate a legitimate maintainer transition or an account compromise.
v6.7.0
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-03-09. This could indicate a legitimate maintainer transition or an account compromise.
v6.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
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.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findingsThis version was published by a different npm account than previous versions on 2016-01-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.18
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 2015-12-14. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.13
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.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.