Is semver healthy, maintained, and safe?
Mostly yes — semver is maintained, with a couple of watch-items rather than red flags.
The verdict
On the OSPulse health scale, semver lands at 70/100 — low risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — semver is maintained, with a couple of watch-items rather than red flags.
Its most recent release shipped on 19 June 2026 — 39 days ago — so development is clearly active. Across 119 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. 3 maintainers are listed on npm, so the project isn't hostage to any single contributor.
OSV lists 2 known advisories for semver, including 2 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, semver is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (2)
semver vulnerable to Regular Expression Denial of Service
Regular Expression Denial of Service in semver
Key facts
- Latest version
- v7.8.5
- Last release
- 19 June 2026 (39 days ago)
- Total releases
- 119
- First release
- 12 February 2011
- Package age
- 15.5 years
- Maintainers
- 3
- Known advisories
- 2
- Confidence
- High
Frequently asked
Is semver still maintained?
Yes — semver released as recently as 19 June 2026 (39 days ago), so it is actively maintained.
Does semver have known security vulnerabilities?
Yes — OSV lists 2 advisories for semver. See the advisory list on this page for the OSV/GHSA identifiers.
Is semver safe to use?
Mostly yes — semver is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 70/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
semver is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.