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

pi-dep-audit

v1.0.1

Published

Audit npm dependencies for vulnerabilities, outdated packages, and license compliance — integrated into pi.dev workflow

Downloads

52

Readme

pi-dep-audit

Audit npm dependencies for vulnerabilities, outdated packages, and license compliance — integrated into your pi.dev workflow.

Features

  • CVE Scanning — queries OSV.dev for known vulnerabilities (no API key needed)
  • Outdated Detection — semver-aware severity classification (major/minor/patch)
  • License Compliance — detects copyleft licenses in permissive projects
  • Auto-Fix — bump vulnerable packages to safe versions automatically
  • Structured Output — JSON report for CI integration + human-readable summary

Install

pi install npm:pi-dep-audit

Or install from npm directly:

npm install pi-dep-audit

Usage

Slash Command

Type /audit in your pi.dev agent to run a full dependency audit:

> /audit

╔══════════════════════════════════════════════════════════════╗
║  📦 DEPENDENCY AUDIT REPORT
║  Project: my-awesome-app
║  2026-06-25T12:00:00.000Z
╚══════════════════════════════════════════════════════════════╝

🔒 VULNERABILITIES
────────────────────────────────────────
  ✅ No known vulnerabilities found

📊 OUTDATED PACKAGES
────────────────────────────────────────
  Total: 2 (1 major, 1 minor, 0 patch)

  🔴 lodash: 4.17.20 → 4.17.21 (patch)
  🟡 express: 4.18.0 → 4.18.2 (patch)

📜 LICENSES
────────────────────────────────────────
  Total packages: 42
  MIT: 38
  ISC: 3
  BSD-2-Clause: 1

Tools

The extension registers two tools for the LLM:

dep-audit

Run a full dependency audit:

// The LLM calls this when you ask about dependency health
"Check my dependencies for vulnerabilities"

dep-fix

Auto-fix vulnerabilities:

// The LLM calls this when you ask to fix issues
"Fix all dependency vulnerabilities"

Supports a dry_run parameter to preview changes without applying them.

How It Works

Vulnerability Detection

Uses the OSV.dev API — a free, open-source vulnerability database. Queries are made per-package-version, matching against the npm ecosystem.

Outdated Detection

Runs npm outdated --json and classifies version bumps:

  • Major (🔴) — breaking changes likely
  • Minor (🟡) — new features, backward compatible
  • Patch (🟢) — bug fixes only

License Compliance

Scans node_modules/*/package.json for license fields and flags:

  • Copyleft licenses (GPL, AGPL, LGPL) in permissive projects (MIT, BSD, ISC)
  • Unknown or unparseable licenses

Auto-Fix Strategy

  1. Security updates first — bump packages with known CVEs to their fix version
  2. Version updates second — apply non-breaking updates (wanted version)
  3. Reports successes and failures separately

Requirements

  • Node.js 18+
  • npm project with package.json
  • node_modules installed (for license scanning)

License

MIT