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

@openzaps/sdk

v0.1.0

Published

Read-only policy compiler and simulation client for OpenZaps

Readme

@openzaps/sdk

Pure OpenZap policy compilation plus a read-only client for the block-pinned simulation API.

Use the import below only for a release that is visible and provenance-verified on npm. Before the first release, validate the package directly from the repository checkout.

import { OpenZapsClient } from "@openzaps/sdk";

const openzaps = new OpenZapsClient();
const artifact = await openzaps.simulatePolicy({
  routeId: "robinhood-v4-weth-zaps",
  owner: "0xYourAddress",
  amount: "0.01",
  slippageBps: 150
});

The response contains the exact ABI-encoded policy hash, live allowlist reads, adapter runtime code hashes, an exact quote pinned to one block, an unsigned EIP-712 draft, and an eth_call result. It never signs or broadcasts.

The production simulation API is independently gated by OPENZAPS_EXACT_POLICY_API_ENABLED=true and OPENZAPS_EXACT_POLICY_DURABLE_QUOTA_ENABLED=true. Package publication does not enable that route. The discovery API is public chain data; this SDK has no credential surface and cannot authorize execution. Execution requires the capsule owner's EIP-712 signature.

v1.2 candidate Permit2 owner pull

buildUnsignedPermit2OwnerPull prepares the second wallet signature for the source-only v1.2 candidate. It binds the existing OpenZap intent digest as a Permit2 witness, the capsule as spender, and the frozen policy's exact first-step token and amount. It rejects a mismatched policy, a different output/funding asset, a deadline beyond the intent, or a window longer than one hour. The helper remains pure: it does not request either signature, approve Permit2, or submit a transaction.

This path is not present in the live v1.1 implementation. Do not expose it in an app until a v1.2 factory and implementation have been independently deployed, verified, and pinned.