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

@rigkit/cli

v0.2.17

Published

Global `rig` CLI.

Readme

@rigkit/cli

Global rig CLI.

npm i -g @rigkit/cli
rig init
rig plan
rig ls
rig --chdir=examples/smoke plan

rig init creates rigkit/index.ts and package metadata in the current directory, then prompts for bun, pnpm, or npm to install the local Rigkit dependencies. Use rig init --package-manager skip or rig init --no-install to write files without installing.

Interactive terminals use Inquirer prompts and a chalk/log-update run timeline. Set RIGKIT_RENDER=0 to force the plain text renderer; --json and flag-driven flows remain suitable for agents and scripts.

Interactive providers can ask the CLI to open provider-owned URLs. For example, Freestyle terminal sessions are served by the Freestyle provider, while the CLI only opens the presented URL in a browser.

Workspace lifecycle commands are built in: rig create <workspace> creates a workspace and rig rm <workspace> removes one. Workspace-specific operations defined by the project run as rig run <workspace> <operation>, for example rig run website-workspace open-cmux.

rig ls lists workspaces for the selected project. rig ls snapshots lists cached snapshot runs, and rig ls config shows the resolved project paths.

Use global context options before the command to select another project:

rig --chdir=examples/smoke plan
rig --chdir=examples/global-fragments apply --workflow api

Initialized projects pin matching Rigkit package versions locally.