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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fix-react-2-shell

v1.0.6

Published

Fix the React 2 Shell vulnerability (CVE-2025-66478) in Next.js apps with one command

Readme

react-2-shell

One command to fix CVE-2025-66478 (React 2 Shell RCE) in your Next.js / React RSC app.

npx react-2-shell

No AI. No magic. Just deterministic version bumps per the official advisories.

What it does

  1. Recursively scans all package.json files (handles monorepos)
  2. Checks for vulnerable versions of:
    • next
    • react-server-dom-webpack
    • react-server-dom-parcel
    • react-server-dom-turbopack
  3. Patches to the correct fixed version based on your current version
  4. Refreshes your lockfile with the detected package manager

Affected Versions

Next.js

| Current Version | Patched Version | |-----------------|-----------------| | 15.0.0 – 15.0.4 | 15.0.5 | | 15.1.0 – 15.1.8 | 15.1.9 | | 15.2.0 – 15.2.5 | 15.2.6 | | 15.3.0 – 15.3.5 | 15.3.6 | | 15.4.0 – 15.4.7 | 15.4.8 | | 15.5.0 – 15.5.6 | 15.5.7 | | 16.0.0 – 16.0.6 | 16.0.7 | | 15.x canaries | 15.6.0-canary.58 | | 16.x canaries | 16.1.0-canary.12 | | 14.3.0-canary.77+ | Downgrade to 14.3.0-canary.76 or upgrade to 15.0.5 |

React RSC Packages

| Current Version | Patched Version | |-----------------|-----------------| | 19.0.0 | 19.0.1 | | 19.1.0, 19.1.1 | 19.1.2 | | 19.2.0 | 19.2.1 |

Usage

Check & Fix (Interactive)

npx react-2-shell

Auto-fix (CI / Non-interactive)

npx react-2-shell --fix

Check Only (Dry Run)

npx react-2-shell --dry-run

JSON Output (for scripting)

npx react-2-shell --json

Example Output

🔍 react-2-shell - CVE-2025-66478 vulnerability scanner

📂 Found 3 package.json file(s)

🚨 Found 2 vulnerable file(s):

  📄 package.json
     next: ^15.1.0 → 15.1.9

  📄 apps/web/package.json
     next: ^15.4.3 → 15.4.8
     react-server-dom-webpack: 19.1.0 → 19.1.2

🔧 Apply fixes? [Y/n] y

🔧 Applying fixes...

   ✓ Updated package.json
   ✓ Updated apps/web/package.json

📦 Package manager: pnpm
🔄 Refreshing lockfile...

$ pnpm install

✅ Successfully patched!
   Your project is no longer vulnerable to CVE-2025-66478.
   Remember to test your app and commit the changes.

Monorepo Support

The tool automatically finds all package.json files in your project, excluding:

  • node_modules
  • .next, .turbo, .vercel, .nuxt
  • dist, build, .output
  • coverage

Works with npm, yarn, pnpm, and bun workspaces.

Why No AI?

Fixing CVE-2025-66478 is purely a version bump - no code changes needed. The vulnerability is in React's flight protocol used by server components. Upgrading to the patched versions closes the RCE vector completely.

AI might help if the upgrade breaks your build, but that's a separate concern from security. This tool does one thing: patches the CVE deterministically.

Publishing

# 1. Publish main package first
npm publish

# 2. Publish alias packages (all depend on main)
cd packages/fix-react-2-shelll && npm publish   # typo (extra 'l')
cd ../fix-react-two-shell && npm publish        # alternate spelling
cd ../react-2-shell && npm publish              # short name
cd ../react-two-shell && npm publish            # short name alternate

The alias packages depend on the main package, so publish order matters.

References

License

MIT