@wordpress/create-block
Generates PHP, JS and CSS code for registering a block for a WordPress plugin.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): CLI tool with thin index.js entry point is expected; README signals are false positives for this established package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Template loader pattern in a scaffolding CLI; resolves user-supplied template names by design. | ai | |
| phantom-deps | phantom-dep:@wordpress/lazy-import | AI (phantom-deps): Same-org dependency used indirectly via lazy-import mechanism; stable false positive for this package. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 4.94.0 | 13 / 0 | |
| 4.93.0 | 13 / 0 | |
| 4.92.0 | 13 / 0 | |
| 4.91.1 | 13 / 0 | |
| 4.91.0 | 13 / 0 | |
| 4.90.0 | 13 / 0 | |
| 4.89.0 | 13 / 0 | |
| 4.88.0 | 13 / 0 | |
| 4.87.0 | 13 / 0 | |
| 4.86.0 | 13 / 0 | |
| 4.85.0 | 13 / 0 | |
| 4.84.0 | 13 / 0 | |
| 4.83.1 | 13 / 0 | |
| 4.83.0 | 13 / 0 | |
| 4.82.0 | 13 / 0 | |
| 4.81.0 | 13 / 0 | |
| 4.80.0 | 13 / 0 | |
| 4.79.0 | 13 / 0 | |
| 4.78.0 | 13 / 0 | |
| 4.77.0 | 13 / 0 | |
| 4.76.1 | 13 / 0 | |
| 4.76.0 | 13 / 0 | |
| 4.75.0 | 13 / 0 | |
| 4.74.0 | 13 / 0 | |
| 4.73.0 | 13 / 0 | |
| 4.72.0 | 13 / 0 | |
| 4.71.0 | 13 / 0 | |
| 4.70.0 | 13 / 0 | |
| 4.69.0 | 13 / 0 | |
| 4.68.0 | 13 / 0 | |
| 4.67.0 | 13 / 0 | |
| 4.66.0 | 13 / 0 | |
| 4.65.0 | 13 / 0 | |
| 4.64.1 | 13 / 0 | |
| 4.64.0 | 13 / 0 | |
| 4.63.0 | 13 / 0 | |
| 4.62.1 | 13 / 0 | |
| 4.62.0 | 13 / 0 | |
| 4.61.0 | 13 / 0 | |
| 4.60.0 | 13 / 0 | |
| 4.59.0 | 13 / 0 | |
| 4.58.1 | 13 / 0 | |
| 4.58.0 | 13 / 0 | |
| 4.57.0 | 13 / 0 | |
| 4.56.0 | 13 / 0 | |
| 4.55.0 | 13 / 0 | |
| 4.54.0 | 13 / 0 | |
| 4.53.0 | 13 / 0 | |
| 4.52.0 | 13 / 0 | |
| 4.51.1 | 13 / 0 | |
| 4.51.0 | 13 / 0 |
v4.94.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.
v4.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.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.
v4.65.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 (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-04-11, but gziolo 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.
v4.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.58.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 (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-03, but gutenbergplugin 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.
v4.58.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 (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-01-03, but gziolo 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.
v4.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.