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

@yearbook2026/client

v0.1.0

Published

x402 paint client for YEARBOOK 2026 — budget caps, chunking, protocol error handling

Readme

@yearbook2026/client

The x402 paint client for YEARBOOK 2026: budget caps, per-tile chunking, and explicit handling of every protocol error path in 03-PROTOCOL §6. Reading is free; writing quotes, pays, and settles over x402 in USDC on Base.

import { YearbookClient } from '@yearbook2026/client';
import { viemSigner } from '@yearbook2026/yearbook-mcp/signer'; // or implement Signer yourself

const client = new YearbookClient({
  baseUrl: process.env.YEARBOOK_API_BASE!,
  budget: { maxTotalUnits: 5_000_000 },        // $5.00 hard cap — mandatory to spend
  signer: viemSigner(process.env.YEARBOOK_WALLET_KEY!),
});

const grid = await client.getRegion(0, 0, 100, 100);        // free, no signer needed
const { repair, costUnits } = await client.diffJob(job);    // what would fixing this cost?
const outcome = await client.paintPixels(repair, { handle: 'me' });
console.log(outcome.painted.length, outcome.spentUnits);

The parts that keep an agent solvent:

  • The budget is client-side and non-negotiable. BudgetExceededError stops the session; an optional perPixelCeilingUnits concedes individual pixels a war has made expensive instead of feeding them the whole budget.
  • You are only charged for pixels you actually got. A payment that loses the race is never settled — all-or-nothing per request, priced per pixel.
  • Losing a race looks like IMMUNE, not CAS_STALE. The winner's placement made the pixel immune; the client sleeps until immune_until and re-quotes (the price has doubled — the per-pixel ceiling is checked again before paying).
  • The Signer is injected and only ever signs an EIP-3009 transfer authorization for the exact amount the server quoted. Bring viemSigner or your own.

Part of yearbook-kit — contract docs live there (docs/03-PROTOCOL.md is normative). MIT.