@wordpress/build
Build tool for WordPress plugins.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @wordpress/build package; Levenshtein match to uuid is a false positive. | ai | |
| typosquat | typosquat.levenshtein:esbuild | AI (typosquat): Scoped @wordpress/build package; Levenshtein match to esbuild is a false positive. | ai | |
| phantom-deps | phantom-dep:moment-timezone | AI (phantom-deps): Referenced in config files as documented; stable false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:@emotion/babel-plugin | AI (phantom-deps): Referenced in config files as documented; stable false positive for this build tool. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 16 / 1 | |
| 0.18.0 | 16 / 1 | |
| 0.17.0 | 16 / 1 | |
| 0.16.1 | 16 / 1 | |
| 0.16.0 | 16 / 1 | |
| 0.15.0 | 16 / 1 | |
| 0.14.0 | 16 / 1 | |
| 0.13.0 | 15 / 1 | |
| 0.12.0 | 15 / 1 | |
| 0.11.0 | 15 / 1 | |
| 0.10.0 | 15 / 1 | |
| 0.9.0 | 15 / 1 | |
| 0.8.1 | 15 / 1 | |
| 0.8.0 | 15 / 1 | |
| 0.7.0 | 15 / 1 | |
| 0.6.0 | 15 / 1 | |
| 0.5.0 | 15 / 0 | |
| 0.4.0 | 15 / 0 | |
| 0.3.0 | 15 / 0 | |
| 0.2.0 | 15 / 0 |
v0.19.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-07-14, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-06-30, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.