@vscode/jupyter-lsp-middleware

VS Code Python Language Server Middleware for Jupyter Notebook

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

lszomorudbaeumerlramos15sbattenaweinandhticehurstrchiodorebornixbpaseroraymondzhaomistoplekaimaetzelconnor.peetroblourenschrmartityriarjriekenalexandrudimatylerl0706deepak_roboaeschli

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/node/index.js	AI (source-diff): Bundled LSP client code, no evidence of malicious network/exec behavior.	ai	2026/07/25
phantom-deps	phantom-dep:uuid	AI (phantom-deps): uuid likely used via bundled/minified build; no malicious indicator.	ai	2026/07/25
install-scripts	install-script:postinstall	AI (install-scripts): Fetches VS Code API typings via vscode-dts, standard for this package's build.	ai	2026/07/25
phantom-deps	phantom-dep:vscode-languageserver-protocol	AI (phantom-deps): Used as type-only import in TS source, not flagged by naive scan.	ai	2026/07/25
source-diff	obfuscated-file:dist/node/index.js	AI (source-diff): Webpack production build output, not true obfuscation; expected from package's own webpack script.	ai	2026/07/25
bogus-package	bogus-package	AI (bogus-package): Legitimate @vscode org package; missing repo/keywords are cosmetic issues, not spam indicators.	ai	2026/05/16
phantom-deps	phantom-dep:@vscode/lsp-notebook-concat	AI (phantom-deps): Same-org scoped dep; webpack bundling explains lack of direct import detection.	ai	2026/05/16
phantom-deps	phantom-dep:fast-myers-diff	AI (phantom-deps): Webpack-bundled package; declared deps may not appear as direct imports in source.	ai	2026/05/16
phantom-deps	phantom-dep:sha.js	AI (phantom-deps): Webpack-bundled package; declared deps may not appear as direct imports in source.	ai	2026/05/16

Versions (showing 51 of 51)

Version	Deps	Published
0.2.50	6 / 23	2022-10-06
0.2.49	6 / 23	2022-07-14
0.2.48	6 / 23	2022-06-10
0.2.47	6 / 23	2022-06-07
0.2.46	6 / 23	2022-05-31
0.2.45	6 / 23	2022-05-12
0.2.44	6 / 23	2022-05-10
0.2.43	6 / 23	2022-05-04
0.2.42	6 / 23	2022-04-29
0.2.41	6 / 23	2022-03-22
0.2.40	6 / 23	2022-03-22
0.2.39	6 / 23	2022-03-16
0.2.38	6 / 23	2022-02-08
0.2.37	6 / 23	2022-01-27
0.2.36	6 / 23	2022-01-22
0.2.35	6 / 23	2022-01-07
0.2.34	6 / 23	2022-01-04
0.2.33	6 / 23	2022-01-03
0.2.32	5 / 23	2022-01-03
0.2.31	5 / 23	2021-12-16
0.2.30	5 / 23	2021-12-15
0.2.29	5 / 23	2021-12-07
0.2.28	3 / 23	2021-12-02
0.2.27	3 / 23	2021-11-30
0.2.26	3 / 23	2021-11-30
0.2.25	3 / 23	2021-11-20
0.2.24	3 / 23	2021-11-19
0.2.23	2 / 23	2021-11-12
0.2.22	2 / 23	2021-11-12
0.2.21	2 / 23	2021-11-10
0.2.20	2 / 23	2021-11-09
0.2.19	1 / 22	2021-11-03
0.2.18	1 / 22	2021-11-02
0.2.17	1 / 22	2021-10-29
0.2.16	1 / 22	2021-10-22
0.2.15	1 / 22	2021-10-21
0.2.14	1 / 22	2021-10-14
0.2.13	1 / 22	2021-10-13
0.2.12	1 / 22	2021-09-27
0.2.11	1 / 23	2021-09-15
0.2.10	1 / 23	2021-09-15
0.2.9	1 / 23	2021-09-13
0.2.8	1 / 23	2021-09-13
0.2.7	1 / 23	2021-09-13
0.2.6	1 / 22	2021-09-10
0.2.5	2 / 14	2021-09-08
0.2.4	2 / 14	2021-09-07
0.2.3	2 / 14	2021-08-20
0.2.2	2 / 14	2021-08-20
0.2.1	2 / 14	2021-08-18
0.2.0	2 / 14	2021-08-18

v0.2.49

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.48

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.

v0.2.47

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.

v0.2.46

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.

v0.2.45

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.

v0.2.44

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.

v0.2.43

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.

v0.2.42

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.

v0.2.41

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.

v0.2.40

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: npm run download-api

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.

v0.2.39

2 findings

HIGH Package has 'postinstall' script install-scripts

Script: npm run download-api

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.

v0.2.38

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.

v0.2.37

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.

v0.2.36

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.

v0.2.35

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.

v0.2.34

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.

v0.2.33

3 findings

HIGH New obfuscated file: dist/node/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/node/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.32

2 findings

HIGH New obfuscated file: dist/node/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.31

2 findings

HIGH New obfuscated file: dist/node/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.30

2 findings

HIGH New obfuscated file: dist/node/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.29

2 findings

HIGH New obfuscated file: dist/node/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.7

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.

v0.2.6

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.

v0.2.5

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.

v0.2.4

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.

v0.2.3

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.

v0.2.2

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.

v0.2.1

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.

v0.2.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.