@wix/public-editor-platform-events
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Wix internal monorepo package; missing metadata is a known pattern for this publisher family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across Wix internal packages; not a malware signal here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 1.351.0 | 1 / 6 | |
| 1.350.0 | 1 / 6 | |
| 1.349.0 | 1 / 6 | |
| 1.348.0 | 1 / 6 | |
| 1.347.0 | 1 / 6 | |
| 1.346.0 | 1 / 6 | |
| 1.345.0 | 1 / 6 | |
| 1.344.0 | 1 / 6 | |
| 1.343.0 | 1 / 6 | |
| 1.342.0 | 1 / 6 | |
| 1.341.0 | 1 / 6 | |
| 1.340.0 | 1 / 6 | |
| 1.339.0 | 1 / 6 | |
| 1.337.0 | 1 / 6 | |
| 1.336.0 | 1 / 6 | |
| 1.335.0 | 1 / 6 | |
| 1.334.0 | 1 / 6 | |
| 1.333.0 | 1 / 6 | |
| 1.332.0 | 1 / 6 | |
| 1.331.0 | 1 / 6 | |
| 1.330.0 | 1 / 6 | |
| 1.329.0 | 1 / 6 | |
| 1.328.0 | 1 / 6 | |
| 1.327.0 | 1 / 6 | |
| 1.326.0 | 1 / 6 | |
| 1.325.0 | 1 / 6 | |
| 1.324.0 | 1 / 6 | |
| 1.323.0 | 1 / 6 | |
| 1.322.0 | 1 / 6 | |
| 1.321.0 | 1 / 6 | |
| 1.320.0 | 1 / 6 | |
| 1.319.0 | 1 / 6 | |
| 1.318.0 | 1 / 6 | |
| 1.317.0 | 1 / 6 | |
| 1.316.0 | 1 / 6 | |
| 1.315.0 | 1 / 6 | |
| 1.314.0 | 1 / 6 |
v1.351.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.350.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.349.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.348.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.347.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.346.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.345.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.344.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.343.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.342.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.341.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.340.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.339.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.337.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.336.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.335.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.334.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.332.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.331.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.330.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.329.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.328.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.327.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.326.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.325.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.324.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.323.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.322.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.321.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.320.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.319.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.318.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.317.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.316.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.315.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.314.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.