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

@cendor/core

v0.6.0

Published

Wrap your LLM client once and capture exact token counts and cost on every call — the shared foundation the other Cendor tools build on.

Readme

@cendor/core

npm version License: Apache 2.0

Wrap your LLM client once and capture exact token counts and cost on every call — the shared foundation the other Cendor tools build on. The TypeScript port of cendor.core: shared types, an event bus, decimal-safe Money, an offline price table, provider-aware token counting, and instrument(). Every other @cendor/* package cooperates through this.

npm i @cendor/core
# provider SDKs are optional peers — install the one(s) you use:
npm i openai @anthropic-ai/sdk

Using an AI coding assistant? npx @cendor/init (TS) / uvx cendor-init (Python) wires it up — or point it at cendor.ai/docs/for-ai-assistants.

Killer example — wrap once, get cost + tokens on every call

import OpenAI from 'openai';
import { instrument, bus, LLMCall } from '@cendor/core';

const client = instrument(new OpenAI());

bus.subscribe((e) => {
  if (e instanceof LLMCall) console.log(e.model, e.usage?.totalTokens, e.cost?.toString());
});

await client.chat.completions.create({
  model: 'gpt-4o',
  messages: [{ role: 'user', content: 'hello' }],
}); // → gpt-4o 152 0.000... USD

Streaming, the Responses API, Anthropic, interceptors (record/replay), and Reroute (model downgrade / message redaction) all flow through the same instrument().

Surface

| Symbol | Notes | |---|---| | instrument(client) | wraps OpenAI (Chat + Responses) / Anthropic clients; idempotent; async + streaming | | instrumentTool(fn) | emits a ToolCall per invocation | | Money, Usage, LLMCall, ToolCall | the cross-language event vocabulary (events/1) | | bus | subscribe / unsubscribe / emit | | prices | estimate / models / refresh / staleness — exact Decimal, never floats (prices/1) | | tokens | count / method / family / register via js-tiktoken | | trace(id, fn) / currentTraceId() | ambient correlation (async-callback scope; inject AsyncLocalStorage via installTraceContext) | | Reroute, addInterceptor, MISS | pre-call interception seam used by @cendor/cassette & @cendor/acttrace |

Parity & conformance

Field names map snake_case (Python) → camelCase (TS); type and error names are identical (UnknownModelError in both). Cost math, the model table, Money semantics, and token counts are verified against golden vectors generated from the Python reference — see fixtures/. Money is compared by exact decimal value.