← Home

@jupyterlab/application

JupyterLab - Application

7
Versions
BSD-3-Clause
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

darianblink1073jasongroutfcollonvaljtpiombektaskrassowskijupyterlab-release-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 7 of 207)

Version Deps Published
0.5.0 7 / 2
0.4.0 7 / 2
0.3.1 7 / 2
0.3.0 7 / 2
0.2.0 7 / 2
0.1.3 7 / 2
0.1.1 7 / 2

v0.5.0

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.