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

mdlint

v0.1.0

Published

Lints markdown files to find JavaScript syntax errors

Readme

mdlint

Lint JavaScript code blocks in markdown files to find syntax errors.

Installation

npm install -g mdlint

Usage

mdlint is used as a command-line utility. You lint a set of local markdown files matched by a glob, a GitHub repository's README, or query the GitHub API to go bounty hunting for syntax errors.

mdlint <command> <arg(s)> [options]

Commands:

repo  <user/repo>            lints a README from a GitHub repo
glob  <fileGlob>             lints local markdown files that match a file glob
query <queryString> [page]   lints READMEs from repos returned by a GitHub query

Options:

-s, --silent   only report failing lints
-h, --help     output usage information
-V, --version  output the version number

Here is an example of mdlint being run on a GitHub repo's README file:

mdlint repo ChrisWren/grunt-pages

Here is an example of mdlint being run on a set of local files:

mdlint glob docs/*.md

Here is an example of mdlint being run on a collection of READMEs returned from the grunt GitHub repositories search query:

mdlint query grunt

Accepted Psuedocode

mdlint accepts certain pre-defined psuedocode which it will preprocess so that an error isn't thrown during syntax validation.

Object pseudocode

gruntplugin: {
  
}
{
  key: 'value'
}

Function pseudocode

function () {
  
}

Changelog

0.0.0 - Initial Release.