vscode-langservers-extracted
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
hrsh7th
Keywords
language-server-protocol
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): ESLint language server legitimately spawns child processes to run ESLint; this is expected behavior for this package's bundled eslint-language-server component. | ai | |
| phantom-deps | phantom-dep:vscode-nls | AI (phantom-deps): Bundled language server package; vscode-nls is a transitive/indirect dep used by bundled upstream code, not a security concern. | ai | |
| phantom-deps | phantom-dep:jsonc-parser | AI (phantom-deps): Bundled language server package; jsonc-parser is used by bundled upstream code, not a security concern. | ai |
v4.10.0
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.
v4.9.0
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.