@wordpress/block-directory
Extend editor with block directory features to search, download and install 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): mamaduka is an established WordPress contributor (377 approved packages); publisher change reflects legitimate org publishing rotation. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): @wordpress/base-styles is a CSS-only package; not imported via JS but legitimately declared as a dep in this WordPress package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 5.47.0 | 22 / 1 | |
| 5.46.0 | 22 / 1 | |
| 5.45.0 | 22 / 1 | |
| 5.44.0 | 21 / 1 | |
| 5.43.0 | 21 / 1 | |
| 5.42.0 | 21 / 1 | |
| 5.41.0 | 21 / 1 | |
| 5.40.1 | 21 / 1 | |
| 5.40.0 | 21 / 1 | |
| 5.39.0 | 21 / 1 | |
| 5.38.0 | 21 / 1 | |
| 5.37.0 | 21 / 0 | |
| 5.36.0 | 21 / 0 | |
| 5.35.0 | 21 / 0 | |
| 5.34.0 | 21 / 0 | |
| 5.33.11 | 21 / 0 | |
| 5.33.10 | 21 / 0 | |
| 5.33.9 | 21 / 0 | |
| 5.33.8 | 21 / 0 | |
| 5.33.7 | 21 / 0 | |
| 5.33.6 | 21 / 0 | |
| 5.33.5 | 21 / 0 | |
| 5.33.4 | 21 / 0 | |
| 5.33.3 | 21 / 0 | |
| 5.33.2 | 21 / 0 | |
| 5.33.1 | 21 / 0 | |
| 5.33.0 | 21 / 0 | |
| 5.32.0 | 21 / 0 | |
| 5.31.0 | 21 / 0 | |
| 5.30.0 | 21 / 0 | |
| 5.29.0 | 21 / 0 | |
| 5.28.0 | 21 / 0 | |
| 5.27.0 | 21 / 0 | |
| 5.26.0 | 21 / 0 | |
| 5.25.0 | 21 / 0 | |
| 5.24.0 | 21 / 0 | |
| 5.23.0 | 21 / 0 | |
| 5.19.7 | 21 / 0 |
v5.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.11
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.19.7
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.