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

cache-reaper

v1.0.5

Published

Obliterate hidden application caches across your entire system.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

lakshanmuruganandamlakshanmuruganandam

Keywords

cachecleanupclireapernpm-cacheyarn-cachebrewmac

Readme

🧹 Cache Reaper

Interactively obliterate hidden developer caches to reclaim gigabytes of space.

npm version License: MIT

    ██████╗ ██████╗  █████╗ ██╗  ██╗███████╗
    ██╔════╝██╔══██╗██╔══██╗██║  ██║██╔════╝
    ██║     ██████╔╝███████║███████║█████╗  
    ██║     ██╔══██╗██╔══██║██╔══██║██╔══╝  
    ╚██████╗██║  ██║██║  ██║██║  ██║███████╗
     ╚═════╝╚═╝  ╚═╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝
    ██████╗ ███████╗ █████╗ ██████╗ ███████╗██████╗ 
    ██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔════╝██╔══██╗
    ██████╔╝█████╗  ███████║██████╔╝█████╗  ██████╔╝
    ██╔══██╗██╔══╝  ██╔══██║██╔═══╝ ██╔══╝  ██╔══██╗
    ██║  ██║███████╗██║  ██║██║     ███████╗██║  ██║
    ╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝╚═╝     ╚══════╝╚═╝  ╚═╝

Did you know that NPM, Yarn, Pip, Homebrew, Docker, and Bun all silently store gigabytes of cached packages deep inside your computer's hidden directories? Over time, these caches become a graveyard of dead data, stealing massive amounts of your hard drive space.

Cache Reaper is a blazing-fast, interactive CLI that automatically detects which package managers you have installed and lets you mass-clear their caches with a single click.

✨ Features

  • 🧹 Cross-Platform Scanning: Automatically detects NPM, Yarn, Homebrew, Pip, Docker Builders, and Bun environments.
  • ⚡ Interactive UI: Powered by inquirer for a buttery-smooth terminal experience.
  • 🛡️ Safe Obliteration: Executes the official cache-clearing commands (npm cache clean, brew cleanup, etc.) so your system remains perfectly stable.
  • 🎨 Premium Aesthetics: Features custom ASCII art, spinners, and beautifully color-coded outputs.

🚀 Installation

Run it instantly anywhere without installing:

npx cache-reaper

Or install it globally to keep your storage clean forever:

npm install -g cache-reaper

🎮 Usage

Run the command anywhere:

cache-reaper

Controls:

  • ↑ / ↓ : Navigate the list of discovered caches.
  • Space : Select targets to clear.
  • a : Select ALL targets to do a full system sweep.
  • Enter : Proceed to obliteration.

Architected by @lakshanmuruganandam

Because nobody needs the cached version of left-pad from 2017.