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

isvalid-legacy

v1.4.6

Published

Fork isvalid 1.6.7 - Patch merge 1.2.2 CVE (Prototype Pollution) The Unkillable Fork

Readme

🚀 isvalid 1.6.7 - The Unkillable Fork 🏴‍☠️

💀 Because Updating Code is for the Weak 💀

So, you’ve got a 10-year-old codebase held together by duct tape, dreams, and a million custom validations? Guess what? SAME.

This is a patched fork of [email protected], which originally depended on the infamously insecure [email protected]. We fixed that mess by upgrading to [email protected] and removing the risky deep merge operation.

Updating to a new library? Nah. Refactoring millions of validations? LOL, NO.

If you’ve found this repo, chances are:
✅ You’re stuck with legacy code.
✅ You have no time, energy, or patience to rewrite everything.
✅ You just want it to work without security nightmares.

Well, congratulations! You don’t have to choose between security and sanity. This patched version lets you keep using isvalid without getting wrecked by prototype pollution attacks.


🛠 What’s Changed?

  • 🔒 Fixed the CVE in [email protected] by upgrading to [email protected]
  • ⚡ Removed deep merging in lib/schema.js
    • Before:
      var formalizedSchema = merge(true, schema);
    • After:
      let formalizedSchema = {};
      for (let key in schema) {
          formalizedSchema[key] = schema[key];
      }
  • 🦾 Keeps the [email protected] API (because breaking changes are evil)
  • 🚀 No refactoring required – drop it in and move on with your life

🚧 Installation

npm install isvalid-legacy

🤔 Why Not Just Upgrade?

Because:

  • Your code is older than some of team mates junior devs.
  • You have better things to do.
  • Touching this code might summon the demons of tech debt.

🛑 Disclaimer

This package is basically a band-aid on a time bomb. But hey, at least it's a patched time bomb.

🚀 Enjoy your legacy code—safely! 🏴‍☠️