@octokit/plugin-retry
Automatic retry plugin for octokit
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Octokit org migrated publishing from octokitbot to GitHub Actions CI/CD with SLSA provenance; this is a legitimate infrastructure transition for all octokit/* packages. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 8.1.0 | 3 / 11 | |
| 8.0.3 | 3 / 11 | |
| 8.0.2 | 3 / 11 | |
| 8.0.1 | 3 / 11 | |
| 8.0.0 | 3 / 11 | |
| 7.2.1 | 3 / 11 | |
| 7.2.0 | 3 / 11 | |
| 7.1.4 | 3 / 11 | |
| 7.1.3 | 3 / 11 | |
| 7.1.2 | 3 / 11 | |
| 7.1.1 | 3 / 13 | |
| 7.1.0 | 3 / 13 | |
| 7.0.4 | 3 / 13 | |
| 7.0.3 | 3 / 13 | |
| 7.0.2 | 3 / 13 | |
| 7.0.1 | 3 / 13 | |
| 7.0.0 | 3 / 13 | |
| 6.1.0 | 3 / 13 | |
| 6.0.1 | 3 / 13 | |
| 6.0.0 | 3 / 13 | |
| 5.0.5 | 3 / 13 | |
| 5.0.4 | 3 / 13 | |
| 5.0.3 | 3 / 13 | |
| 5.0.2 | 2 / 14 | |
| 5.0.1 | 2 / 14 | |
| 5.0.0 | 2 / 14 | |
| 4.1.6 | 2 / 14 | |
| 4.1.5 | 2 / 14 | |
| 4.1.4 | 2 / 14 | |
| 4.1.3 | 2 / 15 | |
| 4.1.2 | 2 / 15 | |
| 4.1.1 | 2 / 15 | |
| 4.1.0 | 2 / 15 | |
| 4.0.4 | 2 / 15 | |
| 4.0.3 | 2 / 15 | |
| 3.0.9 | 2 / 16 | |
| 3.0.8 | 2 / 16 | |
| 3.0.7 | 2 / 16 | |
| 3.0.6 | 2 / 16 | |
| 3.0.5 | 2 / 16 | |
| 3.0.4 | 2 / 16 | |
| 3.0.3 | 2 / 16 | |
| 3.0.2 | 2 / 16 | |
| 3.0.1 | 2 / 16 | |
| 3.0.0 | 2 / 16 | |
| 2.2.0 | 1 / 9 | |
| 2.1.2 | 1 / 9 | |
| 2.1.1 | 1 / 9 | |
| 2.1.0 | 1 / 8 | |
| 2.0.0 | 1 / 8 | |
| 1.0.0 | 1 / 8 |
v8.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.