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

@ledgelm/reporter

v0.4.0

Published

A thin reporter for sending eval results to LedgeLM

Readme

@ledgelm/reporter

The TypeScript reporter buffers eval results and sends them to LedgeLM. It does not run evals or calculate baselines.

import { flush, report } from '@ledgelm/reporter';

report({
	name: 'response_grounding',
	type: 'judge',
	score: 0.82,
	passed: true,
	usage: {
		target: { input_tokens: 812, output_tokens: 146 },
		judge: { input_tokens: 1042, output_tokens: 87 }
	},
	input: { messages: [{ role: 'user', content: 'Can I return this purchase?' }] },
	output: 'Yes. Refunds are available within 30 days with a receipt.',
	expected_output: 'Explain the 30-day refund policy and receipt requirement.',
	provenance: {
		target_id: 'support-claude-sonnet',
		target: { provider: 'anthropic', model: 'claude-sonnet' },
		dataset: { name: 'support-golden', version: '2026-07' }
	}
});

const verdict = await flush();

Set LEDGELM_API_URL and LEDGELM_API_TOKEN in GitHub Actions. To target a local or alternate deployment explicitly, pass flush({ api_url: 'https://your-tunnel.example' }); the explicit option takes precedence over the environment variable.

Upload failures warn and return an unknown verdict, so LedgeLM availability does not fail the eval job.

For a GitHub Actions matrix, do not flush in each shard. Export a typed artifact and let the LedgeLM fan-in action flush the complete matrix:

import { reportArtifactSchema, type ReportInput } from '@ledgelm/reporter';

const results: ReportInput[] = await runSuite();
const artifact = reportArtifactSchema.parse({
	schema_version: 1,
	shard: process.env.LEDGELM_SHARD!,
	results
});
await Bun.write('ledgelm-results.json', JSON.stringify(artifact));

The action validates this exact schema before it buffers or uploads any result.