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

@noburn/sdk

v0.1.0

Published

Hard LLM spend enforcement for Node.js — pre-call budget checks and per-user metering.

Readme

@noburn/sdk

Hard LLM spend enforcement for Node.js — pre-call budget checks and per-user metering.

Check a planned LLM call against project-, per-user-, and per-run budget caps before you make it, then record what it actually cost.

Install

npm install @noburn/sdk

Requires Node.js ≥ 18 (uses the global fetch).

Quick start

import { NoburnGuard } from '@noburn/sdk';

const guard = new NoburnGuard({
  apiKey: process.env.NOBURN_API_KEY!,
  projectId: process.env.NOBURN_PROJECT_ID!,
  budgetCapUsd: 10,          // optional local fallback cap
  onError: 'allow',          // 'allow' (default, fail-open) | 'block' (fail-closed)
});

const decision = await guard.check({
  model: 'gpt-4o',
  estimatedTokensIn: 1000,
  estimatedTokensOut: 300,
  endUserId: 'user_123',     // optional — enforces that user's cap
});

if (decision.blocked) {
  throw new Error(`Blocked by noburn: ${decision.blockReason}`);
}

// ... make your LLM call ...

await guard.record({
  model: 'gpt-4o',
  tokensIn: 980,
  tokensOut: 290,
  costUsd: 0.005,
  wasBlocked: false,
  endUserId: 'user_123',
});

record() is fire-and-forget — it returns immediately and never throws, so it adds no latency to your call path.

Agent runs

Bound a single agent invocation with its own cap:

const run = await guard.startRun({ budgetCapUsd: 0.5 });

const decision = await guard.check({
  model: 'gpt-4o',
  estimatedTokensIn: 1000,
  estimatedTokensOut: 300,
  runId: run.runId,
});

await guard.record({ /* ... */, runId: run.runId });

const summary = await guard.endRun(run.runId); // { status, spendUsd, ... }

Behavior

  • check() never throws except NoburnAuthError (bad key). Every call asks the server for an authoritative decision; if the server is unreachable it falls back to a local in-memory check.
  • onError controls that fallback when nothing local blocks the call: 'allow' (default) fails open so a noburn outage never breaks your app; 'block' fails closed (blockReason: 'noburn_unreachable').
  • startRun() throws on network/auth error (NoburnTimeoutError on timeout) — a run must be registered before you proceed.

License

MIT