@graphql-codegen/typed-document-node
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 reflects CI migration; SLSA attestation confirms legitimate publish. | ai | |
| provenance | missing-githead | AI (provenance): gitHead absence expected when publishing via GitHub Actions with provenance attestation. | ai | |
| phantom-deps | phantom-dep:change-case-all | AI (phantom-deps): change-case-all is declared and used transitively via visitor-plugin-common config. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.0.2 | 5 / 0 | |
| 7.0.1 | 5 / 0 | |
| 7.0.0 | 5 / 0 | |
| 6.1.8 | 5 / 0 | |
| 6.1.7 | 5 / 0 | |
| 6.1.6 | 5 / 0 | |
| 6.1.5 | 5 / 0 | |
| 6.1.4 | 5 / 0 | |
| 6.1.3 | 5 / 0 | |
| 6.1.2 | 5 / 0 | |
| 6.1.1 | 5 / 0 | |
| 6.1.0 | 5 / 0 | |
| 6.0.2 | 5 / 0 | |
| 6.0.1 | 5 / 0 | |
| 6.0.0 | 5 / 0 |
v7.0.2
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.
v7.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.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.