@octokit/graphql
GitHub GraphQL API client for browsers and Node
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of bkeepers is consistent with normal Octokit org maintainer rotation; no hostile takeover indicators. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from 1KB to 14KB reflects compiled TypeScript dist output (dist-node, dist-web, dist-types) in a major version release — standard Octokit build pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @octokit/types is a first-party Octokit types package; entirely expected dependency for this TypeScript-based library. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (kfcampbell, nickfloyd) are Octokit org contributors; publishing still done via octokitbot automation. Routine org maintainer rotation. | ai | |
| provenance | no-provenance | AI (provenance): Published by the official octokitbot before Sigstore provenance was standard practice. Low risk given publisher track record. | ai | |
| provenance | missing-githead | AI (provenance): Octokit migrated to @pika/pack for v4.x builds; this tool does not inject gitHead. The absence is a build tooling artifact, not a supply chain indicator, and is stable for this package. | ai | |
| dependencies | unvetted-dep:@octokit/request | AI (dependencies): @octokit/request is a core Octokit ecosystem package; a stable, expected dependency for @octokit/graphql. | ai | |
| dependencies | unvetted-dep:@octokit/types | AI (dependencies): @octokit/types is a core Octokit ecosystem package; a stable, expected dependency for all @octokit/* packages. | ai | |
| dependencies | unvetted-dep:universal-user-agent | AI (dependencies): universal-user-agent is a well-known, stable utility used across the Octokit ecosystem for browser/Node user-agent strings. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 9.0.3 | 3 / 10 | |
| 9.0.2 | 3 / 10 | |
| 9.0.1 | 3 / 10 | |
| 9.0.0 | 3 / 10 | |
| 8.2.2 | 3 / 10 | |
| 8.2.1 | 3 / 11 | |
| 8.2.0 | 3 / 11 | |
| 8.1.2 | 3 / 12 | |
| 8.1.1 | 3 / 12 | |
| 8.1.0 | 3 / 12 | |
| 8.0.2 | 3 / 12 | |
| 8.0.1 | 3 / 12 | |
| 8.0.0 | 3 / 12 | |
| 7.1.1 | 3 / 11 | |
| 7.1.0 | 3 / 12 | |
| 7.0.2 | 3 / 12 | |
| 7.0.1 | 3 / 12 | |
| 7.0.0 | 3 / 12 | |
| 6.0.1 | 3 / 12 | |
| 6.0.0 | 3 / 12 | |
| 5.0.6 | 3 / 12 | |
| 5.0.5 | 3 / 13 | |
| 5.0.4 | 3 / 13 | |
| 5.0.3 | 3 / 13 | |
| 5.0.2 | 3 / 13 | |
| 5.0.1 | 3 / 13 | |
| 5.0.0 | 3 / 13 | |
| 4.8.0 | 3 / 14 | |
| 4.7.0 | 3 / 14 | |
| 4.6.4 | 3 / 14 | |
| 4.6.3 | 3 / 14 | |
| 4.6.2 | 3 / 14 | |
| 4.6.1 | 3 / 14 | |
| 4.6.0 | 3 / 14 | |
| 4.5.9 | 3 / 14 | |
| 4.5.8 | 3 / 14 | |
| 4.5.7 | 3 / 14 | |
| 4.5.6 | 3 / 14 | |
| 4.5.5 | 3 / 14 | |
| 4.5.4 | 3 / 14 | |
| 4.5.3 | 3 / 14 | |
| 4.5.2 | 3 / 14 | |
| 4.5.1 | 3 / 14 | |
| 4.5.0 | 3 / 14 | |
| 4.4.1 | 3 / 14 | |
| 4.4.0 | 3 / 14 | |
| 4.3.1 | 3 / 14 | |
| 4.3.0 | 3 / 14 | |
| 4.2.2 | 2 / 14 | |
| 4.2.1 | 2 / 14 | |
| 4.2.0 | 2 / 14 | |
| 4.1.0 | 2 / 14 | |
| 4.0.1 | 2 / 14 | |
| 4.0.0 | 2 / 14 | |
| 3.0.1 | 2 / 15 | |
| 3.0.0 | 2 / 15 | |
| 2.3.0 | 3 / 0 | |
| 2.1.3 | 2 / 15 | |
| 2.1.2 | 2 / 15 | |
| 2.1.1 | 2 / 15 | |
| 2.1.0 | 2 / 15 | |
| 2.0.2 | 2 / 15 | |
| 2.0.1 | 1 / 15 | |
| 2.0.0 | 1 / 15 | |
| 1.0.0 | 1 / 15 |
v9.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.1.0
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: octokitbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
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.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
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.