@elementor/editor-templates
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 monorepo package; lack of provenance is consistent across all 196 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Elementor monorepo package; missing description is a cosmetic issue, not a risk signal. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 6 / 1 | |
| 4.0.9 | 5 / 1 | |
| 4.0.8 | 5 / 1 | |
| 4.0.7 | 5 / 1 | |
| 4.0.5 | 5 / 1 | |
| 4.0.4 | 5 / 1 | |
| 4.0.3 | 5 / 1 | |
| 4.0.2 | 5 / 1 | |
| 4.0.1 | 5 / 1 | |
| 4.0.0 | 5 / 1 | |
| 3.35.9 | 5 / 1 | |
| 3.35.8 | 5 / 1 | |
| 3.35.7 | 5 / 1 | |
| 3.35.6 | 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 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.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. 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.