promise-retry
Retries a function that returns a promise, leveraging the power of the retry module.
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): Legitimate maintainer transition to achingbrain, a highly trusted publisher (787 approved, 0 rejected). Change occurred in 2020 with no code anomalies. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020 before Sigstore provenance was available; no security concern for this established package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.1.1 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.2 | 3 / 3 | |
| 1.0.1 | 3 / 3 | |
| 1.0.0 | 3 / 3 | |
| 0.2.9 | 3 / 2 | |
| 0.2.8 | 3 / 2 | |
| 0.2.7 | 3 / 2 | |
| 0.2.6 | 3 / 2 | |
| 0.2.5 | 3 / 2 | |
| 0.2.4 | 3 / 2 | |
| 0.2.3 | 3 / 2 | |
| 0.2.2 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.1 | 3 / 2 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-06-13. 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.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.