async-listener No license 36 versions

async-listener

npm Repository Homepage

36

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

othiym23qardwatson

Keywords

polyfillshimzestycrazedexperimental

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 occurred in 2015; qard has a strong track record (42 approved packages) and this is a decade-old legitimate transition, not a compromise.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Maintainer addition of qard dates to 2015 and is a well-established historical transition with no signs of compromise.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance on npm by many years; absence is expected and not a risk signal for this package.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process is imported to wrap/patch async behavior as part of the polyfill's core functionality; this is expected and documented behavior for this package.	ai	2026/04/24

Versions (showing 36 of 36)

Version	Deps	Published
0.6.10	2 / 1	2018-10-27
0.6.9	2 / 1	2017-12-21
0.6.8	2 / 1	2017-09-21
0.6.7	2 / 1	2017-06-23
0.6.6	2 / 1	2017-06-23
0.6.5	2 / 1	2017-04-06
0.6.4	2 / 1	2017-03-10
0.6.3	1 / 1	2016-07-25
0.6.2	1 / 1	2016-07-21
0.6.1	1 / 1	2016-07-20
0.6.0	1 / 1	2016-03-18
0.5.8	1 / 1	2016-03-08
0.5.7	1 / 1	2016-03-02
0.5.6	1 / 1	2015-08-04
0.5.5	1 / 1	2015-05-30
0.5.4	1 / 1	2015-05-30
0.5.3	1 / 1	2015-05-26
0.5.2	1 / 1	2015-04-08
0.5.1	1 / 1	2015-03-07
0.5.0	1 / 1	2015-02-19
0.4.7	1 / 1	2014-07-28
0.4.6	1 / 1	2014-07-24
0.4.5	1 / 1	2013-12-07
0.4.4	1 / 1	2013-11-30
0.4.3	1 / 1	2013-10-31
0.4.2	1 / 1	2013-10-28
0.4.1	1 / 1	2013-10-16
0.4.0	1 / 1	2013-10-13
0.3.0	1 / 1	2013-10-12
0.2.2	1 / 1	2013-10-11
0.2.1	1 / 1	2013-10-01
0.2.0	1 / 1	2013-10-01
0.1.2	1 / 1	2013-10-01
0.1.1	1 / 1	2013-09-27
0.0.3	1 / 1	2013-09-04
0.0.2	1 / 1	2013-09-02

v0.6.10

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.

v0.6.9

2 findings

HIGH Publisher changed: othiym23 → watson (on 2017-12-21) provenance

This version was published by a different npm account than previous versions on 2017-12-21. 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.

v0.6.8

2 findings

HIGH Publisher changed: othiym23 → qard (on 2017-09-21) provenance

This version was published by a different npm account than previous versions on 2017-09-21. 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.

v0.6.7

2 findings

HIGH Publisher changed: othiym23 → watson (on 2017-06-23) provenance

This version was published by a different npm account than previous versions on 2017-06-23. 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.

v0.6.6

2 findings

HIGH Publisher changed: othiym23 → watson (on 2017-06-23) provenance

This version was published by a different npm account than previous versions on 2017-06-23. 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.

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-07-25) provenance

This version was published by a different npm account than previous versions on 2016-07-25. 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.

v0.6.2

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-07-21) provenance

This version was published by a different npm account than previous versions on 2016-07-21. 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.

v0.6.1

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-07-20) provenance

This version was published by a different npm account than previous versions on 2016-07-20. 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.

v0.6.0

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-03-18) provenance

This version was published by a different npm account than previous versions on 2016-03-18. 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.

v0.5.8

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-03-08) provenance

This version was published by a different npm account than previous versions on 2016-03-08. 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.

v0.5.7

2 findings

HIGH Publisher changed: othiym23 → qard (on 2016-03-02) provenance

This version was published by a different npm account than previous versions on 2016-03-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.

v0.5.6

2 findings

HIGH Publisher changed: othiym23 → qard (on 2015-08-04) provenance

This version was published by a different npm account than previous versions on 2015-08-04. 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.

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.0.3

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.

v0.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.