@octokit-next/types
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): Publisher change from octokitbot to octokit-next-bot reflects a legitimate bot account transition within the official Octokit GitHub org; octokit-next-bot has 11 approved packages and 0 rejected. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): octokit-next-bot is an established Octokit org bot account with a clean track record; addition is consistent with org-level bot consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of octokitbot paired with addition of octokit-next-bot is consistent with a bot account rename/consolidation within the Octokit org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by publish is explained by the org-level bot account transition; no malicious payload or script changes present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a TypeScript types sub-package in the Octokit Next monorepo. Sparse README and no keywords are expected for internal/programmatic type definition packages. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 3 / 0 | |
| 2.8.0 | 3 / 0 | |
| 2.7.1 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.2 | 3 / 0 | |
| 2.5.1 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.1 | 0 / 0 | |
| 2.4.0 | 0 / 0 | |
| 2.3.1 | 0 / 0 | |
| 2.3.0 | 0 / 0 | |
| 2.2.0 | 0 / 0 | |
| 2.1.1 | 0 / 0 | |
| 2.1.0 | 0 / 0 | |
| 2.0.1 | 0 / 0 | |
| 2.0.0 | 0 / 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
2 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.1
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 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.
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.