p-retry
Retry a promise-returning or async function
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/retry | AI (dependencies): @types/retry is intentionally included as a runtime dep in [email protected] to bundle TypeScript types; this is a deliberate design choice by sindresorhus, not a security concern. | ai | |
| phantom-deps | phantom-dep:@types/retry | AI (phantom-deps): @types/retry is a TypeScript types package; it is not directly imported at runtime by design. This is expected behavior for this package. | ai | |
| provenance | no-provenance | AI (provenance): [email protected] predates widespread provenance adoption; the package is published by a highly trusted author with a long track record. Lack of provenance is not a risk signal here. | ai | |
| dependencies | unvetted-dep:is-network-error | AI (dependencies): is-network-error is a sindresorhus package used legitimately as a runtime dependency for network error detection in retry logic; stable false positive for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 1 / 5 | |
| 7.1.1 | 1 / 4 | |
| 7.1.0 | 1 / 4 | |
| 7.0.0 | 1 / 4 | |
| 6.2.1 | 3 / 4 | |
| 6.2.0 | 3 / 4 | |
| 6.1.0 | 3 / 4 | |
| 6.0.0 | 2 / 4 | |
| 5.1.2 | 2 / 4 | |
| 5.1.1 | 2 / 4 | |
| 5.1.0 | 2 / 4 | |
| 5.0.0 | 2 / 4 | |
| 4.6.2 | 2 / 4 | |
| 4.6.1 | 2 / 4 | |
| 4.6.0 | 2 / 4 | |
| 4.5.0 | 2 / 4 | |
| 4.4.0 | 2 / 4 | |
| 4.3.0 | 2 / 4 | |
| 4.2.0 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.0 | 2 / 4 | |
| 3.0.1 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.0.0 | 1 / 3 | |
| 1.0.0 | 1 / 3 |
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.