@babel/plugin-syntax-logical-assignment-operators
Allow parsing of the logical assignment operators
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Official Babel monorepo package: mass-produced templated names, tiny payload, and inflated semver are all expected characteristics of @babel/* scoped plugins published in lockstep from the monorepo. | ai | |
| provenance | no-provenance | AI (provenance): This version predates Sigstore provenance on npm; absence of attestation is expected for packages published in 2020. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 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 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.