@babel/plugin-proposal-private-property-in-object
This plugin transforms checks for a private property in an object
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 | missing-githead | AI (provenance): Babel monorepo publishing workflow variation; trusted publisher nicolo-ribaudo with extensive track record. | ai | |
| source-diff | source-size-tripled | AI (source-diff): 704B→4KB is trivial absolute growth for an actively developed Babel plugin gaining implementation code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): All three signals are false positives for @babel/* packages: mass production is the Babel monorepo pattern, tiny payload is normal for plugin wrappers, and inflated semver reflects Babel's lockstep versioning strategy. | ai | |
| provenance | no-provenance | AI (provenance): Official Babel monorepo package published by a long-standing core team member; lack of provenance is not a meaningful risk signal for this package. | ai | |
| dependencies | unvetted-dep:@babel/plugin-syntax-private-property-in-object | AI (dependencies): Official @babel scoped package from the same monorepo; unvetted status is a registry artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@babel/helper-annotate-as-pure | AI (dependencies): Official @babel scoped package from the same monorepo; unvetted status is a registry artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@babel/helper-create-class-features-plugin | AI (dependencies): Official @babel scoped package from the same monorepo; unvetted status is a registry artifact, not a real risk. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 7.21.11 | 4 / 2 | |
| 7.21.10 | 4 / 2 | |
| 7.21.0 | 4 / 2 | |
| 7.20.5 | 4 / 2 | |
| 7.18.6 | 4 / 2 | |
| 7.17.12 | 4 / 2 | |
| 7.16.7 | 4 / 2 | |
| 7.16.5 | 4 / 2 | |
| 7.16.0 | 4 / 2 | |
| 7.15.4 | 4 / 2 | |
| 7.14.5 | 4 / 2 | |
| 7.14.0 | 4 / 2 | |
| 7.13.0 | 2 / 2 | |
| 7.12.13 | 2 / 2 | |
| 7.12.1 | 2 / 2 | |
| 7.10.4 | 2 / 2 | |
| 7.10.1 | 2 / 2 | |
| 7.10.0 | 2 / 2 |
v7.21.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.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.20.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nicolo-ribaudo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.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.12.13
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.12.1
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.10.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.10.1
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.10.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.