@wordpress/theme
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only in a build-time token generation script, not in runtime code or install hooks. | ai | |
| provenance | no-provenance | AI (provenance): Gutenberg monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 7 / 16 | |
| 0.17.0 | 7 / 14 | |
| 0.16.0 | 5 / 14 | |
| 0.15.1 | 6 / 10 | |
| 0.15.0 | 5 / 10 | |
| 0.14.0 | 5 / 10 | |
| 0.13.0 | 5 / 10 | |
| 0.12.0 | 4 / 10 | |
| 0.11.0 | 4 / 10 | |
| 0.10.0 | 4 / 10 | |
| 0.9.0 | 4 / 10 | |
| 0.8.0 | 4 / 10 | |
| 0.7.1 | 4 / 10 | |
| 0.7.0 | 4 / 10 | |
| 0.6.0 | 4 / 10 | |
| 0.5.0 | 4 / 10 | |
| 0.4.0 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.0 | 3 / 0 |
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
2 findings[Accepted risk] Package 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.