Skip to content

Cargo package index

TypeBridge 2.1 publishes 17 first-party Rust packages as one lockstep product. Two source-unmodified TypeDB compatibility packages remain public under their fixed versions. This page is the maintained index for those 19 public Cargo packages; private Python and Node native-binding crates are deliberately not part of the crates.io surface.

Most application authors need only type-bridge. Generated Rust bindings depend on that SDK facade and should not assemble the supporting layers directly.

Package layers

generated Rust application packages
                 |
                 v
 type-bridge SDK | type-bridge-cli | type-bridge-server
                 |
                 v
 ORM | query | migration | workspace | schema code generation
                 |
                 v
 schema | schema compatibility | TypeDB runtime
                 |
                 v
 core library | wire contract | retained TypeDB compatibility packages

Arrows mean “uses a lower-level responsibility”, not that every package has a direct Cargo dependency on every package below it. The package manifests remain the exact dependency authority.

Primary entry points

Package Responsibility Use it directly when
type-bridge · rustdoc Generated Rust SDK runtime and public client facade Building an application from generated Rust bindings
type-bridge-cli · rustdoc Reusable CLI library plus the thin type-bridge binary Embedding or installing Split-YAML, generation, and migration commands
type-bridge-server · rustdoc Generic query-server library and production binary Serving generated V2 query authority over the supported transport

Supporting packages

Supporting crates are public so generated packages, integrations, and advanced Rust consumers can use a stable boundary without depending on private native bindings. They are not separate products with independent version lines.

Package Layer responsibility Intended direct consumers
type-bridge-contract · rustdoc Binding-neutral identifiers, values, diagnostics, and wire contracts Alternative bindings and protocol tooling
type-bridge-core-lib · rustdoc Shared compatibility engine retained below public language surfaces TypeBridge adapters that need the established core implementation
type-bridge-schema · rustdoc Lossless Split-YAML schema documents, normalization, and safety classification Schema tools that operate before provider execution
type-bridge-query · rustdoc Immutable provider-neutral query plans and validation Generated query facades and alternate executors
type-bridge-schema-migration · rustdoc Provider-neutral schema migration manifests, profiles, and lowering Migration planners and provider adapters
type-bridge-toml-transpiler · rustdoc TOML recovery-schema to TypeQL transpilation Recovery and compatibility tooling only
type-bridge-schema-compat · rustdoc One-way compatibility parsers into the V2 schema fact graph Importers for retained released schema formats
type-bridge-schema-codegen · rustdoc Python, TypeScript, and Rust source projection from compiled schema authority Generators and build integrations
type-bridge-orm-derive · rustdoc Procedural derives for Rust ORM model metadata Generated Rust model crates through re-exported derives
type-bridge-typedb-runtime · rustdoc TypeDB driver-band selection and provider execution primitives TypeDB-backed executors and server integrations
type-bridge-orm · rustdoc Async model CRUD, transactions, hooks, and query execution Generated Rust models and generated runtime integrations
type-bridge-migration · rustdoc Migration authoring, planning, archives, and execution orchestration CLI and migration automation
type-bridge-schema-migration-typedb · rustdoc TypeDB lowering and execution adapter for provider-neutral schema migrations TypeDB migration runners
type-bridge-workspace · rustdoc Split-YAML workspace discovery, configuration, and generated artifact paths CLI and workspace-aware build tooling

Retained compatibility packages

These packages preserve exact, source-unmodified TypeDB components needed by the supported compatibility band. They keep their upstream-derived licensing and fixed versions; they do not follow the TypeBridge 2.1 version line.

Package Fixed version Purpose
type-bridge-typedb-protocol-b8 · rustdoc 3.11.0 Namespaced protocol package for the retained band-8 driver graph
type-bridge-typedb-driver-b8 · rustdoc 3.11.5 Namespaced TypeDB driver package for the retained band-8 runtime

Release contract

  • All 17 first-party packages use Rust 1.88 or newer and release in dependency order under one TypeBridge version.
  • Every first-party library builds independently with all features and strict rustdoc coverage; changing a package's publish metadata cannot remove it from the inventory-driven gate.
  • The two retained compatibility packages are verified as preexisting, immutable inputs rather than republished as TypeBridge-authored code.
  • See the Rust client guide for application usage and the development internals for release validation.