validator

13.15.35 · 2 Apr 2026MIT35M / weekRepository npm Atom feed

Upgrading validator From 10.11.0 to 11.0.0

Same major only

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 10.11.0Clears its 3 advisories13.15.22 Latest13.15.35

The note of 11.0.0 lists no breaking change or deprecation, which is rare for a major.

10.11.0yours
11.0.0target

?
changes to make: 0
advisories fixed: 2
new: 0
fixes

Security

3 advisories still affect 11.0.0

validator.js has a URL validation bypass vulnerability in its isURL functionmoderate · GHSA-9965-vmph-33xx
Inefficient Regular Expression Complexity in validator.jsmoderate · GHSA-qgmg-gppg-76g5
Validator is Vulnerable to Incomplete Filtering of One or More Instances of Special Elementshigh · GHSA-vghf-hv5q-vc2g

Upgrading to 13.15.22 clears them.

Release by release

11.0.0
23 May 20192 new
- new
  Added a isBase32() validator
- new
  New and improved locales (#999, #1010, #1017, #1022, #1031, #1032)

3 other lines we could not sort, mostly version bumps

Updated isEmail() to validate display names according to RFC2822
11.0.0
Updated isEmail() to check total email length
11.0.0
The internal toString() util is no longer exported (0277eb)
11.0.0

Upgrade to 11.0.0

npm install validator@11.0.0

What 11.0.0 needs

Reading 11.0.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 11.0.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
3 advisories still affect 11.0.0.