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

@orkestrel/probe

v0.0.16

Published

Prove a claim with type, lint, and runtime evidence from the workspace's own toolchain.

Readme

@orkestrel/probe

The claim prover for the @orkestrel line: an instrument that runs a claim's case and its negative control through the workspace's own TypeScript, Oxlint, and Vitest, and returns a Verdict carrying every issue — and a receipt when the case ran clean and the control broke where it said it would.

A claim carries a case — the edit you believe is correct — and a control, the same edit deliberately broken, naming the stage it must fail at. The receipt a proven claim earns is a one-line token naming the claim, the stage, the tool versions, and the TypeScript project that judged the candidates.

Read guides/probe.md before you make a claim. It states the prerequisites, the receipt's verification method and its limits, and what a receipt does not vouch for.

Install

npm install --save-dev @orkestrel/probe

typescript, oxlint, and vitest are optional peers, resolved from the workspace probe inspects.

The probe binary

The package installs a probe binary that serves the prove Model Context Protocol tool over a newline-delimited JSON stdio transport. Register the resolved JavaScript entry rather than a global install, an npx invocation, or the node_modules/.bin shim:

{
	"mcpServers": {
		"probe": {
			"command": "node",
			"args": ["node_modules/@orkestrel/probe/dist/bin/main.js"],
			"cwd": "/srv/checkout"
		}
	}
}

Proving a claim in process

import type { Claim } from '@orkestrel/probe'
import { Probe } from '@orkestrel/probe/server'

const claim: Claim = {
	project: 'configs/src/tsconfig.core.json',
	case: {
		files: [
			{
				path: 'src/core/factories.ts',
				text: "export function createGreeting(): string {\n\treturn 'hi'\n}\n",
			},
		],
		test: {
			path: 'tmp/probe/greeting.test.ts',
			text: "import { expect, test } from 'vitest'\nimport { createGreeting } from '../../src/core/factories.js'\ntest('greets', () => expect(createGreeting()).toBe('hi'))\n",
		},
	},
	control: {
		files: [
			{
				path: 'src/core/factories.ts',
				text: "export function createGreeting(): number {\n\treturn 'hi'\n}\n",
			},
		],
		test: {
			path: 'tmp/probe/greeting.test.ts',
			text: "import { expect, test } from 'vitest'\nimport { createGreeting } from '../../src/core/factories.js'\ntest('greets', () => expect(createGreeting()).toBe('hi'))\n",
		},
		stage: 'type',
		reason: 'a string returned as a number must not compile',
	},
}

const probe = new Probe({ workspace: process.cwd() })
const verdict = await probe.prove(claim)
console.log(verdict.receipt)
await probe.destroy()

probe executes caller-supplied test code with the privileges of the process that hosts it. Give it a workspace and a caller you already trust with a shell.

Development

npm install
npm test