async-lock MIT 20 versions

async-lock

npm Repository Homepage

Lock on asynchronous code

20

Versions

MIT

License

Yes

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

rogierschouten

Keywords

lockasyncconcurrencycriticalsectionmutex

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): async-lock is a well-established package (4100+ days old, 6.6M weekly downloads) from a known publisher; lack of Sigstore provenance is expected for packages of this age.	ai	2026/04/24
install-scripts	install-script:postinstall	AI (install-scripts): Postinstall script is an empty string (no-op); no code is executed. Stable false positive for this package.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
1.4.1	0 / 13	2023-12-22
1.4.0	0 / 13	2022-10-29
1.3.2	0 / 13	2022-06-25
1.3.1	0 / 13	2022-02-04
1.3.0	0 / 13	2021-04-27
1.2.8	0 / 13	2021-01-04
1.2.7	0 / 13	2021-01-04
1.2.6	0 / 13	2020-12-06
1.2.5	0 / 13	2020-12-06
1.2.4	0 / 13	2020-05-12
1.2.3	0 / 13	2020-05-11
1.2.2	0 / 13	2019-07-15
1.2.0	0 / 13	2019-03-13
1.1.4	0 / 13	2019-02-02
1.1.3	0 / 13	2018-06-08
1.1.2	0 / 13	2018-02-26
1.1.1	0 / 13	2018-02-13
1.1.0	0 / 13	2017-10-17
1.0.0	0 / 13	2017-06-29
0.3.10	1 / 12	2017-06-27

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.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.

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.8

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.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.

v1.2.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.

v1.2.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.1.4

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.1.3

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.1.2

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.1.1

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.1.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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.

v1.0.0

2 findings

HIGH Package has 'postinstall' script install-scripts

Script:

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

1 finding

INFO No provenance attestation provenance

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