@lumino/signaling
Lumino Signals and Slots
30
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
blink1073ellisonbgdarianjasongroutjtpiofcollonvalkrassowski
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted publisher (blink1073) with extensive history; missing gitHead is a minor metadata gap, not a security concern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from fcollonval to jupyterlab-release-bot is the standard JupyterLab org move to automated releases; stable for all @lumino packages. | ai | |
| provenance | no-provenance | AI (provenance): Lumino packages published before provenance adoption; trusted publisher with extensive track record. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.1.6 | 2 / 19 | |
| 2.1.5 | 2 / 19 | |
| 2.1.4 | 2 / 19 | |
| 2.1.3 | 2 / 19 | |
| 2.1.2 | 2 / 24 | |
| 2.1.1 | 2 / 25 | |
| 2.1.0 | 2 / 25 | |
| 2.0.0 | 2 / 25 | |
| 1.11.1 | 2 / 22 | |
| 1.11.0 | 2 / 22 | |
| 1.10.2 | 1 / 22 | |
| 1.10.1 | 1 / 22 | |
| 1.10.0 | 1 / 22 | |
| 1.9.0 | 1 / 22 | |
| 1.8.0 | 1 / 22 | |
| 1.7.2 | 1 / 22 | |
| 1.7.1 | 1 / 22 | |
| 1.7.0 | 1 / 22 | |
| 1.6.0 | 1 / 22 | |
| 1.5.0 | 1 / 22 | |
| 1.4.3 | 1 / 22 | |
| 1.4.2 | 1 / 22 | |
| 1.4.1 | 1 / 23 | |
| 1.4.0 | 1 / 22 | |
| 1.3.6 | 1 / 16 | |
| 1.3.5 | 1 / 16 | |
| 1.3.4 | 1 / 16 | |
| 1.3.3 | 1 / 16 | |
| 1.3.2 | 1 / 15 | |
| 1.3.1 | 1 / 14 |
v2.1.6
2 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
Publisher changed: jupyterlab-release-bot → GitHub Actions (on 2026-07-03)
provenance
[Accepted risk] This version was published by a different npm account than previous versions on 2026-07-03. This could indicate a legitimate maintainer transition or an account compromise.