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

steelyard

v0.11.0

Published

The Steelyard SDK: define commerce once, serve it over commerce.json, HTTP, MCP, ACP, UCP, and x402, and run agentic payments from one package.

Readme

steelyard

The Steelyard SDK front door. Define commerce once, serve it everywhere, let buyers buy. One install, one import.

npm install steelyard

Define once, serve everywhere

import { defineCommerce, serveCommerce } from "steelyard";

const manifest = defineCommerce({
  identity: { name: "My Shop", domain: "shop.example", currencies: ["USD"] },
  offers: [
    { id: "tee", title: "T-Shirt", availability: "in_stock",
      pricing: [{ kind: "one_time", amount: 2500, currency: "USD" }] }
  ]
});

serveCommerce(manifest).listen(3000);
// Live now from one manifest:
//   GET /.well-known/commerce.json   GET /commerce/products   POST /mcp
//   GET /acp/feed                    GET /.well-known/ucp + /api/catalog/*
curl localhost:3000/.well-known/commerce.json

serveCommerce is read-only by default (no PSP needed). It returns a Node Server you can .listen(), or use createCommerceReadHandler(manifest) to mount the surfaces inside your own server.

What's re-exported

This package re-exports the symbols 90% of integrators need:

| Need | Symbols | |------|---------| | Define schemas | defineCommerce, types Manifest Offer Price PurchaseIntent | | Serve | serveCommerce, createCommerceReadHandler | | Per-protocol handlers | createMcpServer createMcpHttpHandler createUcpHandler buildUcpDiscovery createAcpFeedHandler buildAcpFeed createCommerceManifestHandler createHttpApiHandler | | Checkout + PSP | createCheckoutServer, stripePsp, referencePsp | | Payment instruments | vaultedCard, stripeSpt, referenceMandate, x402Payments, x402Fetch | | Paid HTTP resources | x402Paywall, exactUsdc | | Policy | PolicyEngine, createPolicyEngine | | Buy | Wallet, Steelyard / connect |

Power users

This is a curated front door, not the whole surface. For anything not above, import the specific package directly — e.g. steelyard/protocol/ucp, steelyard/buyer/vault, steelyard/merchant, steelyard/x402, steelyard/core. The umbrella never hides them; it just gives you a shorter path to the common case.