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

@mcpjam/evaluators

v0.3.0

Published

Pure evaluator contracts, assertions and trajectory matching

Readme

@mcpjam/evaluators

Pure assertions, trajectory matchers, evaluator contracts and bounded execution. The package does not depend on the SDK, MCP clients or model providers. Model judges can implement Evaluator with an injected runner; the SDK's built-in model judge remains available from @mcpjam/sdk.

import { assertion, runEvaluatorsProjected } from '@mcpjam/evaluators';

const results = await runEvaluatorsProjected(
  [assertion({ type: 'responseContains', needle: 'refund' })],
  {
    version: 1,
    scenario: { title: 'Explain the refund policy' },
    trace: { messages: [] },
    transcript: { toolCalls: [], finalAssistantMessage: 'Your refund is approved.' },
  },
);

runEvaluators preserves legacy ScoreResult[]. runEvaluatorsProjected returns canonical EvaluatorResult[]. Errors, skips and inapplicable outcomes carry no score. toFeedbackEvaluator and toNamedEvaluator adapt one canonical result to destination-shaped feedback, representing unscored outcomes as null with status metadata.

For generic messages use normalizeMessages and runMessageEvaluators. The normalizer recognizes text, tool-call/tool-result parts, tool_use/tool_result parts, and function tool calls. Unsupported input returns diagnostics without a transcript. A message array alone does not prove complete tool capture: provide capture only when your producer establishes it. runMessageEvaluators refuses tool-dependent evaluation from incomplete capture. Do not bypass that guard by passing a partially captured transcript directly to a negative assertion.

The normalization defaults are 1,000 messages and 4 MiB of serialized input. Oversized or malformed evidence is refused, not truncated into a pass. Provider output and MCP isError evidence remain separate from successful tool execution.

Existing SDK imports remain compatibility exports of this implementation. Do not rely on object identity or instanceof across separately installed package copies. internal/* exports support SDK compatibility; use the root, assertions, or matchers entry for new consumers.

Run npm run test:packaging:all -w @mcpjam/evaluators to pack and install independent npm and pnpm consumers, execute assertions/matchers/adapters, verify declarations and prove SDK/provider packages are absent.