@graphql-codegen/add
GraphQL Code Generator plugin for adding custom content to your output file
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 with SLSA attestation; legitimate CI migration. | ai | |
| provenance | missing-githead | AI (provenance): gitHead dropped as part of CI migration to GitHub Actions; SLSA provenance compensates. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @graphql-codegen/add is a legitimate scoped package in the official GraphQL Code Generator org, not a typosquat of zod. Levenshtein match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @graphql-codegen/add is a legitimate scoped package in the official GraphQL Code Generator org, not a typosquat of ajv. Levenshtein match is coincidental. | ai | |
| provenance | no-provenance | AI (provenance): Published by theguild-bot with a strong track record (8878 approved packages). Lack of Sigstore provenance is common and not a meaningful risk for this well-established publisher. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 7.0.1 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.0.1 | 2 / 0 | |
| 6.0.0 | 2 / 0 | |
| 5.0.3 | 2 / 0 | |
| 5.0.2 | 2 / 0 | |
| 5.0.1 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.2.3 | 2 / 0 | |
| 3.2.2 | 2 / 0 | |
| 3.2.1 | 2 / 0 | |
| 3.2.0 | 2 / 0 | |
| 3.1.1 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.0.2 | 2 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 | |
| 1.17.7 | 2 / 0 | |
| 1.17.6 | 2 / 0 | |
| 1.17.5 | 2 / 0 | |
| 1.17.4 | 2 / 0 | |
| 1.17.3 | 2 / 0 | |
| 1.17.1 | 2 / 0 | |
| 1.17.0 | 2 / 0 | |
| 1.16.3 | 2 / 0 | |
| 1.16.2 | 2 / 0 | |
| 1.16.1 | 2 / 0 | |
| 1.16.0 | 2 / 0 | |
| 1.15.4 | 2 / 0 | |
| 1.15.3 | 2 / 0 | |
| 1.15.2 | 2 / 0 | |
| 1.15.1 | 2 / 0 | |
| 1.15.0 | 2 / 0 | |
| 1.14.0 | 2 / 0 | |
| 1.13.5 | 2 / 0 | |
| 1.13.4 | 2 / 0 | |
| 1.13.3 | 2 / 0 | |
| 1.13.2 | 2 / 0 | |
| 1.13.1 | 2 / 0 | |
| 1.13.0 | 2 / 0 | |
| 1.12.2 | 2 / 0 | |
| 1.12.1 | 2 / 0 | |
| 1.12.0 | 2 / 0 | |
| 1.11.2 | 2 / 0 | |
| 1.11.1 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.1 | 2 / 0 |
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 finding[Accepted risk] Package 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. 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.