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

cicash

v0.4.3

Published

CIcash - a budget you lend to an AI agent, not money you give it: bounded, revocable, auditable spending authority.

Readme

cicash

JavaScript implementation of CIcash — a budget you lend to an AI agent, not money you give it. Bounded, expiring, revocable, auditable, and worthless once stolen.

node:crypto only. No dependencies. Node >= 20.

npm install cicash
import { Ledger, ci, Denied } from "cicash";

const led   = new Ledger();
const acme  = led.registerPrincipal("acme");
const api   = led.registerMerchant("api.search");

const agent = acme.grant({
  budget: ci(50), perTx: ci(5),
  rate: { max_count: 20, window_s: 60 },
  payees: ["api.search"], purposes: ["research"],
});

agent.pay(api.quote(ci(2), "research"), "run1/step3");   // retry-safe: same key, one charge
const sub = agent.delegate({ budget: ci(5) });           // offline, tighter only
acme.revoke(agent);                                      // kills sub too
led.auditVerify();

A denial tells a planner what to do next rather than just refusing:

try { agent.pay(quote, "run1/step4"); }
catch (e) {
  if (e instanceof Denied) e.asObject();
  // { denied: 'RATE_LIMITED', action: 'RETRY_AFTER', retry_after: 12.4, hint: '…' }
}

RETRY_AFTER · REPLAN · ESCALATE. And Wallet has no setBudget, raiseLimit, or transferTo — the surface an agent can reach cannot express "give me more."

Interoperability

This implementation shares no code with the Python one. Both are held to spec/vectors.json, and CI runs a live handshake on every push: Python mints a wallet, this package verifies it, signs a payment against it, and delegates a tighter child entirely offline — then Python settles both and checks the ancestor debit crossed the language boundary.

npm test          # node --test test/*.test.mjs

The glob is not decoration: node --test <directory> changed meaning in Node 22 and resolves the directory as a module.

Not audited

The construction is standard — HMAC chain, Ed25519, SHA-256 — and two independent implementations agree on the vectors, but no third party has reviewed it, and nothing here settles real value. Treat it as a working reference implementation of a design, not as somewhere to put real money today.

Apache-2.0.