@elementor/editor-notifications
Notifications manager for the Elementor editor
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 |
|---|---|---|---|---|
| license | copyleft-license:GPL-3.0-or-later | AI (license): GPL-3.0 is Elementor's declared license; stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no keywords are expected for internal scoped packages. | ai | |
| dependencies | unvetted-dep:@elementor/ui | AI (dependencies): Internal Elementor monorepo sibling dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@elementor/icons | AI (dependencies): Internal Elementor monorepo sibling dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@elementor/store | AI (dependencies): Internal Elementor monorepo sibling dependency; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@elementor/editor | AI (dependencies): Internal Elementor monorepo sibling dependency; stable pattern across versions. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 5 / 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 | 4 / 1 | |
| 3.35.8 | 4 / 1 | |
| 3.35.7 | 4 / 1 | |
| 3.35.6 | 4 / 1 | |
| 3.35.5 | 4 / 1 | |
| 3.35.4 | 4 / 1 | |
| 3.35.3 | 4 / 1 | |
| 3.35.2 | 4 / 1 | |
| 3.35.1 | 4 / 1 | |
| 3.35.0 | 4 / 1 | |
| 3.34.3 | 4 / 1 | |
| 3.34.2 | 4 / 1 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage 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 findingPackage 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.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.