babel-plugin-transform-es2015-block-scoping
Compile ES2015 block scoping (const and let) 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): amasad and thejameskyle are well-known Babel core team members; their addition is a legitimate and expected contributor expansion for this official Babel package. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from sebmck (Babel creator) to hzoo (long-time Babel core maintainer). Well-documented project handoff. | ai | |
| dependencies | unvetted-dep:babel-traverse | AI (dependencies): babel-traverse is a core Babel ecosystem package and a natural, expected dependency for any Babel transform plugin. Not a risk signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence of attestation is expected for this era of Babel tooling and not a risk signal. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.26.0 | 5 / 1 | |
| 6.23.0 | 5 / 1 | |
| 6.21.0 | 5 / 1 | |
| 6.5.0 | 5 / 1 | |
| 6.4.0 | 5 / 1 | |
| 6.1.10 | 5 / 1 |
v6.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.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-02-07. This could indicate a legitimate maintainer transition or an account compromise.
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.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.