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

@korgg/ledger-verify

v0.1.0

Published

Independent, dependency-free verifier for korg-ledger@v1 receipts and journals (hash chain + causal DAG + Ed25519 tip signature). Runs in Node and the browser via Web Crypto.

Readme

@korgg/ledger-verify

The JavaScript implementation of korg-ledger@v1 — one of three independent verifiers (alongside the Python reference and the Rust korg-verify crate), each written from the spec and checked against the same frozen conformance vectors. Tamper one byte and all three reject it.

  • Zero dependencies. Uses only the Web Crypto standard (crypto.subtle).
  • Isomorphic. The same verify.mjs runs in Node (≥18) and the browser.
  • No network, no trust in the producing tool. A receipt verifies (or doesn't) from its bytes alone.

CLI

npx @korgg/ledger-verify <receipt.json | journal.jsonl> [--key <str>] [--pubkey <hex>] [--json]
# or, from a checkout:
node verify.mjs deliverable.korgreceipt.json

Exit code: 0 valid · 1 invalid/tampered · 2 usage/parse error.

✓ receipt VALID — 6 events, hash-chain + DAG intact · signed by b251a84c2d23d318…

--pubkey <hex> pins the expected signer and rejects any other key, so a green check proves authorship against a key you already trust — not merely against the one the receipt happens to carry.

Library

import { verifyText, verifyChain, canonicalize } from "@korgg/ledger-verify";

const verdict = await verifyText(receiptText, { pinPubkey: "b251a84c…" });
verdict.valid; // boolean

In the browser, import the same module and pass the receipt text — Web Crypto does the SHA-256 / HMAC / Ed25519. (Ed25519 in crypto.subtle requires a recent runtime: Node ≥18.4 and current Chrome/Safari/Firefox; the chain + DAG checks work everywhere.)

What a green verdict proves

The recorded events hash-chain intact and link in a well-formed causal DAG (tamper-evident), the receipt's tip matches the chain head, and — if signed — the holder of the named key attests to that exact tip. It does not prove when it happened (needs an external time anchor) or that the key maps to a real-world identity (the relying party pins that with --pubkey).

Conformance

npm test        # node conformance.mjs — reproduces the frozen tip hashes; exit 0 = conformant

This is the executable oracle: an intact vector must reproduce its frozen tip_entry_hash, a tampered vector must be flagged at the named seq. The same manifest (../conformance.json) drives the Python (../conformance.py) and Rust (../../../crates/korg-verify) implementations.