@wix/editor-platform-transport
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Wix internal package published via wix-ci-publisher; missing repo/keywords is normal for proprietary Wix packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 0 / 8 | |
| 1.14.0 | 0 / 8 | |
| 1.13.0 | 0 / 8 | |
| 1.12.0 | 0 / 8 | |
| 1.11.0 | 0 / 8 | |
| 1.10.0 | 0 / 8 | |
| 1.9.0 | 0 / 8 | |
| 1.8.0 | 0 / 8 | |
| 1.5.0 | 0 / 8 |
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.