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

@windstack/antelope

v2.3.4

Published

Antelope transaction, TAPOS, signing, keosd, contract, account, and verified RPC toolkit.

Readme

@windstack/antelope

Overview

@windstack/antelope provides chain-neutral Antelope transaction primitives, including verified RPC access, ABI-aware contract and account clients, TAPOS preparation, canonical transaction serialization, transaction digests and IDs, required-key resolution, pluggable signers, keosd support, and broadcasting.

A client can be bound to an expected chain ID. When configured, signing is rejected if the RPC endpoint reports a different chain.

Installation

npm install @windstack/antelope

Usage

Chain-bound client

import {
  AntelopeClient,
  PrivateKey,
  PrivateKeySigner,
} from "@windstack/antelope";

const client = new AntelopeClient({
  endpoints: ["https://node.example"],
  chainId: "00".repeat(32),
  contracts: {
    system: "system.cntr",
    token: "token.cntr",
  },
});

const signer = new PrivateKeySigner([
  PrivateKey.fromString("PVT_K1_..."),
]);

const transfer = await client
  .account("alice")
  .transfer("bob", "1.0000 TKN", "Example transfer");

const result = await client.transact({
  actions: [transfer],
  signer,
});

console.log(result.response);

Custom signer

Wallets, hardware signers, secure-storage integrations, and remote signers can implement the exported Signer interface.

A signer receives the chain ID, structured transaction, serialized transaction bytes, signing digest, and required public keys.

import type { Signer } from "@windstack/antelope";

const signer: Signer = {
  async getAvailableKeys() {
    return ["PUB_K1_..."];
  },
  async sign(request) {
    return secureSigner.sign(request.digest, request.requiredKeys);
  },
};

PrivateKeySigner is intended for environments where application-managed private keys are appropriate. For portable chain-neutral key representation, prefer modern PUB_K1_... public-key strings; legacy display prefixes can be configured when required by a chain or integration.

keosd

HTTP and Unix-socket keosd transports are available for Node.js environments. Unix-socket support is exported separately from the browser entrypoint:

import { KeosdSigner } from "@windstack/antelope";
import { KeosdUnixTransport } from "@windstack/antelope/node";

const signer = new KeosdSigner({
  walletName: "default",
  transport: new KeosdUnixTransport({ socketPath: "/run/keosd.sock" }),
});

Security

When a chain ID is configured, it is checked before signing. Signatures returned by a signer are parsed, recovered, and matched against the keys requested by the node before broadcast.

Use broadcast: false when signed transaction data is required without submitting it to the network.

Runtime

The package is ESM-first and requires Node.js 20.19 or newer when used directly in Node.js. Transaction construction uses Web-standard byte APIs and does not require Node.js Buffer.

Read operations can use multiple RPC endpoints. Transaction broadcast is not automatically retried when submission status is uncertain.

License

MIT License.

Created by Gilang Ramadan. Copyright © 2026 PT WIND KRIPTOGRAFI TEKNOLOGI.