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

@benchlocal/sdk

v0.2.0

Published

BenchLocal SDK for authoring Bench Packs on top of the BenchLocal runtime contract.

Readme

@benchlocal/sdk

SDK for authoring Bench Packs that run inside BenchLocal.

This package sits on top of @benchlocal/core and provides the thin authoring layer used by official Bench Packs:

  • typed manifest loading
  • Bench Pack runtime definition helpers
  • host-context lookup helpers
  • result helpers for scoring

Install

npm install @benchlocal/sdk

Typical usage

Keep your benchmark logic in your own repo code, and use the SDK only inside benchlocal/index.ts.

import {
  createHostHelpers,
  defineBenchPack,
  loadBenchPackManifest,
  requireScoredResults
} from "@benchlocal/sdk";

const manifest = loadBenchPackManifest(__dirname);

export { manifest };

export default defineBenchPack({
  manifest,
  async listScenarios() {
    return [];
  },
  async prepare(context) {
    const helpers = createHostHelpers(context);

    return {
      async runScenario(input) {
        const provider = helpers.getRequiredProvider(input.model.provider, { enabledOnly: true });
        const inference = helpers.getInferenceEndpoint(input.model.id);

        return {
          scenarioId: input.scenario.id,
          status: "pass",
          summary: inference?.status === "running" ? inference.baseUrl : provider.baseUrl
        };
      },
      async dispose() {}
    };
  },
  scoreModelResults(results) {
    const scored = requireScoredResults(results);

    return {
      totalScore: scored.reduce((sum, result) => sum + result.score, 0),
      categories: []
    };
  }
});

Main helpers

  • loadBenchPackManifest(__dirname)
  • defineBenchPack(...)
  • defineBenchPackManifest(...)
  • createHostHelpers(context)
  • requireScoredResults(results)

Useful host lookups:

  • getRequiredProvider(providerId, { enabledOnly: true })
  • getRequiredInferenceEndpoint(modelId)
  • getRequiredVerifier(verifierId)

When a pack uses a Docker verifier, the returned inference endpoint may also include dockerBaseUrl. Forward dockerBaseUrl ?? baseUrl to the verifier-side runtime.

@benchlocal/sdk also re-exports the main public types from @benchlocal/core.

Authoring model

  • keep canonical Bench Pack metadata in benchlocal.pack.json
  • load and export that metadata from benchlocal/index.ts
  • keep benchmark logic in your own repo modules such as lib/
  • use the SDK only for the BenchLocal adapter layer

Repository

  • BenchLocal monorepo: https://github.com/stevibe/BenchLocal
  • Issues: https://github.com/stevibe/BenchLocal/issues