@babel/plugin-proposal-async-do-expressions
Transform async do expressions to ES2021
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Official Babel monorepo plugin. Mass-production, tiny payload, and inflated semver signals are all expected for @babel/* packages versioned in lockstep from the monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Package predates widespread Sigstore provenance adoption; published by a trusted Babel core contributor from the official monorepo. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 2 / 2 | |
| 7.27.1 | 2 / 2 | |
| 7.25.9 | 2 / 2 | |
| 7.25.8 | 2 / 2 | |
| 7.25.7 | 3 / 2 | |
| 7.25.6 | 3 / 2 | |
| 7.25.0 | 3 / 2 | |
| 7.24.7 | 3 / 4 | |
| 7.24.6 | 3 / 4 | |
| 7.24.1 | 3 / 4 | |
| 7.23.3 | 3 / 4 | |
| 7.22.5 | 3 / 4 | |
| 7.18.6 | 3 / 4 | |
| 7.17.12 | 3 / 4 | |
| 7.16.7 | 3 / 4 | |
| 7.16.0 | 3 / 4 | |
| 7.14.5 | 3 / 4 | |
| 7.14.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.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.8
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.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
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.24.1
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.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.