@elementor/editor-mcp
> [!WARNING] > This package is under development and not ready for production use.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@elementor-external/angie-sdk | AI (dependencies): Alias for @elementor/angie-sdk — same org, consistent with Elementor monorepo patterns. | ai | |
| phantom-deps | phantom-dep:@elementor/editor-v1-adapters | AI (phantom-deps): Same org scope (@elementor); declared as a pinned dep, phantom-dep heuristic is a stable false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Elementor monorepo package; provenance absence is common and no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; sparse README and no keywords are expected for org-internal packages. | ai | |
| phantom-deps | phantom-dep:@elementor/store | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:zod-to-json-schema | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 7 / 1 | |
| 4.0.9 | 7 / 1 | |
| 4.0.8 | 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 | |
| 3.35.7 | 6 / 1 | |
| 3.35.6 | 6 / 1 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.