Semver Validator
Validate a batch of semantic versions or npm ranges. Find malformed identifiers, duplicates and out-of-order versions, or check a version against each range locally.
Check Prerelease Order and npm Range Matches
Find & replace in input
Undo: Ctrl/Cmd+Z · Redo: Ctrl/Cmd+Shift+Z or Ctrl+Y. Up to 20 steps and 4 million retained characters in this tab. Clear discards history.
Semver Validator: how to use it
- Choose strict SemVer versions or npm ranges. Paste one entry per line or open a UTF-8 version list.
- Choose an expected order for versions. For ranges, optionally enter a version to compare and decide whether all prereleases are eligible.
- Validate the list, review errors and duplicate lines, then download a JSON report or the sorted valid versions.
Limits and notes
Up to 1,000 lines or 100,000 characters. Strict versions allow 256 characters and compare numeric identifiers exactly. npm ranges allow 512 characters and use npm's numeric and prerelease rules.
How your privacy works →Semver Validator: common questions
Is v1.2.3 a strict SemVer version?
Enter 1.2.3 in strict mode. A version-control tag may use a leading v before the underlying version string.
Why do two versions with different build metadata tie?
Build metadata distinguishes builds but does not affect SemVer precedence. The sorted list preserves the pasted order of ties.
When does an npm range match a prerelease?
By default, npm only admits a prerelease through a comparator on the same major, minor and patch tuple. Use the prerelease option to include additional eligible prereleases.