babel-plugin-transform-es5-property-mutators
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): The sebmck→hzoo transition is the well-documented, legitimate Babel project maintainership handoff in early 2016. Not a compromise; stable historical fact for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 2 / 1 | |
| 6.22.0 | 2 / 1 | |
| 6.8.0 | 2 / 1 | |
| 6.6.5 | 2 / 1 | |
| 6.6.4 | 2 / 1 | |
| 6.6.0 | 2 / 1 | |
| 6.5.0 | 2 / 1 | |
| 6.3.13 | 2 / 1 | |
| 6.2.4 | 2 / 1 | |
| 6.1.18 | 2 / 1 | |
| 6.1.17 | 2 / 1 | |
| 6.1.4 | 2 / 1 | |
| 6.0.14 | 2 / 0 | |
| 6.0.2 | 2 / 0 |
v6.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.22.0
2 findingsThis version was published by a different npm account than previous versions on 2017-01-20. 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.8.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
2 findingsThis version was published by a different npm account than previous versions on 2016-03-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.6.4
2 findingsThis version was published by a different npm account than previous versions on 2016-03-02. 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.6.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-29. 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.5.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.