@phosphor/commands
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/domutils | AI (phantom-deps): Same-org @phosphor/* sibling package; phantom detection is a false positive for monorepo-style packages that re-export or use TypeScript namespaces. | ai | |
| phantom-deps | phantom-dep:@phosphor/algorithm | AI (phantom-deps): Same-org @phosphor/* sibling package; consistent with monorepo TypeScript compilation patterns. | ai | |
| phantom-deps | phantom-dep:@phosphor/coreutils | AI (phantom-deps): Same-org @phosphor/* sibling package; consistent with monorepo TypeScript compilation patterns. | ai | |
| phantom-deps | phantom-dep:@phosphor/signaling | AI (phantom-deps): Same-org @phosphor/* sibling package; consistent with monorepo TypeScript compilation patterns. | ai | |
| phantom-deps | phantom-dep:@phosphor/disposable | AI (phantom-deps): Same-org @phosphor/* sibling package; consistent with monorepo TypeScript compilation patterns. | ai | |
| phantom-deps | phantom-dep:@phosphor/keyboard | AI (phantom-deps): Same-org @phosphor/* sibling package; consistent with monorepo TypeScript compilation patterns. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'phosphor' maintainer is part of the same documented 2018 project transition; no hostile takeover indicators. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from sccolbert to blink1073 reflects the documented 2018 PhosphorJS project transition; blink1073 is a listed contributor and highly trusted publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): blink1073 and phosphor-user were added as part of the legitimate 2018 PhosphorJS project handoff to the Jupyter ecosystem. | ai | |
| dependencies | unvetted-dep:@phosphor/coreutils | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai | |
| dependencies | unvetted-dep:@phosphor/signaling | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai | |
| dependencies | unvetted-dep:@phosphor/disposable | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai | |
| dependencies | unvetted-dep:@phosphor/domutils | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai | |
| typosquat | typosquat.levenshtein:commander | AI (typosquat): @phosphor/commands is a scoped package in the PhosphorJS framework, not a typosquat of 'commander'. The match is a false positive due to edit distance on unrelated names. | ai | |
| dependencies | unvetted-dep:@phosphor/keyboard | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai | |
| dependencies | unvetted-dep:@phosphor/algorithm | AI (dependencies): First-party sibling package from the same PhosphorJS monorepo (github.com/phosphorjs/phosphor). | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.7.2 | 6 / 16 | |
| 1.7.1 | 6 / 16 | |
| 1.7.0 | 6 / 16 | |
| 1.6.3 | 6 / 16 | |
| 1.6.2 | 6 / 16 | |
| 1.6.1 | 6 / 3 | |
| 1.6.0 | 6 / 3 | |
| 1.5.0 | 6 / 3 | |
| 1.4.0 | 6 / 3 | |
| 1.3.0 | 6 / 3 | |
| 1.2.3 | 6 / 3 | |
| 1.2.2 | 6 / 3 | |
| 1.2.1 | 6 / 3 | |
| 1.2.0 | 6 / 3 | |
| 1.1.0 | 6 / 2 | |
| 1.0.0 | 6 / 2 | |
| 0.1.5 | 6 / 2 | |
| 0.1.4 | 6 / 2 | |
| 0.1.3 | 6 / 0 | |
| 0.1.2 | 6 / 0 | |
| 0.1.1 | 6 / 0 | |
| 0.1.0 | 5 / 0 |
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.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.
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-08-05. 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.6.3
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version was published by a different npm account than previous versions on 2018-09-05. 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.6.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-05. 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.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.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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 2017-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.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 2017-02-20. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.