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

@appport/recipe-distribution

v0.2.0

Published

The boundary between AppWorks recipe packages and Distribution Protocol releases. The only AppWorks package that depends on Distribution Protocol. Also: a file release channel, publishing, acquisition with receipts, and installation into an environment.

Readme

@appport/recipe-distribution

The boundary between AppWorks recipe packages and Distribution Protocol releases (distribution/1, @distribution-protocol/protocol 1.0.0). The only AppWorks package that depends on Distribution Protocol.

  • recipeReleaseManifest(pkg, options): the release manifest for a recipe package, validated by Distribution Protocol. Sign and publish it with Distribution Protocol's own tools.
  • acceptAcquiredRecipePackage({ release, artifactId, bytes, expect, trust? }): release signature, publisher trust (with a policy), the signed appport/recipe-package/1 binding against the expected package digest, artifact digest and size, then the package itself with its identity recomputed from the bytes.

Since 0.2.0, the whole lifecycle over a file channel (spec/distribution-1.md):

  • FileChannel, publishRecipePackage: a signed release bound to the publisher's document, written so a release never names missing bytes; a published version never changes.
  • acquireRecipePackage: release signature first, then the consumer's anchored trust policy, then bytes fetched against the signed digest (none returned unless they match), then the package against the digest the consumer expects; a validated Distribution Protocol receipt.
  • InstallStore, installRecipePackage, readInstalledPackage: checks the recipe against the receiving environment, builds that environment's own lock, refuses without verified trust, writes the install whole or not at all, and authorizes nothing.
  • appworks package keygen | trust | publish | verify | install | list | show.

Not implemented: an HTTPS registry, mirrors, upgrade or uninstall, key rotation tooling. Acceptance grants no authorization, proves no fulfillment and establishes no business outcome; the result is never executable, and is installable only when publisher trust was evaluated and accepted.