async-helpers No license 27 versions

async-helpers

npm Repository Homepage

27

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

doowbjonschlinkert

Keywords

asyncenginehandlebarshelperhelperslodashtemplatetemplatesunderscore

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 from doowb to jonschlinkert occurred in 2015; jonschlinkert is a highly trusted npm publisher with 1964 approved packages. This is a historical, legitimate maintainer transition.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected for packages of this age and is not a risk signal.	ai	2026/04/24

Versions (showing 27 of 27)

Version	Deps	Published
0.3.17	2 / 9	2017-12-14
0.3.16	3 / 9	2017-11-05
0.3.15	3 / 9	2017-11-05
0.3.14	5 / 9	2017-01-27
0.3.13	5 / 9	2017-01-26
0.3.12	5 / 9	2017-01-26
0.3.11	5 / 9	2017-01-25
0.3.10	5 / 9	2017-01-25
0.3.9	3 / 5	2016-06-06
0.3.8	3 / 5	2016-05-02
0.3.7	3 / 5	2016-03-11
0.3.6	3 / 5	2016-03-10
0.3.5	3 / 3	2015-12-29
0.3.4	3 / 3	2015-08-31
0.3.3	3 / 3	2015-08-21
0.3.2	3 / 3	2015-07-23
0.3.0	1 / 3	2015-06-18
0.2.5	1 / 3	2015-06-05
0.2.4	1 / 3	2015-06-01
0.2.3	1 / 3	2015-06-01
0.2.2	1 / 3	2015-05-31
0.2.1	1 / 3	2015-04-25
0.2.0	1 / 3	2015-04-23
0.1.3	1 / 3	2015-04-17
0.1.2	1 / 3	2015-03-27
0.1.1	1 / 3	2015-03-18
0.1.0	1 / 3	2015-03-18

v0.3.17

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2017-11-05) provenance

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2017-11-05) provenance

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2017-01-27) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.3.12

1 finding

LOW No provenance attestation provenance

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

v0.3.11

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2017-01-25) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-08-21) provenance

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

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-06-18) provenance

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-06-05) provenance

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

1 finding

LOW No provenance attestation provenance

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

v0.2.3

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-04-25) provenance

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-04-23) provenance

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

2 findings

HIGH Publisher changed: doowb → jonschlinkert (on 2015-04-17) provenance

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

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.