← Home

@wordpress/media-fields

npm Repository Homepage

Reusable field definitions for displaying and editing media attachment properties in WordPress.

14
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

garypendergastadamsilversteingziolontwbriadnoisysockskadamwhitegutenbergpluginjorgefilipecostaellatrixiandunn206whyisjakeockhamsirrealnosoloswwpisabelntsekourasnerraddesrosjtalldanwppeterwilsonccryanwelchermamaduka

Keywords

wordpressgutenbergmediafieldsdataviews

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@wordpress/primitives AI (phantom-deps): Same-org WordPress package; phantom-dep heuristic is a false positive for monorepo build artifacts. ai
phantom-deps phantom-dep:@wordpress/base-styles AI (phantom-deps): Same-org WordPress package; used for SCSS imports not caught by JS import analysis. ai

Versions (showing 14 of 14)

Version Deps Published
0.13.0 13 / 2
0.12.1 13 / 2
0.12.0 13 / 2
0.11.0 13 / 2
0.10.0 13 / 2
0.9.0 13 / 2
0.8.0 13 / 2
0.7.0 13 / 2
0.6.0 13 / 2
0.5.1 13 / 2
0.5.0 13 / 2
0.4.0 13 / 2
0.3.0 13 / 2
0.2.0 9 / 0

v0.13.0

1 finding
LOW No provenance attestation provenance

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

v0.12.1

1 finding
LOW No provenance attestation provenance

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

v0.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.8.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.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

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