@wix/sdk
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): Scoped corporate SDK; missing metadata fields are expected for internal Wix packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix corporate SDK; missing description is a stable pattern across versions. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.21.12 | 8 / 17 | |
| 1.21.11 | 8 / 17 | |
| 1.21.10 | 8 / 17 | |
| 1.21.9 | 8 / 17 | |
| 1.21.8 | 8 / 17 | |
| 1.21.7 | 8 / 17 | |
| 1.21.6 | 8 / 17 | |
| 1.21.5 | 8 / 17 | |
| 1.21.4 | 8 / 17 | |
| 1.21.3 | 8 / 17 | |
| 1.21.2 | 8 / 17 | |
| 1.21.1 | 8 / 17 | |
| 1.20.0 | 8 / 17 | |
| 1.19.0 | 8 / 17 | |
| 1.18.0 | 8 / 17 | |
| 1.17.9 | 8 / 17 | |
| 1.17.8 | 9 / 17 | |
| 1.17.7 | 9 / 17 | |
| 1.17.6 | 9 / 17 | |
| 1.17.5 | 10 / 18 | |
| 1.17.4 | 9 / 17 | |
| 1.17.3 | 9 / 17 | |
| 1.17.2 | 9 / 17 | |
| 1.17.1 | 9 / 17 | |
| 1.17.0 | 9 / 17 | |
| 1.16.0 | 9 / 17 | |
| 1.15.27 | 9 / 17 | |
| 1.15.26 | 9 / 17 | |
| 1.15.25 | 9 / 17 | |
| 1.15.24 | 9 / 17 | |
| 1.15.23 | 9 / 17 | |
| 1.15.22 | 9 / 17 | |
| 1.15.21 | 9 / 17 | |
| 1.15.20 | 9 / 17 | |
| 1.15.19 | 9 / 17 |
v1.21.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.