ai
AI SDK by Vercel - build apps like ChatGPT, Claude, Gemini, and more with a single interface for any model using the Vercel AI Gateway or go direct to OpenAI, Anthropic, Google, or any other model provider.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase driven by large test file additions, not bundled/injected runtime payloads. Benign for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are test suites (.test.ts), consistent with expanding test coverage in a major SDK. No injected runtime code. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Flagged URL (127.0.0.1:3000) is in a test fixture file, representing a localhost test server address. This is standard test code, not a real network request to a suspicious IP. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of comparing v6 against v4 baseline. The ai package is actively maintained by Vercel with 1155 versions; major version gaps are expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removals are consistent with Vercel's organizational restructuring for a major v6 release. Publisher remains the official vercel-release-bot. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @ai-sdk/gateway is a first-party Vercel AI SDK package added as part of the v6 architecture. Not a suspicious third-party dependency. | ai | |
| dependencies | unvetted-dep:@ai-sdk/react | AI (dependencies): @ai-sdk/react is a first-party Vercel AI SDK package from the same monorepo; unvetted flag is expected and not a real risk. | ai | |
| osv | osv:GHSA-rwvc-j5jr-mgvh | AI (osv): Advisory affects 5.x versions only (< 5.0.52 and 5.1.0-beta range). Package [email protected] is not in the affected range; this finding is a false positive for the 4.x line. | ai | |
| dependencies | unvetted-dep:@ai-sdk/ui-utils | AI (dependencies): @ai-sdk/ui-utils is a first-party Vercel AI SDK package from the same monorepo; unvetted flag is expected and not a real risk. | ai | |
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): 'ai' is the official Vercel AI SDK package name, not a typosquat of 'hapi'. Short name matches are false positives for this well-known package. | ai | |
| dependencies | unvetted-dep:@opentelemetry/api | AI (dependencies): @opentelemetry/api is a well-known observability library; its use in an AI SDK for tracing is expected and benign. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): 'ai' is the official Vercel AI SDK package name, not a typosquat of 'ajv'. Short name matches are false positives for this well-known package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): 'ai' is the official Vercel AI SDK package name, not a typosquat of 'joi'. Short name matches are false positives for this well-known package. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 'ai' is the official Vercel AI SDK package name, not a typosquat of 'qs'. Short name matches are false positives for this well-known package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 'ai' is the official Vercel AI SDK package name, not a typosquat of 'pg'. Short name matches are false positives for this well-known package. | ai |
Versions (showing 100 of 302)
| Version | Deps | Published |
|---|---|---|
| 6.0.90 | 4 / 12 | |
| 6.0.89 | 4 / 12 | |
| 6.0.88 | 4 / 12 | |
| 6.0.87 | 4 / 12 | |
| 6.0.86 | 4 / 12 | |
| 6.0.85 | 4 / 12 | |
| 6.0.84 | 4 / 12 | |
| 6.0.83 | 4 / 12 | |
| 6.0.82 | 4 / 12 | |
| 6.0.81 | 4 / 12 | |
| 6.0.80 | 4 / 12 | |
| 6.0.79 | 4 / 12 | |
| 6.0.78 | 4 / 12 | |
| 6.0.77 | 4 / 12 | |
| 6.0.76 | 4 / 12 | |
| 6.0.75 | 4 / 12 | |
| 6.0.74 | 4 / 12 | |
| 6.0.73 | 4 / 12 | |
| 6.0.72 | 4 / 12 | |
| 6.0.71 | 4 / 12 | |
| 6.0.70 | 4 / 12 | |
| 6.0.69 | 4 / 12 | |
| 6.0.68 | 4 / 12 | |
| 6.0.67 | 4 / 12 | |
| 6.0.66 | 4 / 12 | |
| 6.0.65 | 4 / 12 | |
| 6.0.64 | 4 / 12 | |
| 6.0.63 | 4 / 12 | |
| 6.0.62 | 4 / 12 | |
| 6.0.61 | 4 / 12 | |
| 6.0.60 | 4 / 12 | |
| 6.0.59 | 4 / 12 | |
| 6.0.58 | 4 / 12 | |
| 6.0.57 | 4 / 12 | |
| 6.0.56 | 4 / 12 | |
| 6.0.55 | 4 / 12 | |
| 6.0.54 | 4 / 12 | |
| 6.0.53 | 4 / 12 | |
| 6.0.52 | 4 / 12 | |
| 6.0.51 | 4 / 12 | |
| 6.0.50 | 4 / 12 | |
| 6.0.49 | 4 / 12 | |
| 6.0.48 | 4 / 12 | |
| 6.0.47 | 4 / 12 | |
| 6.0.46 | 4 / 12 | |
| 6.0.45 | 4 / 12 | |
| 6.0.44 | 4 / 12 | |
| 6.0.43 | 4 / 12 | |
| 6.0.42 | 4 / 12 | |
| 6.0.41 | 4 / 12 | |
| 6.0.40 | 4 / 12 | |
| 6.0.39 | 4 / 12 | |
| 6.0.38 | 4 / 12 | |
| 6.0.37 | 4 / 12 | |
| 6.0.36 | 4 / 12 | |
| 6.0.35 | 4 / 12 | |
| 6.0.34 | 4 / 12 | |
| 6.0.33 | 4 / 12 | |
| 6.0.32 | 4 / 12 | |
| 6.0.31 | 4 / 12 | |
| 6.0.30 | 4 / 12 | |
| 6.0.29 | 4 / 12 | |
| 6.0.28 | 4 / 12 | |
| 6.0.27 | 4 / 12 | |
| 6.0.26 | 4 / 12 | |
| 6.0.25 | 4 / 12 | |
| 6.0.24 | 4 / 12 | |
| 6.0.23 | 4 / 12 | |
| 6.0.22 | 4 / 12 | |
| 6.0.21 | 4 / 12 | |
| 6.0.20 | 4 / 12 | |
| 6.0.19 | 4 / 12 | |
| 6.0.18 | 4 / 12 | |
| 6.0.17 | 4 / 12 | |
| 6.0.16 | 4 / 12 | |
| 6.0.15 | 4 / 12 | |
| 6.0.14 | 4 / 12 | |
| 6.0.13 | 4 / 12 | |
| 6.0.12 | 4 / 12 | |
| 6.0.11 | 4 / 12 | |
| 6.0.10 | 4 / 12 | |
| 6.0.9 | 4 / 12 | |
| 6.0.8 | 4 / 12 | |
| 6.0.7 | 4 / 12 | |
| 6.0.6 | 4 / 12 | |
| 6.0.5 | 4 / 12 | |
| 6.0.4 | 4 / 12 | |
| 6.0.3 | 4 / 12 | |
| 6.0.2 | 4 / 12 | |
| 6.0.1 | 4 / 12 | |
| 6.0.0 | 4 / 12 | |
| 5.0.193 | 4 / 10 | |
| 5.0.192 | 4 / 10 | |
| 5.0.190 | 4 / 10 | |
| 5.0.188 | 4 / 10 | |
| 5.0.187 | 4 / 10 | |
| 5.0.186 | 4 / 10 | |
| 5.0.185 | 4 / 10 | |
| 5.0.184 | 4 / 10 | |
| 5.0.183 | 4 / 10 |
v6.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.193
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.192
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.190
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.188
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.187
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.186
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.185
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.184
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.183
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.