@wix/public-editor-platform-interfaces
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Wix proprietary internal package; UNLICENSED is intentional and consistent across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix CI-published interfaces package; missing metadata is consistent with all other approved Wix packages in this namespace. | ai |
Versions (showing 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 1.89.0 | 2 / 3 | |
| 1.88.0 | 2 / 3 | |
| 1.87.0 | 2 / 3 | |
| 1.86.0 | 2 / 3 | |
| 1.85.0 | 2 / 3 | |
| 1.84.0 | 2 / 3 | |
| 1.83.0 | 2 / 3 | |
| 1.82.0 | 2 / 3 | |
| 1.81.0 | 2 / 3 | |
| 1.80.0 | 2 / 3 | |
| 1.79.0 | 2 / 3 | |
| 1.78.0 | 2 / 3 | |
| 1.77.0 | 2 / 3 | |
| 1.76.0 | 2 / 3 | |
| 1.75.0 | 2 / 3 | |
| 1.74.0 | 2 / 3 | |
| 1.73.0 | 2 / 3 | |
| 1.72.0 | 2 / 3 | |
| 1.71.0 | 2 / 3 | |
| 1.70.0 | 2 / 3 | |
| 1.69.0 | 2 / 3 | |
| 1.68.0 | 2 / 3 | |
| 1.67.0 | 2 / 3 | |
| 1.66.0 | 2 / 3 | |
| 1.65.0 | 2 / 3 | |
| 1.64.0 | 2 / 3 | |
| 1.63.0 | 2 / 3 | |
| 1.62.0 | 2 / 3 | |
| 1.61.0 | 2 / 3 | |
| 1.60.0 | 2 / 3 | |
| 1.59.0 | 2 / 3 | |
| 1.58.0 | 2 / 3 | |
| 1.57.0 | 2 / 3 | |
| 1.56.0 | 2 / 3 | |
| 1.55.0 | 2 / 3 | |
| 1.54.0 | 2 / 3 | |
| 1.53.0 | 2 / 3 | |
| 1.52.0 | 2 / 3 | |
| 1.51.0 | 2 / 3 | |
| 1.50.0 | 2 / 3 | |
| 1.49.0 | 2 / 3 | |
| 1.48.0 | 2 / 3 | |
| 1.46.0 | 2 / 3 | |
| 1.45.0 | 2 / 3 | |
| 1.44.0 | 2 / 3 | |
| 1.43.0 | 2 / 3 | |
| 1.42.0 | 2 / 3 | |
| 1.41.0 | 2 / 3 | |
| 1.40.0 | 2 / 3 | |
| 1.39.0 | 2 / 3 | |
| 1.38.0 | 1 / 3 | |
| 1.37.0 | 1 / 3 | |
| 1.36.0 | 1 / 3 | |
| 1.35.0 | 2 / 3 | |
| 1.34.0 | 1 / 3 | |
| 1.33.0 | 1 / 3 | |
| 1.32.0 | 1 / 3 | |
| 1.31.0 | 1 / 3 | |
| 1.30.0 | 1 / 3 | |
| 1.29.0 | 1 / 3 | |
| 1.28.0 | 1 / 3 | |
| 1.27.0 | 1 / 3 | |
| 1.26.0 | 1 / 3 | |
| 1.25.0 | 1 / 3 | |
| 1.24.0 | 1 / 3 | |
| 1.23.0 | 1 / 3 | |
| 1.22.0 | 1 / 3 | |
| 1.21.0 | 1 / 3 | |
| 1.20.0 | 1 / 3 | |
| 1.19.0 | 1 / 3 | |
| 1.18.0 | 1 / 3 | |
| 1.17.0 | 1 / 3 | |
| 1.16.0 | 1 / 3 | |
| 1.15.0 | 1 / 3 | |
| 1.14.0 | 1 / 3 | |
| 1.13.0 | 1 / 3 | |
| 1.12.0 | 1 / 3 | |
| 1.11.0 | 1 / 3 | |
| 1.10.0 | 1 / 3 | |
| 1.9.0 | 1 / 3 | |
| 1.8.0 | 1 / 3 | |
| 1.7.0 | 1 / 3 | |
| 1.6.0 | 1 / 3 | |
| 1.5.0 | 1 / 3 | |
| 1.4.0 | 1 / 3 | |
| 1.3.0 | 1 / 3 | |
| 1.2.0 | 1 / 3 | |
| 1.1.0 | 1 / 3 | |
| 1.0.0 | 1 / 4 |
v1.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.