@babel/plugin-transform-async-generator-functions
Turn async generator functions into ES2015 generators
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@babel/helper-remap-async-to-generator | AI (dependencies): First-party Babel monorepo helper package; unvetted status reflects review queue lag, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Official Babel packages published via GitHub Actions CI; lack of Sigstore provenance is a known gap for this ecosystem, not a risk indicator. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 3 / 4 | |
| 7.29.0 | 3 / 4 | |
| 7.28.6 | 3 / 4 | |
| 7.28.0 | 3 / 4 | |
| 7.27.1 | 3 / 4 | |
| 7.26.8 | 3 / 4 | |
| 7.25.9 | 3 / 4 | |
| 7.25.8 | 3 / 4 | |
| 7.25.7 | 4 / 4 | |
| 7.25.4 | 4 / 4 | |
| 7.25.0 | 4 / 4 | |
| 7.24.7 | 4 / 4 | |
| 7.24.6 | 4 / 4 | |
| 7.24.3 | 4 / 4 | |
| 7.24.1 | 4 / 4 | |
| 7.23.9 | 4 / 4 | |
| 7.23.7 | 4 / 4 | |
| 7.23.4 | 4 / 4 | |
| 7.23.3 | 4 / 4 | |
| 7.23.2 | 4 / 4 | |
| 7.22.15 | 4 / 4 | |
| 7.22.11 | 4 / 4 | |
| 7.22.10 | 4 / 4 | |
| 7.22.7 | 4 / 4 | |
| 7.22.5 | 4 / 4 | |
| 7.22.3 | 4 / 4 | |
| 7.22.0 | 4 / 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.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.28.0
1 finding[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.26.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.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.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.7
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.2
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.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.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.3
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.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.