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

@proofmeta/spec

v0.2.0

Published

ProofMeta v1 JSON Schemas — canonical machine-readable spec (envelope + payload schemas).

Readme

ProofMeta JSON Schemas

Canonical machine-readable schemas for ProofMeta v1. Normative prose lives in PROOFMETA_ANWEISUNG.md.

Install

npm install @proofmeta/spec
import {
  envelopeSchema,
  manifestPayloadSchema,
  licenseRequestPayloadSchema,
  statusUpdatePayloadSchema,
  payloadSchemas, // { manifest, "license.request", "status.update" }
} from "@proofmeta/spec";

Shape

Every artifact in ProofMeta is a Signed Envelope. The outer wrapper is uniform; the payload inside varies by type.

envelope.schema.json  ──  payload ────┬──  payload.manifest.schema.json        (type: "manifest")
                                      ├──  payload.license-request.schema.json (type: "license.request")
                                      └──  payload.status-update.schema.json   (type: "status.update")

| File | Role | |------|------| | envelope.schema.json | Outer wrapper — required for every artifact. Defines proofmeta, payload, payload_hash, author, signature, timestamp, optional in_reply_to, anchors. | | payload.manifest.schema.json | Provider License Manifest payload (published at /.well-known/proofmeta.json). | | payload.license-request.schema.json | Consumer-signed OPEN envelope that starts a license lifecycle. | | payload.status-update.schema.json | PENDING / GRANTED / DENIED / REVOKED envelopes signed by Provider (or Resolver, for PENDING). |

Validation procedure

  1. Validate the outer object against envelope.schema.json.
  2. Read payload.type and validate payload against the matching payload schema.
  3. Recompute payload_hash from the JCS (RFC 8785) canonicalization of payload and verify it matches.
  4. Verify signature against payload_hash using the public key resolved from author.
  5. If in_reply_to is present, verify that the referenced envelope exists and is the logical predecessor for this payload type (see §3.4).
  6. For scope semantics in manifest payloads, see docs/scope-vocabulary.md.

Schemas are draft-07. The $id URLs are stable references; they are not required to resolve during validation.

License

Apache-2.0. See LICENSE.