Unverified50% confidenceOpinionExact time
@ai-sdk/sandbox-vercel and @ai-sdk/harness are released in sync with the same version number, indicating that the two packages are managed together in release cadence and very likely share the same build and test pipeline.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/9/2026
First Seen
Valid until: 2/7/2027
Sources
Related Entities
Related Claims
UnverifiedAs an adapter layer for a specific vendor, @ai-sdk/topaz must stay in version sync with @ai-sdk/provider and @ai-sdk/provider-utils; otherwise, interface signature mismatches will cause errors at runtime.71% similarUnverified@ai-sdk/sandbox-vercel depends at runtime on preset sandbox templates, which have version state.67% similarUnverifiedVercel AI SDK sub-packages are published independently to npm, with their version numbers decoupled from one another.65% similarUnverifiedFrom the version number (0.0.x), it is evident that @ai-sdk/mcp is still in an early iteration stage, and its API and behavior may evolve rapidly across versions.64% similarUnverifiedIn the Vercel AI SDK ecosystem, the major version numbers of the framework adapter packages are not in sync with the core package: @ai-sdk/vue is at 3.x while ai is at 6.x.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1150028API
curl https://kongchang.com/api/v1/knowledge/claims/1150028MCP
get_claim(id=1150028)