← Home

@jupyterlab/apputils

JupyterLab - Application Utilities

8
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

Keywords

jupyterjupyterlabjupyterlab-extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@jupyterlab/coreutils AI (phantom-deps): Same org scope (@jupyterlab); likely used indirectly or re-exported. Stable false positive for this package. ai
phantom-deps phantom-dep:@types/sanitize-html AI (phantom-deps): Type-only dependency used at compile time, not directly imported at runtime; stable false positive for this package. ai
dependencies unvetted-dep:@types/sanitize-html AI (dependencies): @types/sanitize-html is a TypeScript type definition package for the already-declared sanitize-html runtime dep; its presence as a dependency is a benign early-TypeScript pattern for this package. ai
provenance publisher-changed AI (provenance): jtpio is a well-known JupyterLab core contributor with 1696 approved packages; publisher change from jasongrout is a legitimate project maintainer transition. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers (krassowski, goanpeca, mbektas, loichuder) are known JupyterLab contributors; this is a normal team expansion for an active open-source project. ai
provenance missing-githead AI (provenance): Missing gitHead is consistent with a CI/tooling change during maintainer transition; no malware indicators present. ai
phantom-deps phantom-dep:buffer AI (phantom-deps): Buffer polyfill is a standard pattern for browser-targeting libraries; declared for build/bundler use. ai
provenance no-provenance AI (provenance): Provenance is uncommon (12% adoption); not a material risk for established JupyterLab package. ai
phantom-deps phantom-dep:url AI (phantom-deps): url is a well-known Node.js URL polyfill; phantom detection in config files is a stable false positive for this package. ai
publish-pattern new-deps-added AI (publish-pattern): Diff is cross-major-branch (3.x vs 4.x); added deps are well-known Lumino/React packages consistent with JupyterLab 3.x dependency surface. Not a suspicious addition. ai
maintainer-change maintainer-removed AI (maintainer-change): JupyterLab uses a centralized release bot (jupyterlab-release-bot) for publishing; individual maintainer removals are expected organizational changes, not takeover indicators. ai
dependencies unvetted-dep:@jupyterlab/services AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/coreutils AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/observables AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/translation AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/ui-components AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/settingregistry AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/rendermime-interfaces AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/statusbar AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/widgets AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/commands AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/domutils AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/algorithm AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/coreutils AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/messaging AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/signaling AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/disposable AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@lumino/virtualdom AI (dependencies): First-party Lumino package from the JupyterLab ecosystem monorepo; stable long-term dependency. ai
dependencies unvetted-dep:@jupyterlab/statedb AI (dependencies): First-party JupyterLab package from the same monorepo; stable long-term dependency. ai
dependencies unvetted-dep:sanitize-html AI (dependencies): sanitize-html is a well-known HTML sanitization library; its use in a JupyterLab UI utilities package is legitimate and expected. No advisories affect the pinned range. ai
bogus-package bogus-package AI (bogus-package): JupyterLab monorepo packages always publish at coordinated high semver versions and have minimal sub-package READMEs. These signals are structural false positives for this package. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): @types/react is intentionally listed as a runtime dep in JupyterLab packages for type-sharing conventions; not a security concern. ai

Versions (showing 8 of 8)

Version Deps Published
4.6.7 21 / 6
3.2.7 22 / 9
3.2.6 22 / 9
3.1.16 21 / 9
1.2.4 17 / 5
0.16.0 16 / 4
0.7.0 14 / 2
0.1.1 15 / 2

v4.6.7

3 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Publisher changed: jtpio → GitHub Actions (on 2026-04-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.

v3.2.7

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jtpio.

HIGH Publisher changed: jasongrout → jtpio (on 2022-01-12) provenance

This version was published by a different npm account than previous versions on 2022-01-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.6

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jtpio.

HIGH Publisher changed: jasongrout → jtpio (on 2022-01-07) provenance

This version was published by a different npm account than previous versions on 2022-01-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.16

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.

HIGH Publisher changed: jasongrout → blink1073 (on 2021-10-05) provenance

This version was published by a different npm account than previous versions on 2021-10-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: blink1073 → darian (on 2018-04-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-11. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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.