babel-plugin-syntax-async-generators MIT 18 versions

babel-plugin-syntax-async-generators

npm Repository

Allow parsing of async generator functions

18

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition from sebmck (Babel creator) to hzoo (long-time Babel core maintainer); well-documented org handoff.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): hzoo, jmm, loganfsmyth are all known Babel core team members; legitimate maintainer additions.	ai	2026/04/24
phantom-deps	phantom-dep:babel-runtime	AI (phantom-deps): babel-runtime is a standard Babel dependency used at runtime via compiled output; phantom-dep detection is a false positive.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
6.13.0	0 / 0	2016-08-04
6.8.0	1 / 1	2016-05-02
6.5.0	1 / 1	2016-02-07
6.3.13	1 / 1	2015-12-04
6.2.4	1 / 1	2015-11-25
6.1.18	1 / 1	2015-11-12
6.1.17	1 / 1	2015-11-12
6.1.16	1 / 1	2015-11-12
6.1.13	1 / 1	2015-11-12
6.1.12	1 / 1	2015-11-12
6.1.10	1 / 1	2015-11-12
6.1.8	1 / 1	2015-11-12
6.1.6	1 / 1	2015-11-12
6.1.5	1 / 1	2015-11-12
6.1.4	1 / 1	2015-11-11
6.0.15	1 / 0	2015-11-01
6.0.14	1 / 0	2015-10-30
6.0.2	1 / 0	2015-10-29

v6.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.8.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-05-02) provenance

This version was published by a different npm account than previous versions on 2016-05-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

2 findings

HIGH Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

This version was published by a different npm account than previous versions on 2016-02-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.