Strict SemVer · exact precedence

Separate version precedence from exact equality

Build metadata can change a string without changing SemVer precedence; both facts stay visible.

Open SemverCompare

No registry lookup · no dependency advice · no floating point

Three explicit steps

Enter, compare, reuse

01

Enter two strict versions

No v prefix, whitespace or missing core part.

02

Inspect both equality results

Exact strings and precedence can disagree because of build metadata.

03

Increment or sort

Derive core increments and stably sort up to 200 versions.

Version-string checks

Useful for release notes, fixtures and precedence review

  • Compare two prereleases.
  • Explain build-neutral precedence.
  • Sort a release fixture.
  • Generate the next core candidates.

Reproducible examples

Prerelease-order and build-metadata examples

Parse core, prerelease and build identifiers with BigInt, then compare, increment or sort locally.
View examples

SemVer 2.0.0 · strict syntax

Compare precedence without losing large integers

Parse core, prerelease and build identifiers with BigInt, then compare, increment or sort locally.

Open SemverCompare