Jev GitHub and Open Source

Searches for Jev GitHub, Jev open source, and Jev local usually want a repo and a git clone. That is not how Jev ships today.

What is official

Artifact	Where	Role
HTTP API	https://api.typesafe.ai/v1/systemone	The model
Python SDK	PyPI typesafe-sdk	Official client
JS / TS SDK	npm @typesafe-ai/sdk	Official client
Docs	docs.typesafe.ai	Contract

SDK source may appear on GitHub or a registry tarball depending on how TypeSafe publishes a given version. That is client source, not the Jev model.

This site is also on GitHub (picsai288/JevAIHub). It is an independent content repo, not TypeSafe.

What “Jev local” actually is

A local process:

• your FastAPI / Next.js worker
• a community MCP server
• a CLI that reads TYPESAFE_API_KEY

still sends state and questions to a hosted endpoint (TypeSafe, or a gateway such as OpenRouter / Vercel). Mock providers in community tools are for tests. They are not Jev.

Community GitHub

Independent CLIs and MCP servers exist. They are useful as examples of how people wrap Jev. They are not official TypeSafe products, and they still consume your TypeSafe (or gateway) quota.

Do not paste a community README's API key flow into production without reading it. Prefer the official SDK pages.

Jev docs

Two different “docs” searches:

• TypeSafe AI docs → docs.typesafe.ai
• Independent Jev docs → this hub's Learn Jev index

When to look for GitHub

You want SDK issues, a community wrapper, or this site's source.

When not to

You want to fine-tune or air-gap Jev. Official models docs say Jev is not customer-fine-tuned, and we found no local weight drop.

Common mistakes

• Installing a similarly named package that is not typesafe-sdk / @typesafe-ai/sdk.
• Treating a community MCP repo as “the official Jev GitHub”.
• Expecting jev-latest to run offline after npm install.

Next: How to use Jev or the Python tutorial.