@lumino/commands
Lumino Commands
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 ecosystem package with trusted publisher (blink1073, 1715 approved). Lack of Sigstore attestation is a process gap, not a security indicator for this package. | ai | |
| dependencies | unvetted-dep:@lumino/domutils | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@lumino/keyboard | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@lumino/coreutils | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@lumino/signaling | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@lumino/virtualdom | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| dependencies | unvetted-dep:@lumino/disposable | AI (dependencies): Sibling package in the JupyterLab/Lumino monorepo, published by the same trusted jupyterlab-release-bot. Not a third-party unvetted dependency. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fcollonval and jupyterlab-release-bot are legitimate JupyterLab project maintainers/automation; this reflects an organizational transition, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of ian-r-rose is consistent with the documented JupyterLab maintainer transition; no malicious signal. | ai | |
| provenance | publisher-changed | AI (provenance): fcollonval is a well-established JupyterLab contributor with 1710 approved packages; publisher change reflects legitimate project maintainer transition. | ai | |
| typosquat | typosquat.levenshtein:commander | AI (typosquat): @lumino/commands is the official JupyterLab Lumino command registry package, not a typosquat of 'commander'. The scoped @lumino namespace and SLSA provenance confirm legitimacy. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 2.3.3 | 7 / 18 | |
| 2.3.2 | 7 / 18 | |
| 2.3.1 | 7 / 18 | |
| 2.3.0 | 7 / 23 | |
| 2.2.0 | 7 / 23 | |
| 2.1.3 | 7 / 23 | |
| 2.1.2 | 7 / 24 | |
| 2.1.1 | 7 / 24 | |
| 2.1.0 | 7 / 24 | |
| 2.0.1 | 7 / 24 | |
| 2.0.0 | 7 / 24 | |
| 1.21.1 | 7 / 24 | |
| 1.21.0 | 7 / 24 | |
| 1.20.1 | 7 / 24 | |
| 1.20.0 | 7 / 24 | |
| 1.19.1 | 7 / 24 | |
| 1.19.0 | 7 / 24 | |
| 1.15.2 | 7 / 24 | |
| 1.15.1 | 7 / 24 | |
| 1.15.0 | 7 / 24 | |
| 1.14.0 | 7 / 24 | |
| 1.13.0 | 7 / 24 | |
| 1.12.1 | 7 / 24 | |
| 1.12.0 | 7 / 24 | |
| 1.11.4 | 7 / 24 | |
| 1.11.3 | 7 / 24 | |
| 1.11.2 | 7 / 24 | |
| 1.11.1 | 7 / 25 | |
| 1.11.0 | 7 / 24 | |
| 1.10.3 | 7 / 18 | |
| 1.10.2 | 7 / 18 | |
| 1.10.1 | 7 / 18 | |
| 1.10.0 | 7 / 18 | |
| 1.9.2 | 6 / 18 | |
| 1.9.1 | 6 / 18 | |
| 1.9.0 | 6 / 18 | |
| 1.8.1 | 6 / 18 | |
| 1.8.0 | 6 / 17 | |
| 1.7.2 | 6 / 16 |
v2.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v2.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
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.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.21.1
2 findingsThis version was published by a different npm account than previous versions on 2023-01-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsThis version was published by a different npm account than previous versions on 2022-08-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: blink1073.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.