← Home

@phosphor/signaling

npm Repository Homepage
11
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) is a listed contributor in package.json and a long-standing PhosphorJS team member with excellent track record. Legitimate maintainer transition. ai
maintainer-change maintainer-added AI (maintainer-change): blink1073 and phosphor-user are legitimate PhosphorJS project maintainers; blink1073 is already a listed contributor in package.json. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of 'phosphor' account is part of the documented PhosphorJS project maintainer transition; not indicative of a takeover given the context. ai

Versions (showing 11 of 11)

Version Deps Published
1.3.1 1 / 14
1.3.0 1 / 14
1.2.3 1 / 14
1.2.2 1 / 3
1.2.1 1 / 3
1.2.0 1 / 3
1.1.0 1 / 2
1.0.0 1 / 2
0.1.2 1 / 2
0.1.1 1 / 0
0.1.0 1 / 0

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

2 findings
HIGH Publisher changed: sccolbert → blink1073 (on 2019-08-05) provenance

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

LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

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

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.