@graphql-eslint/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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:lodash.lowercase | AI (dependencies): lodash.lowercase is a well-known lodash utility; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:graphql-depth-limit | AI (dependencies): graphql-depth-limit is a standard GraphQL utility; appropriate dependency for a GraphQL ESLint plugin. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.4.0 | 8 / 0 | |
| 4.3.0 | 8 / 0 | |
| 4.2.1 | 8 / 0 | |
| 4.2.0 | 8 / 0 | |
| 4.1.1 | 8 / 0 | |
| 4.1.0 | 8 / 0 | |
| 4.0.1 | 8 / 0 | |
| 4.0.0 | 8 / 0 |
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.