babel-plugin-transform-async-to-generator
Turn async functions into ES2015 generators
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): amasad → sebmck is a known legitimate transition within the Babel core team; sebmck is the Babel creator. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jmm is a known Babel team member; normal team membership change for the Babel monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo plugin; maintainers (hzoo, sebmck, loganfsmyth, etc.) are canonical Babel team. Tiny payload and mass-production signals are expected for focused monorepo packages. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is injected into transformed output by Babel helpers, not directly imported in plugin source. Standard pattern for Babel plugins. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; published in 2017. No provenance expected for legacy Babel 6 packages. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 3 / 1 | |
| 6.22.0 | 3 / 1 | |
| 6.16.0 | 3 / 1 | |
| 6.8.0 | 3 / 1 | |
| 6.7.4 | 3 / 1 | |
| 6.7.0 | 3 / 1 | |
| 6.5.0 | 3 / 1 | |
| 6.4.6 | 3 / 1 | |
| 6.4.5 | 3 / 1 | |
| 6.4.0 | 3 / 1 | |
| 6.3.13 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.2.4 | 3 / 1 | |
| 6.1.18 | 3 / 1 | |
| 6.1.17 | 3 / 1 | |
| 6.1.13 | 3 / 1 | |
| 6.1.10 | 3 / 1 | |
| 6.1.5 | 3 / 1 | |
| 6.1.4 | 3 / 1 | |
| 6.0.14 | 3 / 0 | |
| 6.0.2 | 3 / 0 |
v6.24.1
2 findingsMatched 3 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jmm, sebmck, amasad, thejameskyle, hzoo, loganfsmyth. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 2219 bytes total.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-09-28. This could indicate a legitimate maintainer transition or an account compromise.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-23. This could indicate a legitimate maintainer transition or an account compromise.
v6.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-09. This could indicate a legitimate maintainer transition or an account compromise.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-01-20. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findingsThis version was published by a different npm account than previous versions on 2016-01-06. 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.
v6.3.13
2 findingsThis version was published by a different npm account than previous versions on 2015-12-04. 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.
v6.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-11-30. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.