parley
Practical, lightweight flow control for Node.js. Supports `await`, callbacks and promises.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): eashaw is a well-established publisher (846 approved packages) associated with the Sails.js ecosystem; transition from mikermcneil is a legitimate org handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): eashaw has a strong track record (846 approved/1 rejected) and is part of the same ecosystem; maintainer addition is a legitimate transition. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 3 / 3 | |
| 3.8.3 | 3 / 3 | |
| 3.8.2 | 3 / 3 | |
| 3.8.1 | 3 / 3 | |
| 3.8.0 | 3 / 3 | |
| 3.7.0 | 3 / 3 | |
| 3.6.1 | 3 / 3 | |
| 3.6.0 | 3 / 3 | |
| 3.5.2 | 3 / 3 | |
| 3.5.1 | 3 / 3 | |
| 3.5.0 | 3 / 3 | |
| 3.4.4 | 3 / 3 | |
| 3.4.3 | 3 / 3 | |
| 3.4.2 | 3 / 3 | |
| 3.4.1 | 3 / 3 | |
| 3.4.0 | 3 / 3 | |
| 3.3.4 | 3 / 3 | |
| 3.3.3 | 3 / 3 | |
| 3.3.2 | 3 / 3 | |
| 3.3.1 | 3 / 3 | |
| 3.3.0 | 3 / 3 | |
| 3.2.3 | 3 / 3 | |
| 3.2.2 | 3 / 3 | |
| 3.2.1 | 3 / 3 | |
| 3.2.0 | 3 / 3 | |
| 3.1.0 | 3 / 3 | |
| 3.0.0 | 3 / 3 | |
| 2.3.1 | 2 / 3 | |
| 2.3.0 | 2 / 3 | |
| 2.2.0 | 2 / 3 | |
| 2.1.1 | 2 / 3 | |
| 2.1.0 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 2 | |
| 0.0.2 | 2 / 0 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.