← Home

@elementor/editor-controls

npm Repository Homepage

This package contains the controls model and utils for the Elementor editor

21
Versions
GPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kingyesmati1000nevosschenecloud-devops

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@elementor/editor-v1-adapters AI (phantom-deps): Same-org monorepo dep; declared for bundler resolution, not direct import. ai
dependencies unvetted-dep:@elementor/icons AI (dependencies): First-party @elementor scoped dep from the same monorepo; stable pattern across versions. ai
dependencies unvetted-dep:@elementor/mixpanel AI (dependencies): First-party @elementor scoped dep from the same monorepo; stable pattern across versions. ai
phantom-deps phantom-dep:@tiptap/pm AI (phantom-deps): Tiptap peer/transitive dep referenced in config; not a direct import by design. ai
dependencies unvetted-dep:@elementor/ui AI (dependencies): First-party @elementor scoped dep from the same monorepo; stable pattern across versions. ai
bogus-package bogus-package AI (bogus-package): Internal monorepo package; sparse README is expected, not a spam indicator. ai
phantom-deps phantom-dep:@monaco-editor/react AI (phantom-deps): Listed as runtime dep in package.json; phantom-dep is a false positive for this monorepo build pattern. ai
phantom-deps phantom-dep:@tiptap/starter-kit AI (phantom-deps): Listed as runtime dep in package.json; phantom-dep is a false positive for this monorepo build pattern. ai

Versions (showing 21 of 21)

Version Deps Published
4.1.0 35 / 2
4.0.9 34 / 2
4.0.8 34 / 2
4.0.7 34 / 2
4.0.5 34 / 2
4.0.4 34 / 2
4.0.3 34 / 2
4.0.2 34 / 2
4.0.1 34 / 2
4.0.0 34 / 2
3.35.9 34 / 2
3.35.8 34 / 2
3.35.7 34 / 2
3.35.6 34 / 2
3.35.5 34 / 2
3.35.4 34 / 2
3.35.3 34 / 2
3.35.2 34 / 2
3.35.1 34 / 2
3.34.3 31 / 2
3.34.2 31 / 2

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.35.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.35.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.35.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.35.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.35.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.35.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.35.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.35.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.35.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.34.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.34.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.