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

@bubuding0809/blob-cli

v0.3.0

Published

Tiny CLI for publishing static files to a private Vercel Blob store, with inline-rendering URLs via your own viewer.

Readme

blob-cli

Tiny CLI for publishing files to your Vercel Blob store and getting back a URL that renders inline in any browser. Designed for AI agents that produce HTML output you'd rather view in a browser than read in a terminal.

How it works (BYOB + BYOV)

You bring your own:

  • Blob store (Vercel Blob, private access)
  • Viewer — a small Next.js app you deploy once at viewer/ that proxies blob content with inline-render headers and gives you a password-gated file dashboard

The CLI uploads to your Blob store and prints URLs that point at your viewer. Your tokens never leave your Vercel account.

Install

curl -fsSL https://raw.githubusercontent.com/bubuding0809/blob-cli/v0.3.0/install.sh | bash

Or with npm directly:

npm i -g @bubuding0809/blob-cli

The install URL pins to a specific tag, so the script that runs is exactly the version you reviewed — never silently changed by a future commit.

Prerequisites

  • Node.js 18 or later. Check with node --version.
  • A Vercel account. Free tier is fine. Sign up at https://vercel.com/signup.
  • 5 minutes for the one-time setup.

Setting this up via an AI agent? See AGENTS.md for the agent-driven flow.

One-time setup

  1. Create a private Vercel Blob store. Vercel dashboard → Storage → Create Database → Blob. Copy the BLOB_READ_WRITE_TOKEN from its .env.local tab.
  2. Deploy the viewer using the Deploy to Vercel button. You'll set three env vars: the blob token, a dashboard password, and a session secret. Copy the deployment URL when it's done.
  3. Run blob init. Paste the blob token, then paste the viewer URL. Done.

First 60 seconds

After blob init:

echo "<h1>Hello from blob-cli</h1>" > /tmp/hello.html
blob upload /tmp/hello.html
# → https://blob-viewer-abc.vercel.app/hello-x7Ka2.html

That URL renders inline in any browser. Send it to a friend, drop it in a chat — the recipient clicks once and sees the page. No download, no terminal output, no copy-pasting raw HTML.

Commands

blob upload report.html
# → https://blob-viewer-xxx.vercel.app/report-x7Ka2.html

blob list
# 2026-04-28T10:00:00Z   1234   https://blob-viewer-xxx.vercel.app/...

blob get <viewer-url-or-pathname> [--out file]

blob delete <viewer-url-or-pathname>

list and delete accept --json for machine-readable output.

init also accepts --token and --viewer-url for non-interactive use:

blob init --force --token "$BLOB_RW_TOKEN" --viewer-url "$VIEWER_URL"

Notes

  • File URLs are open — anyone with a link can view. Security is the unguessable random suffix on the pathname. Don't upload secrets.
  • The dashboard at / on the viewer is password-protected.
  • Each upload gets a random suffix; you can't overwrite an existing file in place.
  • BYOB+BYOV means your data is in your Vercel project. We never see, store, or proxy it.

Troubleshooting

| Symptom | Likely cause | Fix | |---|---|---| | blob init says "token rejected by Vercel" | Token is wrong, or copied from a different store | Re-copy BLOB_READ_WRITE_TOKEN from Vercel store's .env.local tab. | | blob init says "viewer health check failed" | Viewer not deployed, env vars missing, or wrong URL pasted | Open <viewer-url>/api/health in a browser — should return {"ok":true}. If 404 or 500, check viewer deploy logs on Vercel. | | blob upload says "Cannot use public access on a private store" | You're on an old version of blob-cli | npm i -g @bubuding0809/blob-cli@latest | | blob command not found after install | npm global bin dir isn't on PATH | npm config get prefix — add <prefix>/bin to PATH. | | Need to nuke config and start over | ~/.config/blob-cli/config.json exists | Delete the file, or run blob init --force. |

Config and env vars

  • Config lives at ~/.config/blob-cli/config.json (mode 0600).
  • BLOB_READ_WRITE_TOKEN env var overrides the stored token if set.
  • BLOB_VIEWER_URL env var overrides the stored viewer URL if set.

For Claude / agent users

This repo includes:

To install the skills into your Claude Code:

mkdir -p ~/.claude/skills
cp -r .claude/skills/blob-cli-* ~/.claude/skills/