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

buggiest-files

v1.0.1

Published

Find the files in your github repo that have caused the most bugs.

Readme

Buggiest Files

Find the files in your github repo that have caused the most bugs.

Usage

npx buggiest-files get

gets the buggiest files in a repo

Options:
  --version   Show version number                                      [boolean]
  --help      Show help                                                [boolean]
  --token     your github personal access token (required for private repos or
              if you run into rate limits)                              [string]
  --owner     the owner of the repo                          [string] [required]
  --repo      the name of the repo                           [string] [required]
  --bugLabel  the label used to tag issues as bugs     [string] [default: "bug"]

Example

Here's an example of the code running on the react repo:

npx buggiest-files get --owner facebook --repo react --token 04460bce703eba0176c8fef21d36b4d64dbdd11a --bugLabel "Type: Bug"

[
  {
    "file": "packages/react-reconciler/src/ReactFiberCommitWork.js",
    "total": 3,
    "bugs": [
      "https://github.com/facebook/react/issues/14811",
      "https://github.com/facebook/react/issues/13512",
      "https://github.com/facebook/react/issues/13188"
    ]
  },
  {
    "file": "packages/eslint-plugin-react-hooks/__tests__/ESLintRuleExhaustiveDeps-test.js",
    "total": 2,
    "bugs": [
      "https://github.com/facebook/react/issues/18985",
      "https://github.com/facebook/react/issues/18902"
    ]
  },
  {
    "file": "packages/eslint-plugin-react-hooks/src/ExhaustiveDeps.js",
    "total": 2,
    "bugs": [
      "https://github.com/facebook/react/issues/18985",
      "https://github.com/facebook/react/issues/18902"
    ]
  },
  ...
]

How it works

The script associates a file with a bug if there's a commit that references a github issue labelled with the label specified by the bugLabel option.