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

@jswob/llm-evals

v0.1.2

Published

Measure LLM prompts, flows and model settings against reviewed answer keys, on promptfoo

Readme

@jswob/llm-evals

Measures an app's LLM prompts, multi-step flows and model settings against answer keys a person reviewed. promptfoo runs the cases and is the results screen; the harness picks the columns, guards the spending and decides whether a run can be trusted.

bun add -d @jswob/llm-evals

Requires Bun. It ships TypeScript source. promptfoo is run through a pinned npx, not installed. Models are reached through OpenRouter: OPENROUTER_API_KEY in the environment.

Plug in

An evals folder (say apps/evals) with evals.config.ts:

import { defineConfig } from '@jswob/llm-evals';

export default defineConfig({
	title: 'my-app evals', // sent to OpenRouter as X-Title
	tasks: {}, // each task: tasks/<name>/task.ts, listed here
});

and a script that runs the bin there with the environment loaded:

"evals": "bun --env-file=../../.env llm-evals"

A task imports only @jswob/llm-evals and, in its tests, @jswob/llm-evals/testing.

Commands

| Command | What it does | | ------------------------------------------------- | ---------------------------------------------------------- | | doctor <task> | Key, credit, one real call per model setting | | try <task> … | Variants on cases typed by hand | | run <task> … | Without --max-cost, says what the run can cost and stops | | run <task> … --max-cost 0.5 | Variants on the answer key, then the verdict | | report [run] | The verdict on a finished run, again | | view | promptfoo's viewer | | key <queue\|dispute\|draft\|page\|apply> <task> | The answer key's review queue | | selftest | The whole harness against a fake model, with no network |

Answers are cached, so an unchanged run costs nothing (--max-cost 0). A run stops at its spending limit, and a run with too many technical failures reports no numbers.

Claude Code

The package ships the llm-evals skill, the manual for all of the above. @jswob/toolkit copies it into .claude/skills/ (bunx toolkit sync).

License

MIT