@babel/helper-skip-transparent-expression-wrappers
Helper which skips types and parentheses
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from jlhwung to nicolo-ribaudo is a normal rotation among Babel core team members; both are established maintainers. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo helper: mass-produced templated names, no keywords, tiny payload, and inflated semver are all expected patterns for @babel/* helper packages published in lockstep with the monorepo version. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2020 before npm Sigstore provenance was available; absence is expected for this era of Babel releases. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 2 / 0 | |
| 7.27.1 | 2 / 0 | |
| 7.25.9 | 2 / 0 | |
| 7.25.7 | 2 / 0 | |
| 7.24.7 | 2 / 0 | |
| 7.24.6 | 1 / 1 | |
| 7.22.5 | 1 / 1 | |
| 7.20.0 | 1 / 1 | |
| 7.18.9 | 1 / 1 | |
| 7.18.6 | 1 / 1 | |
| 7.16.0 | 1 / 1 | |
| 7.15.4 | 1 / 1 | |
| 7.14.5 | 1 / 1 | |
| 7.12.1 | 1 / 1 | |
| 7.11.0 | 1 / 1 |
v7.29.7
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.
v7.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.6
1 findingPackage 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.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.5
2 findingsThis version was published by a different npm account than previous versions on 2021-06-09. 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.12.1
2 findingsThis version was published by a different npm account than previous versions on 2020-10-15. 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.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.