Workspace crates

Depend on one library crate, alibi. Its public modules re-export the APIs you need from the workspace crates. The table below describes implementation ownership, not additional application dependencies.

Crate	Description	Depend on it directly when…
alibi	Composition and public facade: BetterAuth, AuthBuilder, request dispatch, plugins, stores and framework integrations	Always
alibi-core	Shared contracts and services: configuration, sessions, middleware, store decoration, plugin/endpoint contracts and errors	Never — use alibi::config, alibi::session, alibi::user_validation, and alibi::utils
alibi-api	Built-in plugin implementations and their OpenAPI metadata	Never — use alibi::plugins
alibi-sqlx	SQLx store, AuthEntity and SqlxModel derives, rate-limit storage, bundled migrations	Never — use alibi::sqlx
alibi-seaorm	SeaORM store, entities, AuthEntity derive, rate-limit storage	Never — use alibi::seaorm
alibi-cli	The alibi binary (generate)	Install it as a tool; see the CLI reference
alibi-macros	#[derive(AuthSchema)], PluginConfig	Never — use alibi::AuthSchema and alibi::PluginConfig
alibi-sqlx-macros, alibi-seaorm-macros	Derive implementations behind the SQLx and SeaORM stores	Never — use alibi::sqlx or alibi::seaorm
alibi-schema-registry, alibi-entity-codegen	Plugin schema definitions and shared derive code used by the CLI and macros	Never

Install the CLI as a separate tool using the same release version as your application; see the CLI reference.

The workspace release is 0.1.1. The library and supporting crates are published on crates.io.