@wix/editor-platform-environment-api
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal is part of Wix's centralized CI publisher migration, not a takeover signal. | ai | |
| provenance | publisher-changed | AI (provenance): wix-ci-publisher is Wix's established CI publisher with 2565 approved packages; transition from individual to CI account is expected. | ai | |
| phantom-deps | phantom-dep:@wix/editor-application | AI (phantom-deps): Same-org @wix scoped dep; phantom-dep false positive for internal Wix packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix package; sparse README and no public repo/keywords are expected for org-internal tooling. | ai | |
| provenance | no-provenance | AI (provenance): CI-published Wix internal package; provenance absence is consistent across the org's packages. | ai |
Versions (showing 100 of 145)
| Version | Deps | Published |
|---|---|---|
| 1.147.0 | 6 / 7 | |
| 1.146.0 | 6 / 7 | |
| 1.145.0 | 6 / 7 | |
| 1.144.0 | 6 / 7 | |
| 1.143.0 | 6 / 7 | |
| 1.142.0 | 6 / 7 | |
| 1.141.0 | 6 / 7 | |
| 1.140.0 | 6 / 7 | |
| 1.139.0 | 6 / 7 | |
| 1.138.0 | 6 / 7 | |
| 1.137.0 | 6 / 7 | |
| 1.136.0 | 6 / 7 | |
| 1.135.0 | 6 / 7 | |
| 1.134.0 | 6 / 7 | |
| 1.133.0 | 6 / 7 | |
| 1.132.0 | 6 / 7 | |
| 1.131.0 | 6 / 7 | |
| 1.130.0 | 6 / 7 | |
| 1.129.0 | 6 / 7 | |
| 1.128.0 | 6 / 7 | |
| 1.127.0 | 6 / 7 | |
| 1.126.0 | 6 / 7 | |
| 1.125.0 | 6 / 7 | |
| 1.124.0 | 6 / 7 | |
| 1.123.0 | 6 / 7 | |
| 1.122.0 | 6 / 7 | |
| 1.121.0 | 6 / 7 | |
| 1.120.0 | 6 / 7 | |
| 1.119.0 | 6 / 7 | |
| 1.118.0 | 6 / 7 | |
| 1.117.0 | 6 / 7 | |
| 1.116.0 | 6 / 7 | |
| 1.115.0 | 6 / 7 | |
| 1.114.0 | 6 / 7 | |
| 1.113.0 | 6 / 7 | |
| 1.112.0 | 6 / 7 | |
| 1.111.0 | 6 / 7 | |
| 1.110.0 | 6 / 7 | |
| 1.109.0 | 6 / 7 | |
| 1.108.0 | 6 / 7 | |
| 1.107.0 | 6 / 7 | |
| 1.106.0 | 6 / 7 | |
| 1.104.0 | 6 / 7 | |
| 1.103.0 | 6 / 7 | |
| 1.102.0 | 6 / 7 | |
| 1.101.0 | 6 / 7 | |
| 1.100.0 | 6 / 7 | |
| 1.99.0 | 6 / 7 | |
| 1.98.0 | 6 / 7 | |
| 1.97.0 | 6 / 7 | |
| 1.96.0 | 6 / 7 | |
| 1.95.0 | 6 / 7 | |
| 1.94.0 | 6 / 7 | |
| 1.93.0 | 6 / 7 | |
| 1.92.0 | 6 / 7 | |
| 1.91.0 | 6 / 7 | |
| 1.90.0 | 6 / 7 | |
| 1.89.0 | 6 / 7 | |
| 1.88.0 | 6 / 7 | |
| 1.87.0 | 6 / 7 | |
| 1.86.0 | 6 / 7 | |
| 1.85.0 | 6 / 7 | |
| 1.84.0 | 6 / 7 | |
| 1.83.0 | 6 / 7 | |
| 1.82.0 | 6 / 7 | |
| 1.79.0 | 6 / 7 | |
| 1.78.0 | 6 / 7 | |
| 1.77.0 | 6 / 7 | |
| 1.76.0 | 6 / 7 | |
| 1.75.0 | 6 / 7 | |
| 1.74.0 | 6 / 7 | |
| 1.73.0 | 6 / 7 | |
| 1.72.0 | 6 / 7 | |
| 1.71.0 | 6 / 7 | |
| 1.70.0 | 6 / 7 | |
| 1.69.0 | 6 / 7 | |
| 1.68.0 | 6 / 7 | |
| 1.67.0 | 6 / 7 | |
| 1.66.0 | 6 / 7 | |
| 1.65.0 | 6 / 7 | |
| 1.64.0 | 6 / 7 | |
| 1.63.0 | 6 / 7 | |
| 1.62.0 | 6 / 7 | |
| 1.61.0 | 6 / 7 | |
| 1.60.0 | 6 / 7 | |
| 1.59.0 | 6 / 7 | |
| 1.58.0 | 6 / 7 | |
| 1.57.0 | 6 / 7 | |
| 1.56.0 | 6 / 7 | |
| 1.55.0 | 6 / 7 | |
| 1.54.0 | 6 / 7 | |
| 1.53.0 | 6 / 7 | |
| 1.52.0 | 6 / 7 | |
| 1.51.0 | 6 / 7 | |
| 1.50.0 | 6 / 7 | |
| 1.49.0 | 6 / 7 | |
| 1.48.0 | 6 / 7 | |
| 1.47.0 | 6 / 7 | |
| 1.46.0 | 6 / 7 | |
| 1.45.0 | 6 / 7 |
v1.147.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.146.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.145.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.143.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.141.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.140.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.139.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.137.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.135.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.134.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.133.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.132.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.131.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.