@wix/editor-application
tbd
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 | publisher-changed | AI (provenance): Wix org-wide migration to wix-ci-publisher CI account; consistent with 2565 other approved packages from same publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of Wix CI publisher consolidation; not indicative of takeover. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix monorepo package; missing README/repo/keywords is expected for private org packages published to npm. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 1.430.0 | 4 / 8 | |
| 1.429.0 | 4 / 8 | |
| 1.428.0 | 4 / 8 | |
| 1.427.0 | 4 / 8 | |
| 1.426.0 | 4 / 8 | |
| 1.425.0 | 4 / 8 | |
| 1.424.0 | 4 / 8 | |
| 1.423.0 | 4 / 8 | |
| 1.422.0 | 4 / 8 | |
| 1.421.0 | 4 / 8 | |
| 1.420.0 | 4 / 8 | |
| 1.419.0 | 4 / 8 | |
| 1.418.0 | 4 / 8 | |
| 1.416.0 | 4 / 8 | |
| 1.415.0 | 4 / 8 | |
| 1.414.0 | 4 / 8 | |
| 1.413.0 | 4 / 8 | |
| 1.412.0 | 4 / 8 | |
| 1.411.0 | 4 / 8 | |
| 1.410.0 | 4 / 8 | |
| 1.409.0 | 4 / 8 | |
| 1.408.0 | 4 / 8 | |
| 1.407.0 | 4 / 8 | |
| 1.406.0 | 4 / 8 | |
| 1.405.0 | 4 / 8 | |
| 1.404.0 | 4 / 8 | |
| 1.403.0 | 4 / 8 | |
| 1.402.0 | 4 / 8 | |
| 1.401.0 | 4 / 8 | |
| 1.400.0 | 4 / 8 | |
| 1.399.0 | 4 / 8 | |
| 1.398.0 | 4 / 8 | |
| 1.397.0 | 4 / 8 | |
| 1.396.0 | 4 / 8 | |
| 1.395.0 | 4 / 8 | |
| 1.394.0 | 4 / 8 | |
| 1.79.0 | 4 / 8 | |
| 1.78.0 | 4 / 8 | |
| 1.77.0 | 4 / 8 | |
| 1.76.0 | 4 / 8 | |
| 1.75.0 | 4 / 8 | |
| 1.74.0 | 4 / 8 | |
| 1.73.0 | 4 / 8 | |
| 1.72.0 | 4 / 8 | |
| 1.71.0 | 4 / 8 | |
| 1.70.0 | 4 / 8 | |
| 1.69.0 | 4 / 8 | |
| 1.68.0 | 4 / 8 | |
| 1.67.0 | 4 / 8 | |
| 1.66.0 | 4 / 8 | |
| 1.65.0 | 4 / 8 | |
| 1.64.0 | 4 / 8 | |
| 1.63.0 | 4 / 8 | |
| 1.62.0 | 4 / 8 | |
| 1.61.0 | 4 / 8 | |
| 1.60.0 | 4 / 8 |
v1.430.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.429.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.428.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.427.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.426.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.425.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.424.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.423.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.422.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.421.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.420.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.419.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.418.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.416.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.415.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.414.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.413.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.411.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.410.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.409.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.408.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.407.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.406.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.405.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.404.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.403.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.402.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.401.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.400.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.399.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.398.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.397.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.396.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.395.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.394.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.78.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
2 findingsThis version was published by a different npm account than previous versions on 2025-06-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.66.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.65.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
2 findingsThis version was published by a different npm account than previous versions on 2025-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.