@babel/plugin-syntax-class-properties
Allow parsing of class properties
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): jlhwung is a well-established Babel core team member (156 packages, 2773 approved). Publisher rotation within the Babel team is expected and not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jlhwung is a known Babel team contributor with a long track record. Addition reflects normal team maintenance, not a takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo packages are intentionally tiny, use synchronized semver, and are mass-produced under @babel/* — all bogus-package signals are structural false positives for this ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread npm provenance adoption; published by a verified Babel core team member from the official babel/babel monorepo. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 7.12.13 | 1 / 1 | |
| 7.12.1 | 1 / 1 | |
| 7.10.4 | 1 / 1 | |
| 7.10.1 | 1 / 1 | |
| 7.8.3 | 1 / 1 | |
| 7.8.0 | 1 / 1 | |
| 7.7.4 | 1 / 1 | |
| 7.2.0 | 1 / 1 | |
| 7.0.0 | 1 / 1 | |
| 7.0.0-beta.31 | 0 / 1 |
v7.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.4
2 findingsThis version was published by a different npm account than previous versions on 2020-06-30. 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.
v7.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0-beta.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.