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

@p00f/core

v0.2.0

Published

Zero-knowledge engine for p00f: client-side AES-GCM + HKDF crypto, Link build/parse, and a ciphertext-only protocol client. Web Crypto only, so it runs in browsers, Node 20+, and Cloudflare Workers (workerd).

Readme

p00f-core

The zero-knowledge engine behind p00f: one small module that encrypts and decrypts entirely caller-side, builds and parses share Links, and talks to the p00f API as a ciphertext-only client. It is Web Crypto only, so the same code runs in browsers, Node 20+, and Cloudflare Workers (workerd). The web app and the CLI are thin shells over it.

Trust model

The Fragment Key lives only in the URL fragment (after #) and is never sent to the server. The server holds ciphertext and cannot read content or recover a lost link. Whoever holds the link can decrypt it.

Install

npm install @p00f/core

Use

import { create, read, info, burn } from "@p00f/core";

const base = "https://p00f.example"; // a p00f deployment
const te = new TextEncoder();

// Create a clip. The returned Link carries the key in its fragment.
const { link, ownerToken } = await create(fetch, base, {
  content: te.encode("hello agents"),
  meta: { kind: "text", mime: "text/plain", size: 12 },
  ttlMs: 5 * 60_000,
  revealBudget: 1,
});

// Non-consuming: decrypt only the metadata.
const meta = await info(fetch, link);

// Consuming: reveal and decrypt the content.
const result = await read(fetch, link);
if (result.ok) new TextDecoder().decode(result.content);

// Owner-gated early burn (the owner token never travels in the Link).
await burn(fetch, link, ownerToken);

Lower-level building blocks are also exported: generateMasterKey, generateClipId, encryptBlob, decryptBlob, buildLink, parseLink, and the ciphertext-only protocol client (createClip, getMeta, revealClip, deleteClip). Every network function takes an injected fetch, so the key never reaches anything that talks to the server.

Create-side policy helpers are also exported so thin shells (web, CLI, Raycast) agree on default kind inference and stay in sync: inferCreateKind, inferTextKind, inferFileKind, looksLikeCode, loneHttpUrl, safeHttpUrl, and guessMimeFromFilename. Shared limit constants and helpers are re-exported from ./limits (MAX_CLIP_BYTES, MIN_TTL_MS, MAX_TTL_MS, MAX_REVEAL_BUDGET, clampTtlMs, clampRevealBudget, formatBytes). PIN validation is re-exported from ./pin (isValidPin, PIN_MIN_LEN, PIN_MAX_LEN).

License

MIT