graphql-language-service
The official, runtime independent Language Service for GraphQL
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migration to GitHub Actions CI/CD publishing with SLSA provenance; expected for this project. | ai | |
| phantom-deps | phantom-dep:debounce-promise | AI (phantom-deps): Declared but referenced in config only; stable false positive for this package. | ai |
Versions (showing 100 of 160)
| Version | Deps | Published |
|---|---|---|
| 5.5.1 | 3 / 11 | |
| 5.5.0 | 3 / 11 | |
| 5.4.0 | 3 / 11 | |
| 5.3.1 | 3 / 11 | |
| 5.3.0 | 3 / 11 | |
| 5.2.2 | 3 / 11 | |
| 5.2.1 | 2 / 10 | |
| 5.2.0 | 2 / 10 | |
| 5.1.7 | 2 / 10 | |
| 5.1.6 | 2 / 10 | |
| 5.1.5 | 2 / 10 | |
| 5.1.4 | 2 / 10 | |
| 5.1.3 | 2 / 10 | |
| 5.1.2 | 2 / 10 | |
| 5.1.1 | 2 / 10 | |
| 5.1.0 | 2 / 10 | |
| 5.0.6 | 2 / 10 | |
| 5.0.5 | 2 / 10 | |
| 5.0.4 | 2 / 10 | |
| 5.0.3 | 2 / 10 | |
| 5.0.2 | 2 / 10 | |
| 5.0.1 | 3 / 9 | |
| 5.0.0 | 3 / 9 | |
| 4.1.5 | 4 / 2 | |
| 4.1.4 | 4 / 2 | |
| 4.1.3 | 4 / 2 | |
| 4.1.2 | 5 / 2 | |
| 4.1.1 | 5 / 2 | |
| 4.1.0 | 5 / 2 | |
| 4.0.0 | 5 / 2 | |
| 3.2.5 | 4 / 1 | |
| 3.2.4 | 4 / 1 | |
| 3.2.3 | 4 / 1 | |
| 3.2.2 | 4 / 1 | |
| 3.2.1 | 4 / 1 | |
| 3.2.0 | 4 / 1 | |
| 3.1.6 | 4 / 1 | |
| 3.1.5 | 2 / 1 | |
| 3.1.4 | 2 / 1 | |
| 3.1.3 | 2 / 0 | |
| 3.1.2 | 2 / 0 | |
| 3.1.1 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.6 | 2 / 0 | |
| 3.0.5 | 2 / 0 | |
| 3.0.4 | 2 / 1 | |
| 3.0.3 | 2 / 1 | |
| 3.0.2 | 2 / 1 | |
| 3.0.1 | 2 / 1 | |
| 3.0.0 | 2 / 1 | |
| 2.3.4 | 6 / 0 | |
| 2.3.3 | 6 / 0 | |
| 2.3.2 | 6 / 0 | |
| 2.3.1 | 6 / 0 | |
| 2.3.0 | 6 / 0 | |
| 2.1.0 | 6 / 0 | |
| 2.0.0 | 6 / 0 | |
| 1.3.2 | 6 / 0 | |
| 1.2.2 | 6 / 0 | |
| 1.2.0 | 6 / 0 | |
| 1.1.2 | 6 / 0 | |
| 1.1.1 | 6 / 0 | |
| 1.1.0 | 6 / 0 | |
| 1.0.18 | 6 / 0 | |
| 1.0.16 | 6 / 0 | |
| 1.0.15 | 6 / 0 | |
| 0.1.14 | 6 / 0 | |
| 0.1.13 | 7 / 0 | |
| 0.1.12 | 7 / 0 | |
| 0.1.11 | 7 / 0 | |
| 0.1.10 | 7 / 0 | |
| 0.1.9 | 6 / 0 | |
| 0.1.8 | 6 / 0 | |
| 0.1.7 | 6 / 1 | |
| 0.1.6 | 6 / 1 | |
| 0.1.5 | 6 / 1 | |
| 0.0.42 | 13 / 33 | |
| 0.0.41 | 13 / 33 | |
| 0.0.40 | 13 / 33 | |
| 0.0.39 | 13 / 33 | |
| 0.0.38 | 13 / 33 | |
| 0.0.37 | 13 / 33 | |
| 0.0.36 | 13 / 33 | |
| 0.0.35 | 13 / 33 | |
| 0.0.34 | 13 / 33 | |
| 0.0.33 | 13 / 33 | |
| 0.0.32 | 13 / 33 | |
| 0.0.31 | 13 / 33 | |
| 0.0.30 | 13 / 33 | |
| 0.0.29 | 13 / 33 | |
| 0.0.28 | 13 / 33 | |
| 0.0.27 | 13 / 33 | |
| 0.0.26 | 13 / 33 | |
| 0.0.25 | 13 / 33 | |
| 0.0.24 | 13 / 33 | |
| 0.0.23 | 13 / 33 | |
| 0.0.22 | 13 / 33 | |
| 0.0.21 | 13 / 33 | |
| 0.0.20 | 13 / 33 | |
| 0.0.19 | 13 / 33 |
v5.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-11. 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.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
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.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
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.