@vscode/jupyter-lsp-middleware
VS Code Python Language Server Middleware for Jupyter Notebook
1
Versions
MIT
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
lszomorudbaeumerlramos15sbattenaweinandhticehurstrchiodorebornixbpaseroraymondzhaomistoplekaimaetzelconnor.peetroblourenschrmartityriarjriekenalexandrudimatylerl0706deepak_roboaeschli
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate @vscode org package; missing repo/keywords are cosmetic issues, not spam indicators. | ai | |
| phantom-deps | phantom-dep:sha.js | AI (phantom-deps): Webpack-bundled package; declared deps may not appear as direct imports in source. | ai | |
| phantom-deps | phantom-dep:fast-myers-diff | AI (phantom-deps): Webpack-bundled package; declared deps may not appear as direct imports in source. | ai | |
| phantom-deps | phantom-dep:@vscode/lsp-notebook-concat | AI (phantom-deps): Same-org scoped dep; webpack bundling explains lack of direct import detection. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.2.50 | 6 / 23 |
v0.2.50
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.