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

@zanii/gateway

v0.1.0

Published

Drop-in proxy that receipts every HTTP API call an agent makes - zero code changes. Edge-compatible (fetch handler) plus a Node server and CLI.

Readme

@zanii/gateway

A transparent HTTP proxy that records a signed Zanii receipt for every API call an agent makes — no changes to the agent's code. Point its HTTP client at the gateway; the gateway forwards to the real upstream and receipts each call as http.<method>.<path>.

npm install @zanii/gateway @zanii/sdk

As a fetch handler (edge / serverless)

import { createZaniiHandler } from '@zanii/gateway';
import { ZaniiAgent } from '@zanii/sdk';

const agent = new ZaniiAgent({ /* did, key, delegation … */ });
const handler = createZaniiHandler({ upstream: 'https://api.stripe.com', agent });

// Cloudflare Workers / Vercel edge:
export default { fetch: handler };

Each forwarded request is recorded before the response is returned. Works in any fetch-based runtime (Node 18+, Workers, Vercel edge).

As a CLI

zanii-gateway --upstream https://api.stripe.com --port 4800 --identity identity.json
# now point the agent at http://localhost:4800 instead of api.stripe.com

identity.json is { "agent": { "did": "…", "privateKey": "<hex>" }, "delegation": [ … ] }. Server URL comes from ZANII_SERVER (default https://ledger.zanii.agency), API key from ZANII_API_KEY.

Changelog

  • 0.1.0 — initial release: createZaniiHandler (fetch), createZaniiGateway (Node), zanii-gateway CLI.

License

Apache-2.0.