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

@aidex/evaluation

v1.2.0

Published

Aidex Evaluation Framework — benchmark engines for output quality, token usage, cost, latency, and success rate, and compare providers.

Readme

@aidex/evaluation

Installation

pnpm add @aidex/evaluation
npm install @aidex/evaluation

Benchmarks engines (or anything expressible as () => Promise<TResult>): output quality, token usage, cost, latency, and success rate — and allows comparing providers by running several named cases side by side.

Contents

  • types/BenchmarkCase{ name, execute(): Promise<TResult>, scoreOutput?(result), estimateTokens?(result) }. execute() is deliberately generic — the Evaluator never imports @aidex/engines, @aidex/providers, or @aidex/strategies. A caller's closure is whatever it needs to be (an Engine.execute(context) call, an AI.text() call, a raw Provider.generate() call).
  • evaluator/Evaluatorrun(case, options?) executes a case options.runs times (default 1), catching failures rather than throwing out of run(), and returns a BenchmarkSummary. compare(cases, options?) runs several cases with the same options and returns one summary per case — this is how you compare providers: define one BenchmarkCase per provider/engine/strategy variant, each wrapping a call through that variant.
  • Tracked per run: durationMs (via an injectable clock — options.now, defaulting to Date.now, for deterministic tests), qualityScore (via the case's own scoreOutput() — there is no automatic quality judge), inputTokens/outputTokens and cost (via the case's estimateTokens() plus options.pricing, reusing @aidex/observability's estimateCost() rather than duplicating its math), and success/error.
  • Aggregated per case (BenchmarkSummary): successRate (fraction of runs that didn't throw), averageDurationMs, averageQualityScore, averageCost — each undefined if no run produced that value (e.g. no scoreOutput() supplied, or every run failed).

Dependency direction

@aidex/evaluation depends on @aidex/observability only (estimateCost, CostEstimate, reused rather than reimplemented). No dependency on @aidex/core, @aidex/providers, @aidex/engines, @aidex/strategies, or any application code — a BenchmarkCase's execute() closure is where any of those would actually be used, entirely outside this package.