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

@getbourdon/conformance

v0.7.0

Published

Language-neutral cross-implementation parity fixtures for Bourdon. Python (pip install bourdon) is the oracle; the @getbourdon/* TypeScript mirror asserts against these exact bytes.

Readme

@getbourdon/conformance

Language-neutral cross-implementation parity fixtures for Bourdon.

Python (pip install bourdon) is the oracle. The @getbourdon/* TypeScript mirror is conformant iff it reproduces the oracle's output on these exact fixtures — byte-for-byte where the contract is bytes (redaction, recognition strings, MCP wire), value-for-value where it's structured (F1, schema validity, tool I/O).

Who mints fixtures

The Python repository mints fixtures; this package is a runner and consumer, never a producer. Every fixture is generated by the Python repo's tools/gen_conformance.py (the single writer, which imports the live oracle and emits its actual output). This package vendors a reviewed snapshot of that output under fixtures/ and ships it with typed loaders. No fixture is ever authored or edited here — a change always starts oracle-side and arrives through the re-pin ritual below.

import { loadRedactionBattery, assembleSecret } from "@getbourdon/conformance";

const battery = loadRedactionBattery();
for (const secret of battery.secrets) {
  // a faithful TS redaction port must produce battery's expected output:
  expect(redactText(assembleSecret(secret))).toBe(secret.expect_redacted);
}

The pin

fixtures.pin.json records which contract the vendored snapshot is (conformance_version) and the sha256 fixtures/manifest.json must hash to. The test suite asserts both and prints them, and separately verifies every fixture file against the sha256 its manifest stamps — so a stale, partial, or hand-edited fixture tree cannot pass quietly. A mutation test corrupts a temp copy and asserts the hash gate goes red, proving the gate itself is live.

Re-pin ritual (per contract bump)

  1. Oracle side: regenerate (python tools/gen_conformance.py), review the diff, land it there first.
  2. Here: BOURDON_CONFORMANCE_DIR=<oracle>/conformance pnpm --filter @getbourdon/conformance sync-fixtures
  3. Update fixtures.pin.json with the new conformance_version and the sha256 of the new fixtures/manifest.json.
  4. Run the workspace test suite; fix whatever the new contract flushes out in the mirror packages, never by editing a fixture.

Resolution order: BOURDON_CONFORMANCE_DIR, else the vendored fixtures/ snapshot, else the sibling Python checkout ../bourdon/conformance.

License: Apache-2.0 (the wire-contract surface is permissive so third parties can build conformant implementations). The Bourdon engine is BUSL-1.1.