Skip to content

Compatibility

Auditaur has Rust crates, an npm frontend package, a CLI binary, and app-side runtime code. Keep them from the same release line when possible.

ComponentInstall nameCurrent documented version
CLI binarycargo install auditaur-cli0.4.0
Tauri plugintauri-plugin-auditaur0.4.0
Frontend SDK@auditaur/api0.5.1
Core/collector cratesauditaur-core, auditaur-collector0.4.0
Macro cratetauri-plugin-auditaur-macros0.4.0
[dependencies]
tauri-plugin-auditaur = "0.4.0"
tracing = "0.1"
tracing-subscriber = "0.3"
Terminal window
npm install @auditaur/api@0.5.1
PairWhy it matters
CLI and Rust pluginThey share SQLite schema expectations, discovery metadata, health checks, and drive bridge status interpretation.
Rust plugin and frontend SDKThey share the frontend export command, record envelopes, trace propagation carriers, and drive bridge protocol.
Plugin and macro cratetauri-plugin-auditaur re-exports macros; release automation keeps the macro crate and plugin crate aligned.

Run:

Terminal window
auditaur health --json
auditaur doctor --db "<databasePath>" --json

Version skew commonly appears as schema validation failures, capability warnings, frontend export failures, missing drive bridge fields, or unsupported bridge action compatibility messages.

Inside the Auditaur repository, use source commands when testing local changes:

Terminal window
cargo run -p auditaur-cli -- doctor
cargo run -p auditaur-cli -- apps --json
cd packages\api
npm run build

For the dogfood app, build the local frontend package before starting Tauri:

Terminal window
cd examples\dogfood
npm install
npm run build:api
npm run tauri dev
  1. Update the Rust plugin version in src-tauri\Cargo.toml.
  2. Update @auditaur/api in the frontend package manager lockfile.
  3. Restart the Tauri dev process so a fresh session is created.
  4. Run auditaur doctor tauri --path src-tauri --json.
  5. Run auditaur apps --json and confirm the active session is readable and schema-valid.