← Home

@apollographql/graphql-language-service-types

npm Repository

Types for building GraphQL language services for IDEs

5
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

apollo-botevanshauserhwillsonjbaxleyiiimartijnwalravennimshadaj

Keywords

graphql

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from shadaj to apollo-bot reflects Apollo GraphQL's organizational consolidation under their official bot account; consistent with the @apollographql scoped namespace and apollo-bot's strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): apollo-bot and nim are legitimate Apollo GraphQL maintainers; addition is consistent with organizational transition to the @apollographql namespace. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of mdg and sashko is consistent with Apollo GraphQL's known rebranding from MDG (Meteor Development Group); not indicative of a hostile takeover. ai

Versions (showing 5 of 5)

Version Deps Published
2.0.2 0 / 0
2.0.1 0 / 0
2.0.0 0 / 0
1.3.2 1 / 0
1.3.1 1 / 0

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
HIGH Publisher changed: shadaj → apollo-bot (on 2018-11-04) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.