@wordpress/media-editor GPL-2.0-or-later 11 versions

@wordpress/media-editor

npm Repository Homepage

Media editor components for WordPress.

11

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

wordpressgutenbergmediaeditorattachment

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): Gutenberg packages regularly grow significantly between versions; no malicious content indicated.	ai	2026/05/17
source-diff	source-size-tripled	AI (source-diff): Size increase matches documented feature expansion; publisher is the official WordPress org.	ai	2026/05/17
phantom-deps	phantom-dep:@wordpress/base-styles	AI (phantom-deps): CSS-only dependency; not imported via JS but used via SCSS build pipeline — stable false positive for this package.	ai	2026/05/17
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): @babel/runtime is a standard transitive runtime dep in Gutenberg packages; not directly imported by convention.	ai	2026/04/29

Versions (showing 11 of 11)

Version	Deps	Published
0.11.0	19 / 0	2026-06-04
0.10.1	19 / 0	2026-06-04
0.10.0	18 / 0	2026-05-27
0.9.0	16 / 0	2026-05-14
0.8.0	15 / 0	2026-04-29
0.7.0	5 / 0	2026-04-15
0.6.0	5 / 0	2026-04-01
0.5.0	5 / 0	2026-03-18
0.4.0	5 / 0	2026-03-04
0.3.0	5 / 0	2026-02-18
0.2.0	5 / 0	2026-01-29

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.1

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.