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

@mailworker/cli

v0.1.0

Published

Programmatic inboxes that send and receive real email. The agent-facing surface: human and machine readable at once.

Readme

@mailworker/cli

Programmatic inboxes that send and receive real email, aimed at agents and test automation rather than at humans reading mail. Installs one command, mailworker.

npx @mailworker/cli@latest help --agent

This CLI talks to your own Mailworker deployment on Cloudflare. It is not a hosted service: point it at a deployment you control with MAILWORKER_URL and MAILWORKER_TOKEN.

Why a CLI and not an MCP server

There is no MCP server by design; agents drive Mailworker through this CLI and the REST API. That raises the bar on its design, since it has to work for humans and machines at once:

  • --json on everything, with a schema kept stable within a major version
  • zero interaction when stdin is not a TTY — never block waiting for input
  • one command completes one whole intent (wait --extract otp prints the code itself, not a message to parse)
  • exit codes carry meaning, so a script or agent can branch without reading text

| Code | Meaning | |---|---| | 0 | success | | 1 | generic error | | 2 | usage error | | 3 | authentication failed | | 4 | wait timed out | | 5 | rejected by policy — quota, allowlist, loop breaker or suppression | | 6 | quota or rate limit |

mailworker help --agent prints the whole surface in one page, which is what an agent should read instead of this file.

Configuration

export MAILWORKER_URL=https://mailworker.your-worker.dev
export MAILWORKER_TOKEN=mw_live_…

Both may also come from .mailworker/config.json, project directory first then home. Prefer the environment: a token in argv is visible in ps and in shell history.

The shape of a test

id=$(mailworker inbox create --prefix signup --json | jq -r .id)
# … drive your signup flow against the printed address …
CODE=$(mailworker wait --inbox "$id" --extract otp --timeout 60s) || exit $?

get --raw > fixture.eml into inject fixture.eml is the loop that turns a strange production message into a regression test.

Using it from a coding agent

npx skills add guangzhengli/mailworker

Installs the mailworker skill into Claude Code, Codex, Cursor and other skills-compatible agents.

License

MIT