Cargo package index¶
TypeBridge 2.2 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; the private Python, Node, and C 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.2 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 |
Private native-binding crates¶
These workspace crates are tested from source but are not part of the public Cargo package index:
| Package | Responsibility | Distribution status |
|---|---|---|
type-bridge-core |
PyO3 native engine for the Python product | Private Cargo crate; shipped inside Python artifacts |
type-bridge-node |
N-API native engine for the TypeScript/Node product | Private Cargo crate; shipped inside npm artifacts |
type-bridge-c |
ABI 1.6 projected-value, provider-lifecycle, typed-query, and atomic-batch foundation for generated C | Internal foundation under development; not published or packaged |
The C entry is not a support claim. The internal ABI now covers verified schema packages, projected values/models, synchronous runtime, an exact-TypeDB-3.12.3 database connection, distinct read/write transactions, cancellation, and classified commit outcomes, plus generated nominal exact single-entity and single-relation CRUD/count with closed typed role-player unions. ABI 1.6 also includes typed flat and chunked schema-package admission, policy-aware database and transaction entries, homogeneous atomic mutation batches, and the internal generated nominal typed-query, reduction, schema-function, and caller-owned remote-transport facade. Ordered C-v3 packages additionally generate nominal field-token manager filters over that existing query ABI, including borrowed read-transaction terminals, without adding runtime exports. Chunked schema-package resources and a streaming create builder keep generated C objects within the hosted C11 portability floors. Ordered C-v3 live acceptance on exact TypeDB 3.12.3 leaves ordered values empty and does not claim list-instance evidence. ABI 1.6 also exposes administration, canonical migration and backfill operations, rollback, and canonical model archives. The standalone CLI, native runtime, and generated-package artifacts must complete their public acceptance before C becomes a supported SDK.
The runtime CMake and pkg-config package version is 1.6.0, the C ABI version.
It is distinct from the TypeBridge product version reported by
type_bridge_runtime_version (2.2.2 in this source line).
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.