Skip to main content
The SDK is shipped as local packaged artifacts for all targets. This guide covers the repeatable install flow.

Artifact layout

Verify integrity

Every artifact is covered by dist/manifests/compatibility-manifest.json (artifact hashes) and dist/checksums/SHA256SUMS:
The manifest also pins the exact supported engines and platforms — compare it against your build before releasing:
Native platforms: x86_64-unknown-linux-gnu, x86_64-apple-darwin, aarch64-apple-darwin, x86_64-pc-windows-msvc, aarch64-linux-android, aarch64-apple-ios, x86_64-apple-ios.

Vendor the artifact

Do not rely on a friend’s node_modules — vendor:
  • npm-style targets: commit the tarball and use a file: dependency ("@musterbox/sdk-js": "file:vendor/musterbox-sdk-js-1.0.0.tgz").
  • Rust/Bevy: point Cargo.toml at the extracted crate (musterbox-bevy = { path = "vendor/musterbox-bevy" }).
  • Native FFI: link the libmusterbox_ffi archive for your triple and verify ABI 1.2.0 at link time.

Verify at runtime

After installing, confirm:
A mismatch (wrong ABI/config schema) fails fast with MismatchedVersion instead of a confusing runtime error. Next: Mutual-claim result flow.
Last modified on September 10, 2026