← Home

@wordpress/deprecated

npm Repository Homepage

Deprecation utility for WordPress.

94
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

wordpressgutenbergdeprecated

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): gutenbergplugin is the official Gutenberg monorepo publishing account with 276 approved packages; transition from individual maintainer accounts to this shared account is a known pattern for the WordPress/Gutenberg project. ai

Versions (showing 94 of 195)

Hide prereleases
Version Deps Published
3.30.0 2 / 0
3.29.0 2 / 0
3.28.0 2 / 0
3.27.0 2 / 0
3.26.2 2 / 0
3.26.1 2 / 0
3.26.0 2 / 0
3.25.0 2 / 0
3.24.0 2 / 0
3.23.0 2 / 0
3.22.0 2 / 0
3.21.0 2 / 0
3.20.0 2 / 0
3.19.0 2 / 0
3.18.0 2 / 0
3.17.1 2 / 0
3.17.0 2 / 0
3.16.0 2 / 0
3.15.0 2 / 0
3.14.0 2 / 0
3.13.0 2 / 0
3.12.0 2 / 0
3.11.0 2 / 0
3.10.0 2 / 0
3.9.0 2 / 0
3.8.0 2 / 0
3.7.0 2 / 0
3.6.1 2 / 0
3.6.0 2 / 0
3.5.0 2 / 0
3.4.1 2 / 0
3.4.0 2 / 0
3.3.1 2 / 0
3.3.0 2 / 0
3.2.3 2 / 0
3.2.2 2 / 0
3.2.1 2 / 0
3.2.0 2 / 0
3.1.2 2 / 0
3.1.1 2 / 0
3.1.0 2 / 0
3.0.0 2 / 0
2.12.3 2 / 0
2.12.2 2 / 0
2.12.1 2 / 0
2.12.0 2 / 0
2.11.1 2 / 0
2.11.0 2 / 0
2.10.0 2 / 0
2.9.0 2 / 0
2.8.0 2 / 0
2.7.0 2 / 0
2.6.1 2 / 0
2.6.0 2 / 0
2.5.0 2 / 0
2.4.0 2 / 0
2.3.0 2 / 0
2.2.0 2 / 0
2.1.0 2 / 0
2.0.5 2 / 0
2.0.4 2 / 0
2.0.3 2 / 0
2.0.2 2 / 0
2.0.1 2 / 0
2.0.0 2 / 0
1.0.3 1 / 0
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 0 / 0
4.44.1-next.v.202604201441.0 1 / 0
4.43.1-next.v.202604091042.0 1 / 0
4.41.1-next.v.202603161435.0 1 / 0
4.41.1-next.v.202603102151.0 1 / 0
4.40.1-next.v.202602271551.0 1 / 0
4.40.1-next.v.202602241322.0 1 / 0
4.40.1-next.v.202602200903.0 1 / 0
4.40.1-next.v.202602191100.0 1 / 0
4.39.1-next.v.202602111440.0 1 / 0
4.39.1-next.v.202602091733.0 1 / 0
4.39.1-next.v.20260206T143.0 1 / 0
4.39.1-next.v.0 1 / 0
4.38.1-next.v.0 1 / 0
4.37.1-next.v.0 1 / 0
4.37.1-next.ba3aee3a2.0 1 / 0
4.37.1-next.79a2f3cdd.0 1 / 0
4.37.1-next.06ee73755.0 1 / 0
4.36.1-next.8fd3f8831.0 1 / 0
4.36.1-next.8b30e05b0.0 1 / 0
4.36.1-next.76cff8c98.0 1 / 0
4.36.1-next.738bb1424.0 1 / 0
4.36.1-next.6deb34194.0 1 / 0
4.35.1-next.dc3f6d3c1.0 1 / 0
4.35.1-next.16d95556a.0 1 / 0
4.34.1-next.2f1c7c01b.0 1 / 0

v3.30.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.

v3.29.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.

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

v3.27.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.

v3.26.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.

v3.26.1

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.

v3.26.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.

v3.25.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.

v3.24.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.

v3.23.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.

v3.22.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.

v3.21.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.

v3.20.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.

v3.19.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.

v3.18.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.

v3.17.1

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.

v3.17.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.

v3.16.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.

v3.15.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.

v3.14.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.

v3.13.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.

v3.12.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.

v3.11.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.

v3.10.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.

v3.9.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.

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

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

v3.6.1

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.

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

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

v3.4.1

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.

v3.4.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.

v3.3.1

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.

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

v3.2.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.

v3.2.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.

v3.2.1

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.

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

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

v3.1.1

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.

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

v3.0.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.