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

@devchecks/depcheck

v0.1.0

Published

Check npm, Yarn and pnpm lockfiles or installed trees against the OSV vulnerability database, with fixed-version guidance and severity thresholds.

Downloads

149

Readme

@devchecks/depcheck

Reports known vulnerabilities in your dependencies, with the version that fixes each one. It uses OSV.dev, which aggregates the GitHub Advisory Database, OpenSSF malicious-package reports and other sources, so there is no vulnerability database of its own to go stale.

CLI

npx @devchecks/depcheck                      # auto-detects package-lock.json, pnpm-lock.yaml or yarn.lock
npx @devchecks/depcheck --installed          # check what is actually in node_modules
npx @devchecks/depcheck --production --fail-on critical -f sarif -o depcheck.sarif
npx @devchecks/depcheck --npm-audit audit.json   # convert existing `npm audit --json` output instead

| Option | | |---|---| | -l, --lockfile <file> | lockfile to check | | --installed | walk node_modules (npm, Yarn classic and pnpm layouts) | | --production | skip packages only reachable through devDependencies | | -s, --min-severity <lvl> | hide findings below this level | | --fail-on <lvl> | exit 1 at or above this level (default high) |

Supported inputs: package-lock.json / npm-shrinkwrap.json (v1–v3), yarn.lock (classic and Berry), pnpm-lock.yaml (v5, v6, v9), and npm ls --all --json output.

Each finding includes the advisory id (GHSA, or MAL for malicious packages), severity (from the advisory, else computed from the CVSS v3 vector), fixed version, aliases (CVE ids), and a hint for transitive dependencies (overrides / resolutions). Malicious packages are always critical.

Configuration: .depcheckrc.json

{
  "failOn": "high",
  "production": true,
  "ignore": [
    { "id": "CVE-2024-12345", "package": "some-lib", "reason": "not reachable: server-only code path", "expires": "2026-12-31" }
  ]
}

Ignores expire, so accepted risk is reviewed again.

API

import { checkLockfile, parseLockfile, checkDependencies } from '@devchecks/depcheck';
import { checkProject } from '@devchecks/depcheck/node';

const findings = await checkLockfile(lockfileText, { filename: 'package-lock.json', production: true });

The OSV API allows CORS, so the CDN build works from a page:

<script src="https://cdn.jsdelivr.net/gh/ravikiran476/[email protected]/cdn/depcheck.min.js"></script>
<script>DepCheck.checkLockfile(text).then(console.table)</script>

Package names, versions and nothing else are sent to api.osv.dev.