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

@bursora/sdk

v0.2.0

Published

Bursora SDK: wrap your AI provider client to enforce per-customer and per-agent budgets, no proxy.

Readme

@bursora/sdk

npm bundle size types license

Catch the runaway AI bill before it happens. One line around your provider client.

AI calls bill by token. A stuck loop, a runaway agent, or one abusive customer can burn hundreds of dollars before anyone looks at a graph. Most tools show you the damage after it lands. Bursora checks the budget before the call goes out and blocks it if it would blow a limit. Traffic light, not speed camera.

This package is the wrap. No proxy, no gateway; your app still talks straight to OpenAI, Anthropic, or Google. Bursora just gets a yes/no first, then the real token cost after.

Install

npm i @bursora/sdk

Bring your own provider client (openai, @anthropic-ai/sdk, @google/genai, ...). The SDK detects them by shape, so it never bundles them.

30 seconds

import OpenAI from "openai";
import { BudgetExceededError, withTags, wrap } from "@bursora/sdk";

const openai = wrap(new OpenAI(), {
    apiKey: process.env.BURSORA_API_KEY!,
    endpoint: process.env.BURSORA_ENDPOINT!,
});

await withTags({ tenant_id: "acme", agent_id: "support-bot" }, async () => {
    try {
        await openai.chat.completions.create({
            model: "gpt-4o-mini",
            messages: [{ role: "user", content: "hi" }],
        });
    } catch (e) {
        if (e instanceof BudgetExceededError) {
            // over budget: downgrade the model, queue it, show a fallback
        } else throw e;
    }
});

Tag each call with who it's for (customer, agent, workflow). That's how spend gets grouped in the dashboard and how budgets know what to scope to.

What you get

  • Block before spend. Over a hard limit? BudgetExceededError throws before the provider is ever called. No charge.
  • Soft limits. Notify and throttle modes let the call through and report after.
  • Fail open. Can't reach Bursora? Your call still goes out. We don't become your outage.
  • Streaming-safe. Chunks pass through untouched; usage is read off the final one.
  • Decisions cache for 60 seconds; usage flushes after each call.

More providers

OpenAI, Anthropic, and Google Gemini all wrap exactly like the example above; detection is by client shape. Bedrock has its own wrapBedrock. And on the Vercel AI SDK (ai) you use bursoraMiddleware with wrapLanguageModel instead of wrap, since generateText never constructs a client for wrap to see.

Pick yours and copy the snippet:

Tags, batch metering, sharing one core across clients, budget snapshots, error handling: it's all in the docs. Start at bursora.com/docs/sdk/install.

API key

Sign in at bursora.com, create a workspace, grab your BURSORA_API_KEY.

License

MIT. © 2026 Vildan Bina.