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

@rerout/cli

v0.2.0

Published

Command-line interface for Rerout — branded short links, QR codes, and analytics from your terminal.

Downloads

282

Readme

@rerout/cli

Branded short links, QR codes, and analytics from your terminal — a thin CLI over @rerout/sdk.

npm install -g @rerout/cli

Authenticate

Mint a project API key in the dashboard (Owner/Admin), then:

rerout login --api-key rrk_...

The key is verified against the API and stored at $XDG_CONFIG_HOME/rerout/config.json (default ~/.config/rerout/config.json) with 0600 permissions. Alternatively set REROUT_API_KEY in the environment (it takes precedence over the saved key). Use --base-url / REROUT_BASE_URL for staging or self-hosted APIs.

Commands

rerout whoami                                   # show the key's project
rerout create https://example.com/sale \        # create a link
  --domain go.brand.com --code sale
rerout ls --limit 20                            # list links
rerout get sale                                 # show one link
rerout update sale --inactive                   # patch a link
rerout rm sale                                  # soft-delete a link
rerout stats                                    # project stats (--days 30)
rerout stats sale --days 7                      # per-link stats
rerout qr sale                                  # print the QR URL
rerout qr sale --output sale.svg                # write the QR SVG
rerout webhooks ls
rerout webhooks create --name "Orders" --url https://example.com/hook \
  --events link.created,link.clicked
rerout webhooks rm wh_...
rerout tags ls                                  # tags with link counts
rerout tags create "Spring 2026" --color teal
rerout tags update tag_... --name "Spring '26"
rerout tags rm tag_...

Add --json to any command for raw, machine-readable output.

Development

npm install
npm run typecheck
npm test          # vitest — network is stubbed via an injected fetch
npm run build     # emits dist/ (CLI bin + ./core)

The reusable pieces (config, client factory, formatting) are exported from @rerout/cli/core so other surfaces — like the planned Raycast extension — can share one engine instead of re-implementing auth and rendering.

Publishing

npm run build
npm publish --access public