graphql-language-service-parser
An online parser for GraphQL for use in syntax-highlighters and code intelligence tools
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from asiandrummer to lostplan in 2018 reflects a legitimate organizational maintainer transition within the official GraphQL GitHub org. Publisher lostplan has 197 approved packages and strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers kassens, lostplan, mgadda are consistent with a legitimate team transition within the official GraphQL organization. No compromise indicators. | ai | |
| phantom-deps | phantom-dep:graphql-config | AI (phantom-deps): graphql-config is a sibling package in the graphql-language-service monorepo; phantom dep finding is a false positive for this monorepo structure. | ai | |
| phantom-deps | phantom-dep:graphql-language-service-types | AI (phantom-deps): graphql-language-service-types is a sibling package in the same monorepo; phantom dep finding is a false positive for this monorepo structure. | ai | |
| provenance | missing-githead | AI (provenance): Established graphql/graphiql monorepo package with strong publisher track record; missing gitHead is a minor publish environment change, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established graphql/graphiql monorepo package with long history; lack of Sigstore attestation is a process gap, not a security threat for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.10.4 | 1 / 8 | |
| 1.10.3 | 1 / 8 | |
| 1.10.2 | 1 / 8 | |
| 1.10.1 | 1 / 8 | |
| 1.10.0 | 1 / 8 | |
| 1.9.3 | 1 / 8 | |
| 1.9.2 | 1 / 8 | |
| 1.9.1 | 1 / 7 | |
| 1.9.0 | 1 / 7 | |
| 1.8.0 | 1 / 7 | |
| 1.7.0 | 1 / 7 | |
| 1.6.5 | 1 / 7 | |
| 1.6.4 | 2 / 6 | |
| 1.6.3 | 2 / 6 | |
| 1.6.2 | 0 / 2 | |
| 1.6.1 | 0 / 2 | |
| 1.6.0 | 0 / 2 | |
| 1.5.2 | 2 / 0 | |
| 1.5.1 | 2 / 0 | |
| 1.5.0 | 2 / 0 | |
| 1.3.0 | 2 / 0 | |
| 1.2.2 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.18 | 2 / 0 | |
| 0.1.14 | 1 / 0 | |
| 0.1.12 | 1 / 0 | |
| 0.1.5 | 1 / 0 | |
| 0.0.17 | 1 / 0 | |
| 0.0.16 | 1 / 0 | |
| 0.0.15 | 1 / 0 | |
| 0.0.14 | 1 / 0 | |
| 0.0.13 | 1 / 0 | |
| 0.0.12 | 1 / 0 | |
| 0.0.11 | 1 / 0 | |
| 0.0.10 | 1 / 0 | |
| 0.0.9 | 1 / 0 | |
| 0.0.8 | 1 / 0 | |
| 0.0.7 | 1 / 0 | |
| 0.0.6 | 1 / 0 | |
| 0.0.5 | 1 / 0 | |
| 0.0.4 | 1 / 0 | |
| 0.0.3 | 1 / 31 | |
| 0.0.2 | 1 / 31 | |
| 0.0.1 | 1 / 31 |
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acao.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acao.
v1.9.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acao.
v1.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acao.
v1.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: acao.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-04-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
2 findings[Accepted risk] Package 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 2017-06-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.13
2 findings[Accepted risk] Package 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 2017-05-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findings[Accepted risk] Package 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 2017-04-02. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.4
2 findings[Accepted risk] Package 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 2017-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.3
2 findings[Accepted risk] Package 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 2017-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.