Skip to main content
SDKs expose BRIK64 concepts inside language ecosystems. They are useful for examples, teaching monomer behavior and integrating circuit thinking into existing codebases. The CLI remains the primary path for the public local BRIK64 workflow and is distributed through the curl installer. SDK packages are language libraries; they are not CLI installation channels.

​
Package Surfaces

| Language | Package surface | Current status | Use | | --- | --- | --- | | JavaScript/TypeScript | npm package | @brik64/core@0.1.0-beta.7 | Monomer-oriented helpers and examples. | | Python | PyPI package | brik64==0.1.0b7 | Monomer helpers and EVA composition examples. | | Rust | crates.io package | brik64-core@0.1.0-beta.7 | Rust monomer helpers and EVA composition examples. |

​
Install Commands

Use the beta7 SDK packages from their language registries: 
npm install @brik64/core@0.1.0-beta.7
pip install brik64==0.1.0b7
cargo add brik64-core --version 0.1.0-beta.7
Do not use npm to install the CLI. Install the CLI with: 
curl -fsSL https://brik64.com/cli/install.sh | bash

​
Release-Backed Examples

Release-backed SDK examples should name the package, installed version, example output and relationship to the local brik64 command. Treat SDKs as language packages and brik64 as the command workflow unless the release explicitly says otherwise.