@apollographql/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 shadaj to apollo-bot reflects Apollo GraphQL's org-wide migration to bot-based publishing. apollo-bot has a strong track record across 63 packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): apollo-bot and nim are part of Apollo GraphQL's standard publishing infrastructure; this is a legitimate org-level maintainer transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of mdg/sashko is consistent with Apollo's organizational transition away from individual/legacy maintainers to bot-based publishing. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): graphql-language-service-types replaces the scoped @apollographql/graphql-language-service-types — a straightforward rename, not a suspicious new dependency. | ai | |
| phantom-deps | phantom-dep:graphql-language-service-types | AI (phantom-deps): Declared as a type/config dependency; phantom detection is a false positive for type-only usage in this GraphQL tooling package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.3.2 | 2 / 0 | |
| 1.3.1 | 2 / 0 | |
| 1.3.0 | 2 / 0 |
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-11-04. 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.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.