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

deliverd

v0.9.1

Published

Publish AI-generated reports to a secure URL from your terminal.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

deliverddeliverd

Keywords

mcpaireportspublishingclaudecursor

Readme

deliverd

Ask a person from a build step (deliverd ask "Ship v4?" --wait), and publish AI-generated work to a secure URL — from your terminal, a pipeline or your AI tools.

Connect your AI tools

npx deliverd setup

Finds Claude Code, Codex, Claude Desktop and Cursor on your machine and connects whichever are installed.

No API token is written anywhere. The server implements the MCP authorization spec, so each client registers itself and asks you to approve it in a browser.

It merges into whatever configuration is already there, keeps a timestamped backup of any file it changes, and refuses a file it cannot parse rather than overwriting it — those files hold your other MCP servers.

Codex needs one more step of its own. It does not begin the approval flow on first use the way the Claude clients do, so after setup run:

codex mcp login deliverd

| Option | | |---|---| | --print | Show the settings instead of writing anything | | --agent <id> | Just one: claude-code, codex, claude-desktop, cursor | | --url <url> | A self-hosted server (default https://deliverd.dev) |

Publish from the terminal

npx deliverd login --url https://deliverd.dev
npx deliverd publish ./report --audience "Finance team"
npx deliverd update finance/weekly ./report
npx deliverd rename finance/weekly --title "Weekly Finance"
npx deliverd list

login opens a browser and stores a token in ~/.config/deliverd/config.json.

Renaming keeps the old address working, so links you have already shared do not break.

--task <id> on publish or update keeps a report with the Task Graph task it was written for: it is listed on the task and in deliverd tasks context.

Requirements

Node.js 20 or later.

Documentation

https://deliverd.dev

Licence

MIT. This covers the CLI only — the Deliverd service it talks to is a separate, proprietary product.