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

@zanii/langchain

v0.1.2

Published

Receipt every tool call in a LangChain or LangGraph run with one callback handler - no changes to your tools. Signed, verifiable Zanii proofs across the whole chain.

Readme

@zanii/langchain

Receipt every tool call in a LangChain or LangGraph run with one callback handler — no changes to your tools. Every tool start/end/error across the whole chain (or graph — LangGraph reuses the same callback bus) becomes a signed, verifiable Zanii receipt.

npm install @zanii/langchain @zanii/sdk @langchain/core

Usage

import { ZaniiCallbackHandler, withZaniiConfig } from '@zanii/langchain';
import { ZaniiAgent } from '@zanii/sdk';

const agent = new ZaniiAgent({ /* … */ });
const zanii = new ZaniiCallbackHandler({ agent });

// attach once — every tool call in the run is now receipted:
await chain.invoke(input, { callbacks: [zanii] });

// LangGraph (same handler works):
await graph.invoke(input, withZaniiConfig(config, agent));

Each receipt targets tools.<toolName> (override with { prefix }) and carries the tool's input and output — or the error, on failure. Concurrent tool calls are correlated independently by run_id, so a fan-out node produces one clean receipt per tool.

The handler is duck-typed against LangChain's callback interface, so it adds no LangChain dependency of its own — @langchain/core is an optional peer you already have.

Changelog

  • 0.1.2: A failed receipt upload no longer affects the tool or graph outcome; handlers log a sanitized warning instead of the error message.
  • 0.1.1 — ZaniiGraphHandler: graph node transitions chained by state hash, retrieved documents and model usage, optional run ids for cross-linking; recordCheckpoint / verifyResume, recordInterrupt, a policyGate node and recordMemoryWrite. Still zero dependencies.
  • 0.1.0 — initial release: ZaniiCallbackHandler, zaniiCallbacks, withZaniiConfig.

License

Apache-2.0.