npm Tooling Packages

Swaputer publishes three focused packages under the @swaputer-labs scope. They are public, MIT-licensed, and do not include a wallet or a Base Mainnet release configuration.

Package	Current release	Runtime and module boundary	Purpose
@swaputer-labs/tinysol	0.4.0	Node.js >=22; ESM-only API and tinysol CLI	TinySol compiler, assembler, simulator, fee estimator, and offline CLI
@swaputer-labs/receipt-codec	0.1.2	Node.js >=20; ESM-only API	Strict, dependency-free VMReceiptV1 encoder and decoder
@swaputer-labs/cli	0.1.2	Node.js >=22; ESM-only API and Node.js CLIs; no browser export	Read-only verifier for Swaputer transactions and receipt payloads

Install the libraries

Pin exact versions in applications and release builds:

npm install @swaputer-labs/tinysol@0.4.0 \
  @swaputer-labs/receipt-codec@0.1.2

The compiler can be called directly from an ES module:

import { compileTinySol } from "@swaputer-labs/tinysol";

const result = compileTinySol(source, {
  sourceName: "Counter.tiny.sol"
});

console.log(result.codeHash);
console.log(result.packageBytes);
console.log(result.abi);

See TinySol for the language syntax and bounded ABI rules.

The receipt codec rejects an invalid or incomplete payload before returning any records:

import { decodeVMReceipt } from "@swaputer-labs/receipt-codec";

const receipt = decodeVMReceipt(payload);
console.log(receipt.worldExecution.executedBytes);

Use the Node.js CLIs

Run a pinned TinySol command without a global installation:

npx @swaputer-labs/tinysol@0.4.0 --help

Install the transaction verifier globally, or invoke the pinned package with npx:

npm install --global @swaputer-labs/cli@0.1.2
swaputer --help

npx @swaputer-labs/cli@0.1.2 --help

The verifier is intentionally read-only. It fetches a receipt from an RPC URL stored in a named environment variable, verifies the configured network, Kernel, World, outer Events envelope, and complete receipt, then emits text or JSON. It never loads a wallet, signs, or submits a transaction. Browser applications should use the receipt codec directly; the CLI has no browser entry point.

In CLI 0.1.2, swaputer --version reports 0.1.1. Use the npm package identity when checking the installed release.

Version and trust boundary

• Commit package-lock.json and use npm ci for reproducible application builds.
• Treat a compiler upgrade as an artifact change: rebuild and re-verify every package, ABI, source map, and code hash.
• Verify program identity and the active deployment manifest independently of the npm package name.
• Keep RPC credentials in environment variables or a secret manager.