Download and release artifacts

Download Zerynex without cloning the repository

Zerynex is a Rust-first developer-tool platform with a small WebAssembly SDK and local MCP integrations. No download is required to try the publicly hosted PCZT workbenches at /tools.

Tested distribution formats

Current verified release: v0.2.0. The OS-native Rust CLI archives, @zerynex/sdk@0.2.0 npm package, zerynex-python==0.2.0 PyPI wheel/source distribution, and independently tagged packages/go/v0.2.0 Go module are public. The release builds each distribution from pinned source and verifies real synthetic-policy checks. Match downloaded archives to their adjacent SHA-256 manifests before use; checksums are not cryptographic signatures.

GitHub distribution workflow

The distribution workflow runs automatically when release-related source files change on main, or manually by maintainers, to produce download artifacts retained by GitHub Actions for a limited time. It builds Linux, macOS and Windows CLI executables as well as TypeScript and Python packages.

Verify the version and checksum of a downloaded archive. A SHA-256 checksum does not provide a cryptographic signature.

Download the compiled Rust CLI

Download your OS-specific archive and its adjacent SHA256SUMS file. Verify the checksum, extract the compiled analyzer executable, then run it against your own local synthetic fixture:

zerynex path/to/approved-synthetic.pczt --deny-transparent --json

No monorepo checkout or Rust toolchain is needed to execute the binary. Never upload real confidential PCZTs, wallet keys, mnemonics or private transaction details to GitHub Actions or public sample fixtures.

TypeScript: SDK with bundled Rust/WASM

The npm tarball carries the same compiled Rust/WASM engine as the hosted workbenches. Developers do not have to compile Rust. Install a downloaded tarball with a supported package manager:

npm install ./zerynex-sdk-0.2.0.tgz
yarn add ./zerynex-sdk-0.2.0.tgz
pnpm add ./zerynex-sdk-0.2.0.tgz

The runtime entry point is @zerynex/sdk/browser. It exports createBrowserZerynexClient, which initializes the packaged WASM. The separate @zerynex/sdk/wasm/zerynex_bg.wasm export supports application-specific asset loading when required.

import { createBrowserZerynexClient } from '@zerynex/sdk/browser'

// Supply the trusted packaged wasm bytes through your asset pipeline,
// if your bundler cannot automatically resolve the adjacent WASM asset.
const client = createBrowserZerynexClient({ wasm: trustedWasmBytes })
const report = await client.analyzeBlob(file, { deny_transparent: true })
console.log(report.findings)

When a bundler correctly serves the adjacent WASM asset, createBrowserZerynexClient() can initialize it without a custom loader. Framework compatibility must be tested individually. Both forms execute policy checks locally.

To test the actual tarball from an unrelated temporary application:

cd packages/sdk
npm run build
cd ../..
node scripts/test-sdk-packed.mjs

This uses npm install offline against a local packed artifact and verifies real Rust/WASM scanning and stage comparison, not a fake engine.

Python wheel with locally installed CLI

Download the Python wheel and matching OS-native CLI archive. After installing the verified CLI:

python -m pip install ./zerynex_python-0.2.0-py3-none-any.whl

The MCP integration uses an optional dependency:

python -m pip install './zerynex_python-0.2.0-py3-none-any.whl[mcp]'

Set ZERYNEX_CLI to the installed Rust executable. Configure a dedicated approved synthetic fixture directory through ZERYNEX_AGENT_ALLOWED_ROOT, then follow MCP and agent setup for the doctor command.

The Python wheel delegates to the Rust CLI locally; it does not include a separate cryptographic engine or require Next.js.

Reproduce the public consumer verification

From a checked-out source tree, run node scripts/smoke-published.mjs 0.2.0 to test the public npm, PyPI and Go distributions in an isolated temporary project using nonspendable PCZTs and metadata. This network-dependent smoke installs published packages and executes their Rust/WASM and Python interfaces, and checks the npm-installed refund command. Set ZERYNEX_CLI to a trusted local Rust executable to exercise Python → Rust integration as well. For details and limitations see external developer verification.

Trust boundaries

• Download release artifacts from the intended organization and verify the published SHA-256 digests.
• Pin immutable reviewed commit SHAs for CI integration.
• Local policy lint results do not establish a formal audit, transaction correctness, Zcash consensus validity or anonymity.