@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 |
|---|---|---|
| 4.5.7 | 20 / 5 | |
| 4.5.6 | 20 / 5 | |
| 4.5.5 | 20 / 5 | |
| 4.5.4 | 20 / 5 | |
| 4.5.3 | 20 / 5 | |
| 4.5.2 | 20 / 5 | |
| 4.5.1 | 20 / 5 | |
| 4.5.0 | 20 / 5 | |
| 4.4.10 | 20 / 5 | |
| 4.4.9 | 20 / 5 | |
| 4.4.8 | 20 / 5 | |
| 4.4.7 | 20 / 5 | |
| 4.4.6 | 20 / 5 | |
| 4.4.5 | 20 / 5 | |
| 4.4.4 | 20 / 5 | |
| 4.4.3 | 20 / 5 | |
| 4.4.2 | 20 / 5 | |
| 4.4.1 | 20 / 5 | |
| 4.4.0 | 20 / 5 | |
| 4.3.8 | 20 / 5 | |
| 4.3.7 | 20 / 5 | |
| 4.3.6 | 20 / 5 | |
| 4.3.5 | 20 / 5 | |
| 4.3.4 | 20 / 5 | |
| 4.3.3 | 20 / 5 | |
| 4.3.2 | 20 / 5 | |
| 4.3.1 | 20 / 5 | |
| 4.3.0 | 20 / 5 | |
| 4.2.7 | 20 / 5 | |
| 4.2.6 | 20 / 5 | |
| 4.2.5 | 20 / 5 | |
| 4.2.4 | 20 / 5 | |
| 4.2.3 | 20 / 5 | |
| 4.2.2 | 20 / 5 | |
| 4.2.1 | 20 / 5 | |
| 4.2.0 | 20 / 5 | |
| 4.1.8 | 20 / 6 | |
| 4.1.7 | 20 / 6 | |
| 4.1.6 | 20 / 6 | |
| 4.1.5 | 20 / 6 | |
| 4.1.4 | 20 / 6 | |
| 4.1.3 | 20 / 6 | |
| 4.1.2 | 20 / 6 | |
| 4.1.1 | 20 / 6 | |
| 4.1.0 | 20 / 6 | |
| 4.0.13 | 20 / 6 | |
| 4.0.12 | 20 / 6 | |
| 4.0.11 | 20 / 6 | |
| 4.0.10 | 20 / 6 | |
| 4.0.9 | 20 / 6 | |
| 4.0.8 | 20 / 6 | |
| 4.0.7 | 20 / 6 | |
| 4.0.6 | 20 / 6 | |
| 4.0.5 | 20 / 6 | |
| 4.0.4 | 20 / 6 | |
| 4.0.3 | 20 / 6 | |
| 4.0.2 | 20 / 6 | |
| 4.0.1 | 20 / 6 | |
| 4.0.0 | 20 / 6 | |
| 3.6.8 | 20 / 7 | |
| 3.6.7 | 20 / 7 | |
| 3.6.6 | 20 / 7 | |
| 3.6.5 | 20 / 7 | |
| 3.6.4 | 20 / 7 | |
| 3.6.3 | 20 / 7 | |
| 3.6.2 | 20 / 7 | |
| 3.6.1 | 20 / 7 | |
| 3.6.0 | 20 / 7 | |
| 3.5.3 | 20 / 7 | |
| 3.5.2 | 20 / 7 | |
| 3.5.1 | 20 / 7 | |
| 3.5.0 | 20 / 7 | |
| 3.4.8 | 20 / 7 | |
| 3.4.7 | 20 / 7 | |
| 3.4.6 | 20 / 7 | |
| 3.4.5 | 20 / 7 | |
| 3.4.4 | 20 / 7 | |
| 3.4.3 | 20 / 7 | |
| 3.4.2 | 20 / 7 | |
| 3.4.1 | 20 / 7 | |
| 3.4.0 | 20 / 7 | |
| 3.3.4 | 20 / 7 | |
| 3.3.3 | 20 / 7 | |
| 3.3.2 | 20 / 7 | |
| 3.3.1 | 20 / 7 | |
| 3.3.0 | 20 / 7 | |
| 3.2.9 | 20 / 7 | |
| 3.2.8 | 20 / 7 | |
| 3.2.7 | 20 / 7 | |
| 3.2.6 | 20 / 7 | |
| 3.2.5 | 20 / 7 | |
| 3.2.4 | 20 / 7 | |
| 3.2.3 | 20 / 7 | |
| 3.2.2 | 20 / 7 | |
| 3.2.1 | 20 / 7 | |
| 3.2.0 | 20 / 7 | |
| 3.1.18 | 20 / 7 | |
| 3.1.17 | 20 / 7 | |
| 3.1.16 | 20 / 7 | |
| 3.1.15 | 20 / 7 |
v4.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.