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

bun-scan

v1.1.2

Published

Vulnerability scanner for Bun projects

Readme

Bun-Scan

A security scanner for Bun that checks packages for known vulnerabilities during installation.

Features

  • Real-time Scanning: Checks packages against configured sources (OSV, npm, or both) during installation
  • Whitelists: Specific warnings can be ignored
  • Fail-safe: Can configure non-critical advisories to not prevent installations

Installation

# Install as a dev dependency
bun add -d bun-scan

Add to your bunfig.toml:

[install.security]
scanner = "bun-scan"

Select your source from npm, osv (default), or run checks against both by setting up your config in .bun-scan.config.json

Note to set the schema version in the URL to the correct version:

{
  "$schema": "https://raw.githubusercontent.com/rawtoast/bun-scan/v1.1.0/schema/bun-scan.schema.json",
  "source": "npm"
}

Ignoring Vulnerabilities

A package may have a vulnerability, but your project is not affected. In this scenario, you would not want installations to be prevented. To work around this, the vulnerability can be flagged as ignored in your .bun-scan.config.json

{
  "$schema": "https://raw.githubusercontent.com/rawtoast/bun-scan/v1.1.0/schema/bun-scan.schema.json",
  "source": "npm",
  "packages": {
    "hono": {
      "vulnerabilities": ["CVE-2026-22818"],
      "reason": "Project does not use JWT from hono, verify again in June",
      "until": "2026-06-01"
    }
  }
}

Note that bunReportWarnings can be set false to print warning-level advisories without triggering Bun's install prompt:

{
  "bunReportWarnings": false
}

Advisory Levels

Fatal (Installation Blocked)

  • CVSS Score: ≥ 7.0 (High/Critical)
  • Database Severity: CRITICAL or HIGH
  • Action: Installation is immediately blocked

Warning (User Prompted)

  • CVSS Score: < 7.0 (Medium/Low)
  • Database Severity: MEDIUM, LOW, or unspecified
  • Action: User is prompted to continue or cancel

License

MIT License - see the LICENSE file for details.

Acknowledgments

  • maloma7: For the original implementation of the Bun OSV Scanner

Related Projects