← Home

@phosphor/domutils

npm Repository Homepage
9
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 well-established Jupyter/PhosphorJS maintainer. The 2019 transition aligns with the known PhosphorJS project handoff. ai
maintainer-change maintainer-added AI (maintainer-change): blink1073 and phosphor-user are legitimate maintainers for the PhosphorJS ecosystem; this reflects the known 2019 project transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of 'phosphor' maintainer is part of the known PhosphorJS project transition in 2019; not indicative of a hostile takeover. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.4 0 / 14
1.1.3 0 / 14
1.1.2 0 / 3
1.1.1 0 / 3
1.1.0 0 / 3
1.0.0 0 / 2
0.1.2 0 / 2
0.1.1 0 / 0
0.1.0 0 / 0

v1.1.4

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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.