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

@murmurations-ai/llm

v0.8.0

Published

Provider-agnostic LLM client for the Murmuration Harness — SecretValue auth, per-call cost hook, pluggable ProviderRegistry (ADR-0025).

Downloads

1,942

Readme

@murmurations-ai/llm

Typed LLM client for the Murmuration Harness. Four concurrent provider adapters behind a single LLMClient interface:

| Provider | Priority | API | | ------------- | -------- | ------------------------ | | Google Gemini | P0 | Generative AI v1beta | | Anthropic | P1 | Messages API v2023-06-01 | | OpenAI | P1 | Chat Completions v1 | | Ollama | P1 | Local HTTP /api/chat |

Designed by TypeScript / Runtime Agent #24. See docs/adr/0014-llm-client.md for the full rationale.

Why four adapters concurrently

The four-adapter mandate exists so the LLMClient interface cannot be Gemini-shaped (or any-other-shaped) by accident. Cross-validation is the test.

Key design choices

  • Native fetch in production. No vendor SDKs.
  • SecretValue authreveal() called exactly once per paid adapter (grep-checkable).
  • Per-call cost hook — daemon-long-lived client cooperates with per-wake WakeCostBuilder.
  • Errors-as-values for expected failures; AbortError re-throws.
  • Pricing stays out — the cost hook emits token counts only; the daemon resolves price via @murmurations-ai/llm/pricing (ADR-0015).
  • Streaming / tools / vision / JSON mode — all deferred to Phase 3+.

Usage

import { makeSecretKey } from "@murmurations-ai/core";
import { DotenvSecretsProvider } from "@murmurations-ai/secrets-dotenv";
import { createLLMClient } from "@murmurations-ai/llm";

const GEMINI_KEY = makeSecretKey("GEMINI_API_KEY");
const provider = new DotenvSecretsProvider({ envPath: ".env" });
await provider.load({ required: [GEMINI_KEY], optional: [] });

const llm = createLLMClient({
  provider: "gemini",
  token: provider.get(GEMINI_KEY),
  tier: "balanced",
});

const result = await llm.complete({
  model: "gemini-2.5-pro",
  messages: [{ role: "user", content: "Hello, world." }],
  maxOutputTokens: 200,
});
if (result.ok) {
  console.log(result.value.content);
}

Provider swap is a one-line config change:

const llm = createLLMClient({
  provider: "ollama", // swap to local, no auth, zero cost
  token: null,
  model: "llama3.2",
});