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

@rio-cloud/audit-filter

v1.0.0

Published

Filters npm audit JSON output using project-local audit exclusions

Readme

RIO Audit Filter

Filters npm audit --json output using project-local exclusions from package.json.

Usage

Install this package as a development dependency:

npm install --save-dev --save-exact @rio-cloud/audit-filter

Add an audit script to the consuming project where you feed the JSON output of your npm audit call to the filter. You can fine-tune which parts end up in the audit report, e.g. with --omit=dev if you don't want to see vulnerabilities in your devDependencies. You can (and should) also pass in your desired

// in your package.json:
{
  // ...
  "scripts": {
    // ...
    "audit": "npm audit --registry https://registry.npmjs.org --json | rio-audit-filter --audit-level=moderate"
  }
}

rio-audit-filter exits with:

  • 0 when no vulnerabilities at or above the configured audit level remain after filtering
  • 1 when vulnerabilities at or above the configured audit level remain
  • 2 when stdin, CLI options, or package.json exclusions are invalid

Informational messages about used or unused exclusions are written to stdout. Warnings about detected vulnerabilities and outdated exclusions are written to stderr. When --json is given and vulnerabilities remain, the filtered audit JSON is also written to stderr.

Exclusions

Exclusions live in the consuming project's package.json under rioAuditFilterExclusions.

Each entry needs a package value, a non-empty description value, and a suppressedOn value. Such vulnerabilities are only hidden while suppressedOn is within the grace period. By default, that grace period is 14 days.

{
  // ... in your package.json
  "rioAuditFilterExclusions": [
    {
      // Vulnerabilities from npm package should be ignored.
      "package": "brace-expansion",

      // Describe WHY this exclusion exists.
      "description": "The vulnerability is not affecting us because we do not allow arbitrary input to reach it. brace-expansion is a bundled dependency which we cannot control.",

      // RFC 9557 date string, i.e. YYY-MM-DD. Excluded vulnerabilities re-surface after a grace period.
      "suppressedOn": "2026-05-30"
    }
  ]
}

Use ISO calendar dates in YYYY-MM-DD format. The value must not be more than one day in the future.

CLI Options

rio-audit-filter --help
rio-audit-filter --audit-level high
rio-audit-filter --grace-period-days 7
rio-audit-filter --json

The --audit-level option accepts info, low, moderate, high, and critical. The default is moderate.

The --grace-period-days option accepts only positive integers. The default is 14.

The --json option writes the filtered audit report to stderr when vulnerabilities remain.