@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 — 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 |
|---|---|---|---|---|
| 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 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 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.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.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.