@babel/plugin-transform-optional-chaining
Transform optional chaining operators into a series of nil checks
Supply chain provenance
Status for the latest visible version.
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): Babel project migrated publishing to GitHub Actions CI/CD automation. This is a documented, expected transition for @babel/* packages — not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo (Henry Zhu) is a well-known Babel core maintainer, not a spam publisher. This is a stable false positive for all @babel/* packages. | ai | |
| dependencies | unvetted-dep:@babel/helper-skip-transparent-expression-wrappers | AI (dependencies): @babel/helper-skip-transparent-expression-wrappers is an official Babel internal helper from the same monorepo; it is a trusted dependency for all @babel/* plugins. | ai | |
| provenance | no-provenance | AI (provenance): Babel publishes via GitHub Actions CI without Sigstore provenance; this is consistent across the entire Babel ecosystem and not a security concern. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 2 / 4 | |
| 7.28.6 | 2 / 4 | |
| 7.28.5 | 2 / 4 | |
| 7.27.1 | 2 / 4 | |
| 7.25.9 | 2 / 4 | |
| 7.25.8 | 2 / 4 | |
| 7.25.7 | 3 / 4 | |
| 7.24.8 | 3 / 4 | |
| 7.24.7 | 3 / 4 | |
| 7.24.6 | 3 / 4 | |
| 7.24.5 | 3 / 4 | |
| 7.24.1 | 3 / 4 | |
| 7.23.4 | 3 / 4 | |
| 7.23.3 | 3 / 4 | |
| 7.23.0 | 3 / 4 | |
| 7.22.15 | 3 / 4 | |
| 7.22.12 | 3 / 4 | |
| 7.22.11 | 3 / 4 | |
| 7.22.10 | 3 / 4 | |
| 7.22.6 | 3 / 4 | |
| 7.22.5 | 3 / 4 | |
| 7.22.3 | 3 / 4 | |
| 7.22.0 | 3 / 4 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.28.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-23. 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.27.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.25.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
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.24.6
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.24.5
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.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.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.