@jupyterlab/coreutils
JupyterLab - Core Utilities
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:path-posix | AI (dependencies): path-posix is a well-known, stable POSIX path utility. No security concerns with this dependency. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') in pageconfig.js is a documented Webpack trick to prevent static analysis of dynamic require calls — a stable, legitimate pattern in this package. | ai | |
| phantom-deps | phantom-dep:path-browserify | AI (phantom-deps): path-browserify is declared in the browser field as a path module substitute — not directly imported in JS but legitimately referenced in package.json config. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects JupyterLab monorepo versioning convention; short README and no keywords are quality issues, not security signals. SLSA provenance confirms legitimate CI/CD origin. | ai |
Versions (showing 79 of 179)
| Version | Deps | Published |
|---|---|---|
| 5.1.12 | 7 / 10 | |
| 5.1.11 | 7 / 10 | |
| 5.1.10 | 7 / 10 | |
| 5.1.9 | 7 / 10 | |
| 5.1.8 | 7 / 10 | |
| 5.1.7 | 7 / 10 | |
| 5.1.6 | 7 / 10 | |
| 5.1.5 | 7 / 10 | |
| 5.1.4 | 7 / 10 | |
| 5.1.3 | 7 / 10 | |
| 5.1.2 | 7 / 10 | |
| 5.1.1 | 7 / 10 | |
| 5.1.0 | 7 / 10 | |
| 5.0.7 | 7 / 10 | |
| 5.0.6 | 7 / 10 | |
| 5.0.5 | 7 / 10 | |
| 5.0.4 | 7 / 10 | |
| 5.0.3 | 7 / 10 | |
| 5.0.2 | 7 / 10 | |
| 5.0.1 | 7 / 10 | |
| 5.0.0 | 7 / 10 | |
| 4.3.1 | 7 / 9 | |
| 4.3.0 | 7 / 9 | |
| 4.2.5 | 7 / 9 | |
| 4.2.4 | 7 / 8 | |
| 4.2.3 | 7 / 8 | |
| 4.2.2 | 7 / 8 | |
| 4.2.1 | 7 / 8 | |
| 4.2.0 | 7 / 8 | |
| 4.1.0 | 7 / 4 | |
| 4.0.2 | 7 / 4 | |
| 4.0.1 | 7 / 4 | |
| 4.0.0 | 7 / 4 | |
| 3.2.0 | 11 / 5 | |
| 3.1.0 | 11 / 5 | |
| 3.0.1 | 11 / 5 | |
| 3.0.0 | 11 / 5 | |
| 2.2.1 | 10 / 5 | |
| 2.1.4 | 10 / 4 | |
| 2.1.3 | 10 / 4 | |
| 2.1.2 | 10 / 4 | |
| 2.1.0 | 10 / 4 | |
| 2.0.3 | 10 / 4 | |
| 2.0.2 | 10 / 4 | |
| 2.0.1 | 10 / 4 | |
| 1.1.3 | 10 / 4 | |
| 1.1.2 | 10 / 4 | |
| 1.1.1 | 10 / 4 | |
| 1.1.0 | 10 / 4 | |
| 1.0.10 | 10 / 4 | |
| 1.0.9 | 10 / 4 | |
| 1.0.8 | 10 / 4 | |
| 1.0.7 | 10 / 4 | |
| 1.0.6 | 10 / 4 | |
| 1.0.5 | 10 / 4 | |
| 1.0.4 | 10 / 4 | |
| 1.0.3 | 10 / 4 | |
| 1.0.2 | 10 / 4 | |
| 1.0.1 | 10 / 4 | |
| 1.0.0 | 10 / 4 | |
| 0.13.0 | 10 / 4 | |
| 0.12.0 | 10 / 3 | |
| 0.11.1 | 10 / 4 | |
| 0.11.0 | 10 / 4 | |
| 0.10.1 | 10 / 4 | |
| 0.10.0 | 10 / 4 | |
| 0.9.0 | 10 / 4 | |
| 0.8.1 | 10 / 4 | |
| 0.8.0 | 10 / 4 | |
| 0.7.1 | 9 / 3 | |
| 0.7.0 | 9 / 3 | |
| 0.6.0 | 9 / 3 | |
| 0.5.0 | 8 / 2 | |
| 0.4.0 | 8 / 2 | |
| 0.3.1 | 8 / 2 | |
| 0.3.0 | 8 / 2 | |
| 0.2.0 | 8 / 2 | |
| 0.1.3 | 8 / 2 | |
| 0.1.1 | 8 / 2 |
v5.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
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.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.0
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.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
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.
v1.1.3
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
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.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.