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

@axiorank/log-witness

v0.1.0

Published

A self-hostable witness for an AxioRank audit transparency log. Countersigns each sealed signed tree head with an Ed25519 key you control, so your records are an independent split-view defense. Zero runtime dependencies.

Readme

@axiorank/log-witness

A self-hostable witness for an AxioRank audit transparency log.

AxioRank's audit log is tamper-evident on its own (Merkle-sealed, signed tree heads). What a log operator cannot prove by itself is that it never showed two different histories to two different observers, the "split view." The defense is external witnessing: an independent party countersigns each sealed head. If the log ever forked, the witness's signatures over the two heads expose it.

This package is that witness. You run it on infrastructure you control, with an Ed25519 key only you hold. Point a workspace's witness URL at it, and every sealed head is countersigned by a key AxioRank does not have, so your records are a genuinely independent attestation.

Run it

npx @axiorank/log-witness --port 8787

Generate a stable key (do this once, keep it secret):

node -e "const {generateKeyPairSync}=require('node:crypto');console.log(generateKeyPairSync('ed25519').privateKey.export({format:'der',type:'pkcs8'}).toString('base64'))"
AXR_WITNESS_NOTE_KEY="<base64-from-above>" \
AXR_WITNESS_NAME="note:acme-witness" \
npx @axiorank/log-witness --port 8787

Without AXR_WITNESS_NOTE_KEY an ephemeral key is generated and a restart invalidates every record. That is fine for a quick try and never for production.

Optionally require a shared bearer on the witnessing endpoint:

AXR_WITNESS_AUTH_TOKEN="..." npx @axiorank/log-witness

HTTP API

| Route | Purpose | | --- | --- | | POST /witness | Body { signedTreeHead, signedAt }. Returns a WitnessRecord. | | GET /key | { witness, keyId, publicJwk }. Pin this out-of-band. | | GET /healthz | Liveness. |

A WitnessRecord is an Ed25519 signature over canonicalize({ subjectHash, witness, signedAt }), where subjectHash is the SHA-256 of the canonical signed tree head with its own signature stripped. It is verified by @axiorank/audit-verify and the @axiorank/log-watchdog monitor.

Connect it to AxioRank

In Settings → Security → Witnesses (Enterprise plan), add this daemon's URL. AxioRank POSTs each sealed head to it and stores the returned record alongside the checkpoint, exposed on the public log so anyone, including you, can verify the split-view defense with the watchdog.

Programmatic use

import { createWitnessServer } from "@axiorank/log-witness";

const witness = createWitnessServer({ name: "note:acme", rawKey: process.env.KEY });
await witness.listen(8787);

Zero runtime dependencies; built on node:http and node:crypto. MIT licensed.