@octokit/plugin-request-log
Log all requests and request errors
Supply chain provenance
Status for the latest visible version.
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): gr2m → octokitbot is the documented Octokit org transition to their official bot publisher account; stable and expected for all Octokit packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): kfcampbell and nickfloyd are known Octokit org contributors; addition reflects legitimate org growth, not a takeover. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 0 / 11 | |
| 5.3.1 | 0 / 13 | |
| 5.3.0 | 0 / 13 | |
| 5.2.0 | 0 / 13 | |
| 5.1.1 | 0 / 13 | |
| 5.1.0 | 0 / 13 | |
| 5.0.0 | 0 / 13 | |
| 4.0.1 | 0 / 13 | |
| 4.0.0 | 0 / 13 | |
| 3.0.0 | 0 / 13 | |
| 2.0.1 | 0 / 13 | |
| 1.0.4 | 0 / 15 | |
| 1.0.3 | 0 / 15 | |
| 1.0.2 | 0 / 15 | |
| 1.0.1 | 0 / 15 | |
| 1.0.0 | 0 / 15 |
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsThis version was published by a different npm account than previous versions on 2024-03-01. 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.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-07-10. 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.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-06-12. 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.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2023-06-09. 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.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.