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

@spendgraph/tools

v0.15.0

Published

Declare a tool once, offer the right few, and record what was called.

Downloads

1,254

Readme

@spendgraph/tools

Declare a tool once, offer the right few, and record what was called.

npm install @spendgraph/tools
import { calculate, tool, toolbus } from "@spendgraph/tools";

const lookup = tool({
  name: "lookup_contract",
  description: "Finds a contract clause by its reference, such as MSA 2.4.",
  args: [{ name: "ref", type: "string", required: true }] as const,
  run: ({ ref }) => search(ref),
});

const bus = toolbus([lookup, calculate()], { limit: 6 });
const turn = bus.trace(question);

What you get

  • A description and a handler in one object, so a rename is a compile error rather than an undefined mid-loop.
  • A shortlist, not a catalogue. Fifty tools is 7.5k tokens before the user has said anything, and more tools makes a model worse at picking.
  • Effects, so a gate can refuse what it must not retry — and name the tools nobody labelled.
  • Twenty-two builtins and twelve mocks, none registered for you. Four of them are one memory set, with an in-process store for testing it offline.

Docs

| | | | --- | --- | | Overview | A tool, a bus, and a turn | | Declaring a tool | Args, as const, and what is checked at import | | A stored tool | Wording in the dashboard, handler in code | | Effects | What running one does to the world outside | | The bus | Holds, picks, converts, runs — and nests | | Selecting | The shortlist, and why it is a shortlist | | A turn | Offered, called, and what the rollout keeps | | Builtins | Sixteen factories, none registered for you | | Bogus tools | Twelve mocks for testing the pipeline, not the provider |

License

Apache-2.0