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

@wpbevel/upload

v1.0.1

Published

Send files to a Bevel MCP upload link from a shell: globs, SHA-256 receipts, retries. No dependencies.

Readme

@wpbevel/upload

Send files to a Bevel MCP upload link from a shell. For assistants that can run commands (Claude Code, Codex, Cowork) and for anyone with a terminal: the bytes go straight from the disk to the site, never through the conversation.

npx @wpbevel/upload "https://example.com/wp-json/bevel-mcp/v1/upload/<ticket>" ./brand/logo.png ./brand/logo-white.png
npx @wpbevel/upload "<link>" "./fonts/Aeonik-*.woff2" --family "Aeonik"

The link is the one the assistant gets from upload_media {request_upload_url:true} or upload_font {request_upload_url:true, family}. It accepts images and fonts alike: an image lands in the media library, a font in Bevel Kit's Custom Fonts as one face of the family (weight and style are read from the file name, or passed with --weight and --style).

What it does for you:

  • expands ~, *, ** and {a,b} patterns;
  • hashes every file first, so a retry after a lost answer returns the same asset instead of a duplicate;
  • retries a busy link three times with backoff;
  • prints one line per file with the id, URL and tone hint (dark or light artwork), or the family, weight and format for a font;
  • --json prints the full result for a script to read; exit code 1 when any file failed.

Node 18.17 or newer. No dependencies.