babel-plugin-transform-class-properties
This plugin transforms static class properties as well as properties declared with the property initializer syntax
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): Publisher change from amasad to hzoo reflects the well-documented Babel maintainer transition; hzoo is the canonical Babel maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jmm is a known Babel team member; addition is part of the legitimate Babel org maintainer roster. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; no provenance is expected for 2015-era publishes. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 4 / 1 | |
| 6.23.0 | 4 / 1 | |
| 6.22.0 | 4 / 1 | |
| 6.19.0 | 4 / 1 | |
| 6.18.0 | 3 / 1 | |
| 6.16.0 | 3 / 1 | |
| 6.11.5 | 3 / 1 | |
| 6.10.2 | 2 / 1 | |
| 6.9.1 | 2 / 1 | |
| 6.9.0 | 2 / 1 | |
| 6.8.0 | 2 / 1 | |
| 6.6.0 | 2 / 1 | |
| 6.5.2 | 2 / 1 | |
| 6.5.0 | 2 / 1 | |
| 6.4.0 | 2 / 1 | |
| 6.3.13 | 2 / 1 | |
| 6.3.2 | 2 / 1 | |
| 6.3.0 | 2 / 1 | |
| 6.2.4 | 2 / 1 | |
| 6.2.2 | 2 / 1 | |
| 6.1.20 | 2 / 1 | |
| 6.1.18 | 2 / 1 | |
| 6.1.17 | 2 / 1 | |
| 6.1.10 | 2 / 1 | |
| 6.1.5 | 2 / 1 | |
| 6.1.4 | 2 / 1 | |
| 6.0.14 | 2 / 0 | |
| 6.0.2 | 2 / 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage 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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.1
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.8.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.5.0
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.3.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.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 2015-11-30. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.20
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.10
1 findingPackage 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.1.4
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.