babel-plugin-transform-es2015-classes
Compile ES2015 classes 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 contributors; their addition is a legitimate team expansion, not a suspicious takeover. | ai | |
| dependencies | unvetted-dep:babel-traverse | AI (dependencies): babel-traverse is a core Babel ecosystem package published by the same org; flagging it as unvetted is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Legacy Babel package predating Sigstore provenance; no provenance is expected and stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged maintainers (hzoo, loganfsmyth, sebmck, thejameskyle, etc.) are well-known Babel core contributors; spam designation is a false positive for this established official Babel package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from loganfsmyth to hzoo is a legitimate Babel core team maintainer change in 2017; both are known Babel contributors. | ai | |
| phantom-deps | phantom-dep:babel-messages | AI (phantom-deps): babel-messages is a legitimate Babel package listed as a dependency; phantom-dep finding is a false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 9 / 1 | |
| 6.23.0 | 9 / 1 | |
| 6.22.0 | 9 / 1 | |
| 6.18.0 | 9 / 1 | |
| 6.14.0 | 9 / 1 | |
| 6.9.0 | 9 / 1 | |
| 6.6.0 | 9 / 1 | |
| 6.5.2 | 9 / 1 | |
| 6.4.5 | 9 / 1 | |
| 6.4.0 | 9 / 1 | |
| 6.3.13 | 9 / 1 | |
| 6.2.4 | 9 / 1 | |
| 6.2.2 | 9 / 1 | |
| 6.2.0 | 9 / 1 | |
| 6.1.21 | 9 / 1 | |
| 6.1.18 | 9 / 1 | |
| 6.1.10 | 9 / 1 | |
| 6.1.5 | 9 / 1 | |
| 6.0.15 | 9 / 0 | |
| 6.0.8 | 9 / 0 |
v6.24.1
2 findingsThis 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.
Package 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.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.14.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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.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-01-06. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.13
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-04. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.21
1 findingPackage 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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package 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.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.