@elementor/editor-documents
> [!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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Elementor org package; lack of Sigstore provenance is consistent across their entire package suite. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Elementor monorepo package; sparse README/no keywords is a consistent pattern across all @elementor/* packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 6 / 1 | |
| 4.0.9 | 6 / 1 | |
| 4.0.8 | 6 / 1 | |
| 4.0.7 | 6 / 1 | |
| 4.0.5 | 6 / 1 | |
| 4.0.4 | 6 / 1 | |
| 4.0.3 | 6 / 1 | |
| 4.0.2 | 6 / 1 | |
| 4.0.1 | 6 / 1 | |
| 4.0.0 | 6 / 1 | |
| 3.35.9 | 5 / 1 | |
| 3.35.8 | 5 / 1 | |
| 3.35.7 | 5 / 1 | |
| 3.35.6 | 5 / 1 | |
| 3.35.5 | 5 / 1 | |
| 3.35.4 | 5 / 1 | |
| 3.35.3 | 5 / 1 | |
| 3.35.2 | 5 / 1 | |
| 3.35.1 | 5 / 1 | |
| 3.35.0 | 5 / 1 | |
| 3.34.3 | 5 / 1 | |
| 3.34.2 | 5 / 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.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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.