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

readme-score-cli

v1.0.0

Published

Score any README.md for completeness and quality. Checks title, badges, install instructions, usage examples, API docs, contributing guide, license, and more.

Downloads

105

Readme

readme-score-cli

npm version License: MIT

Score any README.md for completeness and quality. Get instant feedback on what's missing and how to improve your project documentation.

A CLI tool that analyzes README files and scores them across 10 key sections, giving you an overall grade (A+ to F) with actionable suggestions for improvement.

Table of Contents

Installation

npm install -g readme-score-cli

Or use with npx:

npx readme-score-cli .

Usage

Score a local README

# Score README in current directory
readme-score .

# Score a specific file
readme-score ./path/to/README.md

Score a GitHub repo

# Using owner/repo format
readme-score facebook/react

# Using full URL
readme-score https://github.com/expressjs/express

JSON output (for CI)

readme-score . --json

Quiet mode (just the number)

readme-score . --quiet
# Output: 73

Scoring Criteria

Each section is scored 0-10 points (100 total):

| Section | What's Checked | |---------|---------------| | Title | Clear H1 heading, proper length, description below | | Description | Word count, clarity, presence of key info | | Badges | npm version, CI status, license, coverage, downloads | | Installation | Code blocks, package manager commands, context | | Usage Examples | Multiple code examples, detailed explanations | | API Documentation | Code samples, parameter tables, completeness | | Contributing Guide | PR workflow, setup commands, code of conduct | | License | License type specified, LICENSE file linked | | Screenshots/GIFs | Visual demos, multiple images, animated demos | | Table of Contents | Navigation links, section coverage |

Options

| Flag | Description | |------|-------------| | -j, --json | Output results as JSON | | -q, --quiet | Only output the score number (0-100) | | --no-suggestions | Hide improvement suggestions | | -V, --version | Show version number | | -h, --help | Show help |

CI Integration

Use readme-score in your CI pipeline to enforce documentation quality:

# GitHub Actions
- name: Check README quality
  run: |
    npx readme-score-cli . --quiet
    # Exits with code 1 if score < 50%

The CLI exits with code 1 if the score is below 50%, making it easy to use as a quality gate.

Contributing

Contributions are welcome! Please follow these steps:

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/my-feature
  3. Install dependencies: npm install
  4. Make your changes in src/
  5. Build: npm run build
  6. Test locally: node dist/index.js .
  7. Submit a pull request

License

MIT License - see LICENSE for details.