@jupyterlab/application
JupyterLab - Application
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established JupyterLab monorepo package published via release bot; lack of Sigstore provenance is a known gap for this publisher, not a security risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): JupyterLab consolidated publishing to a release bot account; large-scale maintainer removal is expected and consistent with the project's release automation strategy. | ai | |
| dependencies | unvetted-dep:@phosphor/commands | AI (dependencies): @phosphor/commands is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/algorithm | AI (dependencies): @phosphor/algorithm is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/coreutils | AI (dependencies): @phosphor/coreutils is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/messaging | AI (dependencies): @phosphor/messaging is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/disposable | AI (dependencies): @phosphor/disposable is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/properties | AI (dependencies): @phosphor/properties is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/application | AI (dependencies): @phosphor/application is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| phantom-deps | phantom-dep:font-awesome | AI (phantom-deps): font-awesome is referenced in jupyterlab.extraStyles config for CSS bundling — the documented JupyterLab pattern for CSS assets, not a JS import. | ai | |
| dependencies | unvetted-dep:@phosphor/signaling | AI (dependencies): @phosphor/signaling is part of the legitimate Phosphor.js framework used throughout JupyterLab. | ai | |
| dependencies | unvetted-dep:@phosphor/widgets | AI (dependencies): @phosphor/widgets is the legitimate Phosphor.js UI framework, a core dependency of JupyterLab. Not suspicious. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: @jupyterlab/application is a core JupyterLab package with SLSA provenance. Inflated semver signal is because prior versions aren't in this registry, not because it's a new/spam package. | ai |
Versions (showing 100 of 207)
| Version | Deps | Published |
|---|---|---|
| 3.1.13 | 20 / 7 | |
| 3.1.12 | 20 / 7 | |
| 3.1.11 | 20 / 7 | |
| 3.1.10 | 20 / 7 | |
| 3.1.9 | 20 / 7 | |
| 3.1.8 | 20 / 7 | |
| 3.1.7 | 20 / 7 | |
| 3.1.6 | 20 / 7 | |
| 3.1.5 | 20 / 7 | |
| 3.1.4 | 20 / 7 | |
| 3.1.3 | 20 / 7 | |
| 3.1.2 | 20 / 7 | |
| 3.1.1 | 20 / 7 | |
| 3.1.0 | 20 / 7 | |
| 3.0.13 | 20 / 7 | |
| 3.0.12 | 20 / 7 | |
| 3.0.11 | 20 / 7 | |
| 3.0.10 | 20 / 7 | |
| 3.0.9 | 20 / 7 | |
| 3.0.8 | 20 / 7 | |
| 3.0.7 | 20 / 7 | |
| 3.0.6 | 20 / 7 | |
| 3.0.5 | 20 / 7 | |
| 3.0.4 | 20 / 7 | |
| 3.0.3 | 20 / 7 | |
| 3.0.2 | 20 / 7 | |
| 3.0.1 | 20 / 7 | |
| 3.0.0 | 20 / 7 | |
| 2.3.1 | 19 / 7 | |
| 2.3.0 | 19 / 7 | |
| 2.2.7 | 19 / 7 | |
| 2.2.6 | 19 / 7 | |
| 2.2.5 | 19 / 7 | |
| 2.2.4 | 19 / 7 | |
| 2.2.3 | 19 / 7 | |
| 2.2.2 | 19 / 7 | |
| 2.2.1 | 19 / 7 | |
| 2.2.0 | 19 / 7 | |
| 2.1.2 | 19 / 3 | |
| 2.1.1 | 19 / 3 | |
| 2.1.0 | 19 / 3 | |
| 2.0.3 | 19 / 3 | |
| 2.0.2 | 19 / 3 | |
| 2.0.1 | 19 / 3 | |
| 2.0.0 | 19 / 3 | |
| 1.2.11 | 17 / 3 | |
| 1.2.10 | 17 / 3 | |
| 1.2.9 | 17 / 3 | |
| 1.2.8 | 17 / 3 | |
| 1.2.7 | 17 / 3 | |
| 1.2.6 | 17 / 3 | |
| 1.2.5 | 17 / 3 | |
| 1.2.4 | 17 / 3 | |
| 1.2.3 | 17 / 3 | |
| 1.2.2 | 17 / 3 | |
| 1.2.1 | 17 / 3 | |
| 1.2.0 | 17 / 3 | |
| 1.1.3 | 17 / 3 | |
| 1.1.2 | 17 / 3 | |
| 1.1.1 | 17 / 3 | |
| 1.1.0 | 17 / 3 | |
| 1.0.5 | 16 / 3 | |
| 1.0.4 | 16 / 3 | |
| 1.0.3 | 16 / 3 | |
| 1.0.2 | 16 / 3 | |
| 1.0.1 | 16 / 3 | |
| 1.0.0 | 16 / 3 | |
| 0.19.1 | 15 / 3 | |
| 0.18.6 | 15 / 2 | |
| 0.18.5 | 15 / 2 | |
| 0.18.4 | 15 / 2 | |
| 0.18.3 | 15 / 2 | |
| 0.18.2 | 15 / 2 | |
| 0.18.0 | 15 / 2 | |
| 0.17.2 | 15 / 2 | |
| 0.17.1 | 15 / 2 | |
| 0.16.3 | 15 / 2 | |
| 0.16.2 | 15 / 2 | |
| 0.16.1 | 15 / 2 | |
| 0.16.0 | 15 / 2 | |
| 0.15.4 | 15 / 2 | |
| 0.15.3 | 15 / 2 | |
| 0.15.2 | 15 / 2 | |
| 0.15.1 | 15 / 2 | |
| 0.15.0 | 15 / 2 | |
| 0.14.1 | 15 / 2 | |
| 0.14.0 | 15 / 2 | |
| 0.13.1 | 15 / 2 | |
| 0.13.0 | 15 / 2 | |
| 0.12.0 | 15 / 2 | |
| 0.11.1 | 15 / 2 | |
| 0.11.0 | 15 / 2 | |
| 0.10.0 | 15 / 2 | |
| 0.9.0 | 12 / 2 | |
| 0.8.3 | 12 / 2 | |
| 0.8.2 | 12 / 2 | |
| 0.8.1 | 12 / 2 | |
| 0.8.0 | 12 / 2 | |
| 0.7.0 | 9 / 2 | |
| 0.6.0 | 7 / 2 |
v3.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.
v2.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.
v2.2.7
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.2.6
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.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.
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.2.11
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.2.10
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.2.9
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.2.8
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.2.7
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.2.6
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.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.
v1.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.
v1.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.
v1.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.
v1.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.
v1.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.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.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.18.6
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.18.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.
v0.18.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.18.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.18.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.18.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.17.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.17.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.16.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.16.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.16.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.16.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.15.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.15.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.15.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.15.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.15.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.14.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.14.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.13.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.13.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.12.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.11.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.11.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.10.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.9.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.8.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.8.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.8.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.8.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.7.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.6.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.