← Home

@wordpress/upload-media

Core media upload logic.

48
Versions
GPL-2.0-or-later
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

garypendergastadamsilversteingziolontwbriadnoisysockskadamwhitegutenbergpluginjorgefilipecostaellatrixiandunn206whyisjakeockhamsirrealnosoloswwpisabelntsekourasnerraddesrosjtalldanwppeterwilsonccryanwelchermamaduka

Keywords

wordpressmedia

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@shopify/web-worker AI (dependencies): Legitimate, well-known Shopify package used for web worker offloading. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is an in-org first-party WordPress package. ai
dependencies unvetted-dep:@wordpress/video-conversion AI (dependencies): Official same-org WordPress package, not an unvetted third party. ai
phantom-deps phantom-dep:@shopify/web-worker AI (phantom-deps): Used in build/config context in a monorepo; not directly imported at source level but legitimately referenced. ai
phantom-deps phantom-dep:@wordpress/api-fetch AI (phantom-deps): Same org scope (@wordpress); indirect usage via WordPress ecosystem is expected for this package. ai
provenance no-provenance AI (provenance): Gutenberg monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. ai
phantom-deps phantom-dep:@wordpress/preferences AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for monorepo packages that re-export via index. ai

Versions (showing 48 of 48)

Version Deps Published
0.36.0 11 / 0
0.35.0 10 / 0
0.34.1 10 / 0
0.34.0 10 / 0
0.33.1 11 / 0
0.33.0 10 / 0
0.32.0 10 / 0
0.31.0 10 / 0
0.30.0 10 / 0
0.29.0 10 / 0
0.28.0 10 / 0
0.27.0 10 / 0
0.26.0 11 / 0
0.25.2 10 / 0
0.25.1 11 / 0
0.25.0 11 / 0
0.24.0 10 / 0
0.23.0 10 / 0
0.22.0 10 / 0
0.21.0 10 / 0
0.20.0 10 / 0
0.19.0 10 / 0
0.18.5 10 / 0
0.18.4 10 / 0
0.18.3 10 / 0
0.18.2 10 / 0
0.18.1 10 / 0
0.18.0 10 / 0
0.17.0 11 / 0
0.16.0 11 / 0
0.15.0 11 / 0
0.14.0 11 / 0
0.13.0 11 / 0
0.12.0 11 / 0
0.11.0 11 / 0
0.10.0 11 / 0
0.9.0 11 / 0
0.8.0 11 / 0
0.7.0 11 / 0
0.6.0 12 / 0
0.5.0 12 / 0
0.4.4 12 / 0
0.4.3 12 / 0
0.4.2 12 / 0
0.4.0 12 / 0
0.3.0 12 / 0
0.2.0 12 / 0
0.1.0 11 / 0

v0.36.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: gutenbergplugin → desrosj (on 2026-07-14, known maintainer) provenance

This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-07-14, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.35.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: desrosj → gutenbergplugin (on 2026-07-01, known maintainer) provenance

This version was published by a different npm account (gutenbergplugin) than the most recent previously approved version (desrosj) on 2026-07-01, but gutenbergplugin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.34.1

1 finding
INFO No provenance attestation provenance

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

v0.25.2

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: gutenbergplugin → desrosj (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-06-30, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.7.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
INFO No provenance attestation provenance

[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
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.