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

docdelta

v1.0.0

Published

Gives your documentation a check-up

Readme

docdr

Gives your documentation a checkup.

Usage

I created this tool to help me remember to keep README files up to date. If code has changed significantly since its corresponding README file was last updated, the README is probably overdue for a checkup.

$ npx docdr [directory_name]

Checking on the health of README.md files...

 86.63% ./account/activity
      ! ./app
      ! ./home/iframes
 59.79% ./home/widgets
      ! ./utilities/report

found 3 missing and 2 outdated READMEs

A percentage next to a directory means the directory has changed that much (according to Git) since its README.md file was last updated. You might want to give that README some attention!

A "!" next to a directory means the README.md file is missing altogether.

If any problems are found, docdr exits with code 1. Otherwise it exits with code 0, so you can add it to your build system.

Options

The --skipMissing flag causes docdr to ignore directories that don't have a README.md.

The --threshhold=n option sets the percent change you want to allow before a README is considered outdated (for example, --threshhold=5 allows up to 5% change).

Installation

Run directly without installing using npx:

npx docdr

Or install globally:

npm install -g docdr

Or install as a dev dependency and add docdr to the "scripts" section of your package.json:

npm install --save-dev docdr
{
  "scripts": {
    "docdr": "docdr --skipMissing --threshhold=5"
  }
}