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

github-pewpew

v1.5.1

Published

Clean up unnecessary GitHub repositories, Codespaces, and gists. Pew pew!

Downloads

492

Readme

Installation and Usage

To install the latest version of github-pewpew CLI, run this command:

npm i -g github-pewpew

To quickly start using it, run the following command:

ghpew

Available commands:

ghpew repos
ghpew repos --archive
ghpew repos -a
ghpew repos --force
ghpew repos --regex '^adrianmg/demo-'
ghpew repos --list 'adrianmg/one,adrianmg/two'
ghpew repos --list 'adrianmg/one,adrianmg/two' --force
ghpew gists
ghpew codespaces
ghpew help

Repository selection is interactive by default. --regex uses a case-sensitive JavaScript regular expression against each full owner/repository name; pass the pattern without / delimiters. --list accepts exact, comma-separated owner/repository names and stops without processing anything if a name is not available. Every selection mode asks for confirmation unless --force is provided, and either filtering flag can be combined with --archive. Because --force processes the selection immediately, review it carefully first.

Codespaces and gists use interactive multi-selection and always ask for confirmation before deleting anything. Gists are identified by their description or first filename, visibility, and unique ID. Gist deletion cannot be undone. The first run after upgrading may ask you to sign in again so the CLI can request permission to manage gists.

Why?

Have you ever had too much fun with GitHub and ended up creating too many throwaway repositories, Codespaces, or gists? Me too 😅!

I made this little CLI tool to clean up GitHub clutter quickly. Let me know what you think.

Do you want to know more? Visit the official website.

Development

The important parts of the project are the following:

├── .github                GitHub Actions workflows and repo settings
├── src
│   ├── commands
│   │   ├── codespaces.js  Contains the command to delete codespaces
│   │   ├── gists.js       Contains the command to delete gists
│   │   └── repos.js       Contains the command to process repositories
│   ├── config.js          Contains the configuration manager
│   ├── github.js          Business logic: authentication and API calls
│   ├── repo-options.js    Parses and resolves repository selection options
│   ├── ui.js              CLI interactions
│   └── utils.js           Lightweight utility functions
├── test
│   └── test.js            Test coverage with the Node.js test runner
├── .prettierrc            Code formatting configuration
├── index.js               The main thread of execution
├── README.md              you're looking at it

To set up your environment to develop this tool, run:

  • Install Node.js 20 or newer
  • npm install
  • node index

You can also run node index DEV=true CLIENT_ID=<YOUR_TESTING_CLIENT_ID> if you want to use your own client id for development and testing purposes.

The tests use the built-in Node.js test runner and can be run with npm test.

Questions? Ideas? Bugs?

If you run into any issues or you'd like to share your thoughts, feel free to open an issue in this repository or hit me up on Twitter.

Contributions

Logo designed by Rapha Lopes. Thanks to @sergiou87, @zschiller, @mamuso, @anishde12020, and @jdvr for contributing with their feedback and ideas 🙇‍♂️.

License

The tool is available as open-source under the terms of the MIT License.