@phosphor/widgets
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@phosphor/virtualdom | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/algorithm | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/coreutils | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/messaging | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/signaling | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/disposable | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/properties | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/commands | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/domutils | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/dragdrop | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| phantom-deps | phantom-dep:@phosphor/keyboard | AI (phantom-deps): Phantom deps in @phosphor/* framework libraries are expected; dependencies are re-exported or used indirectly through the public API. | ai | |
| dependencies | unvetted-dep:@phosphor/utilities | AI (dependencies): @phosphor/utilities is a sibling package in the same PhosphorJS ecosystem/monorepo, published by the same trusted publisher. This dependency relationship is stable and expected across all versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): blink1073 and phosphor-user are legitimate maintainers for the PhosphorJS ecosystem; blink1073 was already a contributor. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'phosphor' account alongside addition of blink1073/phosphor-user reflects a legitimate project maintainer reorganization. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): PhosphorJS is a mature, largely stable library; long dormancy followed by a maintenance release from a known contributor is expected behavior for this package. | ai | |
| provenance | publisher-changed | AI (provenance): blink1073 (Steven Silvester) was already a listed contributor in package.json; transition from sccolbert is a documented legitimate handoff within the PhosphorJS project. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected for this age cohort and not a security signal. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.9.3 | 11 / 18 | |
| 1.9.2 | 11 / 18 | |
| 1.9.1 | 11 / 18 | |
| 1.9.0 | 11 / 18 | |
| 1.8.1 | 11 / 18 | |
| 1.8.0 | 11 / 18 | |
| 1.7.1 | 11 / 18 | |
| 1.7.0 | 11 / 18 | |
| 1.6.0 | 11 / 3 | |
| 1.5.0 | 11 / 3 | |
| 1.4.0 | 11 / 3 | |
| 1.3.2 | 11 / 3 | |
| 1.3.1 | 11 / 3 | |
| 1.3.0 | 11 / 3 | |
| 1.2.0 | 11 / 3 | |
| 1.1.0 | 11 / 2 | |
| 1.0.1 | 11 / 2 | |
| 1.0.0 | 11 / 2 | |
| 0.3.1 | 11 / 2 | |
| 0.3.0 | 11 / 2 | |
| 0.2.0 | 11 / 2 | |
| 0.1.7 | 11 / 2 | |
| 0.1.6 | 11 / 2 | |
| 0.1.5 | 11 / 0 | |
| 0.1.4 | 11 / 0 | |
| 0.1.3 | 11 / 0 | |
| 0.1.2 | 11 / 0 | |
| 0.1.1 | 10 / 0 | |
| 0.1.0 | 10 / 0 |
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
2 findingsThis version was published by a different npm account than previous versions on 2019-09-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findingsThis version was published by a different npm account than previous versions on 2019-09-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
2 findingsThis version was published by a different npm account than previous versions on 2019-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsThis version was published by a different npm account than previous versions on 2019-06-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
2 findingsThis version was published by a different npm account than previous versions on 2019-06-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2019-06-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.