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

right-tool

v1.2.5

Published

Lets you setup scripts in package.json such that they use the same tool (npm/npx | yarn | pnpm | bun) or (node | bun) that you used to execute it. Also detects container implementation (docker|podman|kubectl|buildah|incus|nerdctl|colima).

Readme

right-tool

Select the right tool for the job!

Provides placeholder keywords you can use in package.json to represent a class of tools (node.js: package manager, runtime), (container engine) to be replaced at runtime by the most appropriate tool, determined by different conditions.

cascade

This keyword is a drop in replacement for your package manager: npm, yarn, bun or pnpm If you have a script cascade run build && cascade run test it will use the same tool you used on the command line to execute the script from package.json if your scripts call other scripts and other project.json that use cascade, the same tool will continue to be used across the board, providing consistency and avoiding mixed contexts, clashes between lockfiles and dependency resolution within the project.

escapade

This is virtually identical to cascade except it provides support for npx commands.

launcher

This tool uses the logic of cascade to select the runtime node or bun depending on whether bun was used to launch package.json

containment

Use this keyword to identify and execute the container runtime present on that system. Most popular options are podman, docker, kubectl for container management and deployment, also detects: buildah, incus, nerdctl, colima

API

You can include the API in your code to get the string result of which command is executed on the command line:

import { containerengine, nodepackagemgmt, nodelauncher } from 'right-tool'
let ce = containerengine(); // returns "podman"
let pm = nodepackagemgmt(true); // returns "yarn" (parameter: npx - boolean: whether to return npx instead of npm)
let cl = nodelauncher() // returns "node"

main

You can use this shortcut in your esm modules for scripts that you want to create commands from:

In package.json

	"bin":{
		"myscript": "./my.js"
	}

In my.js

#!/usr/bin/env node
import main from 'right-tool/main'

function _main_() {
	// body...
}

// Main always requires you to pass it import.meta
if (main(import.meta)){
	_main_();
}