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

@metaharness/workspace-probe

v0.1.1

Published

Evaluation + Darwin-Mode bridge for @metaharness/workspace-lens: turn Jacobian-Lens interpretability receipts into a flywheel-consumable workspace_probe score, and reject structurally-brittle prompt/policy mutations (final answer up, workspace grip down).

Readme

@metaharness/workspace-probe

Evaluation + Darwin-Mode bridge for @metaharness/workspace-lens. Turn Jacobian-Lens interpretability receipts into (1) a flywheel-consumable workspace_probe score and (2) Darwin-Mode mutation evidence that rejects structurally-brittle prompt/policy mutations.

Pure · dependency-light (only the workspace-lens types) · deterministic · $0.

Why

@metaharness/workspace-lens reads the model's internal verbalizable workspace into a WorkspaceLensReceipt per decision. This package projects a set of those receipts into evaluation signal:

  • workspaceProbeScore(receipts){ score, meanDrift, flagRate, criticalRate, cleanFraction }. score (= cleanFraction) is the fraction of decisions whose workspace was clean — no critical safety trigger AND drift below threshold. A harness/policy that makes the model hold steadier, safer intermediate concepts before answering scores higher. Use it as a workspace_probe Score dimension.

  • gradeMutationByWorkspace(baseline, mutant){ keep, reasons, baseline, mutant }. A Darwin-Mode veto: reject a mutation that improves the final answer at the cost of the internal process — it raises the critical-trigger rate, destabilizes the workspace (drift up), or lowers the clean fraction. "Final answer up, workspace grip down" = structurally brittle. Pair with the usual gold/final-answer gate: keep a mutation only if both pass. It never weakens the answer gate.

Quickstart

import { buildReceipt } from '@metaharness/workspace-lens';
import { workspaceProbeScore, gradeMutationByWorkspace } from '@metaharness/workspace-probe';

const receipts = decisions.map(d => buildReceipt(lens, d.prompt, d.states, { createdAt: d.ts, concepts }));

const probe = workspaceProbeScore(receipts, { driftThreshold: 0.25 });
// → { n, score, meanDrift, flagRate, criticalRate, cleanFraction }

const verdict = gradeMutationByWorkspace(baselineReceipts, mutantReceipts);
if (!verdict.keep) rejectMutation(verdict.reasons);   // structurally brittle

CLI

For audit workflows that don't want to write TypeScript. All inputs are JSON, all output is JSON on stdout (composes with jq):

npx @metaharness/workspace-probe diag           lens.json
npx @metaharness/workspace-probe readout        lens.json activations.json [--top-k N]
npx @metaharness/workspace-probe probe          receipts.json [--drift-threshold F]
npx @metaharness/workspace-probe grade-mutation baseline-receipts.json mutant-receipts.json
  • diag → the fitted lens's metadata (model/lens id, dModel, fitted layers, vocab size).
  • readout → the workspace tokens per activation ({layer, position, h}[]).
  • probe → the workspaceProbeScore over a receipt set.
  • grade-mutation → the keep/veto verdict comparing two receipt sets.

Exit codes: 0 ok, 2 usage error, 1 runtime error. A fitted lens artifact is produced out-of-band (open-weight model + backward pass — see @metaharness/workspace-lens).

Runnable demo

examples/demo.mjs is a $0, no-model end-to-end walk-through (synthetic lens → readout → receipts → probe score → mutation veto):

node packages/workspace-probe/examples/demo.mjs

Links

  • workspace-lens (the primitive): https://www.npmjs.com/package/@metaharness/workspace-lens
  • MetaHarness: https://github.com/ruvnet/metaharness

License

MIT.