Is standard-version still maintained?
No — standard-version stopped being maintained around May 2022. commit-and-tag-version is a community fork that picked standard-version up and carried it on.
- Status
- No longer maintained
- Last maintained
- May 2022
- Use instead
commit-and-tag-version— on npm- Succession
- Maintained fork
- Drop-in
- yes — swap the import
- Confidence
- medium
Is there a maintained fork of standard-version?
commit-and-tag-version is a community fork that picked standard-version up and carried it on. commit-and-tag-version is close enough to a drop-in replacement that most projects only change the dependency and the import.
How to migrate from standard-version to commit-and-tag-version
commit-and-tag-version is a drop-in replacement: swap the dependency and change the npm script to commit-and-tag-version. Existing .versionrc / .versionrc.json files and the standard-version package.json config key are still read.
Why standard-version is on this list
standard-version's README declares the project deprecated, and its last release was 9.5.0 in May 2022. The maintainer's first recommendation is release-please for projects that can use GitHub Actions, and they point anyone who needs to stay on the same tool at the commit-and-tag-version fork, which is actively released and keeps the original CLI and configuration. Because the maintainer names two different destinations, which one is right depends on whether you want to keep the existing workflow.
The succession is well supported, but it is not the only defensible choice.
standard-version alternatives
Beyond the primary recommendation, these are credible for standard-version's use case:
release-please— view on npmsemantic-release— view on npmchangesets— view on npm
Check your own project for standard-version
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If standard-version is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.
Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.
Evidence
Every claim on this page traces to a primary source. Check them:
- standard-version README: "standard-version is deprecated", recommends release-please and names the forkgithub.com
- commit-and-tag-version README: "a fork of standard-version", drop-in migrationgithub.com
Packages related to standard-version
- colorsMaintained fork: @colors/colors · unmaintained since January 2022
- fakerMaintained fork: @faker-js/faker · unmaintained since January 2022
- eslint-plugin-nodeMaintained fork: eslint-plugin-n · unmaintained since March 2020
- uglify-esMaintained fork: terser · unmaintained since February 2018
- angularReimplementation: @angular/core · unmaintained since January 2022
See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.