@octokit-next/request
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): is-plain-object and universal-user-agent are canonical Octokit ecosystem deps; their addition aligns this experimental package with the main @octokit/* library's standard dependency set. | ai | |
| source-diff | encoded-string-file:test/request.test.js | AI (source-diff): The encoded string is a hex-encoded gzip binary fixture in a test file used to mock binary HTTP responses. This is a standard testing pattern for HTTP client libraries, not a malicious payload. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from octokitbot to octokit-next-bot is a documented Octokit org transition. octokit-next-bot has 15 approved packages and 0 rejected, confirming legitimacy. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): octokit-next-bot is the Octokit organization's dedicated bot account for @octokit-next/* packages. Addition is part of a legitimate org-level transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): octokitbot removal is the other side of the same legitimate Octokit org bot account transition. No takeover indicators. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): type-fest is a TypeScript type utility used in config/type declaration files only; not a runtime import. This is a stable, expected pattern for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 5 / 1 | |
| 2.8.0 | 5 / 1 | |
| 2.7.1 | 5 / 1 | |
| 2.7.0 | 5 / 1 | |
| 2.6.1 | 5 / 1 | |
| 2.6.0 | 4 / 1 | |
| 2.5.2 | 4 / 1 | |
| 2.5.1 | 4 / 1 | |
| 2.5.0 | 4 / 1 | |
| 2.4.1 | 4 / 1 | |
| 2.4.0 | 4 / 1 | |
| 2.3.1 | 4 / 1 | |
| 2.3.0 | 4 / 1 | |
| 2.2.0 | 4 / 1 | |
| 2.1.1 | 3 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.1 | 3 / 0 | |
| 2.0.0 | 3 / 0 |
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
3 findingsThis version was published by a different npm account than previous versions on 2024-04-03. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.1
3 findingsThis version was published by a different npm account than previous versions on 2023-07-17. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
3 findingsThis version was published by a different npm account than previous versions on 2022-12-22. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
3 findingsThis version was published by a different npm account than previous versions on 2022-12-21. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
3 findingsThis version was published by a different npm account than previous versions on 2022-10-13. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
3 findingsThis version was published by a different npm account than previous versions on 2022-10-11. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
3 findingsThis version was published by a different npm account than previous versions on 2022-10-10. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
3 findingsThis version was published by a different npm account than previous versions on 2022-10-08. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
3 findingsThis version was published by a different npm account than previous versions on 2022-10-06. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
3 findingsThis version was published by a different npm account than previous versions on 2022-10-05. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
3 findingsThis version was published by a different npm account than previous versions on 2022-10-03. This could indicate a legitimate maintainer transition or an account compromise.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.