@lumino/messaging — Greenflagged

Lumino Message Passing

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

blink1073ellisonbgdarianjasongroutjtpiojupyterlab-release-botfcollonval

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change reflects a legitimate JupyterLab org maintainer transition; fcollonval is a highly trusted publisher with 1726 approved packages and 0 rejections.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers (fcollonval, jtpio, jasongrout) are well-known JupyterLab contributors; this is a legitimate org-level maintainer update.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of ian-r-rose is consistent with a routine JupyterLab org maintainer rotation, not a hostile takeover.	ai	2026/04/23
provenance	missing-githead	AI (provenance): Established JupyterLab ecosystem package with trusted publisher (blink1073, 1721 approved). Missing gitHead reflects a publish environment change, not a security concern.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Lumino packages predate Sigstore provenance; absence is expected for this package family and not a security risk given publisher track record.	ai	2026/04/23
dependencies	unvetted-dep:@lumino/collections	AI (dependencies): Dependency is within the same @lumino monorepo ecosystem; version constraint is pinned appropriately.	ai	2026/04/21

Versions (showing 24 of 24)

Version	Deps	Published
2.0.4	2 / 19	2025-11-13
2.0.3	2 / 19	2025-03-31
2.0.2	2 / 19	2024-06-28
2.0.1	2 / 24	2023-07-27
2.0.0	2 / 25	2023-03-15
1.10.3	2 / 23	2022-10-05
1.10.2	2 / 23	2022-08-08
1.10.1	2 / 23	2021-11-04
1.10.0	2 / 23	2021-10-25
1.9.0	2 / 23	2021-09-30
1.8.0	2 / 23	2021-09-22
1.7.2	2 / 23	2021-08-23
1.7.1	2 / 23	2021-08-12
1.7.0	2 / 23	2021-04-27
1.6.0	2 / 23	2021-04-19
1.5.0	2 / 23	2021-04-09
1.4.3	2 / 23	2020-07-21
1.4.2	2 / 23	2020-06-26
1.4.1	2 / 24	2020-06-25
1.4.0	2 / 23	2020-05-23
1.3.3	2 / 17	2020-01-02
1.3.2	2 / 17	2019-12-17
1.3.1	2 / 15	2019-12-09
1.3.0	2 / 14	2019-11-17

v2.0.4

1 finding

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.

v2.0.3

1 finding

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.

v2.0.2

1 finding

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.

v2.0.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.10.3

3 findings

HIGH Missing gitHead — previous versions had it provenance

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.

HIGH Publisher changed: blink1073 → fcollonval (on 2022-10-05) provenance

This version was published by a different npm account than previous versions on 2022-10-05. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.2

3 findings

HIGH Missing gitHead — previous versions had it provenance

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.

HIGH Publisher changed: blink1073 → fcollonval (on 2022-08-08) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

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.

HIGH Publisher changed: blink1073 → jasongrout (on 2021-11-04) provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.