Stability

Each Baeta package falls into one of three stability tiers. Pick the ones that fit your tolerance for change.

Stability levels

🟢 Stable

Tested, with a stable public API. Breaking changes only land in major version bumps. Baeta as a project is still young, but these packages are safe to depend on.

🟡 Beta

Feature-complete, but may take breaking changes in minor versions. Fine for most production use cases — pin minor versions if you want extra safety.

🟠 Early testing

Experimental. Expect significant API churn. Not recommended for production.

Package status

Core packages

Package	Status	Tests
@baeta/core	🟢 Stable	✅
@baeta/env	🟢 Stable	✅
@baeta/errors	🟢 Stable	✅
@baeta/directives	🟢 Stable	✅
@baeta/cache	🟡 Beta	✅

App plugins

Package	Status	Tests
@baeta/auth	🟢 Stable	✅
@baeta/complexity	🟢 Stable	✅

Cache adapters

Package	Status	Tests
@baeta/cache-cloudflare	🟡 Beta	✅
@baeta/cache-ioredis	🟡 Beta	✅
@baeta/cache-iovalkey	🟡 Beta	✅
@baeta/cache-upstash	🟡 Beta	✅

Subscriptions

Package	Status	Tests
@baeta/subscriptions-cloudflare	🟡 Beta	❌
@baeta/subscriptions-pubsub	🟢 Stable	✅

Federation

Package	Status	Tests
@baeta/federation	🟡 Beta	✅
@baeta/plugin-federation	🟡 Beta	✅

Development tools

Package	Status	Tests
@baeta/cli	🟢 Stable	✅
@baeta/plugin-cloudflare	🟢 Stable	❌
@baeta/plugin-directives	🟢 Stable	✅
@baeta/plugin-exec	🟢 Stable	✅
@baeta/plugin-gitignore	🟢 Stable	✅
@baeta/plugin-graphql	🟢 Stable	✅
@baeta/plugin-pagination	🟢 Stable	✅
@baeta/plugin-prisma	🟢 Stable	❌

Testing coverage

Every runtime package ships with unit tests except where flagged ❌ in the tables above. Test coverage is enforced in CI and gates releases — a ❌ row means the package has no public test suite yet, not that its tests are failing. Coverage gaps for current ❌ entries are tracked as project work.