SemVer filter

semver-filter · version 1.0.0 · Versions & config · free, no key needed

Filter strict versions that satisfy a range, preserving original order and strings.

Use when you need to: semver filter · filter versions by range · select matching semver.

Supported

• semver filter
• filter versions by range
• select matching semver

Not supported

• sort
• loose
• npm lookup

Behavior

• Each versions item must be a strict SemVer. range as semver-satisfies.
• Return the original strings that satisfy, original order, no sort.
• include_prerelease defaults false. Max 5000 versions.

Input

• versions (array of string, required): max items 5000; each min length 1; each max length 256
• range (string, required): min length 1; max length 512
• include_prerelease (boolean, optional)

Output

• versions (array of string, required)

Limits

• max versions: 5000
• max version length: 256
• max range length: 512

Example

Request input:

{
  "versions": [
    "1.0.0",
    "2.0.0",
    "1.5.0"
  ],
  "range": "^1.0.0"
}

Response:

{
  "result": {
    "versions": [
      "1.0.0",
      "1.5.0"
    ]
  }
}

How to call it

MCP

Connect https://computefirst.net/mcp (setup), then call execute with:

{
  "id": "semver-filter",
  "version": "1.0.0",
  "input": {
    "versions": [
      "1.0.0",
      "2.0.0",
      "1.5.0"
    ],
    "range": "^1.0.0"
  }
}

HTTP (no key)

curl -X POST https://computefirst.net/v1/tools/semver-filter/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"versions":["1.0.0","2.0.0","1.5.0"],"range":"^1.0.0"}'

The machine-readable contract is at /v1/tools/semver-filter/versions/1.0.0.

CLI

node cli.mjs run semver-filter 1.0.0 --input input.json --base-url https://computefirst.net

Get the client at /clients/cli/.

Related tools

• SemVer sort: Sort strict valid Semantic Versions in ascending precedence order.
• SemVer compare: Compare two strict Semantic Versions by precedence.
• SemVer satisfies: Test whether a strict version satisfies a semver range.
• .env merge: Overlay two dotenv-subset documents, replacing left values and appending right-only keys.
• .env parse: Parse a strict dotenv-subset document into ordered key/value entries.
• .env stringify: Serialize unique env key/value entries to a canonical dotenv-subset document.