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

reachble

v0.1.3

Published

VEX generator for npm/JS/TS projects backed by reachability analysis

Readme

Reachble

Auto-generated VEX for npm projects, backed by reachability analysis.

Most CVEs flagged in your package-lock.json are not actually exploitable in your code. Research shows 60–80% sit in dependency code paths that are never called. SBOM mandates (US EO 14028, EU CRA) increasingly require a VEX statement explaining why each unaffected CVE is unaffected. Today that's a spreadsheet. Reachble produces it from your code.

npx reachble scan

Outputs CycloneDX VEX + OpenVEX with machine-checkable evidence: "vulnerable function never imported", "reachable but no path from any HTTP entry point", "reachable from unauthenticated POST /api/upload".

What's different

| | Traditional SCA | OSV-Scanner | Endor Labs | Reachble | |---|---|---|---|---| | CVE in lockfile detection | ✓ | ✓ | ✓ | ✓ | | Function-level reachability | | | ✓ | ✓ | | Attack-surface scoring (entry points) | | | ✓ | ✓ | | Auto-generates VEX | | | partial | | | Open source | varies | ✓ | | | | JS/TS specialization | | partial | partial | |

Verdict tiers

CRITICAL — reachable from unauthenticated external input
HIGH     — reachable from authenticated route or internal service
LOW      — reachable in code, no external input path found
SAFE     — vulnerable symbol never reached  → VEX `not_affected`

Install

npm install -g reachble
# or run directly
npx reachble scan

Usage

reachble scan                          # scan cwd, output table + VEX
reachble scan --path ./my-app          # specify project directory
reachble scan --format vex             # CycloneDX VEX output
reachble scan --format json            # JSON output
reachble scan --fail-on high           # exit 1 if any HIGH/CRITICAL found

Demo

A minimal Express app with two lodash CVEs side-by-side:

Package   Version   CVE              Verdict   CVSS   Reason
──────────────────────────────────────────────────────────────────────────
lodash    4.17.18   CVE-2020-28500   SAFE      5.0    Vulnerable symbol(s) not imported
lodash    4.17.18   CVE-2021-23337   LOW       7.5    Vulnerable symbol(s) imported at src/routes/render.ts:8

2 CVEs · 0 CRITICAL · 0 HIGH · 1 LOW · 1 SAFE
VEX written to reachble-vex.cdx.json

What it supports

  • Lockfiles: npm, yarn, pnpm
  • CVE data: OSV.dev, NVD, GHSA, EPSS scoring
  • Output formats: CycloneDX VEX, OpenVEX, JSON, table
  • CI integration: --fail-on high exits 1 when real threats are found

MIT. No telemetry. No tracking.