Skip to main content
Vendo speaks both live AI SDK majors — ai@6 and ai@7 — so this check only fires outside that pair. Above it:
deps/ai-sdk-major
Below it, an older-than-6 install gets a different message:
deps/ai-sdk-major
check: deps/ai-sdk-major · error_code: E-DEP-001 · doctor exits: 1

​
What you’re seeing

Every static check passes. Then every internal Vendo turn fails, because @vendoai/vendo drives your ai package with call shapes that major does not accept — and npm installs the peer conflict without failing on its own.

​
Why

Vendo’s peer range is ai >=6 <8, and its suites run against both majors. A major above that pair has never been run at all; a pre-v6 ai predates the call shapes entirely. The pre-v6 case is usually a hoisted copy: another package in the workspace depends on ai@5, the workspace root hoists it, and your app resolves that copy because it never declared its own.

​
The fix

Pin ai to either supported major, with the @ai-sdk/* majors that pair with it — 4 with ai@7, 3 with ai@6.
For a pre-v6 ai, giving the app its own copy is enough.
In a workspace whose root pins another package’s ai@5, an override or packageExtension (resolutions, pnpm overrides, yarn packageExtensions) also works. Re-run npx vendo doctor once the resolved version is in range.
  • E-DEP-003: the same peer-floor problem, for zod instead of ai
  • E-DEP-002: a version mismatch between the CLI and the running wire, not a dependency floor