@ai-sdk/xai No license 43 versions

@ai-sdk/xai

npm Repository Homepage

43

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

vercel-release-botmatheussmatt.straka

Keywords

ai

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): CI migration from vercel-release-bot to GitHub Actions; both are Vercel's automated publishers.	ai	2026/04/29
source-diff	large-new-source-files	AI (source-diff): Major version bump (v2→v3) explains new files; package is well-established.	ai	2026/04/29
typosquat	typosquat.levenshtein:hapi	AI (typosquat): @ai-sdk/xai is a legitimate Vercel AI SDK scoped package; levenshtein match against 'hapi' is a false positive on the full scoped name.	ai	2026/04/25
typosquat	typosquat.levenshtein:joi	AI (typosquat): @ai-sdk/xai is a legitimate Vercel AI SDK scoped package; levenshtein match against 'joi' is a false positive on the full scoped name.	ai	2026/04/25
phantom-deps	phantom-dep:@ai-sdk/openai-compatible	AI (phantom-deps): @ai-sdk/openai-compatible is a legitimate runtime dependency in the same org scope; phantom-dep detection is a false positive here.	ai	2026/04/25

Versions (showing 43 of 145)

Version	Deps	Published
2.0.70	3 / 6	2026-04-30
2.0.69	3 / 6	2026-04-29
2.0.68	3 / 6	2026-04-17
2.0.67	3 / 6	2026-04-08
2.0.66	3 / 6	2026-04-08
2.0.65	3 / 6	2026-04-02
2.0.64	3 / 6	2026-03-30
2.0.63	3 / 6	2026-03-23
2.0.62	3 / 6	2026-03-05
2.0.61	3 / 6	2026-02-12
2.0.60	3 / 6	2026-02-12
2.0.59	3 / 6	2026-02-11
2.0.58	3 / 6	2026-02-11
2.0.57	3 / 6	2026-02-09
2.0.56	3 / 6	2026-01-30
2.0.55	3 / 6	2026-01-24
2.0.54	3 / 6	2026-01-20
2.0.53	3 / 6	2026-01-12
2.0.52	3 / 6	2026-01-12
2.0.51	3 / 6	2026-01-11
2.0.50	3 / 6	2026-01-11
2.0.49	3 / 6	2026-01-11
2.0.48	3 / 6	2026-01-09
2.0.47	3 / 6	2026-01-09
2.0.46	3 / 6	2026-01-09
2.0.45	3 / 6	2026-01-09
2.0.44	3 / 6	2026-01-06
2.0.43	3 / 6	2025-12-30
2.0.42	3 / 6	2025-12-19
2.0.41	3 / 6	2025-12-15
2.0.40	3 / 6	2025-12-11
2.0.39	3 / 6	2025-11-27
2.0.38	3 / 6	2025-11-25
2.0.37	3 / 6	2025-11-25
2.0.36	3 / 6	2025-11-24
2.0.35	3 / 6	2025-11-22
2.0.34	3 / 6	2025-11-20
2.0.33	3 / 6	2025-11-14
2.0.32	3 / 6	2025-11-10
2.0.31	3 / 6	2025-11-03
2.0.30	3 / 5	2025-10-31
2.0.29	3 / 5	2025-10-29
2.0.28	3 / 5	2025-10-27

v2.0.70

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.68

1 finding

LOW No provenance attestation provenance

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

v2.0.67

1 finding

LOW No provenance attestation provenance

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

v2.0.66

1 finding

LOW No provenance attestation provenance

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

v2.0.65

1 finding

LOW No provenance attestation provenance

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

v2.0.64

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.

v2.0.63

1 finding

LOW No provenance attestation provenance

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

v2.0.62

1 finding

LOW No provenance attestation provenance

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

v2.0.61

1 finding

LOW No provenance attestation provenance

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

v2.0.60

1 finding

LOW No provenance attestation provenance

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

v2.0.59

1 finding

LOW No provenance attestation provenance

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

v2.0.58

1 finding

LOW No provenance attestation provenance

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

v2.0.57

1 finding

LOW No provenance attestation provenance

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

v2.0.56

1 finding

LOW No provenance attestation provenance

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

v2.0.55

1 finding

LOW No provenance attestation provenance

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

v2.0.54

1 finding

LOW No provenance attestation provenance

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

v2.0.53

1 finding

LOW No provenance attestation provenance

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

v2.0.52

1 finding

LOW No provenance attestation provenance

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

v2.0.51

1 finding

LOW No provenance attestation provenance

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

v2.0.50

1 finding

LOW No provenance attestation provenance

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

v2.0.49

1 finding

LOW No provenance attestation provenance

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

v2.0.48

1 finding

LOW No provenance attestation provenance

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

v2.0.47

1 finding

LOW No provenance attestation provenance

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

v2.0.46

1 finding

LOW No provenance attestation provenance

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

v2.0.45

1 finding

LOW No provenance attestation provenance

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

v2.0.44

1 finding

LOW No provenance attestation provenance

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

v2.0.43

1 finding

LOW No provenance attestation provenance

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

v2.0.42

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.

v2.0.41

1 finding

LOW No provenance attestation provenance

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

v2.0.40

1 finding

LOW No provenance attestation provenance

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

v2.0.39

1 finding

LOW No provenance attestation provenance

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

v2.0.38

1 finding

LOW No provenance attestation provenance

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

v2.0.37

1 finding

LOW No provenance attestation provenance

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

v2.0.36

1 finding

LOW No provenance attestation provenance

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

v2.0.35

1 finding

LOW No provenance attestation provenance

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

v2.0.34

1 finding

LOW No provenance attestation provenance

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

v2.0.33

1 finding

LOW No provenance attestation provenance

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

v2.0.32

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.30

1 finding

LOW No provenance attestation provenance

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

v2.0.29

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.

v2.0.28

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.