npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




[![npm version](]( [![Codecov](](





npm version Codecov


$ yarn global add git-secret-scanner


git-secret-scanner scan

Scans local git repositories for committed secrets

  $ git-secret-scanner scan [OPTIONS]

  -d, --dir=dir                      directory to scan (current direction if omitted)
  -g, --githubOrgName=githubOrgName  clone all repositories from this GitHub org (requires GITHUB_ACCESS_TOKEN env var)
  -h, --help                         show CLI help
  -l, --createLogFiles               create log files
  -o, --outputDir=outputDir          output directory (log files)
  -r, --redact                       redact all matched secret strings

  $ git-secret-scanner scan -lo ~/logs -d ~/code/
  2020-11-05T09:14:01.619Z [info] SCAN STARTED: ~/code/
  2020-11-05T09:14:01.620Z [info] scanning ~/code/
  2020-11-05T09:14:01.622Z [info] analysing files at commit 66f005f82edc4684559df25a74d859583572dd9f (main)
  2020-11-05T09:14:01.641Z [warn] (github-secret-scanner) [AWS_ACCESS_KEY_ID] found AKIAIOSFODNN7OSFODNN in test/commands/scan.test.ts on line 15 (f8e28a25a59d4e727f132f831fbb926ac68047cb by [email protected] at 2020-11-04T16:06:09.000Z)
  2020-11-05T09:14:01.641Z [warn] (github-secret-scanner) [AWS_ACCESS_KEY_ID] found AKIAIOSFODNN7OSFODNN in test/commands/scan.test.ts on line 22 (4f35f8a6d9234cdc3688e914ac52b3bf8a5c0012 by [email protected] at 2020-11-03T20:57:26.000Z)


Logs are written to the console and, when the --createLogFiles flag is set, to a timestamp-named log file in the current directory.

To enable debug logs, set the LOG_LEVEL env var to debug.