@graphql-codegen/client-preset
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): Migration from theguild-bot to GitHub Actions with SLSA provenance; legitimate CI change for this org. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions publishing drops gitHead; SLSA attestation compensates. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/utils | AI (phantom-deps): Declared dep used transitively by sibling codegen packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/typescript | AI (phantom-deps): Same-org plugin loaded dynamically by the codegen framework; stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established The Guild package published via theguild-bot; provenance absence is consistent across all their releases and not a risk indicator for this publisher. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 13 / 0 | |
| 6.0.0 | 13 / 0 | |
| 5.3.0 | 13 / 0 | |
| 5.2.4 | 13 / 0 | |
| 5.2.3 | 13 / 0 | |
| 5.2.2 | 13 / 0 | |
| 5.2.1 | 13 / 0 | |
| 5.2.0 | 13 / 0 | |
| 5.1.3 | 13 / 0 | |
| 5.1.2 | 13 / 0 | |
| 5.1.1 | 13 / 0 | |
| 5.1.0 | 13 / 0 | |
| 5.0.3 | 13 / 0 | |
| 5.0.2 | 13 / 0 | |
| 5.0.1 | 13 / 0 | |
| 5.0.0 | 13 / 0 |
v6.0.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.