@elementor/editor-variables
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @elementor/utils from the same Elementor monorepo at the same pinned version; consistent with coordinated monorepo releases. | ai | |
| dependencies | unvetted-dep:@elementor/mixpanel | AI (dependencies): Internal Elementor analytics dependency; consistent with the monorepo pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo package; description omission is stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): Elementor's CI/CD may not yet support Sigstore; not a blocker for established org. | ai | |
| dependencies | unvetted-dep:@elementor/ui | AI (dependencies): First-party Elementor org dependency; consistent with monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@elementor/icons | AI (dependencies): First-party Elementor org dependency; consistent with monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@elementor/editor-canvas | AI (dependencies): First-party Elementor org dependency; consistent with monorepo publishing pattern. | ai | |
| dependencies | unvetted-dep:@elementor/editor-controls | AI (dependencies): First-party Elementor org dependency; consistent with monorepo publishing pattern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 17 / 1 | |
| 4.0.9 | 17 / 1 | |
| 4.0.8 | 17 / 1 | |
| 4.0.7 | 17 / 1 | |
| 4.0.5 | 17 / 1 | |
| 4.0.4 | 17 / 1 | |
| 4.0.3 | 17 / 1 | |
| 4.0.2 | 17 / 1 | |
| 4.0.1 | 17 / 1 | |
| 4.0.0 | 17 / 1 | |
| 3.35.9 | 17 / 1 | |
| 3.35.8 | 17 / 1 | |
| 3.35.7 | 17 / 1 | |
| 3.35.6 | 17 / 1 | |
| 3.35.5 | 17 / 1 | |
| 3.35.4 | 17 / 1 | |
| 3.35.3 | 17 / 1 | |
| 3.35.2 | 17 / 1 | |
| 3.35.1 | 17 / 1 | |
| 3.35.0 | 17 / 1 | |
| 3.34.3 | 16 / 1 | |
| 3.34.2 | 16 / 1 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package 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.2
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.