REGEXVAULTv2.0
Dev & Systems/SemVer
Verified Safe

SemVer Comparison Operator Range Regex for Go

/^(?:>=?|<=?|=)(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(?:-((?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*)(?:\.(?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*))*))?$/

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching semver comparison operator range, ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

Go
// SemVer Comparison Operator Range
// ReDoS-safe | RegexVault — Dev & Systems > SemVer

package validation

import "regexp"

var semverComparisonOperatorRangeRe = regexp.MustCompile(`^(?:>=?|<=?|=)(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(?:-((?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*)(?:\.(?:0|[1-9][0-9]*|[0-9]*[a-zA-Z\-][a-zA-Z0-9\-]*))*))?$`)

func ValidateSemverComparisonOperatorRange(s string) bool {
    return semverComparisonOperatorRangeRe.MatchString(s)
}

// Example
// fmt.Println(ValidateSemverComparisonOperatorRange(">=1.2.3")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
>=1.2.31.2.3
<=2.0.0~1.2.3
>0.0.1^1.2.3
<1.0.0=>1.2.3
=1.0.0>=1.2
>=1.0.0-alpha>= 1.0.0

When to use this pattern

This pattern is drawn from the Dev & Systems > SemVer category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

=> is not a valid operator. Only >=, <=, >, <, = are valid.

Technical Notes

Spaces between the operator and version are not allowed. Ranges can be combined with space (AND) or || (OR) — parse and validate each component separately.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern