← Home

promise-coalesce

npm Repository Homepage

Coalesces multiple promises for the same identifier into a single request

6
Versions
BSD-3-Clause
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

douglascayers

Keywords

promisecoalesceasync

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): postinstall runs `husky install` — a dev tool accidentally left in scripts. Husky is a devDep so it's absent at install time; harmless failure. Not malicious. ai
provenance no-provenance AI (provenance): No provenance is common (~12% adoption). Package is well-established with 660k weekly downloads and clean history. ai

Versions (showing 6 of 6)

Version Deps Published
1.5.0 0 / 21
1.3.0 0 / 21
1.1.2 0 / 21
1.1.1 0 / 21
1.1.0 0 / 21
1.0.0 0 / 21

v1.5.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.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

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

v1.0.0

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: husky install

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.