@wordpress/blocks
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 org publisher with strong track record; rotation from gutenbergplugin is expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established WordPress/Gutenberg monorepo package; provenance not yet adopted by this publisher. | ai | |
| license | copyleft-license:GPL-2.0-or-later | AI (license): GPL-2.0-or-later is the standard license for all WordPress/Gutenberg packages; stable across versions. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 15.21.0 | 26 / 1 | |
| 15.20.0 | 26 / 1 | |
| 15.19.0 | 26 / 1 | |
| 15.18.0 | 26 / 1 | |
| 15.17.0 | 26 / 1 | |
| 15.16.0 | 26 / 1 | |
| 15.15.0 | 26 / 1 | |
| 15.14.0 | 26 / 1 | |
| 15.13.0 | 26 / 1 | |
| 15.12.0 | 26 / 1 | |
| 15.11.0 | 26 / 1 | |
| 15.10.0 | 26 / 0 | |
| 15.9.0 | 26 / 0 | |
| 15.8.0 | 26 / 0 | |
| 15.7.0 | 26 / 0 | |
| 15.6.3 | 26 / 0 | |
| 15.6.2 | 26 / 0 | |
| 15.6.1 | 26 / 0 | |
| 15.6.0 | 26 / 0 | |
| 15.5.0 | 27 / 0 | |
| 15.4.0 | 27 / 0 | |
| 15.3.0 | 27 / 0 | |
| 15.2.0 | 27 / 0 | |
| 15.1.0 | 27 / 0 | |
| 15.0.0 | 27 / 0 |
v15.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.3
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.