@jupyterlab/services
Client APIs for the Jupyter services REST APIs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a legitimate runtime dependency used for WebSocket support; phantom-dep fires due to dynamic/conditional import patterns in this isomorphic library. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): node-fetch is loaded via eval('require')('node-fetch') to avoid bundler inclusion; static analysis cannot detect this dynamic import. Legitimate runtime dependency. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') is a hardcoded static string used to conditionally load node-fetch in Node.js environments without bundler interference — a well-known legitimate isomorphic pattern with no dynamic input. | ai | |
| phantom-deps | phantom-dep:@types/text-encoding | AI (phantom-deps): Type-only package used for TypeScript compilation; not directly imported at runtime is expected behavior for @types packages. | ai | |
| provenance | no-provenance | AI (provenance): This is a legacy version predating npm provenance attestation; absence is expected and not a risk signal for this well-established package. | ai | |
| dependencies | unvetted-dep:@types/text-encoding | AI (dependencies): @types/text-encoding is a TypeScript type definition package with no runtime code; it poses no security risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/minimist | AI (phantom-deps): @types/minimist as a runtime dep is a harmless quirk of older TypeScript project conventions; no security implication. | ai | |
| dependencies | unvetted-dep:phosphor | AI (dependencies): phosphor was the official predecessor UI framework for JupyterLab; its use in early @jupyterlab/services versions is expected and legitimate. | ai | |
| provenance | publisher-changed | AI (provenance): Migration from jupyterlab-release-bot to GitHub Actions OIDC publishing with SLSA provenance; legitimate CI/CD infrastructure change for the JupyterLab project. | ai | |
| dependencies | unvetted-dep:@jupyterlab/coreutils | AI (dependencies): Known JupyterLab sibling package; expected dependency for @jupyterlab/services. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver is expected for JupyterLab monorepo packages published at their monorepo version. README signal is a false positive for this legitimate Project Jupyter package. | ai | |
| dependencies | unvetted-dep:@jupyterlab/settingregistry | AI (dependencies): Known JupyterLab sibling package; expected dependency for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@jupyter/ydoc | AI (dependencies): Known JupyterLab ecosystem dependency; expected transitive dep for this package. | ai | |
| dependencies | unvetted-dep:@lumino/polling | AI (dependencies): Known Lumino ecosystem dependency; expected for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@lumino/coreutils | AI (dependencies): Known Lumino ecosystem dependency; expected for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@lumino/signaling | AI (dependencies): Known Lumino ecosystem dependency; expected for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@lumino/disposable | AI (dependencies): Known Lumino ecosystem dependency; expected for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@lumino/properties | AI (dependencies): Known Lumino ecosystem dependency; expected for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@jupyterlab/statedb | AI (dependencies): Known JupyterLab sibling package; expected dependency for @jupyterlab/services. | ai | |
| dependencies | unvetted-dep:@jupyterlab/nbformat | AI (dependencies): Known JupyterLab sibling package; expected dependency for @jupyterlab/services. | ai |
Versions (showing 100 of 216)
| Version | Deps | Published |
|---|---|---|
| 6.1.12 | 12 / 13 | |
| 6.1.11 | 12 / 13 | |
| 6.1.10 | 12 / 13 | |
| 6.1.9 | 12 / 13 | |
| 6.1.8 | 12 / 13 | |
| 6.1.7 | 12 / 13 | |
| 6.1.6 | 12 / 13 | |
| 6.1.5 | 12 / 13 | |
| 6.1.4 | 12 / 13 | |
| 6.1.3 | 12 / 13 | |
| 6.1.2 | 12 / 13 | |
| 6.1.1 | 12 / 13 | |
| 6.1.0 | 12 / 13 | |
| 6.0.10 | 12 / 13 | |
| 6.0.9 | 12 / 13 | |
| 6.0.8 | 12 / 13 | |
| 6.0.7 | 12 / 13 | |
| 6.0.6 | 12 / 13 | |
| 6.0.5 | 12 / 13 | |
| 6.0.4 | 12 / 13 | |
| 6.0.3 | 12 / 13 | |
| 6.0.2 | 12 / 13 | |
| 6.0.1 | 12 / 13 | |
| 6.0.0 | 12 / 13 | |
| 5.3.1 | 12 / 13 | |
| 5.3.0 | 12 / 13 | |
| 5.2.5 | 12 / 13 | |
| 5.2.4 | 12 / 13 | |
| 5.2.3 | 12 / 13 | |
| 5.2.2 | 12 / 13 | |
| 5.2.1 | 12 / 13 | |
| 5.2.0 | 12 / 13 | |
| 5.1.0 | 12 / 8 | |
| 5.0.3 | 12 / 8 | |
| 5.0.2 | 12 / 8 | |
| 5.0.1 | 12 / 8 | |
| 5.0.0 | 12 / 8 | |
| 4.2.3 | 8 / 8 | |
| 4.2.2 | 8 / 8 | |
| 4.2.1 | 8 / 8 | |
| 4.2.0 | 8 / 8 | |
| 4.1.1 | 8 / 8 | |
| 4.1.0 | 8 / 8 | |
| 4.0.5 | 8 / 8 | |
| 4.0.4 | 8 / 8 | |
| 4.0.3 | 8 / 8 | |
| 4.0.2 | 8 / 8 | |
| 4.0.1 | 8 / 8 | |
| 4.0.0 | 8 / 8 | |
| 3.2.1 | 6 / 7 | |
| 3.1.4 | 8 / 14 | |
| 3.1.3 | 8 / 14 | |
| 3.1.2 | 8 / 14 | |
| 3.1.0 | 8 / 14 | |
| 3.0.3 | 8 / 13 | |
| 3.0.2 | 8 / 13 | |
| 3.0.1 | 8 / 13 | |
| 2.0.3 | 8 / 13 | |
| 2.0.2 | 8 / 13 | |
| 2.0.1 | 8 / 13 | |
| 2.0.0 | 8 / 13 | |
| 1.1.4 | 8 / 13 | |
| 1.1.3 | 8 / 13 | |
| 1.1.2 | 8 / 13 | |
| 1.1.1 | 8 / 13 | |
| 1.1.0 | 8 / 13 | |
| 1.0.1 | 8 / 13 | |
| 1.0.0 | 8 / 13 | |
| 0.52.0 | 6 / 14 | |
| 0.51.0 | 5 / 14 | |
| 0.50.2 | 5 / 14 | |
| 0.50.1 | 5 / 14 | |
| 0.50.0 | 5 / 14 | |
| 0.49.0 | 5 / 14 | |
| 0.48.0 | 6 / 13 | |
| 0.47.1 | 6 / 13 | |
| 0.47.0 | 6 / 13 | |
| 0.46.0 | 6 / 13 | |
| 0.45.0 | 6 / 13 | |
| 0.44.0 | 10 / 13 | |
| 0.43.0 | 10 / 14 | |
| 0.42.1 | 10 / 13 | |
| 0.42.0 | 10 / 13 | |
| 0.41.0 | 10 / 13 | |
| 0.40.4 | 9 / 13 | |
| 0.40.3 | 9 / 13 | |
| 0.40.2 | 9 / 13 | |
| 0.40.1 | 9 / 13 | |
| 0.40.0 | 9 / 13 | |
| 0.39.1 | 10 / 13 | |
| 0.39.0 | 10 / 13 | |
| 0.38.0 | 6 / 15 | |
| 0.37.0 | 6 / 15 | |
| 0.36.1 | 6 / 15 | |
| 0.36.0 | 6 / 15 | |
| 0.35.1 | 6 / 15 | |
| 0.35.0 | 6 / 15 | |
| 0.34.3 | 6 / 15 | |
| 0.34.2 | 6 / 15 | |
| 0.34.1 | 6 / 15 |
v6.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.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.
v5.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.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.
v5.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.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.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.
v4.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.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.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.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.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.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.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.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.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v0.52.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.
v0.51.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.
v0.50.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.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.
v0.49.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.
v0.48.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.
v0.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.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.
v0.46.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.
v0.45.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.
v0.44.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.
v0.43.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.
v0.42.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.