@graphql-codegen/typescript-operations
GraphQL Code Generator plugin for generating TypeScript types for GraphQL queries, mutations, subscriptions and fragments
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): Transition from theguild-bot to GitHub Actions CI; SLSA provenance confirms legitimate publish pipeline. | ai | |
| provenance | missing-githead | AI (provenance): gitHead absence is expected when publishing via GitHub Actions with npm provenance. | ai |
Versions (showing 100 of 443)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 5 / 0 | |
| 6.0.2 | 5 / 0 | |
| 6.0.1 | 5 / 0 | |
| 6.0.0 | 5 / 0 | |
| 5.1.0 | 5 / 0 | |
| 5.0.9 | 5 / 0 | |
| 5.0.8 | 5 / 0 | |
| 5.0.7 | 5 / 0 | |
| 5.0.6 | 5 / 0 | |
| 5.0.5 | 5 / 0 | |
| 5.0.4 | 5 / 0 | |
| 5.0.3 | 5 / 0 | |
| 5.0.2 | 5 / 0 | |
| 5.0.1 | 5 / 0 | |
| 5.0.0 | 5 / 0 | |
| 4.6.1 | 5 / 0 | |
| 4.6.0 | 5 / 0 | |
| 4.5.1 | 5 / 0 | |
| 4.5.0 | 5 / 0 | |
| 4.4.1 | 5 / 0 | |
| 4.4.0 | 5 / 0 | |
| 4.3.1 | 5 / 0 | |
| 4.3.0 | 5 / 0 | |
| 4.2.3 | 5 / 0 | |
| 4.2.2 | 5 / 0 | |
| 4.2.1 | 5 / 0 | |
| 4.2.0 | 5 / 0 | |
| 4.1.3 | 5 / 0 | |
| 4.1.2 | 5 / 0 | |
| 4.1.1 | 5 / 0 | |
| 4.1.0 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.0.4 | 5 / 0 | |
| 3.0.3 | 5 / 0 | |
| 3.0.2 | 5 / 0 | |
| 3.0.1 | 5 / 0 | |
| 3.0.0 | 5 / 0 | |
| 2.5.13 | 5 / 0 | |
| 2.5.12 | 5 / 0 | |
| 2.5.11 | 5 / 0 | |
| 2.5.10 | 5 / 0 | |
| 2.5.9 | 5 / 0 | |
| 2.5.8 | 5 / 0 | |
| 2.5.7 | 5 / 0 | |
| 2.5.6 | 5 / 0 | |
| 2.5.5 | 5 / 0 | |
| 2.5.4 | 5 / 0 | |
| 2.5.3 | 5 / 0 | |
| 2.5.2 | 5 / 0 | |
| 2.5.1 | 5 / 0 | |
| 2.5.0 | 5 / 0 | |
| 2.4.3 | 5 / 0 | |
| 2.4.2 | 5 / 0 | |
| 2.4.1 | 5 / 0 | |
| 2.4.0 | 5 / 0 | |
| 2.3.7 | 5 / 0 | |
| 2.3.6 | 5 / 0 | |
| 2.3.5 | 5 / 0 | |
| 2.3.4 | 5 / 0 | |
| 2.3.3 | 5 / 0 | |
| 2.3.2 | 5 / 0 | |
| 2.3.1 | 5 / 0 | |
| 2.3.0 | 5 / 0 | |
| 2.2.4 | 5 / 0 | |
| 2.2.3 | 5 / 0 | |
| 2.2.2 | 5 / 0 | |
| 2.2.1 | 5 / 0 | |
| 2.2.0 | 5 / 0 | |
| 2.1.8 | 5 / 0 | |
| 2.1.7 | 5 / 0 | |
| 2.1.6 | 5 / 0 | |
| 2.1.5 | 5 / 0 | |
| 2.1.4 | 5 / 0 | |
| 2.1.3 | 5 / 0 | |
| 2.1.2 | 5 / 0 | |
| 2.1.1 | 5 / 0 | |
| 2.1.0 | 5 / 0 | |
| 2.0.1 | 5 / 0 | |
| 2.0.0 | 5 / 0 | |
| 1.18.4 | 5 / 0 | |
| 1.18.3 | 5 / 0 | |
| 1.18.2 | 5 / 0 | |
| 1.18.1 | 5 / 0 | |
| 1.18.0 | 5 / 0 | |
| 1.17.16 | 5 / 0 | |
| 1.17.15 | 5 / 0 | |
| 1.17.14 | 5 / 0 | |
| 1.17.13 | 5 / 0 | |
| 1.17.12 | 5 / 0 | |
| 1.17.11 | 5 / 0 | |
| 1.17.10 | 5 / 0 | |
| 1.17.9 | 5 / 0 | |
| 1.17.8 | 5 / 0 | |
| 1.17.7 | 5 / 0 | |
| 1.17.6 | 5 / 0 | |
| 1.17.5 | 5 / 0 | |
| 1.17.4 | 5 / 0 | |
| 1.17.3 | 5 / 0 | |
| 1.17.2 | 5 / 0 |
v6.0.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-27. 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.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.