eslint-plugin-graphql
GraphQL ESLint plugin.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): apollo-bot is Apollo's official publishing account; transition from individual maintainer jnwng to org bot is a documented, legitimate handoff consistent with Apollo's publishing practices. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is constrained to graphql/validation/rules/ namespace — loading GraphQL validation rules by name is core functionality of this ESLint plugin. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 4 / 12 | |
| 3.1.1 | 2 / 12 | |
| 3.1.0 | 2 / 12 | |
| 3.0.3 | 2 / 11 | |
| 3.0.2 | 2 / 11 | |
| 3.0.1 | 2 / 11 | |
| 3.0.0 | 2 / 11 | |
| 2.1.1 | 2 / 12 | |
| 2.1.0 | 2 / 12 | |
| 2.0.0 | 2 / 12 | |
| 1.5.0 | 2 / 11 | |
| 1.4.1 | 2 / 11 | |
| 1.4.0 | 2 / 11 | |
| 1.3.0 | 3 / 10 | |
| 1.2.0 | 2 / 10 | |
| 1.1.0 | 2 / 10 | |
| 1.0.0 | 2 / 10 | |
| 0.8.2 | 2 / 10 | |
| 0.8.1 | 2 / 10 | |
| 0.8.0 | 2 / 10 | |
| 0.7.0 | 2 / 10 | |
| 0.6.1 | 2 / 10 | |
| 0.6.0 | 3 / 9 | |
| 0.5.0 | 3 / 9 | |
| 0.4.3 | 3 / 9 | |
| 0.4.2 | 3 / 9 | |
| 0.4.1 | 3 / 9 | |
| 0.4.0 | 3 / 9 | |
| 0.3.1 | 3 / 9 | |
| 0.3.0 | 3 / 9 | |
| 0.2.7 | 3 / 9 | |
| 0.2.6 | 3 / 9 | |
| 0.2.4 | 3 / 9 | |
| 0.2.3 | 2 / 7 | |
| 0.2.2 | 2 / 7 | |
| 0.2.1 | 1 / 7 | |
| 0.2.0 | 1 / 7 | |
| 0.1.1 | 1 / 6 | |
| 0.1.0 | 1 / 6 | |
| 0.0.2 | 1 / 6 | |
| 0.0.1 | 0 / 0 |
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-09-20. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-13. This could indicate a legitimate maintainer transition or an account compromise.