@wordpress/upload-media
Core media upload logic.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 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.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.4.4 | 12 / 0 | |
| 0.4.3 | 12 / 0 |
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
2 findingsThis version was published by a different npm account than previous versions on 2025-07-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.