@elementor/editor-widget-creation
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with documented repo; description gap is stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is optional; not a blocker for established monorepo packages. | ai | |
| dependencies | unvetted-dep:@elementor/editor | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai | |
| dependencies | unvetted-dep:@elementor/events | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai | |
| dependencies | unvetted-dep:@elementor/ui | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai | |
| dependencies | unvetted-dep:@elementor/editor-mcp | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai | |
| dependencies | unvetted-dep:@elementor/editor-ui | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai | |
| dependencies | unvetted-dep:@elementor/icons | AI (dependencies): Sibling Elementor monorepo package; unvetted status reflects review lag, not risk. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 7 / 1 | |
| 4.0.8 | 7 / 1 | |
| 4.0.7 | 7 / 1 | |
| 4.0.5 | 7 / 1 | |
| 4.0.4 | 7 / 1 | |
| 4.0.3 | 7 / 1 | |
| 4.0.2 | 7 / 1 | |
| 4.0.1 | 7 / 1 | |
| 4.0.0 | 7 / 1 |
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.