vscode-languageserver
Language server implementation for node
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Microsoft monorepo publish pipeline change; vscode-bot is the established publisher for this org's packages. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used legitimately to spawn npm/tooling processes in the language server install helper; expected for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Copies process.env to pass to child_process spawn with NO_UPDATE_NOTIFIER; standard pattern for this package. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 9.0.1 | 1 / 1 | |
| 9.0.0 | 1 / 1 | |
| 8.0.2 | 1 / 0 | |
| 8.0.1 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.1.1 | 1 / 0 | |
| 6.1.0 | 1 / 0 | |
| 6.0.1 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.2.1 | 2 / 0 | |
| 5.2.0 | 2 / 0 | |
| 5.1.0 | 2 / 0 | |
| 5.0.3 | 2 / 0 | |
| 5.0.2 | 2 / 0 | |
| 5.0.1 | 2 / 0 | |
| 5.0.0 | 2 / 0 | |
| 4.4.2 | 2 / 0 | |
| 4.4.1 | 2 / 0 | |
| 4.4.0 | 2 / 0 | |
| 4.3.0 | 2 / 0 | |
| 4.2.1 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.3 | 2 / 0 | |
| 4.1.2 | 2 / 0 | |
| 4.1.1 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.5.1 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.4.3 | 2 / 0 | |
| 3.4.2 | 2 / 0 | |
| 3.4.1 | 2 / 0 | |
| 3.4.0 | 2 / 0 | |
| 3.3.0 | 2 / 4 | |
| 3.2.2 | 2 / 4 | |
| 3.2.1 | 2 / 4 | |
| 3.2.0 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.5 | 2 / 4 | |
| 3.0.4 | 2 / 4 | |
| 3.0.3 | 2 / 4 | |
| 2.6.2 | 2 / 2 | |
| 2.6.1 | 2 / 2 | |
| 2.6.0 | 2 / 2 | |
| 2.5.1 | 2 / 2 | |
| 2.5.0 | 2 / 2 | |
| 2.2.1 | 1 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.2 | 1 / 2 | |
| 2.1.1 | 1 / 2 | |
| 2.1.0 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.4.1 | 1 / 2 | |
| 1.4.0 | 1 / 2 | |
| 1.3.1 | 1 / 2 | |
| 1.3.0 | 1 / 2 | |
| 1.1.4 | 1 / 2 | |
| 1.1.3 | 1 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 0.10.6 | 1 / 2 | |
| 0.10.5 | 1 / 2 | |
| 0.10.4 | 1 / 2 | |
| 0.10.3 | 1 / 2 | |
| 0.10.2 | 1 / 2 | |
| 0.10.1 | 1 / 2 | |
| 0.10.0 | 1 / 2 |
v9.0.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: vscode-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
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: vscode-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
2 findingsPackage 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: dbaeumer.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.