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

@rianbotha/coverage-summary

v2.0.0

Published

Summarizes istanbul coverage report for specified folders.

Readme

Coverage Summary

Summarize istanbul coverage report for specific folders

Installation

npm install @rianbotha/coverage-summary -g

Usage

coverage-report <filename> [options]

Example

coverage-report ./clover.xml --config ./.coverage-summary.js

Example output

Summary for report generated on 19/11/2019, 08:02:31
┌───────────┬─────────┬───────┬────────────┐
│ Section   │ Covered │ Lines │ Coverage % │
├───────────┼─────────┼───────┼────────────┤
│ All Files │    8087 │ 10215 │     79.17% │
│ Account   │     148 │   174 │     85.06% │
│ Checkout  │     465 │   869 │     53.51% │
└───────────┴─────────┴───────┴────────────┘

Filename

Path to a clover.xml report generated by Istanbul

Options

Config

Path to a config file. If no config file is supplied, you will only get a summary for All Files.

It should be in the following format:

module.exports = {
  bundles: [
    {
      path: ['src/bundles/account', 'src/bundles/other],
      name: 'Account',
    },
    {
      path: ['src/bundles/checkout'],
      name: 'Checkout',
    },
  ],
  threshold: [50, 75],
};

Each bundle should contain a path. This is an array of starting paths for parts of the report to summarize together. src/sample will combine coverage numbers for src/sample and any sub-directories eg. src/sample/component

name is optional and will be used in the summary table. The first entry in path will be used if name is not defined.

threshold is used to colour code percentage values. Anything below the first number will be red. Below the second number will be yellow. And above the second number will be green. The default value is [50, 75].

Limitations

Coverage can only be tracked at folder level. You can't summarize based on individual files.