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

run-ready

v1.1.0

Published

Any repo. One command. It just runs.

Readme

⚡ run-ready

Any repo. One command. It just runs.

npm License: MIT Node

npx run-ready https://github.com/vercel/next.js

✨ What it does

1. Smart Clone

Paste any GitHub link. It shallow clones with --depth 1 for speed.
No git? Falls back to zip download. Auto cds into the project.

2. Env Detective

Scans your entire codebase for process.env.*, import.meta.env.*, os.getenv() and generates a perfect .env.example.
No more guessing env vars from broken docs.

3. System Doctor

Cross-platform checks:

  • ✔️ Node version vs package.json engines
  • ✔️ Port 3000 / 8000 busy?
  • ✔️ Package manager detection (pnpm, yarn, npm)
  • ✔️ docker-compose.yml found but not running?

4. Auto Fix

One flag to fix it all.

rr --fix
# ✔ Created .env from .env.example
# ✔ Started docker compose services
# ✔ All set! Run: pnpm dev

🚀 Install

No install needed. Use directly:

npx run-ready https://github.com/vercel/next.js

Or install globally:

npm i -g run-ready
rr https://github.com/vercel/next.js

You get two commands: run-ready and short rr


📖 Commands

rr <github-url>   # Clone + Scan + Check (the magic)
rr --check        # Check health of current repo
rr --fix          # Auto-fix all issues (.env, docker)
rr --env          # Only generate .env.example
rr --help         # Help

Examples

# Clone express and make it ready
rr https://github.com/expressjs/express

# You are already inside a project, just check it
cd my-project
rr --check

# It found issues, fix them
rr --fix

🛠️ Output Example

⚡ run-ready  —  Any repo. One command. It just runs.

√ Cloned express
✔ Ready in C:\Users\HOME\Desktop\run ready\express

√ Found 2 env vars: NODE_ENV, NO_DEPRECATION
✔ Generated .env.example

✔ Node v24.12.0 (requires >= 18)
✔ Port 3000 is free
⚠ Package manager: No lock file found

Why?

I built this because I was tired of cloning cool GitHub repos and spending an hour just to run them.
READMEs lie. Env vars are hidden. Docker is always down.

This is for developers, by a developer.


Tech Stack

  • TypeScript + Node.js — ESM, fully typed, strict mode
  • Zero config — works on Windows / Mac / Linux
  • commander — CLI framework
  • chalk — terminal colors
  • ora — spinners
  • glob — file scanning
  • adm-zip — zip extraction fallback

🤝 Contributing

PRs welcome! This is MIT licensed.

# Fork it, then:
git clone https://github.com/vinyassystems/Run_Ready
cd Run_Ready
npm install
npm run build
node dist/index.js --check

⭐ Star History

If this saved you 30 minutes, give it a star ⭐


Built by Vinyas Poojary — 19, building tools for devs.