Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Mercurial
Long-running distributed VCS (2005), extensible in Python with Rust speedups; changeset evolution and topics add safe history rewriting. Basis for Sapling.
www.mercurial-scm.org/Active
mercurial 7.2.4 uploaded to PyPI 2026-08-11. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? community, foundation, or research (25% of 16 others)
- How does it relate to git repositories? own storage format, one-time import or no git interop (21% of 19 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? available, but not the main workflow (13% of 15 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (67% of 18 others)
- Who is it for? developers (90% of 20 others)
- Can you commit, branch, and read history with no network connection? yes (94% of 17 others)
- Is it designed with AI coding agents in mind? no (65% of 20 others)
- What is the basic unit of history? (pick the most specific that applies) snapshots (commits) with no identity that survives a rewrite (74% of 19 others)
- How are merge conflicts mainly handled? must be resolved before the merge or commit completes (65% of 17 others)
- What size of project is it designed for? ordinary source repositories (74% of 19 others)
Nearest neighbors
- Pijul 81% of 16 shared answers match
- Darcs 76% of 17 shared answers match
- Fossil 75% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | copyleft or source-available with restrictions GPL-2.0-or-later. | source 2026-10-25 |
| How is it mainly sustained? | stands apart community, foundation, or research Free community project run by steering committee and mailing lists; no revenue. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Local distributed VCS; no account. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Own format; git only via the hg-git extension. | source 2026-10-26 |
| How does it relate to git repositories? | stands apart own storage format, one-time import or no git interop Core has no git interop; the separate hg-git extension adds two-way interop. | source 2026-10-25 |
| Where does the authoritative copy of a project live? | every clone is a full peer; servers are optional | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | no | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the version control system itself | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | snapshots (commits) with no identity that survives a rewrite Changesets (snapshots); the evolve extension adds obsolescence markers. | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | stands apart available, but not the main workflow Possible with evolve/topics; not the default workflow. | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes | source 2026-10-25 |
| What size of project is it designed for? | ordinary source repositories | source 2026-10-25 |
| Is code review part of the product? | no review workflow Core has none; Heptapod (a GitLab fork) and Phabricator served this role. | source 2026-10-25 |
Sources
This page was derived from:
- Package registry · pypi.org/project/mercurial/ · read 2026-10-25
- Web page · www.mercurial-scm.org/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.