← Home

@wordpress/components

npm Repository Homepage
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

wordpressgutenbergcomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@wordpress/style-runtime AI (dependencies): Same-org @wordpress scoped package from the Gutenberg monorepo; consistent with established release pattern. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Type-only dep used by convention in TS projects; not directly imported at runtime. ai
phantom-deps phantom-dep:@types/gradient-parser AI (phantom-deps): Type-only dep; stable false positive for this package. ai
phantom-deps phantom-dep:@wordpress/base-styles AI (phantom-deps): SCSS-only dep consumed via build pipeline, not JS imports; stable false positive. ai
phantom-deps phantom-dep:@types/highlight-words-core AI (phantom-deps): Type-only dep; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
35.0.0 52 / 9
34.0.0 52 / 9
33.1.0 50 / 9
33.0.0 49 / 9
32.6.0 49 / 9
32.5.0 49 / 9

v35.0.0

1 finding
LOW No provenance attestation provenance

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

v34.0.0

1 finding
LOW No provenance attestation provenance

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

v33.1.0

1 finding
LOW No provenance attestation provenance

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

v33.0.0

1 finding
LOW No provenance attestation provenance

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

v32.5.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.