Free tools

Free Semver Compare Tool

Compare semantic versions, detect major/minor/patch deltas, and validate range compatibility.

Copy-paste outputs

The autonomous growth engine for your business.

Brand Armor AI finds where your customers are, decides what to create, distributes it across the channels that matter, and learns from every result.

Discover customer opportunitiesPlan campaignsCreate posts, images, and videosPublish across channelsMeasure what worksAI search visibilityDiscover customer opportunitiesPlan campaignsCreate posts, images, and videosPublish across channelsMeasure what worksAI search visibility
Social publishingBlog and CMS deliveryEmail outreachAutopilot workflowsBrand IdentityWeekly reportsSocial publishingBlog and CMS deliveryEmail outreachAutopilot workflowsBrand IdentityWeekly reports
Shopping IntelligenceCompetitor AnalysisBrand IdentityShopping IntelligenceCompetitor AnalysisBrand Identity

Tool 01

Semver Compare Tool

Compare semantic versions and validate compatibility ranges for package releases.

Semver Compare Tool
Compare semantic versions and validate whether a version satisfies a range.
Comparison summary

1.12.0 is newer than 1.9.5.

Delta: major 0, minor 3, patch -5

Range match for Version A: Yes

{
  "versionA": "1.12.0",
  "versionB": "1.9.5",
  "relation": "newer than",
  "deltas": {
    "major": 0,
    "minor": 3,
    "patch": -5
  },
  "range": ">=1.8.0 <2.0.0",
  "versionASatisfiesRange": true
}

How it works

Semver Compare Tool: methodology and worked example

How this tool computes its result

Parses two version strings against a strict major.minor.patch regex (optional leading "v", optional -prerelease, optional +build metadata) and compares major, then minor, then patch numerically. If those three match, prerelease identifiers are compared segment by segment (numeric segments compared as numbers, string segments as strings), and a version with any prerelease tag always ranks below the same version with none. A separate range expression field is checked only against Version A: it supports space-separated comparators (>, >=, <, <=, =), ||-joined OR groups, and caret (^) / tilde (~) shorthand, both of which get expanded into an equivalent >=/< pair before evaluation.

Worked example

With the tool's defaults -- Version A "1.12.0", Version B "1.9.5", range ">=1.8.0 <2.0.0" -- the result reads "1.12.0 is newer than 1.9.5" with deltas major 0 / minor 3 / patch 5, and Version A satisfies the range. Changing the range to "^1.9.0" expands internally to ">=1.9.0 <2.0.0" before the same check runs.

When not to use this tool

Build metadata (the +xxx suffix) is parsed but never used in comparisons, so "1.0.0+abc" and "1.0.0+xyz" always compare equal -- correct per the semver spec, but worth knowing if you expected build tags to break ties.

Common mistakes

  • - Assuming a prerelease-tagged version (e.g. "2.0.0-beta") ranks above the plain release because it looks newer -- per the comparison logic, any version carrying a prerelease segment ranks below the same version with none.
  • - Typing a version with the wrong number of segments, like "1.2" or "1.2.3.4" -- the regex requires exactly three dot-separated numeric components, so anything else throws "Invalid semantic version" and blanks the whole comparison.
  • - Forgetting the range field only validates Version A -- entering a range and expecting a satisfies/doesn't-satisfy result for Version B too will not happen; only one Yes/No is shown, for A.

Ready to put your growth work on autopilot?

Connect your business once, then let Brand Armor AI find opportunities, create content, publish it, and learn from what brings customers in.