← Home

@wix/ai

npm

Wix AI SDK

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yoavwix-cishahatawixnpmwix-ambassadorwix-ci-publisherwix-bi-publishergalil-teamusability-sessionsyurynixydanivmayacoamitde007haimbrum-wixyoungshinobiethanparielhwix-org-headlessitai.bendafalconciroir-wixdorchaouat

Keywords

wixaiopenairunware

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Wix CI mass-produces scoped SDK packages with templated names and no repo links; pattern is structural, not malicious. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @wix package; Levenshtein match to 'hapi' is a false positive with no plausible confusion. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @wix package; Levenshtein match to 'pg' is a false positive with no plausible confusion. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @wix package; Levenshtein match to 'qs' is a false positive with no plausible confusion. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @wix package; Levenshtein match to 'joi' is a false positive with no plausible confusion. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @wix package; Levenshtein match to 'ajv' is a false positive with no plausible confusion. ai

Versions (showing 12 of 12)

Version Deps Published
1.13.0 3 / 6
1.12.0 3 / 6
1.11.0 2 / 6
1.10.0 2 / 6
1.9.0 2 / 6
1.8.0 2 / 6
1.7.0 2 / 6
1.6.0 2 / 6
1.5.0 2 / 6
1.4.0 1 / 6
1.3.0 1 / 6
1.2.0 1 / 6

v1.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.