@wordpress/interface No license 33 versions

@wordpress/interface

npm Repository Homepage

33

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

wordpressgutenberginterfacecomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): peterwilsoncc is a known WordPress contributor with clean publish history; transition from gutenbergplugin org account is expected for Gutenberg packages.	ai	2026/05/16
phantom-deps	phantom-dep:@wordpress/a11y	AI (phantom-deps): Same-org WordPress package; phantom-dep heuristic fires on build-time/style deps common in Gutenberg monorepo.	ai	2026/04/29
phantom-deps	phantom-dep:@wordpress/base-styles	AI (phantom-deps): SCSS-only dependency used in build pipeline; not directly imported in JS — stable false positive for this package.	ai	2026/04/29

Versions (showing 33 of 33)

Version	Deps	Published
9.33.0	14 / 0	2026-06-04
9.32.0	14 / 0	2026-05-27
9.31.0	14 / 0	2026-05-14
9.30.0	14 / 0	2026-04-29
9.29.0	14 / 0	2026-04-15
9.28.0	14 / 0	2026-04-01
9.27.0	14 / 0	2026-03-18
9.26.0	14 / 0	2026-03-04
9.25.0	14 / 0	2026-02-18
9.24.0	14 / 0	2026-01-29
9.23.0	14 / 0	2026-01-16
9.22.0	13 / 0	2025-12-23
9.21.0	13 / 0	2025-11-26
9.20.0	13 / 0	2025-11-12
9.19.0	13 / 0	2025-10-29
9.18.5	13 / 0	2026-01-29
9.18.4	13 / 0	2025-11-11
9.18.3	13 / 0	2025-11-10
9.18.2	13 / 0	2025-11-07
9.18.1	13 / 0	2025-10-28
9.18.0	13 / 0	2025-10-17
9.17.0	13 / 0	2025-10-01
9.16.0	13 / 0	2025-09-17
9.15.0	13 / 0	2025-09-03
9.14.0	13 / 0	2025-08-20
9.13.0	13 / 0	2025-08-07
9.12.0	13 / 0	2025-07-23
9.11.0	13 / 0	2025-06-25
9.10.0	13 / 0	2025-06-04
9.9.0	13 / 0	2025-05-22
9.8.0	13 / 0	2025-05-07
9.4.4	13 / 0	2025-07-08
9.4.3	13 / 0	2025-04-28

v9.33.0

1 finding

LOW No provenance attestation provenance

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

v9.32.0

1 finding

LOW No provenance attestation provenance

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

v9.31.0

1 finding

LOW No provenance attestation provenance

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

v9.30.0

1 finding

LOW No provenance attestation provenance

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

v9.28.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.

v9.27.0

1 finding

LOW No provenance attestation provenance

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

v9.26.0

1 finding

LOW No provenance attestation provenance

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

v9.25.0

1 finding

LOW No provenance attestation provenance

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

v9.24.0

1 finding

LOW No provenance attestation provenance

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

v9.23.0

1 finding

LOW No provenance attestation provenance

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

v9.22.0

1 finding

LOW No provenance attestation provenance

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

v9.21.0

1 finding

LOW No provenance attestation provenance

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

v9.20.0

1 finding

LOW No provenance attestation provenance

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

v9.19.0

1 finding

LOW No provenance attestation provenance

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

v9.18.5

2 findings

HIGH Publisher changed: gutenbergplugin → peterwilsoncc (on 2026-01-29) provenance

This version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v9.18.4

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.

v9.18.3

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.

v9.18.2

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.

v9.18.1

1 finding

LOW No provenance attestation provenance

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

v9.18.0

1 finding

LOW No provenance attestation provenance

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

v9.17.0

1 finding

LOW No provenance attestation provenance

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

v9.16.0

1 finding

LOW No provenance attestation provenance

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

v9.15.0

1 finding

LOW No provenance attestation provenance

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

v9.14.0

1 finding

LOW No provenance attestation provenance

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

v9.13.0

1 finding

LOW No provenance attestation provenance

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

v9.12.0

1 finding

LOW No provenance attestation provenance

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

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

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

v9.4.4

2 findings

HIGH Publisher changed: gutenbergplugin → mamaduka (on 2025-07-08) provenance

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

LOW No provenance attestation provenance

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

v9.4.3

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.