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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@davidsneighbour/markdownlint-config

v2025.3.5

Published

Markdownlint configuration for use in @davidsneighbour projects.

Readme

Adds a configuration file for Markdownlint.

Usage with VSCode

Install the VSCode plugin Markdownlint by David Anson. Then add a local configuration file in .markdownlint.json or markdownlint.jsonc:

{
  "extends": "@davidsneighbour/markdownlint-config"
}

The filename, and -format can be any of the ones listed on the markdownlint-cli2 configuration page but my advice is to stay with JSON or JSONC.

Add local rule overrides:

{
  "extends": "@davidsneighbour/markdownlint-config",
  "MD040": false
}

The configuration differs from the default ruleset in the following points:

  • MD004 (unordered list style) is set to "consistent". That is by preference.
  • MD013 (line-length) is disabled. I find that today the editor can take care of line flow and having only 80 characters long lines breaks the ease of working with these files.
  • MD025 (single-title/single-h1) is disabled. The rule should be kept in mind, but every now and then multiple top level headlines are useful.
  • MD030 (list-marker-space) is disabled. There is no reason to have two spaces after list item markers.
  • MD041 (first-line-heading/first-line-h1) is disabled. Many README files might start with badges instead of headings.

Usage with CLI (or Lint Staged)

Additional tips for the work with Markdown

All configurations