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

@mightbeandrew/wtfcli

v1.0.8

Published

Why is my computer slow right now? One command that diagnoses CPU, memory, disk, and network.

Downloads

82

Readme

wtf

Why is my computer slow right now?

One command that tells you exactly what's eating your CPU, memory, disk, and network — in plain English. Not top. Not 10 tools. One answer.

$ wtf

 CPU  ████████░░  82%
   Chrome                          42.3%
   node                             8.1%
   Slack                            3.4%

 MEM  ███████░░░  71%  11.4 GB / 16.0 GB
   Chrome                        4.2 GB
   node                          1.1 GB
   Slack                         800 MB

 DSK
   /dev/sda1             ██████░░░░  58%  230 GB / 400 GB

 NET
   eth0          ↓      1.2 MB/s  ↑    200 KB/s

────────────────────────────────────────────────────────
 High CPU: Chrome is using 42% CPU

Install

npm install -g @mightbeandrew/wtfcli

Usage

wtf                       # full diagnosis
wtf --cpu --mem           # CPU and memory only
wtf -v                    # verbose: top 10 processes, extra stats
wtf -j | jq '.cpu'        # JSON output piped to jq
wtf -w 5                  # live refresh every 5 seconds
wtf --no-color > out.txt  # plain text to file

Flags

| Flag | Description | |------|-------------| | -v, --verbose | More processes, extra detail | | -j, --json | JSON output (pipe-friendly, no color) | | --no-color | Strip ANSI colors | | --cpu | CPU section only | | --mem | Memory section only | | --disk | Disk section only | | --net | Network section only | | -t, --top <n> | Top N processes per section (default: 5) | | -w, --watch [secs] | Live refresh, default every 2s | | --version | Print version | | -h, --help | Show help |

License

MIT