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

@zweer/coverage-badge-readme

v1.2.2

Published

A small utility to apply your coverage badge on the README file

Readme

@zweer/coverage-badge-readme

npm version License: MIT

A simple CLI tool to automatically read your test coverage summary and inject an up-to-date Shields.io badge into your README.md.

Never manually update your coverage percentage again!

🤔 Why?

Keeping the coverage badge in your README synchronized with your latest test run can be a manual and error-prone task. This tool automates the process by reading the coverage-summary.json file generated by popular testing frameworks and updating a placeholder in your README.

⚙️ Prerequisites

Your testing framework must be configured to generate a coverage summary report in json-summary format.

For Jest, Vitest, or Istanbul/nyc, add json-summary to your coverageReporters configuration.

Example for jest.config.js or vite.config.ts:

// jest.config.js
module.exports = {
  // ... other configs
  coverageReporters: ['json-summary', 'text', 'lcov'],
};

This will generate the required coverage/coverage-summary.json file when you run your tests with the --coverage flag.

📦 Installation

You can install the package globally:

npm install -g @zweer/coverage-badge-readme

Or use it directly with npx without a global installation (recommended for CI environments):

npx @zweer/coverage-badge-readme --help

🚀 Usage

  1. Add your template badge in the README.md file, for example:

    # @zweer/utils
    
    ![Coverage Badge](https://img.shields.io/badge/coverage-100%25-brightgreen?style=flat)
  2. Run the CLI command after your tests have completed:

    npx coverage-badge-readme

Your README.md will be automatically updated:

![Coverage Badge](https://img.shields.io/badge/coverage-88%25-brightgreen)

🛠️ Options

| Option | Alias | Description | Default | Required | | :--- | :--- | :--- |:--- |:--- | | --readme-path | | Path to the README.md file. | ./README.md | No | | --coverage-path | | Path to the coverage-summary.json file. | ./coverage/coverage-summary.json | No | | --help | -h | Show the help menu. | | |

📄 License

Licensed under the MIT License.