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

controller-benchmark-data

v0.1.5

Published

Versioned benchmark bundle and lightweight readers for the controller phase-stratified benchmark.

Readme

controller-benchmark-data

Published by SproutSeeds. Research stewardship: Fractal Research Group (frg.earth).

Versioned benchmark bundle and lightweight readers for the controller phase-stratified benchmark.

Install

npm install controller-benchmark-data

For local development inside this repo:

cd packages/controller-benchmark-data
npm test
npm pack --dry-run

What This Is

controller-benchmark-data packages the current live public benchmark bundle as versioned data with small Node readers.

It currently ships:

  • the accession-pinned study corpus
  • the negative-family registry
  • the live compiled condition records
  • the compiler coverage and trust receipt
  • the benchmark shell receipt
  • the contradiction ledger and contradiction-kernel receipt
  • the passive recommendation scaffold and receipt
  • the CX-004 validation handoff and receipt
  • the baseline and controller output tables
  • the study-specific compiler rule packs that produced the live bundle

The point is not to turn one research thread into npm theater.

The point is:

  • preserve one exact benchmark bundle
  • make it easy to inspect from Node tooling
  • keep the bundle versioned and attributable
  • let downstream tools use the same artifact set without re-deriving it from prose memory

What This Is Not

controller-benchmark-data is not:

  • the controller compiler
  • the benchmark runner
  • a generic ETL framework
  • a matrix extraction toolkit
  • a claim that the bundle is final or universally authoritative

It is a versioned benchmark bundle with lightweight readers.

Package Positioning

The clean split is:

  • controller-benchmark-schemas
    • stable contracts and validators
  • controller-benchmark-data
    • one current benchmark bundle and thin readers

That means the schema package can travel widely, while this package can carry one exact benchmark state honestly.

Quick Start

import {
  BUNDLE_ID,
  BUNDLE_MANIFEST,
  listCompilerRules,
  readBenchmarkShellReceipt,
  readConditionRecords,
  readCx004ValidationHandoffReceipt,
  readStudyCorpusRows,
} from "controller-benchmark-data";

console.log(BUNDLE_ID);
console.log(BUNDLE_MANIFEST.condition_count);
console.log(listCompilerRules());
console.log(readStudyCorpusRows().length);
console.log(readConditionRecords().length);
console.log(readCx004ValidationHandoffReceipt().handoff_verdict);
console.log(readBenchmarkShellReceipt().summary.controller_output_counts);

API Surface

  • BUNDLE_ID
  • BUNDLE_MANIFEST
  • listArtifacts()
  • listCompilerRules()
  • getArtifactPath(name)
  • getArtifactUrl(name)
  • readArtifactRaw(name)
  • readStudyCorpusRaw()
  • readStudyCorpusRows()
  • readNegativeFamilyRegistry()
  • readConditionFixture()
  • readConditionRecords()
  • readCompileReceipt()
  • readCoverageTrustReceipt()
  • readAgeOnlyBaselineOutputRaw()
  • readAgeOnlyBaselineOutputRows()
  • readControllerOutputRaw()
  • readControllerOutputRows()
  • readBenchmarkShellReceipt()
  • readContradictionLedger()
  • readContradictionKernelReceipt()
  • readCx004ValidationHandoff()
  • readCx004ValidationHandoffReceipt()
  • readPassiveRecommendationScaffold()
  • readPassiveRecommendationReceipt()
  • readCompilerRule(name)
  • loadLatestBundle()

Current Boundary

This package distributes a public-neutral benchmark bundle derived from the controller canon.

The public package should not leak reviewer-specific naming, private packet context, or relationship-layer labels into the release surface.