@wordpress/media-utils
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mamaduka is an established WordPress org contributor with 354 approved packages; transition from gutenbergplugin is consistent with org-level publishing rotation. | ai | |
| dependencies | unvetted-dep:@wordpress/views | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/element | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/notices | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/api-fetch | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/core-data | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/dataviews | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/icons | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/media-fields | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/ui | AI (dependencies): Official WordPress org sibling package; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@wordpress/blob | AI (dependencies): Official WordPress org sibling package. | ai | |
| dependencies | unvetted-dep:@wordpress/data | AI (dependencies): Official WordPress org sibling package. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): CSS-only dependency from same org; not imported in JS but legitimately used for styles. | ai | |
| provenance | no-provenance | AI (provenance): WordPress/Gutenberg monorepo publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@wordpress/components | AI (dependencies): Official WordPress org sibling package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 5.48.0 | 16 / 0 | |
| 5.47.0 | 16 / 0 | |
| 5.46.0 | 16 / 0 | |
| 5.45.0 | 16 / 0 | |
| 5.44.0 | 16 / 0 | |
| 5.43.0 | 15 / 0 | |
| 5.42.0 | 15 / 0 | |
| 5.41.0 | 13 / 0 | |
| 5.40.1 | 13 / 0 | |
| 5.40.0 | 13 / 0 | |
| 5.39.0 | 13 / 0 | |
| 5.38.0 | 12 / 0 | |
| 5.37.0 | 11 / 0 | |
| 5.36.0 | 10 / 0 | |
| 5.35.0 | 10 / 0 | |
| 5.34.0 | 9 / 0 | |
| 5.33.1 | 5 / 0 | |
| 5.33.0 | 5 / 0 | |
| 5.32.0 | 6 / 0 | |
| 5.31.0 | 6 / 0 | |
| 5.30.0 | 6 / 0 | |
| 5.29.0 | 6 / 0 | |
| 5.28.0 | 6 / 0 | |
| 5.27.0 | 6 / 0 | |
| 5.26.0 | 6 / 0 | |
| 5.25.0 | 6 / 0 | |
| 5.24.0 | 6 / 0 | |
| 5.23.0 | 6 / 0 | |
| 5.19.2 | 6 / 0 |
v5.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.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.
v5.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.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.
v5.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.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.
v5.24.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.
v5.23.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.
v5.19.2
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.