@wix/sdk-types
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legit internal Wix maintainer handoff; both accounts tied to @wix org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Wix internal team rotation via wix-ci-publisher; consistent with org-level maintainer management. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Wix internal team rotation; removal paired with addition is expected for org handoffs. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Wix SDK package; dormancy followed by resumption is consistent with SDK lifecycle, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Wix scoped types package; missing metadata is expected for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Wix SDK types package; no description is consistent across its version history. | ai |
Versions (showing 51 of 176)
| Version | Deps | Published |
|---|---|---|
| 1.17.11 | 3 / 6 | |
| 1.17.10 | 3 / 6 | |
| 1.17.9 | 3 / 6 | |
| 1.17.8 | 3 / 6 | |
| 1.17.7 | 3 / 6 | |
| 1.17.6 | 3 / 6 | |
| 1.17.5 | 3 / 6 | |
| 1.17.4 | 3 / 6 | |
| 1.17.3 | 3 / 6 | |
| 1.17.2 | 3 / 6 | |
| 1.17.1 | 3 / 6 | |
| 1.17.0 | 3 / 6 | |
| 1.16.0 | 3 / 6 | |
| 1.14.0 | 3 / 6 | |
| 1.13.41 | 3 / 6 | |
| 1.13.40 | 3 / 6 | |
| 1.13.39 | 3 / 6 | |
| 1.13.38 | 3 / 6 | |
| 1.13.37 | 3 / 6 | |
| 1.13.36 | 3 / 6 | |
| 1.13.35 | 3 / 6 | |
| 1.13.34 | 3 / 6 | |
| 1.13.33 | 3 / 6 | |
| 1.13.32 | 3 / 6 | |
| 1.13.31 | 3 / 6 | |
| 1.13.30 | 3 / 6 | |
| 1.13.29 | 3 / 6 | |
| 1.13.28 | 3 / 6 | |
| 1.13.27 | 3 / 6 | |
| 1.13.26 | 3 / 6 | |
| 1.13.25 | 3 / 6 | |
| 1.13.24 | 2 / 6 | |
| 1.13.23 | 2 / 6 | |
| 1.13.22 | 2 / 6 | |
| 1.13.21 | 2 / 6 | |
| 1.13.20 | 2 / 6 | |
| 1.13.19 | 2 / 6 | |
| 1.13.18 | 2 / 6 | |
| 1.13.17 | 2 / 6 | |
| 1.13.16 | 2 / 6 | |
| 1.13.15 | 2 / 6 | |
| 1.13.14 | 2 / 5 | |
| 1.13.13 | 2 / 5 | |
| 1.13.12 | 2 / 5 | |
| 1.13.11 | 2 / 5 | |
| 1.13.10 | 2 / 5 | |
| 1.13.9 | 1 / 6 | |
| 1.13.8 | 1 / 6 | |
| 1.13.7 | 1 / 6 | |
| 1.13.6 | 1 / 6 | |
| 1.13.5 | 1 / 6 |
v1.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.13
2 findingsThis version was published by a different npm account than previous versions on 2025-04-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.