@ai-sdk/openai
The **[OpenAI provider](https://ai-sdk.dev/providers/ai-sdk-providers/openai)** for the [AI SDK](https://ai-sdk.dev/docs) contains language model support for the OpenAI chat and completion APIs and embedding model support for the OpenAI embeddings API.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transition from jaredpalmer to vercel-release-bot is a standard Vercel org move; bot has 458 approved packages and 1528-day history. | ai | |
| provenance | missing-githead | AI (provenance): Bot-based publishing from Vercel monorepo commonly omits gitHead; no security concern given trusted publisher. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from jaredpalmer to vercel-release-bot is a legitimate Vercel organizational transition. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a standard monorepo placeholder version in the Vercel AI SDK; 517 registry versions and 5.5M weekly downloads confirm this is a legitimate, established package. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher (jaredpalmer/Vercel); lack of provenance is common for packages of this age and does not indicate risk. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 60 new files consistent with major version adding new API surface; new large files are a language model implementation and documentation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Vercel team roster changes are expected for an actively developed SDK; publisher remains vercel-release-bot with a strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of jaredpalmer reflects normal Vercel team evolution; no hostile takeover indicators given consistent bot publisher. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Major version bump (v3→v4 beta) with new OpenAI Responses API implementation explains the 5.9x size increase; no obfuscated code flagged. | ai | |
| dependencies | unvetted-dep:@ai-sdk/provider-utils | AI (dependencies): @ai-sdk/provider-utils is a sibling package in the Vercel AI SDK monorepo; it is always a dependency of @ai-sdk/openai and is not a third-party risk. | ai |
Versions (showing 100 of 529)
v4.0.0-beta.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0-beta.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.