vscode-languageserver-protocol
VSCode Language Server Protocol implementation
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 | publisher-changed | AI (provenance): Publisher changed from individual (dbaeumer) to Microsoft org bot (vscode-bot) with 786 approved versions. Legitimate org-level migration. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead consistent with CI/CD pipeline change during Microsoft's org-wide publisher migration to vscode-bot. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (microsoft1es, lszomoru, vscode-bot) are Microsoft organizational accounts replacing individual devs. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers were individual MS employees replaced by org accounts; standard Microsoft consolidation pattern. | ai | |
| source-diff | obfuscated-file:lib/common/protocol.d.ts | AI (source-diff): TypeScript .d.ts declaration file with long import lines from LSP type definitions; not obfuscated. Normal for compiler-generated protocol typings. | ai | |
| source-diff | large-new-source-files | AI (source-diff): LSP 3.17 is a major protocol update adding many features; 60 new files reflects the new lib/common+node+browser structure and new protocol capabilities. | ai | |
| provenance | no-provenance | AI (provenance): vscode-languageserver-protocol is a well-established Microsoft package published by vscode-bot; lack of Sigstore provenance is informational, not a risk signal. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.17.5 | 2 / 0 | |
| 3.17.4 | 2 / 0 | |
| 3.17.3 | 2 / 0 | |
| 3.17.2 | 2 / 0 | |
| 3.17.1 | 2 / 0 | |
| 3.17.0 | 2 / 0 | |
| 3.16.0 | 2 / 0 | |
| 3.15.3 | 2 / 0 | |
| 3.15.2 | 2 / 0 | |
| 3.15.1 | 2 / 0 | |
| 3.15.0 | 2 / 0 | |
| 3.14.1 | 2 / 0 | |
| 3.14.0 | 2 / 0 | |
| 3.13.0 | 2 / 0 | |
| 3.12.0 | 2 / 0 | |
| 3.11.0 | 2 / 0 | |
| 3.10.5 | 2 / 0 | |
| 3.10.4 | 2 / 0 | |
| 3.10.3 | 2 / 0 | |
| 3.10.1 | 2 / 0 | |
| 3.10.0 | 2 / 0 | |
| 3.9.0 | 2 / 0 | |
| 3.8.1 | 2 / 0 | |
| 3.8.0 | 2 / 0 | |
| 3.7.2 | 2 / 0 | |
| 3.7.1 | 2 / 0 | |
| 3.7.0 | 2 / 0 | |
| 3.6.0 | 2 / 0 | |
| 3.5.1 | 2 / 0 | |
| 3.5.0 | 2 / 0 | |
| 3.4.4 | 2 / 0 | |
| 3.4.2 | 2 / 0 | |
| 3.4.1 | 2 / 0 | |
| 3.4.0 | 2 / 0 | |
| 3.1.2 | 2 / 2 | |
| 3.1.1 | 2 / 2 | |
| 3.1.0 | 2 / 2 |
v3.17.5
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.
v3.17.4
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: vscode-bot.
v3.17.3
3 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.
This version was published by a different npm account than previous versions on 2023-02-14. 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.
v3.17.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: dbaeumer.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.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 2018-08-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
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 2018-08-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.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-09-23. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.2
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-09-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
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-09-08. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.2
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-09-04. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.