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

readme-doctor

v0.1.1

Published

Lint + auto-fix your README to make repos enterprise-ready. CLI + GitHub Action.

Readme

README Doctor

Make your repo look enterprise-ready in minutes. A tiny CLI + GitHub Action that lints and auto-fixes README.md: badges, quick start, usage, config, CI, security, license, and more.

CI Release npm License: MIT


Table of contents


Overview

readme-doctor scores your README on the sections teams expect (badges, quick start, usage, config, CI, security, contributing, license, ToC, roadmap, FAQ), prints suggestions, and can auto-append missing sections in a safe, idempotent way.


Quick start

CLI

# check (no changes)
npx readme-doctor check

# fail CI if score below 80
npx readme-doctor check --fail-below 80

# write missing sections (idempotent, adds markers)
npx readme-doctor fix

GitHub Action

name: README Doctor
on: [push, pull_request]
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx readme-doctor check --fail-below 80

Usage

Run against the README in the current repo (defaults to README.md):

# Basic check
npx readme-doctor check

# Specify a different file
npx readme-doctor check --path DOCS.md

# Enforce minimum score (non-zero exit if below)
npx readme-doctor check --fail-below 90

# Auto-append missing sections between markers (no overwrite)
npx readme-doctor fix

What gets added on fix:

  • Sections are appended between markers like:
    <!-- readme-doctor:start:SECTION --> … <!-- readme-doctor:end:SECTION -->
  • Re-running fix won’t duplicate sections.

Configuration

Create readme-doctor.config.json in the repo root (all fields optional):

{
  "path": "README.md",
  "minScore": 80,
  "sections": {
    "title": true,
    "badges": true,
    "install": true,
    "quickstart": true,
    "usage": true,
    "config": true,
    "ci": true,
    "security": true,
    "license": true,
    "contributing": true,
    "toc": true,
    "roadmap": true,
    "faq": true,
    "altImages": true,
    "links": true
  }
}

CI

This repo includes a minimal CI workflow that runs the doctor on pushes/PRs:

name: readme-doctor CI
on: [push, pull_request]
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx readme-doctor check --fail-below 80

Tip: make this check Required on your protected branches.


Security

See SECURITY.md for how to report vulnerabilities. No telemetry and no network calls: the CLI only reads your README and optional config.


Contributing

Contributions welcome! Please see CONTRIBUTING.md and follow the zero-dependency guideline (Node ≥ 18). If you add checks, document the scoring and include a template for fix.


License

MIT © README Doctor contributors


Roadmap

  • [ ] Score badge endpoint (shields-style) to display README score
  • [ ] Link checker with per-section hints
  • [ ] Language-specific install snippets (npm/pip/brew/go)
  • [ ] Optional auto-generate ToC

FAQ

Does it overwrite my README?
No. check is read-only. fix appends curated sections at the end between markers and won’t duplicate content.

Can I disable sections?
Yes—set sections.<name> to false in readme-doctor.config.json.

Why fail in CI?
Docs are part of DX. A threshold prevents regressions and keeps repos adoption-ready.

How do I add it quickly to any repo?
Add the CI step above and run npx readme-doctor fix once locally to scaffold missing sections.