@jupyterlab/ui-components
JupyterLab - UI components written in React
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@blueprintjs/core | AI (dependencies): BlueprintJS is a well-known Palantir React UI library; a legitimate dependency in JupyterLab 3.x branch. Not a security concern. | ai | |
| dependencies | unvetted-dep:@blueprintjs/select | AI (dependencies): BlueprintJS Select is part of the Palantir BlueprintJS suite; legitimate dependency in JupyterLab 3.x branch. | ai | |
| phantom-deps | phantom-dep:@lumino/commands | AI (phantom-deps): @lumino/commands is declared for transitive/config use in JupyterLab; not a security concern for this package. | ai | |
| dependencies | unvetted-dep:@lumino/polling | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency for JupyterLab ecosystem packages. | ai | |
| dependencies | unvetted-dep:@lumino/widgets | AI (dependencies): Official Jupyter/Lumino package; core widget library for JupyterLab. | ai | |
| dependencies | unvetted-dep:@lumino/commands | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@lumino/algorithm | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@lumino/coreutils | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@lumino/messaging | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@lumino/signaling | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@lumino/disposable | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:typestyle | AI (dependencies): typestyle is a well-established CSS-in-JS library; legitimate dependency for a UI components package. | ai | |
| dependencies | unvetted-dep:@lumino/virtualdom | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@jupyterlab/coreutils | AI (dependencies): Official JupyterLab sibling package; expected dependency within the monorepo. | ai | |
| dependencies | unvetted-dep:@jupyter/web-components | AI (dependencies): Official Jupyter web components package; legitimate dependency for JupyterLab UI. | ai | |
| dependencies | unvetted-dep:@jupyterlab/observables | AI (dependencies): Official JupyterLab sibling package; expected dependency within the monorepo. | ai | |
| dependencies | unvetted-dep:@jupyterlab/translation | AI (dependencies): Official JupyterLab sibling package; expected dependency within the monorepo. | ai | |
| dependencies | unvetted-dep:@jupyter/react-components | AI (dependencies): Official Jupyter React components package; legitimate dependency for JupyterLab UI. | ai | |
| dependencies | unvetted-dep:@jupyterlab/rendermime-interfaces | AI (dependencies): Official JupyterLab sibling package; expected dependency within the monorepo. | ai | |
| dependencies | unvetted-dep:@lumino/properties | AI (dependencies): Official Jupyter/Lumino package; legitimate dependency. | ai | |
| dependencies | unvetted-dep:@rjsf/core | AI (dependencies): react-jsonschema-form (@rjsf/core) is a widely-used, legitimate form library; expected dependency for JupyterLab UI. | ai | |
| dependencies | unvetted-dep:@rjsf/utils | AI (dependencies): Sibling utility package of @rjsf/core; same rationale applies. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 3.1.12 | 13 / 15 | |
| 3.1.11 | 13 / 15 | |
| 3.1.10 | 13 / 15 | |
| 3.1.9 | 12 / 15 | |
| 3.1.8 | 12 / 15 | |
| 3.1.7 | 12 / 15 | |
| 3.1.6 | 12 / 15 | |
| 3.1.5 | 12 / 15 | |
| 3.1.4 | 12 / 15 | |
| 3.1.3 | 12 / 15 | |
| 3.1.2 | 12 / 15 | |
| 3.1.1 | 12 / 15 | |
| 3.1.0 | 12 / 15 | |
| 3.0.8 | 10 / 15 | |
| 3.0.7 | 10 / 15 | |
| 3.0.6 | 10 / 15 | |
| 3.0.5 | 10 / 15 | |
| 3.0.4 | 10 / 15 | |
| 3.0.3 | 10 / 15 | |
| 3.0.2 | 10 / 15 | |
| 3.0.1 | 10 / 15 | |
| 3.0.0 | 10 / 15 | |
| 2.3.1 | 10 / 17 | |
| 2.3.0 | 10 / 17 | |
| 2.2.4 | 10 / 17 | |
| 2.2.3 | 10 / 17 | |
| 2.2.2 | 10 / 17 | |
| 2.2.1 | 10 / 17 | |
| 2.2.0 | 10 / 17 | |
| 2.1.1 | 10 / 13 | |
| 2.1.0 | 10 / 13 | |
| 2.0.2 | 10 / 13 | |
| 2.0.1 | 10 / 13 | |
| 2.0.0 | 10 / 13 | |
| 1.2.1 | 9 / 5 | |
| 1.2.0 | 9 / 5 | |
| 1.1.2 | 9 / 5 | |
| 1.1.1 | 9 / 5 | |
| 1.1.0 | 9 / 5 | |
| 1.0.0 | 4 / 4 |
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.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.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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.