npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@orderly.network/orderly

v2.2.2

Published

WebAssembly SDK for Orderly Network, built from the Orderly CLI core

Readme

orderly

CLI for Orderly Network trading, with secure OS keychain authentication. Ships as a single static binary — no Node.js runtime required.

Features

  • Secure key storage — wallet and API keys live in the OS keychain, never in files
  • AI-friendly — keys are never exposed in output; the CLI returns only results
  • Full trading support — place/cancel orders, algo orders, positions, leverage
  • Orderly Predict — 5-minute BTC Up/Down rounds, UP/DOWN order books, protected closes
  • Multi-chain — EVM (Arbitrum, Base, Optimism, …) and Solana

Install

One line — detects Linux/macOS and x86_64/arm64, verifies the release checksum, and installs to ~/.local/bin:

curl -fsSL https://raw.githubusercontent.com/OrderlyNetwork/cli/main/install.sh | sh

Override the target with ORDERLY_INSTALL_DIR=/usr/local/bin, or pin a release with ORDERLY_VERSION=v2.0.1. Windows has no shell installer yet:

# Windows x86_64 (use aarch64-pc-windows-msvc on ARM)
Invoke-WebRequest https://github.com/OrderlyNetwork/cli/releases/latest/download/orderly-x86_64-pc-windows-msvc.zip -OutFile orderly.zip
Expand-Archive orderly.zip -DestinationPath "$env:LOCALAPPDATA\orderly"

Manual archives, per-platform assets, verification and building from source are in INSTALL.md.

Every release asset is covered by SHA-256 checksums, a GitHub build-provenance attestation and a cosign signature — see INSTALL.md.

Quick Start (Testnet)

# 1. Create a new EVM wallet
orderly wallet-create --type EVM --network testnet

# 2. Register Orderly account
orderly wallet-register --broker-id demo --network testnet

# 3. Request test USDC (wait a few minutes for delivery)
orderly faucet-usdc <address> --broker-id demo --chain-id 421614 --network testnet

# 4. Add API key for trading (generates Ed25519 key automatically)
orderly wallet-add-key --broker-id demo --scope read,trading --network testnet

# 5. List accounts to get your account ID
orderly auth-list --network testnet

# 6. Check balance
orderly account-balance --account <account-id> --network testnet

# 7. Place an order
orderly order-place PERP_ETH_USDC BUY MARKET 0.01 --account <account-id> --network testnet

If the account already has an API key, you can credit the Orderly account directly and wait for the balance to arrive:

orderly faucet-account --account <account-id> --chain-id 421614 --wait --network testnet

Note: --account is required for all authenticated commands. Use auth-list to see available accounts.

Common Commands

# Account management
orderly account-info --account <account-id>
orderly account-balance --account <account-id>

# Trading - Orders
orderly order-place PERP_ETH_USDC BUY LIMIT 0.01 --price 3500 --account <account-id>
orderly order-place PERP_ETH_USDC BUY MARKET 0.01 --client-order-id my-order-123 --account <account-id>
orderly order-cancel <order-id> --symbol PERP_ETH_USDC --account <account-id>
orderly order-list --status NEW --account <account-id>

# Trading - Algo Orders (TP/SL)
orderly algo-order-place PERP_ETH_USDC BUY STOP 0.01 --trigger-price 2000 --account <account-id>
orderly algo-order-place PERP_ETH_USDC SELL TP_SL 0.01 --tp-trigger-price 2500 --sl-trigger-price 1500 --account <account-id>
orderly algo-order-list --account <account-id>

# Positions
orderly positions-list --account <account-id>
orderly positions-close PERP_ETH_USDC --account <account-id>

# Orderly Predict (5-minute BTC Up/Down; mainnet and testnet)
orderly predict-rounds --current
orderly predict-round
orderly predict-orderbook
orderly predict-buy <round-symbol> UP 5 --price 0.53 --type IOC --account <account-id>
orderly predict-buy <round-symbol> DOWN 5 --price 0.58 --type IOC --account <account-id>
orderly positions-list --product-type BINARY --account <account-id>
orderly predict-close <round-symbol> --account <account-id>
orderly order-list --product-type BINARY --account <account-id>
orderly positions-history --product-type BINARY --account <account-id>
orderly order-cancel-all --symbol <round-symbol> --account <account-id>

# Market data
orderly market-price PERP_ETH_USDC
orderly market-trades PERP_ETH_USDC --limit 20
orderly funding-rates
orderly kline PERP_ETH_USDC 1h --limit 100 --account <account-id>
orderly symbols

Orderly Predict notes

  • Round symbols are permanent and per-round. Always read the symbol from predict-rounds / predict-round; never construct or reuse one.
  • The matching engine only has the UP book. --price is always in the selected direction: buying DOWN at d is sent as SELL UP @ 1-d, and selling DOWN at d is sent as BUY UP @ 1-d. predict-orderbook shows both sides.
  • Use down_asks to buy DOWN and down_bids to sell DOWN. predict-close computes a protected IOC price two ticks beyond the best bid/ask.
  • The minimum notional is always checked against the UP-book price, even for DOWN orders.
  • order-place and positions-close are perpetual-futures commands. Use predict-buy / predict-sell / predict-close for Predict rounds. MARKET orders are rejected by Predict.
  • fee-tier includes a predict block with the account's binary maker/taker rates.

Run orderly --help for the complete command reference.

JavaScript/TypeScript SDK (WASM)

The CLI's signing and request layer is also published as a WebAssembly package. It uses the same Rust code as the binary, but takes a signer instead of reading the OS keychain.

import { MemorySigner, OrderlyClient } from "@orderly.network/orderly";

const client = new OrderlyClient({
  network: "testnet",
  signer: new MemorySigner({ accountId, privateKey }),
});

const candles = await client.klines("PERP_BTC_USDC", "5m", 200);
const position = await client.positions("PERP");
await client.setLeverage("PERP_BTC_USDC", 3);
await client.placeOrder({
  symbol: "PERP_BTC_USDC",
  side: "BUY",
  orderType: "MARKET",
  quantity: 0.002,
});

The package is published from the repository root and built from sdk/ plus bindings/wasm. It runs in Node, Bun, browsers, and Cloudflare Workers. The signer interface keeps key material outside the WebAssembly module; MemorySigner is intended for testnet and local use. The native binary remains the keychain-backed path for interactive and long-lived local use.

Build and test it:

pnpm install
pnpm build
pnpm test

Output Format

By default, output is compact JSON (no whitespace) for AI/programmatic use:

orderly market-price PERP_ETH_USDC
# {"symbol":"PERP_ETH_USDC","index_price":2124.82,"mark_price":2124.89,...}

Use --csv for tabular data (more token-efficient for lists):

orderly symbols --csv
# symbol,index_price,mark_price,...
# PERP_ETH_USDC,2124.82,2124.89,...
# PERP_BTC_USDC,71551.7,71551.7,...

Security

  • Private keys are stored in the OS keychain:
    • macOS: Keychain
    • Windows: Credential Manager
    • Linux: Secret Service (libsecret / gnome-keyring)
  • Keys are never written to disk in plain text, printed in output, or accessible to agents.
  • Request signing (Ed25519, EIP-712, Solana) is byte-identical to the original TypeScript implementation.

Keychain compatibility

On Linux the crate talks to the Secret Service directly using the org.freedesktop.Secret.Generic schema with service/account attributes — the same items keytar used — so credentials created by the legacy TypeScript/npm CLI remain readable, and vice versa. On macOS/Windows the OS store is used via keyring.

On Linux, credentials are enumerated directly from the Secret Service, so auth-list, wallet-list and account auto-resolution return the same set. On macOS/Windows the keyring crate cannot enumerate, so an index at ~/.orderly-cli/keys-index.json is used as a fallback; secrets themselves only ever live in the keychain.

Compatibility

This is a behavioral replacement for the legacy TypeScript CLI (@orderly.network/cli ≤ 1.2.0): same commands, flags, output, config path (~/.orderly-cli/config.json), keychain entries and wire signatures.

Known divergences — all restricted to invalid input; valid usage is byte-identical:

| Case | TypeScript | Rust | | --- | --- | --- | | Non-numeric value for a numeric arg/flag (e.g. leverage SYM abc, --size abc) | parseFloat/parseInt → NaN, propagated (often silently omitted or sent as null) | rejected at parse time with a clear error | | Unexpected extra positional (orderly settle-pnl-history x) | ignored by cac | rejected | | --network bogus | crashes with a JS TypeError | clean error message | | --version | orderly/<v> <platform> node-<ver> | orderly <v> | | Network/DNS failure | Node's getaddrinfo ... text | reqwest's error text |

The top-level --help text, the Commands: list and the "missing required args" diagnostic reproduce the TypeScript CLI for the legacy command surface. Rust-only additions (schema, the predict-* commands and faucet-account) are listed in --help and stripped in the parity test.

Development

cargo build --release          # -> target/release/orderly (~5 MB)
cargo test                     # unit + offline parity fixtures
cargo clippy --all-targets     # must be warning-free
cargo fmt --check

Live tests (tests/api_live.rs, tests/ws_live.rs, tests/keychain_interop.rs) skip automatically when offline.

Cargo.toml uses a size-optimized profile (opt-level = "z", LTO, panic = "abort", strip).

Parity fixtures

parity/fixtures/ holds output recorded from the real TypeScript implementation before it was removed (JSON/CSV rendering, Ed25519, EIP-712, Solana signing, and the full --help text). The tests diff the Rust implementation against those recorded bytes offline, so behavior is pinned without a Node.js toolchain.

WASM SDK release

The npm package @orderly.network/orderly is the repository root. Its TypeScript wrapper lives in sdk/; the Rust binding crate lives in bindings/wasm.

pnpm install
pnpm build          # cargo + wasm-bindgen + tsc -> dist/, wasm/
pnpm test

dist/ and wasm/ are committed so the npm release job does not need a Rust toolchain. GitLab is canonical and uses the shared npm-release.yaml pipeline. npm version runs scripts/sync-cli-version.mjs, which updates Cargo.toml and Cargo.lock to the same version, so a vX.Y.Z tag matches both the npm package and the GitHub binary release.

WASM builds are path-dependent at the byte level (Rust embeds path-derived symbol metadata), so CI compares wasm/source-hash.txt and dist/ instead of diffing orderly_wasm_bg.wasm. Commit the regenerated hash and artifacts when SDK inputs change.

License

MIT