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

@victor-software-house/is-node-vulnerable

v1.0.1

Published

TypeScript-based Node.js security vulnerability checker with Zod validation and bundled security data

Readme

Node.js Security Vulnerability Checker

TypeScript-based Node.js security vulnerability checker with Zod validation and bundled security data.

Based on is-my-node-vulnerable but fully typed and properly structured.

Features

  • TypeScript: Full type safety with comprehensive type definitions
  • Zod Validation: All external JSON data validated with Zod schemas
  • Bundled Data: Security data included with package, no network calls at runtime
  • Daily Auto-Updates: Data automatically updated via GitHub Actions
  • Platform-Specific: Checks platform-specific vulnerabilities
  • Modular: Clean separation of concerns

Installation

npm install @victor-software-house/is-node-vulnerable
# or
pnpm add @victor-software-house/is-node-vulnerable

Usage

As CLI

# Check current Node.js version
npx @victor-software-house/is-node-vulnerable

# With debug output
DEBUG=1 npx @victor-software-house/is-node-vulnerable

# Skip check (emergency)
SKIP_NODE_SECURITY_CHECK=1 node index.js

As Module

import {
	isNodeVulnerable,
	isNodeEOL,
} from '@victor-software-house/is-node-vulnerable';

// Check if a specific version is vulnerable
const vulnerable = isNodeVulnerable('v20.10.0', 'darwin');
console.log(vulnerable); // false

// Check if a version is end-of-life
const isEOL = isNodeEOL('v16.0.0');
console.log(isEOL); // true

In Package Scripts

{
	"scripts": {
		"prebuild": "@victor-software-house/is-node-vulnerable",
		"check:security": "DEBUG=1 @victor-software-house/is-node-vulnerable"
	}
}

API

isNodeVulnerable(version: string, platform?: Platform): boolean

Check if a Node.js version is vulnerable to known CVEs.

Parameters:

  • version: Node.js version (e.g., "v20.10.0", "18.0.0")
  • platform: Optional platform ("darwin", "linux", "win32", etc.)

Returns: true if vulnerable or EOL, false otherwise

isNodeEOL(version: string): boolean

Check if a Node.js version is end-of-life.

Parameters:

  • version: Node.js version (e.g., "v16.0.0")

Returns: true if EOL, false otherwise

Data Source

Security data is bundled with the package and automatically updated daily via GitHub Actions:

Data is synchronized daily at midnight UTC. For the latest security updates, use the most recent package version.

Exit Codes (CLI)

  • 0 - Node.js version is secure
  • 1 - Node.js version is vulnerable or EOL
  • 2 - Check failed (unexpected error)

Environment Variables

  • DEBUG=1 - Enable debug logging
  • SKIP_NODE_SECURITY_CHECK=1 - Skip security check (emergency use only)

License

MIT © Victor Araújo

Credits

Based on is-my-node-vulnerable by Rafael Gonzaga.