Skip to content

Main content
Bookmark this: tool.io/development/semver-build-identifier-format

Development: SemVer Build Identifier Format Tool

Inspect a single SemVer build-metadata identifier, where numeric leading zeros are allowed unlike prerelease numeric identifiers; no full-version parsing.

Loading tool…

Description

Inspect one build-identifier spelling.

Semantic versions separate core numbers, prerelease identifiers and build metadata. Numeric prerelease leading zeros are restricted while build identifiers preserve text; local identifier or bound checks do not implement complete dependency-range resolution.

Inspect one build-identifier spelling.

When to use this tool

Use Development: SemVer Build Identifier Format when checking one explicit version-token or core-bound convention.

How to use the tool and how it works

  1. Enter identifier. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Inspect one build-identifier spelling. valid checks nonempty ASCII alphanumeric/hyphen text; numericOnly checks digits and leadingZeroAllowed is always true.1

Numeric prerelease identifiers exclude leading zeros; build metadata identifiers can retain them and do not affect version precedence.2

Input fieldMeaning and unitsAccepted input
identifierIdentifierRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultReturned object; expand its named members below.Required. Object.
result.validValidCalculated result member: boolean.
result.numericOnlyNumeric OnlyCalculated result member: boolean.
result.leadingZeroAllowedLeading Zero AllowedCalculated result member: boolean.
json
{
  "input": {
    "identifier": "001"
  },
  "output": {
    "result": {
      "valid": true,
      "numericOnly": true,
      "leadingZeroAllowed": true
    }
  }
}

Limitations and assumptions

  • The policy flag does not mean invalid identifiers are valid; no complete build sequence is parsed.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use a conforming full version/range implementation and package-manager resolution when compatibility or installation is the question.

References

  1. Calculation and input contract: development/semver-build-identifier-format — tool.io

  2. Semantic Versioning 2.0.0 — Semantic Versioning

Similar or alternative tools

Support Tool.io