@jupyterlab/statusbar
JupyterLab statusbar package.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jupyterlab/observables | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared for bundling/peer dependency purposes in JupyterLab extensions; pattern is consistent across the ecosystem. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/cells | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/tooltip | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/mainmenu | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@phosphor/virtualdom | AI (phantom-deps): Referenced in config files for JupyterLab extension bundling; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/inspector | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@phosphor/application | AI (phantom-deps): Referenced in config files for JupyterLab extension bundling; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/docregistry | AI (phantom-deps): Same-org @jupyterlab package declared for config/bundling; not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@phosphor/commands | AI (phantom-deps): Referenced in config files for JupyterLab extension bundling; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@phosphor/domutils | AI (phantom-deps): Referenced in config files for JupyterLab extension bundling; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@jupyterlab/console | AI (dependencies): First-party JupyterLab org package; expected dependency for a JupyterLab extension. | ai | |
| dependencies | unvetted-dep:@jupyterlab/tooltip | AI (dependencies): First-party JupyterLab org package; expected dependency for a JupyterLab extension. | ai | |
| dependencies | unvetted-dep:@jupyterlab/mainmenu | AI (dependencies): First-party JupyterLab org package; expected dependency for a JupyterLab extension. | ai | |
| dependencies | unvetted-dep:@jupyterlab/inspector | AI (dependencies): First-party JupyterLab org package; expected dependency for a JupyterLab extension. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance availability (published 2018); absence is expected and not a risk signal. | ai | |
| provenance | publisher-changed | AI (provenance): JupyterLab migrated releases to GitHub Actions with SLSA provenance; publisher change from jupyterlab-release-bot to GitHub Actions is a documented, legitimate CI/CD transition for this org. | ai |
Versions (showing 71 of 171)
| Version | Deps | Published |
|---|---|---|
| 3.1.13 | 14 / 6 | |
| 3.1.12 | 14 / 6 | |
| 3.1.11 | 14 / 6 | |
| 3.1.10 | 14 / 6 | |
| 3.1.9 | 14 / 6 | |
| 3.1.8 | 14 / 6 | |
| 3.1.7 | 14 / 6 | |
| 3.1.6 | 14 / 6 | |
| 3.1.5 | 14 / 6 | |
| 3.1.4 | 15 / 6 | |
| 3.1.3 | 15 / 6 | |
| 3.1.2 | 15 / 6 | |
| 3.1.1 | 15 / 6 | |
| 3.1.0 | 15 / 6 | |
| 3.0.10 | 15 / 6 | |
| 3.0.9 | 15 / 6 | |
| 3.0.8 | 15 / 6 | |
| 3.0.7 | 15 / 6 | |
| 3.0.6 | 15 / 6 | |
| 3.0.5 | 15 / 6 | |
| 3.0.4 | 15 / 6 | |
| 3.0.3 | 15 / 6 | |
| 3.0.2 | 15 / 6 | |
| 3.0.1 | 15 / 6 | |
| 3.0.0 | 15 / 6 | |
| 2.3.1 | 15 / 6 | |
| 2.3.0 | 15 / 6 | |
| 2.2.4 | 15 / 6 | |
| 2.2.3 | 15 / 6 | |
| 2.2.2 | 15 / 6 | |
| 2.2.1 | 15 / 6 | |
| 2.2.0 | 15 / 6 | |
| 2.1.1 | 15 / 2 | |
| 2.1.0 | 15 / 2 | |
| 2.0.3 | 15 / 2 | |
| 2.0.2 | 15 / 2 | |
| 2.0.1 | 15 / 2 | |
| 2.0.0 | 14 / 2 | |
| 1.2.11 | 13 / 2 | |
| 1.2.10 | 13 / 2 | |
| 1.2.9 | 13 / 2 | |
| 1.2.8 | 13 / 2 | |
| 1.2.7 | 13 / 2 | |
| 1.2.6 | 13 / 2 | |
| 1.2.5 | 13 / 2 | |
| 1.2.4 | 13 / 2 | |
| 1.2.3 | 13 / 2 | |
| 1.2.2 | 13 / 2 | |
| 1.2.1 | 13 / 2 | |
| 1.2.0 | 13 / 2 | |
| 1.1.3 | 13 / 2 | |
| 1.1.2 | 13 / 2 | |
| 1.1.1 | 13 / 2 | |
| 1.1.0 | 13 / 2 | |
| 1.0.5 | 12 / 2 | |
| 1.0.4 | 12 / 2 | |
| 1.0.3 | 12 / 2 | |
| 1.0.2 | 12 / 2 | |
| 1.0.1 | 12 / 2 | |
| 1.0.0 | 12 / 2 | |
| 0.5.0 | 30 / 7 | |
| 0.4.3 | 30 / 7 | |
| 0.4.2 | 30 / 7 | |
| 0.4.1 | 30 / 7 | |
| 0.4.0 | 30 / 7 | |
| 0.3.2 | 30 / 7 | |
| 0.3.1 | 30 / 7 | |
| 0.3.0 | 30 / 6 | |
| 0.2.0 | 30 / 6 | |
| 0.1.1 | 30 / 6 | |
| 0.1.0 | 30 / 6 |
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.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage 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 findingPackage 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.5.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.4.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.4.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.4.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.4.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.3.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.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.
v0.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.
v0.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.
v0.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.
v0.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.