@elementor/editor-components
Elementor editor components
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Elementor org package; provenance absence is consistent across all 758 versions. | ai | |
| dependencies | unvetted-dep:@elementor/mixpanel | AI (dependencies): First-party @elementor scoped sibling dep; stable pattern across all versions of this monorepo package. | ai | |
| dependencies | unvetted-dep:@elementor/ui | AI (dependencies): Same org (@elementor) internal dependency; consistent pattern across all versions of this monorepo package. | ai | |
| dependencies | unvetted-dep:@elementor/icons | AI (dependencies): Same org (@elementor) internal dependency; consistent pattern across all versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@elementor/editor-mcp | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; sparse README and no keywords are expected for org-internal packages. | ai | |
| phantom-deps | phantom-dep:@elementor/query | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 25 / 1 | |
| 4.0.8 | 25 / 1 | |
| 4.0.7 | 25 / 1 | |
| 4.0.5 | 25 / 1 | |
| 4.0.4 | 25 / 1 | |
| 4.0.3 | 25 / 1 | |
| 4.0.1 | 25 / 1 | |
| 4.0.0 | 25 / 1 | |
| 3.35.9 | 25 / 1 | |
| 3.35.8 | 25 / 1 | |
| 3.35.7 | 25 / 1 | |
| 3.35.6 | 25 / 1 | |
| 3.35.5 | 24 / 1 | |
| 3.35.4 | 24 / 1 | |
| 3.35.3 | 24 / 1 | |
| 3.35.2 | 24 / 1 | |
| 3.35.1 | 24 / 1 | |
| 3.35.0 | 24 / 1 | |
| 3.34.3 | 21 / 1 | |
| 3.34.2 | 21 / 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage 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.
v3.35.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.