← Home

@wordpress/editor

6
Versions
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

wordpressgutenbergeditor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Active Gutenberg monorepo package; dormancy signal is a false positive for this well-established package. ai
publish-pattern new-deps-added AI (publish-pattern): @wordpress/ui is a same-org WordPress package; low risk for this monorepo. ai
phantom-deps phantom-dep:client-zip AI (phantom-deps): client-zip is a declared runtime dep used in build config; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@wordpress/base-styles AI (phantom-deps): SCSS-only dep; not imported in JS but used in build pipeline — stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@wordpress/reusable-blocks AI (phantom-deps): Same-org dep used indirectly; phantom-dep heuristic false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
14.48.0 55 / 1
14.47.0 55 / 1
14.46.0 55 / 1
14.45.0 55 / 1
14.44.0 55 / 1
14.43.0 55 / 1

v14.48.0

1 finding
LOW No provenance attestation provenance

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

v14.47.0

1 finding
LOW No provenance attestation provenance

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

v14.46.0

1 finding
LOW No provenance attestation provenance

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

v14.45.0

1 finding
LOW No provenance attestation provenance

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

v14.43.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.