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

@ktlsr/assay-core

v0.1.3

Published

Assertion engine, three-valued verdicts, Wilson-interval scoring and canonical run records for Assay — a CI test runner for Agent Skills. Pure TypeScript, no I/O.

Readme

@ktlsr/assay-core

The measurement layer of Assay, a CI test runner for Agent Skills.

This package is pure TypeScript: no file system, no network, no child processes. It takes evidence that somebody else collected and turns it into a verdict. That constraint is enforced by a lint rule and a test, not by good intentions — it is what lets the same assertion produce the same verdict in Node, in a browser, and in a hosted service re-scoring an old run.

npm install @ktlsr/assay-core

What it does

Parses and validates case sets. parseSuite reads the YAML suite format and returns typed issues instead of throwing. A trigger suite without a negative case is rejected at the schema level.

Evaluates assertions. evaluateAssertion / evaluateAssertions cover file existence, structure and JSON Schema validation, text and regex matching, tool call traces, side effects and numeric thresholds. Deterministic only — there is no LLM judge in the scoring path.

Produces three-valued verdicts. pass, fail, unknown. Each assertion type declares which evidence fields it needs; the dispatch layer refuses to call an evaluator whose evidence is missing and returns unknown instead. A quiet pass on unmeasured data is structurally impossible, not merely discouraged.

Scores runs. proportion returns a Proportion, never a bare number:

import { proportion, formatProportion } from '@ktlsr/assay-core'

const p = proportion(14, 20)
// { successes: 14, n: 20, rate: 0.7,
//   ci: { low: 0.481027181646, high: 0.854522755132, level: 0.95 } }

formatProportion(p) // '70% (N=20, 95% CI 48%–85%)'

The interval is Wilson, not Wald: at 10/10 Wald claims 100%–100% and hides all uncertainty, where Wilson reports 100% (N=10, 95% CI 72%–100%). With n === 0 both rate and ci are null, because at N=0 there is no rate to show.

Compares runs. compareRuns refuses to compare two runs unless four pins match — skill version and content hash, model id, system prompt hash, and case set version and content hash. If one drifted it names which, and the result is unknown. A score that fell because the model changed is not a regression.

Reading evidence

core never gathers evidence itself. A runner collects an Evidence object — captured files, tool trace, exit code, environment diff — and hands it over. The same Evidence always yields the same verdict, which is what makes a measurement reproducible and re-scorable later.

License

Apache-2.0. See LICENSE and NOTICE.