@lumino/collections
Lumino Generic Collections
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 | missing-githead | AI (provenance): Consistent with maintainer transition within JupyterLab org; publisher fcollonval is a well-established JupyterLab contributor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal team transition within the JupyterLab organization; removed maintainer was replaced by known JupyterLab contributors. | ai | |
| provenance | publisher-changed | AI (provenance): jupyterlab-release-bot is the official JupyterLab CI/CD publisher (3583 approved, 0 rejected). Transition from fcollonval is a standard org move to automated releases. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jupyterlab-release-bot is the standard JupyterLab release automation account; adding it as maintainer is expected. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 1 / 18 | |
| 2.0.3 | 1 / 18 | |
| 2.0.2 | 1 / 18 | |
| 2.0.1 | 1 / 23 | |
| 2.0.0 | 1 / 24 | |
| 1.9.3 | 1 / 22 | |
| 1.9.2 | 1 / 22 | |
| 1.9.1 | 1 / 22 | |
| 1.9.0 | 1 / 22 | |
| 1.8.0 | 1 / 22 | |
| 1.7.0 | 1 / 22 | |
| 1.6.2 | 1 / 22 | |
| 1.6.1 | 1 / 22 | |
| 1.6.0 | 1 / 22 | |
| 1.5.0 | 1 / 22 | |
| 1.4.0 | 1 / 22 | |
| 1.3.3 | 1 / 22 | |
| 1.3.2 | 1 / 22 | |
| 1.3.1 | 1 / 23 | |
| 1.3.0 | 1 / 22 | |
| 1.2.3 | 1 / 16 | |
| 1.2.2 | 1 / 16 | |
| 1.2.1 | 1 / 15 | |
| 1.2.0 | 1 / 14 |
v2.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2023-03-15. 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.9.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: fcollonval.
v1.9.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: fcollonval.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v1.9.1
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: jasongrout.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v1.9.0
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.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: blink1073.
v1.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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: blink1073.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.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.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.