apollo-language-server
A language server for Apollo GraphQL projects
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() is used to read package.json files discovered in the workspace to check for apollo config keys — a standard monorepo tooling pattern, not arbitrary code loading. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit runtime polyfill dependency; properly declared for Node.js compatibility. | ai | |
| phantom-deps | phantom-dep:minimist | AI (phantom-deps): minimist is a CLI/build tool dependency referenced in configuration; properly declared in dependencies. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a legitimate WebSocket dependency used transitively by apollo-link-ws; properly declared in dependencies. | ai | |
| phantom-deps | phantom-dep:recursive-readdir | AI (phantom-deps): recursive-readdir is a build/config tool dependency; properly declared in dependencies. | ai | |
| phantom-deps | phantom-dep:subscriptions-transport-ws | AI (phantom-deps): subscriptions-transport-ws is a GraphQL subscription transport dependency; properly declared in dependencies. | ai | |
| phantom-deps | phantom-dep:apollo-link-ws | AI (phantom-deps): apollo-link-ws is a transitive WebSocket transport dependency for GraphQL subscriptions; properly declared. | ai |
Versions (showing 100 of 106)
| Version | Deps | Published |
|---|---|---|
| 1.26.9 | 25 / 0 | |
| 1.26.8 | 25 / 0 | |
| 1.26.7 | 25 / 0 | |
| 1.26.6 | 25 / 0 | |
| 1.26.5 | 25 / 0 | |
| 1.26.4 | 25 / 0 | |
| 1.26.3 | 25 / 0 | |
| 1.26.2 | 25 / 0 | |
| 1.26.1 | 25 / 0 | |
| 1.26.0 | 25 / 0 | |
| 1.25.9 | 25 / 0 | |
| 1.25.8 | 25 / 0 | |
| 1.25.7 | 25 / 0 | |
| 1.25.5 | 25 / 0 | |
| 1.25.2 | 25 / 0 | |
| 1.25.0 | 25 / 0 | |
| 1.24.1 | 25 / 0 | |
| 1.24.0 | 25 / 0 | |
| 1.23.4 | 25 / 0 | |
| 1.23.3 | 25 / 0 | |
| 1.23.2 | 25 / 0 | |
| 1.23.1 | 25 / 0 | |
| 1.23.0 | 25 / 0 | |
| 1.22.3 | 25 / 0 | |
| 1.22.2 | 25 / 0 | |
| 1.22.1 | 25 / 0 | |
| 1.22.0 | 25 / 0 | |
| 1.21.4 | 25 / 0 | |
| 1.21.3 | 25 / 0 | |
| 1.21.1 | 25 / 0 | |
| 1.21.0 | 25 / 0 | |
| 1.20.1 | 25 / 0 | |
| 1.20.0 | 25 / 0 | |
| 1.19.2 | 25 / 0 | |
| 1.19.1 | 25 / 0 | |
| 1.19.0 | 25 / 0 | |
| 1.18.0 | 25 / 0 | |
| 1.17.2 | 25 / 0 | |
| 1.17.1 | 25 / 0 | |
| 1.17.0 | 25 / 0 | |
| 1.16.1 | 25 / 0 | |
| 1.16.0 | 25 / 0 | |
| 1.15.3 | 24 / 0 | |
| 1.15.2 | 24 / 0 | |
| 1.15.1 | 23 / 0 | |
| 1.15.0 | 23 / 0 | |
| 1.14.3 | 23 / 0 | |
| 1.14.2 | 23 / 0 | |
| 1.14.1 | 23 / 0 | |
| 1.14.0 | 23 / 0 | |
| 1.13.1 | 23 / 0 | |
| 1.13.0 | 23 / 0 | |
| 1.12.0 | 23 / 0 | |
| 1.11.0 | 23 / 0 | |
| 1.10.1 | 23 / 0 | |
| 1.10.0 | 23 / 0 | |
| 1.9.1 | 23 / 0 | |
| 1.9.0 | 23 / 0 | |
| 1.8.4 | 23 / 0 | |
| 1.8.3 | 23 / 0 | |
| 1.8.2 | 23 / 0 | |
| 1.8.1 | 28 / 0 | |
| 1.8.0 | 28 / 0 | |
| 1.7.3 | 28 / 0 | |
| 1.7.2 | 28 / 0 | |
| 1.7.1 | 28 / 0 | |
| 1.7.0 | 28 / 0 | |
| 1.6.3 | 27 / 0 | |
| 1.6.2 | 27 / 0 | |
| 1.6.1 | 27 / 0 | |
| 1.6.0 | 27 / 0 | |
| 1.5.4 | 27 / 0 | |
| 1.5.3 | 27 / 0 | |
| 1.5.2 | 27 / 0 | |
| 1.5.1 | 27 / 0 | |
| 1.5.0 | 27 / 0 | |
| 1.4.3 | 27 / 0 | |
| 1.4.2 | 27 / 0 | |
| 1.4.1 | 27 / 0 | |
| 1.4.0 | 27 / 0 | |
| 1.3.1 | 27 / 0 | |
| 1.3.0 | 27 / 0 | |
| 1.2.0 | 27 / 0 | |
| 1.1.8 | 27 / 0 | |
| 1.1.7 | 27 / 0 | |
| 1.1.6 | 27 / 0 | |
| 1.1.5 | 27 / 0 | |
| 1.1.4 | 27 / 0 | |
| 1.1.3 | 27 / 0 | |
| 1.1.2 | 27 / 0 | |
| 1.1.1 | 27 / 0 | |
| 1.1.0 | 27 / 0 | |
| 1.0.14 | 27 / 0 | |
| 1.0.13 | 27 / 0 | |
| 1.0.12 | 27 / 0 | |
| 1.0.11 | 27 / 0 | |
| 1.0.10 | 27 / 0 | |
| 1.0.9 | 27 / 0 | |
| 1.0.8 | 27 / 0 | |
| 1.0.7 | 27 / 0 |
v1.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.