SDKs and lightweight installation
Zero-install browser tooling, source SDKs and versioned release roadmap.
SDKs and lightweight installation
No installation is needed to try Zerynex. Open the public workbench at /tools, select a harmless synthetic fixture, and analyze it locally through the Rust/WebAssembly engine.
For applications, use the smallest compatible interface:
| Language | Integration | Current availability |
|---|---|---|
| TypeScript | SDK backed by Rust/WASM | Repository-local, not yet npm-published |
| Rust | Canonical library and CLI | Source/Cargo Git install |
| Python | Adapter invoking the trusted Rust CLI | Source package, not PyPI-published |
| Go | Source module invoking the trusted Rust CLI | Not independently tagged yet |
| Agents | Restricted stdio MCP and Agent Skill | Explicit opt-in source integration |
| CI | Composite GitHub Action | Commit-SHA pinning and synthetic fixtures |
One Rust parser and policy engine avoids duplicated security-critical cryptographic code and keeps findings consistent. TypeScript runs it as WASM. Python and Go currently invoke the local executable.
Rust CLI without cloning the Next.js app
Cargo Git installation fetches and builds the CLI executable:
cargo install --git https://github.com/Oluwa-Laughter/zerynex --locked --bin zerynex
This is still compilation from source, not a prebuilt binary release. A compatible Rust toolchain is required. The website does not need Rust installed when analyzing PCZTs in-browser.
Before claiming one-command SDK distribution
- Pin supported PCZT and Rust versions.
- Build and test standalone binaries for supported platforms.
- Publish immutable binaries with checksums.
- Publish compiled TypeScript/WASM SDK to npm and test from an unrelated clean React/Next app.
- Publish a Python wheel with a clear native/CLI dependency model.
- Tag and test the Go module's consumer path.
- Tag the CI action and recommend reviewed commit-SHA pinning.
- Update website installation snippets only after successful release tests.
Package management must not be a substitute for actual integration tests. Read the installation guide for current source workflows.
Organization ownership
When an owner-authorized Zerynex GitHub organization exists, source and CI/install links can be migrated deliberately. Until then, retain valid links only in technical provenance, not the homepage or main navigation.