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

@alexar76/awr-emit

v2.0.0

Published

Emit a signed AWR/2 WorkReceipt from Node with zero runtime dependencies — W3C Verifiable Credential, eddsa-jcs-2022 over RFC 8785, did:key. Includes an MCP tool-call wrapper.

Readme

@alexar76/awr-emit

Emit a signed AWR/2 WorkReceipt from Node. Zero runtime dependencies — the RFC 8785 canonicalizer, base58btc, did:key derivation and the Ed25519 signing all sit in one file over node:crypto.

There are two sides to AWR and they need different code. A verifier reads a receipt and checks it. An emitter writes one: it takes what your system just did and signs a document saying so. This is an emitter, and it verifies nothing — deliberately, because a component that both issues and judges its own work is not evidence of anything.

npm install @alexar76/awr-emit
import { emitReceipt, generateKey, jcsPayload } from '@alexar76/awr-emit';

const key = generateKey();              // keep this; its .did is your issuer identity

const receipt = emitReceipt({
  key,
  modelId: 'claude-opus-5@anthropic',
  inputPayload: jcsPayload({ prompt: 'summarise this', n: 3 }),
  outputPayload: '...the model\'s answer...',
  latencyMs: 2340,
});

receipt is a plain object, ready for JSON.stringify. Anyone can check it without this package and without trusting you:

pip install awr
python -m awr verify receipt.json

MCP tool calls

./mcp wraps an MCP tool handler so every call it serves produces a receipt — including the calls that fail, because an unverifiable failure is what a dispute usually turns on.

import { withAwrReceipts } from '@alexar76/awr-emit/mcp';

const handler = withAwrReceipts(myToolHandler, {
  key,
  modelId: 'my-server@v1',
  onReceipt: (doc, err) => save(doc),   // required: a receipt nobody keeps is not evidence
});

Cross-implementation agreement

The Python emitter and this one produce byte-identical documents for the same inputs and key. That is not a claim, it is a test: test_the_typescript_emitter_agrees_byte_for_byte runs Node from pytest and compares the bytes, and the timestamp-derivation rules are pinned on both sides after a real divergence was found by diffing partial inputs.

The format itself has three independent verifiers — Python, Rust and browser JavaScript — that agree on 354 conformance cases, and an unmodified off-the-shelf W3C VC library verifies these documents given nothing but a did:key resolver.

Links

MIT.