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 🙏

© 2024 – Pkg Stats / Ryan Hefner




Test your Markdown files for Standard JavaScript Style™




standard-markdown Build Status

Test your Markdown files for Standard JavaScript Style™


npm install standard-markdown --save



This module works just like standard, but instead of linting javascript files, it lints GitHub-Flavored js and javascript code blocks inside markdown files.

Lint everything in the current directory:


Or lint some other directory:

standard-markdown some/other/directory

All files with .md or .markdown extension are linted, and the following directories are ignored:

  • .git
  • node_modules
  • vendor

If you want to specify which files to lint / which files to ignore you can use glob patterns

# This will lint everything in some/directory except everything in some/directory/api
standard-markdown some/directory **/*.md !api/**/*.md

# You also don't need to specify CWD to use globs
# This will only lint markdown file in the current directory
standard-markdown *.md


This module also provides the ability to automatically fix common syntax issues like extra semicolons, bad whitespacing, etc. This functionality is provided by standard.

standard-markdown some/directory --fix

Once the module has attempted to fix all your issues it will run the linter on the generated files so you can see how much it fixed.


This module disables certain rules that were considered inappropriate for linting JS blocks:

See #2, #18, and #19 for reasons.

For more examples of what is and isn't allowed, see the clean and dirty test fixtures.


npm install
npm test


  • commander: The complete solution for node.js command-line programs
  • globby: Extends glob with support for multiple patterns and exposes a Promise API
  • standard: JavaScript Standard Style

Dev Dependencies

  • tap-spec: Formatted TAP output like Mocha's spec reporter
  • tape: tap-producing test harness for node and browsers