@wordpress/block-editor
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:src/components/global-styles/test/use-global-styles-output.js | AI (source-diff): Test file with large inline style fixtures; long lines are data, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Emotion used via config/JSX pragma; stable FP for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active Gutenberg monorepo package with 415 versions; dormancy signal is a false positive for this package. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a well-known animation library; long-standing dep in this package. | ai | |
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): deepmerge is a declared dep used in build/config context; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@wordpress/escape-html | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:react-easy-crop | AI (phantom-deps): react-easy-crop is a declared dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@wordpress/wordcount | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): Same-org sibling dep used for styles; phantom-dep heuristic false positive. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 16.0.0 | 52 / 8 | |
| 15.23.0 | 52 / 6 | |
| 15.22.1 | 52 / 6 | |
| 15.22.0 | 52 / 6 | |
| 15.21.1 | 53 / 5 | |
| 15.21.0 | 52 / 2 | |
| 15.20.0 | 52 / 2 | |
| 15.19.0 | 52 / 2 | |
| 15.18.0 | 52 / 2 | |
| 15.17.0 | 51 / 2 | |
| 15.16.0 | 52 / 2 | |
| 15.15.0 | 52 / 2 | |
| 15.14.0 | 52 / 2 | |
| 15.13.2 | 52 / 2 | |
| 15.13.1 | 52 / 2 | |
| 15.13.0 | 52 / 2 | |
| 15.12.0 | 52 / 2 | |
| 15.11.0 | 52 / 2 | |
| 15.10.0 | 52 / 0 | |
| 15.9.0 | 53 / 0 | |
| 15.8.0 | 52 / 0 | |
| 15.6.9 | 51 / 0 | |
| 15.6.8 | 51 / 0 | |
| 15.6.7 | 51 / 0 | |
| 15.6.6 | 51 / 0 | |
| 15.6.5 | 51 / 0 | |
| 15.6.4 | 51 / 0 | |
| 15.6.3 | 50 / 0 | |
| 15.6.2 | 50 / 0 |
v16.0.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.
v15.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.13.2
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.
v15.13.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 (peterwilsoncc) on 2026-02-23, 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.
v15.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.9
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 (peterwilsoncc) than the most recent previously approved version (gutenbergplugin) on 2026-01-29, but peterwilsoncc 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.
v15.6.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.7
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.