@wordpress/lazy-editor
Lazy-loading editor component with automatic asset and settings management.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/components/preview/index.cjs | AI (source-diff): Standard esbuild CJS bundle from WordPress/Gutenberg monorepo; long lines are inlined CSS, not obfuscation. | ai | |
| source-diff | obfuscated-file:build-module/components/preview/index.mjs | AI (source-diff): Standard esbuild ESM bundle from WordPress/Gutenberg monorepo; same pattern as CJS counterpart. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): @wordpress/base-styles is a SCSS-only package imported at build time, not via JS imports; phantom-dep false positive. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.14.0 | 12 / 0 | |
| 1.13.0 | 12 / 0 | |
| 1.12.0 | 12 / 0 | |
| 1.11.0 | 12 / 0 | |
| 1.10.0 | 12 / 0 | |
| 1.9.0 | 12 / 0 | |
| 1.8.0 | 12 / 0 | |
| 1.7.0 | 12 / 0 | |
| 1.6.1 | 12 / 0 | |
| 1.6.0 | 12 / 0 | |
| 1.5.0 | 12 / 0 | |
| 1.4.0 | 12 / 0 | |
| 1.3.0 | 12 / 0 | |
| 1.2.0 | 12 / 0 | |
| 1.1.0 | 9 / 0 |
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.