@graphql-codegen/gql-tag-operations
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): Migrated to GitHub Actions with SLSA provenance; standard CI publish for The Guild org. | ai | |
| provenance | missing-githead | AI (provenance): Expected side-effect of GitHub Actions publish flow; SLSA attestation compensates. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard utility library implicitly used by TypeScript-compiled code; legitimate dependency for this package. | ai | |
| phantom-deps | phantom-dep:auto-bind | AI (phantom-deps): auto-bind is a legitimate utility dependency for this code generator plugin; platform-specific binary usage is expected. | ai | |
| phantom-deps | phantom-dep:@graphql-tools/utils | AI (phantom-deps): @graphql-tools/utils is a core dependency for GraphQL tooling; referenced in config and used transitively throughout the plugin. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 5 / 0 | |
| 6.0.0 | 5 / 0 | |
| 5.2.0 | 5 / 0 | |
| 5.1.4 | 5 / 0 | |
| 5.1.3 | 5 / 0 | |
| 5.1.2 | 5 / 0 | |
| 5.1.1 | 5 / 0 | |
| 5.1.0 | 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 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
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. 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. 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.