← Home

@phosphor/collections

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

blink1073phosphor-usersccolbert

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): blink1073 (Steven Silvester) was already a listed contributor in package.json and has a strong npm track record (3783 approved packages). This is a legitimate maintainer transition for the PhosphorJS project. ai
maintainer-change maintainer-added AI (maintainer-change): blink1073 is a well-established npm publisher with strong track record; phosphor-user is a project account. Addition is consistent with legitimate PhosphorJS project governance transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of 'phosphor' maintainer is consistent with the known PhosphorJS project transition to new maintainers; no malicious indicators present. ai

Versions (showing 8 of 8)

Version Deps Published
1.2.0 1 / 14
1.1.3 1 / 14
1.1.2 1 / 3
1.1.1 1 / 3
1.1.0 1 / 3
1.0.0 1 / 2
0.1.1 1 / 2
0.1.0 1 / 0

v1.2.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.1.3

2 findings
HIGH Publisher changed: sccolbert → blink1073 (on 2019-06-01) provenance

This 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.

LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.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.

v0.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: phosphor → sccolbert (on 2017-03-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.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.