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

@wisp_/js

v0.2.1

Published

Wisp cryptographic primitives — Poseidon2, Merkle trees, nullifiers, witness builder

Readme

@wisp_/js

Wisp cryptographic primitives — Poseidon2, Merkle trees, nullifiers, and Circom witness builder.

Beta / demo release only. Intended for evaluation and testnet integrations; interfaces may change.

Low-level building block; most apps should use @wisp_/sdk for the full prove/settle flow.

Install

npm install @wisp_/[email protected]

Quick start

import {
  buildWitnessInput,
  proofPackageToWitnessInput,
  computeNullifier,
  merkleRootForLeafAtIndex,
} from "@wisp_/js";

// From a demo fixture or issuer proof package
const witness = proofPackageToWitnessInput(proofPackage);

// Or build from params directly
const input = buildWitnessInput(demoParams);

// Standalone primitives
const nullifier = computeNullifier({ /* … */ });
const root = merkleRootForLeafAtIndex(leaves, index);

Subpath exports

import { buildWitnessInput } from "@wisp_/js/witness";
import { decodeStrkey } from "@wisp_/js/strkey";

Modules

| Module | Exports | | ------ | ------- | | field | BN254 scalar field ops | | poseidon2 | Poseidon2 t=4 hash | | merkle | Merkle root, paths, SMT sanctions | | protocol | Nullifier, corridor config hash, address limbs | | witness | buildWitnessInput, proofPackageToWitnessInput | | publicInputs | 17-field public input helpers | | strkey | Stellar address decode |

Public inputs

17 fields in canonical order — see bindings/public-inputs.json.

Address limbs: hi = bytes[0..16], lo = bytes[16..32] as big-endian field elements.

Test vectors

pnpm --filter @wisp_/js test     # witness + publicInputs unit tests
pnpm test:witness                  # from repo root

Fixtures: bindings/fixtures/.

Build from source

pnpm --filter @wisp_/js build

Related