@jupyterlab/shared-models
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): Trusted publisher (blink1073) with 3655 approved packages; missing gitHead reflects a publish environment change, not a security risk for this well-established JupyterLab package. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is a best-practice gap, not a security threat, for this long-established package from a highly trusted publisher. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to jupyterlab-release-bot, the official JupyterLab CI/CD release automation account with 3556 approved packages. This is a permanent, legitimate transition for the JupyterLab org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 3.x is a maintenance branch; infrequent patch releases are expected. SLSA attestation confirms legitimate CI/CD origin, ruling out account takeover. | ai | |
| phantom-deps | phantom-dep:@jupyterlab/nbformat | AI (phantom-deps): Same-org dependency used for types/transitive purposes; standard pattern in the JupyterLab monorepo ecosystem. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.6.8 | 2 / 2 | |
| 3.6.7 | 2 / 2 | |
| 3.6.6 | 2 / 2 | |
| 3.6.5 | 2 / 2 | |
| 3.6.4 | 2 / 2 | |
| 3.6.3 | 2 / 2 | |
| 3.6.2 | 2 / 2 | |
| 3.5.3 | 6 / 6 | |
| 3.5.2 | 6 / 6 | |
| 3.5.1 | 6 / 6 | |
| 3.5.0 | 6 / 6 | |
| 3.4.8 | 6 / 6 | |
| 3.4.7 | 6 / 6 | |
| 3.4.6 | 6 / 6 | |
| 3.4.5 | 6 / 6 | |
| 3.4.4 | 6 / 6 | |
| 3.4.3 | 6 / 6 | |
| 3.4.2 | 6 / 6 | |
| 3.4.1 | 6 / 6 | |
| 3.4.0 | 6 / 6 | |
| 3.3.4 | 6 / 6 | |
| 3.3.3 | 6 / 6 | |
| 3.3.2 | 6 / 6 | |
| 3.3.1 | 6 / 6 | |
| 3.3.0 | 6 / 6 | |
| 3.2.9 | 6 / 6 | |
| 3.2.8 | 6 / 6 | |
| 3.2.7 | 6 / 6 | |
| 3.2.6 | 6 / 6 | |
| 3.2.5 | 6 / 6 | |
| 3.2.4 | 6 / 6 | |
| 3.2.3 | 6 / 6 | |
| 3.2.2 | 6 / 6 | |
| 3.2.1 | 6 / 6 | |
| 3.2.0 | 6 / 6 | |
| 3.1.18 | 6 / 6 | |
| 3.1.17 | 6 / 6 | |
| 3.1.16 | 6 / 6 | |
| 3.1.15 | 6 / 6 | |
| 3.1.13 | 6 / 6 | |
| 3.1.12 | 6 / 6 | |
| 3.1.11 | 6 / 6 | |
| 3.1.10 | 6 / 6 | |
| 3.1.9 | 6 / 6 | |
| 3.1.8 | 6 / 6 | |
| 3.1.7 | 6 / 6 | |
| 3.1.6 | 6 / 6 | |
| 3.1.5 | 6 / 6 | |
| 3.1.4 | 6 / 6 | |
| 3.1.3 | 6 / 6 | |
| 3.1.2 | 6 / 6 |
v3.6.8
2 findingsThis version was published by a different npm account than previous versions on 2024-08-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
2 findingsPackage 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 2023-09-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.5
2 findingsPackage 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 2023-06-26. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.4
2 findingsPackage 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 2023-05-31. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
2 findingsPackage 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-12-05. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.0
2 findingsPackage 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-10-24. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
2 findingsPackage 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-07-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.3
2 findingsPackage 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-06-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.2
2 findingsPackage 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-05-13. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.1
2 findingsPackage 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-05-12. This could indicate a legitimate maintainer transition or an account compromise.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
2 findingsPackage 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-04-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.3
2 findingsPackage 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-04-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.2
2 findingsPackage 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-03-14. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.1
2 findingsPackage 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-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
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: jtpio.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
2 findingsPackage 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-01-07. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.5
2 findingsPackage 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 2021-12-10. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.4
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: blink1073.
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 2021-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.3
2 findingsPackage 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 2021-11-11. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.2
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.
v3.2.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.
v3.2.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.
v3.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.17
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.
v3.1.16
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.
v3.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
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.
v3.1.12
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.
v3.1.11
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.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.