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

rcl-cli

v1.0.0

Published

Save terminal commands as named, reusable procedures. Like npm run for your entire terminal life.

Readme

rcl

Save commands. Run them later.

I got tired of scrolling through shell history trying to find that one deploy command I ran two weeks ago. And aliases are fine, but I never remember what I named them.

So I built this. It's like npm run but for... everything else.

Install

npm install -g rcl-cli

How it works

# First time setup
rcl init

# Save a command you'll want to run again
rcl save deploy "git push origin {{branch}} && ssh prod 'cd /app && git pull'"

# Later, run it
rcl run deploy --branch main

# Forgot what it does?
rcl explain deploy

That's pretty much it.

Commands

rcl init — Sets things up. Run this once.

rcl save <name> "<command>" — Save a command. Use {{param}} for stuff you want to fill in later.

rcl list — See what you've saved.

rcl find <keyword> — Search your commands.

rcl run <name> --param value — Run a saved command with your values filled in.

rcl explain <name> — Show the full command and what params it needs.

A few things worth knowing

  • Commands live in ~/.rcl/commands.json
  • If a command has rm, delete, or --force in it, you'll need to add --confirm to run it
  • That's a feature, not a bug

Why not just use aliases?

You could! But I always forget:

  1. What I named them
  2. What arguments they take
  3. Where I defined them

This fixes all three.

License

MIT — do whatever you want with it.


GitHub