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

docaudit

v0.0.5

Published

Audit documentation code coverage.

Readme

Docaudit

Audit documentation code coverage.

To install Docaudit:

npm install --global docaudit

And to audit a file:

docaudit README.md

Docaudit will scan the directory for .MD or .MDX files and check the content of each file for two attributes:

  • Any headings that are marked as code spans
  • A code block containing npm install OR the title of the document

With that information, Docaudit will download the npm package identified in the markdown file and scan the package exports. If an export has a corresponding heading in the markdown file, Docaudit will mark the export as documented (aka "yes"). If not, it will mark the export as undocumented (aka "no").

Docaudit logs a summary of findings to the console and saves a timestamped report as JSON in the directory.

Commands

docaudit

docaudit [<filePath> | <folderPath>]

Audit a file or folder. By default, Docaudit will scan the folder where it is executed. If it receives a <filePath>, it will only audit the specified file. If it receives a <folderPath>, it will audit the contents of that folder.