semver/semver resource
Semantic Versioning Specification observed · 2026-08-28
Health v2 · maintenance only
45/100
- Activity 50
- Release rhythm 8
- Longevity 100
Flags: no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5575
- days_rel: n/a
- days_push: 301
- n_releases_24m: 0
Adoption not part of the score
7842 stars · 777 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
The canonical Semantic Versioning (SemVer) specification, a set of rules dictating how software version numbers are assigned and incremented. It is a reference document published at semver.org rather than executable software.
Use cases
- understand how semantic version numbers work
- decide when to bump major vs minor vs patch versions
- cite a standard for versioning a library's releases
- resolve arguments about pre-release and build metadata version formats
- adopt a versioning convention for an open-source project
When to choose
- you need the authoritative definition of SemVer 2.0.0 to reference or implement
- you are designing tooling that parses or validates version strings
When to avoid
- you need a library or CLI that actually parses and compares versions in a specific language
- you need an alternative scheme like CalVer or zero-based versioning
Facets
learning-resource · maturity stable
documentation version-control developer-tools developer-tools version-control documentation specification semantic-versioning semver standards reference-document web-server
1 source
- readme: https://github.com/semver/semver · fetched 2026-08-28 · bb5eb4cbf91d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| semver/semver | main | 45 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem