Desktop Git clients for checking and committing your changes: GitComet, Nori, SourceGit, Fork and GitHub Desktop
GitComet gives you line staging, blame, interactive rebase and merge tools free and open source, with a clear privacy policy, though it is still before version 1.0. Nori, SourceGit and Fork follow close behind.
GitComet
Line staging, split and structural diffs, blame, interactive rebase and merge tools, free and open source with no account, a published privacy policy and signed Windows and Mac installers.
It launched in March 2026 and is still before version 1.0, one developer writes most of it, and it publishes no security policy.
Why GitComet is our PickTeam behind GitComet? Get your award badge
Nori
A free client launched in July 2026 by one developer in France, with line staging, file history, blame, interactive rebase with a preview, a conflict resolver and an undo for commits, branch deletions and discards.
It is four months old, one person maintains it, its own release notes record data-loss and security fixes in October, and on a Mac it needs Apple silicon with macOS 26 or later.
Why Nori earned Rising StarWho is this article for? Developers on a Mac or Windows computer who want a graphical Git client to check what changed, commit only what they intend, look back through history and resolve conflicts, on repositories they already have.
About 41 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Prices for use with private hosted repositories. Compare how you pick lines for a commit, what history and conflict tools each documents, and what each says about your data.
Prices checked November 12, 2026, in US dollars, before tax and promotions. GitComet, Nori, SourceGit and GitHub Desktop have no charge for this job; GitComet’s Pro client and Nori’s Pro edition add pull-request features and are not needed. Fork is a one-time licence for one user on up to three machines. Your hosting service is separate.
The comparison at a glance
Compare what each client lets you choose for a commit, the history and conflict tools it documents, what it costs with private repositories and what it says about your data.
Order follows our verdict for checking and committing changes on Mac or Windows: our Pick, our Rising Star, then the others. It is not measured speed or merge correctness. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | GitComet | Nori | SourceGit | Fork | GitHub Desktop |
|---|---|---|---|---|---|
| Best fit | Preferred Pick: a free, open-source client with line staging, blame, interactive rebase and merge tools, a published privacy policy and signed installers, if you accept a project launched in March 2026 and still before version 1.0 | Rising Star: a free client with no account, line staging, file history, blame, interactive rebase, a conflict resolver and a 30-day undo, if you accept a one-person project four months old and, on a Mac, Apple silicon with macOS 26 or later | Also consider: free, open source and the longest record of the free options, if you accept that its lead maintainer is handing the project over and its Mac download steps | Also consider: the fullest documented history and conflict tools, including reflog recovery, for a one-time licence | Also consider: everyday review and focused commits, free, open source, without an account and from a company that publishes security advisories |
| Price with private hosted repositories, checked November 12, 2026 | Free for personal and commercial use (AGPL-3.0). A separate Pro client for pull-request review costs EUR 4 a month billed annually and is not needed for this job | Free on public and private repositories, no account. Optional Pro, US$20 once, adds pull requests and issues | Free; MIT-licensed open source | US$59.99 once: one user, up to three Mac or Windows machines; free evaluation, purchase required for long-term use | Free; MIT-licensed open source |
| Official platforms | Windows (x86-64 and ARM64; signed installer; Microsoft Store), macOS (notarized; Apple silicon and Intel) and Linux (glibc 2.35 or newer) | macOS (Apple silicon, macOS 26 or later), Windows 10 and 11, and x86-64 Linux; uses the Git you install (2.30 or later) | Windows, macOS and Linux; needs Git 2.25.1 or later installed separately; its maintainer tests Linux only on Debian 12 | macOS and Windows | macOS and 64-bit Windows 10 or later; no Linux. September 2026 beta notes drop macOS 12 |
| Account to start | None for the free client; the Pro client uses a GitComet account | None | None | None mentioned on the purchase or licence pages; activation steps not published | None for local repositories; sign in only to connect GitHub |
| Choosing what goes into a commit | Files, hunks or selected lines; edit a file in place before staging | Hunks, single lines or a run of lines from the gutter; discards can be undone | Files, hunks or selected lines (stage, unstage or discard) | Stage and unstage line by line | Whole files or individual changed lines |
| Looking back through history | Per-file history, blame, five history views, search by message, author or SHA | File history that follows renames, blame, search by author, path, content, regex, date or hash, and a reflog listing | File and folder history that follows renames, blame, commit search, bisect | File and directory history, blame, repository tree at any commit | Commit history; file history view marked not planned by its maintainers; blame not documented |
| Conflict help without AI | Built-in 2-way and 3-way merge tools; warns before staging a file with conflict markers | Built-in resolver: your side and the incoming side with the result below; take a line, a block or a whole side; continue or abort at any step | Built-in conflict editor added in February 2026: take mine, theirs or both, then save and stage; or open an external merge tool | Built-in merge-conflict helper and resolver | No built-in merge editor documented |
| What the publisher says about your data | Open source; no account. Its privacy policy (updated November 11, 2026) says the client sends no usage analytics; update checks go to GitHub (on by default, can be turned off) and Markdown previews load remote images by default (can be changed) | No account. Its privacy policy (version dated October 16, 2026) says the app has no telemetry, analytics or crash reporting and that your code goes only to the Git remotes, hosts and AI tools you choose; update checks run once a day by default. We found no link to its source code, so these statements cannot be audited | Open source, no privacy policy. Settings and logs stay on your computer; its code fetches author pictures from Gravatar, using a hash of each author’s email, and from GitHub | No privacy policy; the developer said in 2024 that Fork gathers no customer data and has no telemetry, and declined to publish a formal policy | Open source; usage stats (counts and a pseudonymous ID) controlled in Preferences; Copilot features tracked separately |
Graphical Git clients for your own computer, used on repositories you already have. Public-source research: no installs, accounts, purchases or repository operations by us. All five work on ordinary Git repositories, so switching clients later needs no migration; settings, profiles and integrations do not carry over. AI features were given no weight. Next substantive review: December 18, 2026, or sooner after a price or licence change.
All features and sources 16 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Price, platforms and access
Show 7 criteria
| Feature | GitComet | Nori | SourceGit | Fork | GitHub Desktop |
|---|---|---|---|---|---|
| Best fit | Preferred Pick: a free, open-source client with line staging, blame, interactive rebase and merge tools, a published privacy policy and signed installers, if you accept a project launched in March 2026 and still before version 1.0 | Rising Star: a free client with no account, line staging, file history, blame, interactive rebase, a conflict resolver and a 30-day undo, if you accept a one-person project four months old and, on a Mac, Apple silicon with macOS 26 or later | Also consider: free, open source and the longest record of the free options, if you accept that its lead maintainer is handing the project over and its Mac download steps | Also consider: the fullest documented history and conflict tools, including reflog recovery, for a one-time licence | Also consider: everyday review and focused commits, free, open source, without an account and from a company that publishes security advisories |
| Price with private hosted repositories, checked November 12, 2026 | Free for personal and commercial use (AGPL-3.0). A separate Pro client for pull-request review costs EUR 4 a month billed annually and is not needed for this job | Free on public and private repositories, no account. Optional Pro, US$20 once, adds pull requests and issues | Free; MIT-licensed open source | US$59.99 once: one user, up to three Mac or Windows machines; free evaluation, purchase required for long-term use | Free; MIT-licensed open source |
| Official platforms | Windows (x86-64 and ARM64; signed installer; Microsoft Store), macOS (notarized; Apple silicon and Intel) and Linux (glibc 2.35 or newer) | macOS (Apple silicon, macOS 26 or later), Windows 10 and 11, and x86-64 Linux; uses the Git you install (2.30 or later) | Windows, macOS and Linux; needs Git 2.25.1 or later installed separately; its maintainer tests Linux only on Debian 12 | macOS and Windows | macOS and 64-bit Windows 10 or later; no Linux. September 2026 beta notes drop macOS 12 |
| Account to start | None for the free client; the Pro client uses a GitComet account | None | None | None mentioned on the purchase or licence pages; activation steps not published | None for local repositories; sign in only to connect GitHub |
| Continued use | Nothing to renew for the free edition | Nothing to renew; the maker says the free app never expires | Nothing to renew | No subscription; whether later major versions need a new purchase is not stated | Nothing to renew |
| Who makes it | AutoExplore Oy, a Finnish software company; one main developer | Quentin Hermiteau, a sole proprietor in France; one maintainer | A volunteer lead maintainer who publishes under a GitHub handle, with outside contributors; in September 2026 he announced he is handing the project over | Dan Pristupov and Tanya Pristupova; licence under Czech law | GitHub (Microsoft) |
| Latest release, checked November 12, 2026 | v0.3.4 (November 10, 2026); launched March 2026; before version 1.0 | 1.16.0 (November 9, 2026); first public release July 16, 2026; roughly weekly releases | 2026.24 (November 9, 2026); 24 releases so far in 2026. First release July 2020 for Windows; macOS since February 2024 | Mac 2.71 (October 23, 2026); Windows 2.24 (November 6, 2026); release notes start in 2016 | 3.6.10 (October 30, 2026) |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for price, platforms and access
Checked November 12, 2026: GitComet site and editions, Pro edition and releases; Nori pricing and release notes; SourceGit repository and README, releases, hand-over announcement and licence; Fork purchase, licence, Mac and Windows release notes; GitHub Desktop repository, releases and installation. Prices exclude tax and promotions.
Checking and reshaping changes
Show 7 criteria
| Feature | GitComet | Nori | SourceGit | Fork | GitHub Desktop |
|---|---|---|---|---|---|
| Choosing what goes into a commit | Files, hunks or selected lines; edit a file in place before staging | Hunks, single lines or a run of lines from the gutter; discards can be undone | Files, hunks or selected lines (stage, unstage or discard) | Stage and unstage line by line | Whole files or individual changed lines |
| Diff views | Split or inline; structural diffs with Difftastic; image, SVG and rendered Markdown diffs; search within a diff | Unified or split diffs with syntax colouring; image previews and whitespace visibility, per its release notes; one Stage button per hunk | Unified or side by side; ignore whitespace; show more lines or the whole file; image diffs side by side, swipe, blend or difference | Side-by-side text diffs and image diffs | Unified or split; hide whitespace; expand context or the whole file; image diffs |
| Looking back through history | Per-file history, blame, five history views, search by message, author or SHA | File history that follows renames, blame, search by author, path, content, regex, date or hash, and a reflog listing | File and folder history that follows renames, blame, commit search, bisect | File and directory history, blame, repository tree at any commit | Commit history; file history view marked not planned by its maintainers; blame not documented |
| Rewriting commits | Interactive rebase: drag to reorder; pick, reword, squash, fixup or drop; reset; revert merges | Interactive rebase: reorder, pick, reword, edit, squash, fixup or drop, with a preview of the result; amend, cherry-pick, revert | Interactive rebase: drag to reorder, edit, reword, squash, fixup or drop; amend | Visual interactive rebase: edit, reorder, squash | Amend, reorder, squash, cherry-pick, revert; no general interactive rebase (decided June 2026); reset only back to the last pushed commit |
| Conflict help without AI | Built-in 2-way and 3-way merge tools; warns before staging a file with conflict markers | Built-in resolver: your side and the incoming side with the result below; take a line, a block or a whole side; continue or abort at any step | Built-in conflict editor added in February 2026: take mine, theirs or both, then save and stage; or open an external merge tool | Built-in merge-conflict helper and resolver | No built-in merge editor documented |
| Other documented capability | Worktrees, Git LFS and git-annex, multi-repository workspaces | 30-day Undo of commits, branch deletions, stash drops and discards; worktrees; submodules; stashes | Worktrees, Git-flow, Git LFS, submodules; discarding changes cannot be undone | Reflog recovery, worktrees, Git-flow, Git LFS, submodules | Worktrees (3.6); discarded changes kept in the Trash until it is emptied |
| AI features (given no weight) | None in the free edition; the Pro edition advertises Claude Code, Codex, OpenCode and Copilot CLI integrations and optional AI with your own provider | Optional actions (commit messages, explanations, conflict suggestions) that call Claude Code, Codex, Gemini CLI or Cursor already installed and signed in on your computer | Optional commit messages through an OpenAI-compatible service you configure | Optional commit messages and code review through Claude Code, Codex or Cursor, installed separately | Copilot commit messages and conflict suggestions; Copilot access required |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for checking and reshaping changes
Documented capabilities, not our tests: GitComet features; Nori site and release notes; Fork features and release notes; SourceGit README, interface text, release notes and maintainer’s reply on line staging; GitHub Desktop commits and diffs, managing commits, maintainers’ replies on file history and interactive rebase, and 3.6 announcement. A conflict tool does not make a merge correct; check the final file.
Data and security
Show 2 criteria
| Feature | GitComet | Nori | SourceGit | Fork | GitHub Desktop |
|---|---|---|---|---|---|
| What the publisher says about your data | Open source; no account. Its privacy policy (updated November 11, 2026) says the client sends no usage analytics; update checks go to GitHub (on by default, can be turned off) and Markdown previews load remote images by default (can be changed) | No account. Its privacy policy (version dated October 16, 2026) says the app has no telemetry, analytics or crash reporting and that your code goes only to the Git remotes, hosts and AI tools you choose; update checks run once a day by default. We found no link to its source code, so these statements cannot be audited | Open source, no privacy policy. Settings and logs stay on your computer; its code fetches author pictures from Gravatar, using a hash of each author’s email, and from GitHub | No privacy policy; the developer said in 2024 that Fork gathers no customer data and has no telemetry, and declined to publish a formal policy | Open source; usage stats (counts and a pseudonymous ID) controlled in Preferences; Copilot features tracked separately |
| Security record found, 2024 to November 2026 | No published advisories or security policy (November 12, 2026). Earlier releases hardened submodule, symlink and merge-tool handling. Reads repositories with the gitoxide library at versions newer than the fixes for its 2026 high-severity advisories. A pre-1.0 client with one main developer | No advisory page or security policy found. Its own release notes record data-loss fixes in 1.7.0 (October 5, 2026: force push overwriting commits, interactive rebase dropping commits) and code-execution fixes in 1.14.0 (October 26, 2026); all are fixed in the current release. Native on the Mac; the Windows and Linux window uses the system web view, not Electron | No published advisories and no security policy (November 12, 2026). Its GitHub macOS packages are unsigned; Homebrew offers signed ones. An open crash report on Windows (2026.22 and 2026.23). Uses the Git you install | No published advisories or NVD entries found; closed source. Its own Git is old: release notes last record Git 2.45.2 on the Mac (June 2024) and 2.47.1 on Windows (February 2025), both affected by since-fixed high-severity Git advisories | Five GitHub advisories published since May 2024; the latest fixed in 3.6.6 (September 2026). 3.6.10 runs on Electron 44.9.1, supported until March 2027. Bundled Git was 2.53.0 when we checked on October 20, 2026 |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for data and security
GitComet privacy policy, security page, dependency lock file and gitoxide advisories; Nori privacy policy and release notes; SourceGit picture-download code, security page and macOS install notes; Fork developer statement, 2024 and Fork Mac and Windows release notes; GitHub Desktop usage data, security advisories, 3.6.10 build file and Electron release schedule. We did not inspect network traffic or audit any app. A search that finds no advisory is not proof that none exists.
What matters when choosing
GitComet is our Practical Pick for a developer on a Mac or Windows computer who wants a graphical client to check exactly what changed, commit only the lines they meant, look back through a file’s history and get through a conflict. It is free and open source under the AGPL-3.0 licence, needs no account, and runs on Windows, macOS and Linux. Its maker describes staging by file, hunk or selected line, split and structural diffs, per-file history, blame shaded by age, an interactive rebase in which you drag commits into order, and 2-way and 3-way merge tools. Its Windows installer is signed and its Mac disk image is notarized. Its privacy policy, updated November 11, 2026, names the company behind it, AutoExplore Oy of Finland, and says the free client sends no usage analytics. It scored 4.18 out of 5, against 4.13 for Nori, our Rising Star, 4.10 for SourceGit and 4.04 for Fork. Its lead is narrow: each gap is smaller than one point on our most heavily weighted criterion, and it rests partly on our judgment of how well each project’s maintenance record will hold. Site, features, privacy policy, releases
The main compromise is its maintenance record. GitComet is still before version 1.0 (0.3.4 arrived on November 10, 2026), one main developer writes most of it, contributions are accepted under a contributor licence agreement, and it publishes no security policy and no advisories. Its public issue list includes a macOS report of the app starting so many child processes on a large repository that the system’s process limit runs out. The maker has also launched a separate paid Pro client for reviewing pull requests; you do not need it for this job. If you want a longer record, choose SourceGit or Fork; if your employer requires a client from an identifiable company that publishes security advisories, choose GitHub Desktop. Issues, security page, Pro edition
Every client here uses Git, so keep Git itself current. A Git flaw published in July 2025 (CVE-2025-48384) lets a repository with a crafted submodule run a script when you clone it with its submodules, and the US Cybersecurity and Infrastructure Security Agency lists it as exploited in attacks. On Windows, Git for Windows has published six security advisories since March 2026, and two of them listed no patched version on October 19, 2026. SourceGit, GitComet and Nori use the Git you install, or helpers from it, so you get Git’s fixes by updating Git. Clients that bundle their own copy need their own updates for these fixes. Fork’s copy is old: its release notes last record Git 2.47.1 on Windows (February 2025) and Git 2.45.2 on the Mac (June 2024), versions affected by fixed high-severity advisories, so Fork lost half a point on security. Git advisory, Git for Windows advisories, Fork Windows release notes, Fork Mac release notes
Disclosure: GitComet’s paid Pro edition advertises Claude Code integrations; Nori’s optional actions call Claude Code and other agent tools you have installed; and Fork advertises optional commit-message and code-review features that use Claude Code, which you install separately. Practical Picks is researched and written with Anthropic’s Claude. We have no relationship with AutoExplore, Nori’s maker, Fork or Anthropic, and AI features carried no weight in our judgment. GitComet editions, Nori’s AI actions, Fork developer statement, about Fork
Nori is our Rising Star for the same developer who wants a free client with a built-in undo and can accept a very young project from one person. Its first public release was on July 16, 2026. It is free on public and private repositories with no account; an optional Pro edition at US$20 once adds pull requests and issues. Its maker documents staging a hunk, one line or a run of lines, file history that follows renames, blame, an interactive rebase that previews the result, a side-by-side conflict resolver, and a 30-day undo for commits, branch deletions, stash drops and discards. It runs on Windows 10 and 11, on Linux, and on Macs with Apple silicon and macOS 26 or later. It scored 4.13, ahead of the next newer client we scored, AngKorGit (3.90); that lead is narrow. Its limits: it is four months old and one person maintains it; its own release notes record data-loss fixes (a force push that overwrote commits, a rebase that dropped commits) in early October and code-execution fixes in late October, all fixed in the current release; and we found no link to its source code and no security policy, so its privacy statements cannot be audited. Site, pricing, release notes, privacy policy
Also consider SourceGit if you want a free, open-source client with a six-year record and can accept a project that is changing hands. It is MIT-licensed, needs no account, and documents line staging, file and folder history, blame, an interactive rebase and a built-in conflict editor. In September 2026 its lead maintainer announced that he is handing the project to other developers; he keeps fixing bugs until a successor is found, several volunteers have offered, none is named yet, and the release of November 9 says the date of the next one will be decided by the new maintainer. It also has no privacy or security policy, its Mac downloads on GitHub are unsigned, and discarding changes cannot be undone. It scored 4.10. Repository, hand-over announcement, releases, line staging
Also consider Fork if you want the fullest documented history and conflict tools for a one-time US$59.99. It documents reflog access for recovering lost commits, which neither GitComet nor SourceGit documents, alongside line staging, file and directory history, blame, a visual interactive rebase and a built-in resolver, and its release notes run back to 2016. It scored 4.04. It is closed source with no privacy policy, its developer declined to publish one, it has no Linux version, and its bundled Git is out of date; point it at a separately installed Git in its preferences. Features, purchase, issue 2247
Also consider GitHub Desktop if you want a free, open-source client from a large maintainer that publishes its security advisories. It is free, MIT-licensed and needs no account for local repositories. It lets you pick whole files or individual changed lines for a commit and shows unified or split diffs. It has no file history view, which its maintainers mark as not planned, and its documentation describes no blame or built-in merge editor, which is why it scored 3.93. Its current release, 3.6.10, runs on Electron 44, which receives security fixes until March 2027. GitHub Desktop commits and diffs, GitHub Desktop advisories, 3.6.10 build file, Electron support dates
These are researched judgments from documentation, licences, release notes, source code and public reports checked October 19 to November 12, 2026. We did not install any client, open a repository in one or buy a licence. Two conditions would change our recommendation: an employer that requires a client from an identifiable company with published advisories (choose GitHub Desktop), or a wish for the longest record and reflog recovery and a budget of US$59.99 (choose Fork). All five work on ordinary Git repositories, so changing client later means learning a new interface, not migrating data. Whatever you choose, read the final file after a conflict, not only the word “resolved”.
GitComet
Preferred Pick · free, open source, clear about your data
Choose GitComet when you want to see exactly what changed, commit only the lines you meant, trace a line back through history and resolve conflicts inside the app, free, with no account and a published privacy policy, and you accept a client that is still before version 1.0.
Reasons to choose it
- Stage files, hunks or selected lines; edit a file in place first
- Blame, per-file history, drag-to-reorder rebase and 2-way and 3-way merge tools
- Open source, no account, a published privacy policy and signed Windows and Mac installers
What to watch
- Launched March 2026 and still before version 1.0
- One main developer; no security policy published
- The paid Pro client holds the pull-request and AI integrations
GitComet is a free, open-source Git client for Windows, macOS and Linux, written in Rust by AutoExplore, a Finnish company whose main business is automated software testing. It was launched publicly in March 2026; version 0.3.4 arrived on November 10, 2026. Under our fixed criteria it scored 4.18 out of 5, the highest of the clients we scored, ahead of Nori (4.13), SourceGit (4.10) and Fork (4.04). That lead is narrow, smaller than one point on our most heavily weighted criterion. It leads because it matches most of Fork’s documented tools at no cost, with open code, no account and a published privacy policy. Its pre-1.0 releases, one main developer and lack of a security policy are the main reasons it does not lead by more. Site, releases, launch post, AutoExplore on GitHub
Its features page describes the tools this job needs. You can stage a file, a hunk or the lines you select, discard a single hunk, and edit a file in place before staging the rest. Diffs show split or inline, can compare code structure with the built-in Difftastic engine, and show image, SVG and rendered Markdown changes. It has per-file history, blame shaded by age, five history views and search, an interactive rebase in which you drag commits into order and pick, reword, squash, fix up or drop them, and 2-way and 3-way merge tools; it warns before you stage a file that still contains conflict markers. These are the maker’s descriptions and demonstrations; we did not run them. Features, line staging walkthrough, merge tool
Read the full GitComet analysis and sources
The Open Source edition is free for personal and commercial use under the AGPL-3.0 licence, with no account; the site says “Your repositories stay on your machine. No account, no sync, no upload.” The privacy policy, updated November 11, 2026, names AutoExplore Oy as the controller and says the open-source client needs no GitComet account and sends the company no usage analytics. It lists what the client does contact: GitHub for update checks, on by default and switchable, and the image hosts of any remote images in Markdown previews, also on by default and changeable; a crash report leaves your computer only when you choose Report Issue, and then goes to GitHub as a public issue you can edit first. A separate Pro client, EUR 4 a month billed annually for one person, adds pull-request review and AI integrations; none of that is needed for this job, and AI features carried no weight. See the disclosure in Our assessment. The Windows installer is signed and also available from the Microsoft Store, the Mac disk image is notarized for Apple silicon and Intel, and Linux packages need glibc 2.35 or newer. Editions and install, privacy policy, Pro edition
The limits come from its maintenance record. It is still before version 1.0, it was restructured in large refactors in October, and its GitHub organisation lists one member, with one developer writing most of the code. It publishes no security policy, and its GitHub security page lists no advisories; earlier releases did harden how it handles submodules, symbolic links and repository-defined merge tools. Its public tracker held 64 open issues on November 12, 2026, mostly feature requests and interface bugs. It reads repositories with the gitoxide library, in versions newer than the fixes for gitoxide’s two high-severity advisories of August and September 2026, and it finds Git helpers such as Git LFS on your computer. Choose SourceGit or Fork for a longer record. Releases, security page, issues, dependency versions, gitoxide advisories
Used GitComet? Share your experience to help other readers choose.
Nori
Rising Star · free, no account, a 30-day undo for Git
Why Rising Star? Nori is the highest-scoring newer client after our Pick, GitComet, by a small margin. Its maker documents line staging, file history, blame, interactive rebase with a preview of the result, a conflict resolver and a 30-day undo, free with no account, on Windows and Mac. It launched in July 2026, one person maintains it, its release notes record data-loss and security fixes in October, and on a Mac it needs Apple silicon with macOS 26 or later.
Consider Nori if you want a free client with a built-in undo for commits, branch deletions and discards, and you accept a four-month-old project from one person and a recent Mac.
Reasons to choose it
- Stage hunks, single lines or a run of lines; discards can be undone
- File history, blame, a rebase with a preview and a side-by-side conflict resolver
- Free with no account; a privacy policy says it has no telemetry
What to watch
- Four months old, one maintainer; data-loss and security fixes in October
- Mac support is Apple silicon with macOS 26 or later
- No link to its source code found, so its privacy statements cannot be audited
Nori is a Git client for Windows, macOS and Linux, published by Quentin Hermiteau, a sole proprietor in France, according to its privacy policy. Its first public release was on July 16, 2026, version 1.0.0 followed on August 12 and 1.16.0 on November 9, roughly a release a week. Under our fixed criteria it scored 4.13 out of 5, the highest of the newer clients after our Pick, ahead of AngKorGit (3.90) and just behind GitComet (4.18). Its lead over the next newer client is narrow, smaller than one point on our most heavily weighted criterion. Site, release notes, privacy policy
Its site describes the tools this job needs. You can stage a hunk, a single line or a run of lines from the gutter, in unified or split diffs; its release notes also describe image previews and whitespace visibility in diffs. It follows a file through renames, shows blame and the commit behind any line, searches history by author, path, content, regular expression, date or hash, and lists the reflog. An interactive rebase lets you reorder, reword, edit, squash, fix up or drop commits and shows the resulting history before Git runs; a merge-conflict resolver shows your side and the incoming side with the result below, lets you take a line, a block or a whole side, and continues or aborts at any step. Before every commit, branch deletion, stash drop and discard it keeps a snapshot, so you can undo from a prompt or from a list covering the last 30 days. These are the maker’s descriptions and demonstrations; we did not run them. Features, release notes
Read the full Nori analysis and sources
It is free for every Git feature, on public and private repositories, with no account; the pricing page says nothing you use today becomes paid and the free app never expires. An optional Pro edition, US$20 once for up to two devices, adds pull-request and issue features for GitHub and GitLab; you do not need it here, and the page said purchases were paused for a moment when we read it. Its privacy policy says the app has no telemetry, analytics or crash reporting, that your code goes only to the Git remotes, hosts and AI tools you choose, and that it checks for updates once a day by default. Its optional AI actions call agent tools such as Claude Code, Codex, Gemini CLI or Cursor that you have installed and signed in to yourself; see the disclosure in Our assessment. Pricing, privacy policy
The limits are real. It is four months old and one person maintains it. Its own release notes say version 1.7.0, on October 5, 2026, closed “data-loss and security issues found before the public launch”: among them a force push that could overwrite commits, an interactive rebase that dropped commits made after its plan opened, a checkout that wiped edits, and a branch deleted when its undo snapshot could not be saved. Version 1.14.0, on October 26, closed code-execution risks, such as an automatic fetch running a program named in a repository’s own Git settings. All are fixed in the current release, and we count them as the record of a young product, not an unpatched flaw. We found no link to its source code, no public issue tracker and no security policy, so its statements about your data cannot be checked against code. On a Mac it needs Apple silicon and macOS 26 or later; it runs on Windows 10 and 11 and on x86-64 Linux, and uses the Git you install. Release notes, pricing, with platform requirements
Used Nori? Share your experience to help other readers choose.
SourceGit
Also consider · free and open source, longest record of the free options
Choose SourceGit when you want most of what Fork documents without paying, with code you can read and a six-year record, and you accept that its lead maintainer is handing the project to someone else.
Reasons to choose it
- Stage, unstage or discard files, hunks or selected lines
- File and folder history, blame and drag-to-reorder interactive rebase
- Built-in conflict editor; uses the Git you install; releases about every two weeks
What to watch
- The lead maintainer announced in September that he is handing over the project; no successor is named yet
- Mac packages on GitHub are unsigned; install the signed Homebrew package
- No privacy policy or security policy; discarding changes cannot be undone
SourceGit is a free, MIT-licensed Git client for Windows, macOS and Linux. Its first release, for Windows only, was tagged on July 3, 2020, and version 8.0 added the Mac in February 2024. Under our fixed criteria it scored 4.10 out of 5, behind GitComet (4.18) and Nori (4.13) and just ahead of Fork (4.04). Its code, interface text and maintainer’s replies show the tools this job needs at no cost, with open code and no account, and it uses the Git you install rather than a bundled copy. It is a volunteer project: its copyright notice names “sourcegit”, and its lead maintainer publishes as “leo” (love-linger) in the public repository, with no company named. Repository, first releases, Windows-only README at 6.9, Windows and macOS README at 8.0, licence
Its README, interface text and source code describe the tools this job needs. You can stage, unstage or discard a whole file, a hunk or only the lines you select; asked in June 2026 for line-by-line commits, the maintainer replied, “You can select the lines you want to stage/unstage/discard.” Diffs show unified or side by side, can ignore whitespace and can expand to the whole file, and images compare side by side, by swiping, by blending or as a difference. It shows file and folder history, following renames since early 2026, blame, commit search and bisect. Its interactive rebase lets you drag commits into order and edit, reword, squash, fix up or drop them. Version 2026.03, released February 9, 2026, added what its notes call “a simple built-in conflicts resolving tool”: take your side, theirs or both, then save and stage the file. It can also open an external merge tool. These are the project’s descriptions; we did not run them. README, interface text, diff view source, release notes, line staging reply
Read the full SourceGit analysis and sources
The main risk for a job that runs for years is continuity. On September 18, 2026 the lead maintainer opened a pinned issue titled “Find volunteers to take over the project”. He wrote that he has found himself stretched thin, has decided “to hand over the maintenance of this project to other capable developers”, will keep maintaining it “limited to bug fixes” until a candidate is found and will then step back completely, and asked that the new maintainer keep it open source and free. Several developers volunteered in early November. The release of November 9, 2026 (2026.24, the twenty-fourth this year) says he is still talking to candidates and that the new maintainer will decide when the next version appears. Until that settles, expect bug fixes rather than a promised schedule. Hand-over announcement, 2026.24 release notes
It works through the Git you install: it needs Git 2.25.1 or later, and on Windows the official Git for Windows. You therefore get Git’s security fixes by updating Git yourself rather than waiting for the client. Its GitHub security page shows no security policy and no published advisories, and its README says the Mac packages on its release page are all unsigned and tells you to clear the Mac’s download quarantine with a sudo command. Install from Homebrew instead (brew install --cask sourcegit); the project’s 2025.41 notes say the official Homebrew cask carries signed packages. The maintainer tests Linux only on Debian 12. It is built with .NET and Avalonia and bundles no browser engine. Compared with Fork it documents no reflog view, its conflict editor is only nine months old, and discarding changes cannot be undone; its confirmation dialog says so. How to use, 2025.41 notes, security page
No account is needed. Settings, downloaded pictures and crash logs are kept in a folder on your computer. Its source code fetches commit authors’ pictures from Gravatar, sending an MD5 hash of each author’s email address, and from GitHub; we found no option in its interface text to turn that off, and it publishes no privacy policy. Optional AI commit messages go to an OpenAI-compatible service that you configure; we gave them no weight. Choose GitComet if you want a published privacy policy and a company behind the project, GitHub Desktop if your employer needs a client from an identifiable company, and Fork if you want a reflog view and a longer record behind its conflict tools. README, picture-download code
Used SourceGit? Share your experience to help other readers choose.
Fork
Also consider · fullest documented history tools, one-time licence
Choose Fork when you want the fullest documented history and conflict tools, including reflog recovery, from identifiable developers with a ten-year record, for one payment.
Reasons to choose it
- Line staging, side-by-side and image diffs
- File and directory history, blame and visual interactive rebase
- Built-in merge-conflict resolver and reflog recovery
What to watch
- No privacy policy; the developer says it collects no data
- Its bundled Git is out of date; point it at a current Git
- Paid, closed source, no Linux version
Fork’s feature page describes what you need to check a change before and after you commit it. You can stage and unstage changes line by line, compare text side by side, compare common image formats, see every commit that changed a file or directory, find the last commit that changed a line, and browse the repository tree at any commit. A visual interactive rebase lets you edit, reorder and squash commits, a merge-conflict helper and built-in resolver handle conflicts, and the reflog gives you a way back to commits a rebase or reset left behind. Recent releases add worktrees, a check for whether a cherry-pick or revert will conflict before you start, and --update-refs in interactive rebase. Under our fixed criteria Fork scored 4.04 out of 5, behind GitComet (4.18), Nori (4.13) and SourceGit (4.10). These are the vendor’s descriptions and release notes; we did not run them. Features, Mac release notes, Windows release notes
We verified that the purchase page lists US$59.99 as a one-time purchase for personal and commercial use, for one user on up to three machines. The licence lets that key run on Mac and Windows, says you may download and evaluate Fork free but “need to purchase a license for long-term use”, disclaims warranties and is governed by Czech law, with Danil Pristupov named as author. Neither page says whether a later major version will need a new purchase, how activation works or whether it needs an internet connection; we could not establish those. There is no hosted-repository tier: the licence does not depend on where your remote lives. Purchase, licence
Read the full Fork analysis and sources
Fork is made by Dan Pristupov and Tanya Pristupova, who describe themselves as a family of software developers working on Fork full-time. The Mac release notes start in April 2016; Mac 2.71 arrived on October 23, 2026 and Windows 2.24 on November 6, 2026. That is a long, steady record, but it is a small team, and we found no published security contact, advisory list or entry in the US National Vulnerability Database. Fork ships its own copy of Git, and its release notes last record updating it to Git 2.45.2 on the Mac in June 2024 and to Git 2.47.1 on Windows in February 2025. Both versions are affected by high-severity Git or Git for Windows advisories that have since been fixed, so Fork lost half a point on security. Its preferences let you choose a separately installed Git instead. For a closed-source app, that absence tells you little either way. A 2022 discussion on Fork’s public issue tracker shows the developer directing a company asking about team licensing to email; individual purchase terms do not answer fleet-management questions. About, team-licence discussion, Mac release notes, Windows release notes
On data, Fork has no privacy policy; the address that would usually hold one returns an error. In a June 2024 thread on its public tracker, the developer said Fork is “just a wrapper around git”, “doesn’t gather any customer data” and has no telemetry, and that payments go through Paddle. Asked in October 2024 for a formal privacy policy, he answered “No, we will not do that.” These are the developer’s statements, not an audit, and we did not inspect Fork’s network traffic. An EU commenter in the same thread said NIS2 obligations meant they could not allow Fork at their company. If you need that kind of document, Fork will not supply it. Issue 2247
Fork’s AI features are optional and use agents you install yourself: Claude Code for branch reviews and commit messages since November 2025, then Codex and Cursor on the Mac. We gave them no weight. Choose Fork over GitComet if reflog recovery, a ten-year record and identifiable developers matter more to you than open code and a zero price. Choose GitHub Desktop if you want free, open-source code from a maintainer that publishes security advisories.
Used Fork? Share your experience to help other readers choose.
GitHub Desktop
Also consider · free and open source, from a company that publishes advisories
Choose GitHub Desktop when paying nothing, signing in to nothing or being able to read the code matters more than history tools, or your employer needs a client from an identifiable company. It covers focused commits well.
Reasons to choose it
- Pick whole files or individual lines for a commit
- No account needed for local repositories
- GitHub publishes its security advisories
What to watch
- No file history view (not planned); no documented blame or merge editor
- No Linux version
- No general interactive rebase (decided in June 2026)
GitHub Desktop is the choice here if you want a free, open-source client from a large maintainer that publishes its security advisories, and history tools matter less to you. We verified that it is MIT-licensed, installs on macOS and 64-bit Windows 10 or later, and does not support Linux. You do not need a GitHub account for local repositories; you sign in only to connect to GitHub or GitHub Enterprise. Its documentation shows how to include or exclude whole files, exclude individual changed lines by clicking them, switch between unified and split diffs, hide whitespace changes and expand the surrounding context or the whole file. Under our fixed criteria it scored 3.93 out of 5. Repository and licence, installation, connections, commits and diffs
Its main limit for this job is history and conflicts. GitHub documents amending, reordering, squashing, cherry-picking, reverting and undoing commits, and resetting only as far back as the last pushed commit. A request for a file history view has been open since April 2021 and has carried the maintainers’ “not planned” label since July 2024. In June 2026 the maintainers closed a request for interactive rebase, saying they had decided against a general interactive-rebase interface and would extend the reorder, squash and amend actions instead. We found no documentation of blame or a built-in merge editor; that is undocumented, not proven absent. Version 3.6, announced June 26, 2026, added Git worktrees and lets Copilot explain a conflict and suggest a resolution that you review, accept or edit. Copilot features need Copilot access and offer a model picker, including your own key; we gave them no weight. Managing commits, file history request, interactive rebase decision, 3.6 announcement
Read the full GitHub Desktop analysis and sources
Discarding is different from leaving changes out. Discarded changes go to a dated file in the Trash, and you can recover them only until the Trash is emptied. Discarding single lines is unavailable inside a group of changes that both adds and removes lines. Commits and diffs
GitHub publishes advisories for Desktop, and keeping it updated matters because it holds your credentials. Five appear since May 2024. The newest, published September 24, 2026 and fixed in 3.6.6, let a malicious repository make Desktop write to a file outside the clone when you used the ignore action on a changed path, if the repository’s .gitignore was a symbolic link. A November 2025 advisory, CVE-2025-26625, concerned the bundled Git LFS and was fixed in 3.5.4. The current release is 3.6.10, from October 30, 2026; its build file pins Electron 44.9.1, the browser engine inside the app, which receives security fixes until March 2027. Its own copy of Git was recent when we checked on October 20, 2026: Git 2.53.0, packaged on Windows as Git for Windows 2.53.0.windows.4 in August 2026. Version 3.6.6-beta1 notes say support for macOS 12 was dropped, while the installation page still lists macOS 12; on macOS 12, check before upgrading. Advisories, September 2026 advisory, Git LFS advisory, releases, 3.6.10 build file, bundled Git package, Electron support dates
GitHub describes the usage statistics Desktop sends as counts of actions, app and system details and a pseudonymized identifier, controlled in Preferences; Copilot features track their own metrics separately. Choose Fork if you need file history, blame or a built-in conflict resolver and can pay once; choose GitComet or SourceGit for those tools free. Usage data, GitHub privacy statement
Used GitHub Desktop? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
Public discussion is a check on vendor claims, not a measured reliability score. Fork’s public issue tracker holds a June to November 2024 thread in which a company asked for ISO 27001 or SOC 2 certification, a privacy statement and a software bill of materials. The developer said Fork has none of those certifications, gathers no customer data and has no telemetry, pointed to the in-app list of third-party libraries, and declined to write a formal privacy policy. Another commenter said NIS2 rules meant their company could not allow Fork. Issue 2247
A 2022 Hacker News discussion of Fork mixes favourable switching reports with adverse experiences, includes disagreement over whether problems came from Git or the client, and has a developer response. A 2024 Reddit report describes GitKraken treating every repository as private, with the user’s observations changing during troubleshooting; GitKraken’s current plan page confirms the general boundary between local, public and private repositories, but we did not reproduce the report. Both were read September 6, 2026 and are dated, self-selected accounts. Hacker News, 2022, Reddit, 2024
SourceGit’s public tracker had 166 open issues on November 12, 2026, including a report of crashes on Windows in releases 2026.22 and 2026.23. In June 2026 its maintainer answered a request for line-by-line commits by pointing out that you can already select the lines to stage, and in September a report that a branch-switch dialog closed by itself turned out to concern only untracked files, which the app leaves in place. Its hand-over announcement had 21 thumbs-up and 24 heart reactions by November 12, and several developers have offered to take over. GitComet’s tracker held 64 open issues, mostly feature requests and interface bugs. We found no public issue tracker for Nori; its site points to a Discord server and a feedback email. Issue 2415, issue 2733, issue 2722, GitComet issues
We did not find representative current ratings for these clients and used no star scores or speed rankings. Our searches for vulnerabilities, incidents, lawsuits, ownership changes and shutdown notices involving the original four clients and their publishers (October 19) and our checks of the security pages and issue trackers of SourceGit, GitComet and GitHub Desktop (October 20 and November 12) found nothing beyond the items in this article that changed our conclusions. A search that finds nothing is not proof that nothing exists.
How we researched
This is public-source research. We did not install any client, open or change a repository, connect credentials, buy or activate a licence, or inspect network traffic. No vendor supplied access, payment or input, and we use no affiliate links. We first compared four clients on September 6, 2026 and rechecked every material claim for them on October 19, 2026: prices, plans, licences, platform support, account requirements, documented staging, history and conflict features, data statements, release notes and security records. On October 20 we added SourceGit and GitComet and checked every client’s browser engine and bundled Git; on November 12 we rechecked prices, releases, licences, privacy statements and security pages for all five clients in this article and for the other clients we scored, added Nori, and searched again for newer clients. Sources were vendor documentation, licences, privacy policies, release notes, GitHub security advisories, the US National Vulnerability Database, Atlassian’s issue tracker, the CVE record, a state breach-notice filing and public discussions.
We wrote this for a developer on Mac or Windows who wants a graphical client to check what changed, commit only what they intend, look back through history and get through conflicts, on repositories they already have, and who will keep using it for years. We fixed five criteria and their weights before comparing: choosing and reviewing changes (30%), history and conflict help without AI (20%), cost over three years of use with private repositories (15%), account and data handling (15%), and maintenance and security record (20%). We applied the same checks to every client. A client that ships a browser engine no longer receiving security fixes, or its own copy of Git older than the fixes for high-severity Git or Git for Windows advisories, lost half a point on maintenance and security; Fork lost half a point for its old Git, and GitHub Desktop, now on a supported Electron, lost none. We priced each client over three years and gave the cheapest suitable plan for one developer with private repositories; free clients scored 5 on cost, and paid clients scored lower in proportion to how far their price sits above the typical paid price. We could not read SmartGit’s current commercial price, so we left its cost out of its score. Scores out of 5: GitComet 4.18, Nori 4.13, SourceGit 4.10, Fork 4.04, GitHub Desktop 3.93. Requiring a client from an identifiable company that publishes security advisories points to GitHub Desktop. We did not evaluate terminal interfaces, code editors’ built-in Git panels or hosting services. AI features in these clients carried no weight.
We searched again for newer clients on November 12, 2026, starting from the clients screened in October and adding Hacker News launch posts, GitHub repositories and topic lists, releases and alternatives lists. A newer client had to have its first public release in the last 24 months, run on both Mac and Windows, show the core job in its public pages and have no known unpatched serious flaw. GitComet and Nori qualified; GitComet became our Pick, so the Rising Star goes to Nori. AngKorGit (an MIT-licensed client first released in August 2026, with file, hunk and line staging, interactive rebase and a conflict editor, but unsigned builds and no blame or file history found) scored about 3.90. GitWand (an MIT-licensed client with line staging, blame and a conflict-resolution engine, whose commit notes show that its release builds include an analytics plugin) scored about 4.03, but the pages we read do not show its first-release date. GeeTree publishes no source code and names only a handle for its maker. RelaGit, rgitui and gitru showed no complete account of the core job. Gitnuro (3.90) first released in 2022 and GitButler (about 3.60) in 2023, so neither is a newer client now; GitButler sorts changes into parallel branches and fixed bugs that deleted tracked files this summer. GitBrowser, TinyGit and several other launches run only on the Mac.
Established clients missing from this comparison, scored the same way from their makers’ pages: Sublime Merge 3.99 (US$99 once with three years of updates), Tower 3.90 (US$69 a year), Git Cola 3.83 (free, with blame, history and conflicts handed to outside tools), SmartGit (paid; price unknown), Sourcetree 3.68 and GitKraken Desktop 3.61. Sourcetree is free and documents hunk-level staging, but Atlassian’s install guide says you need an Atlassian account, it relies on an external merge tool, and its embedded Git is older than the fixes for high-severity Git for Windows advisories. GitKraken Desktop offers Linux packages from a company that supports them, but private remotes need Pro at US$120 per user per year (its pricing page also advertises a lower first-year price, which we did not count); it needs an account, its privacy policy says it stores the folder and file names where you keep code, its release notes show Electron 41, which lost security support in August 2026, and an April 2026 notice to Massachusetts reported that employee payroll data reached its internal telemetry through Anthropic’s Claude for Excel; it concerned employees, not customer repositories. None of these placed in the top four overall, so none gets a column in the chart. TortoiseGit and Git Extensions run only on Windows, so they do not serve a reader who may be on either system.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| GitComet | Site, features page and walkthroughs, Pro page, privacy policy, release list, dependency lock file at 0.3.1, security page, issue tracker, GitHub organisation page; gitoxide advisories. | AutoExplore’s company-register entry; whether it calls a separately installed Git beyond helpers; how its young tools hold up in use. |
| Nori | Site, pricing page, release notes, privacy policy. | Source code, security process and an independent register entry for its publisher; whole-app behaviour; its published performance figures are the maker’s own. |
| SourceGit | Repository, README and licence; release notes and tags back to its first release; interface text and source code; maintainer replies on its issue tracker; hand-over announcement; security page. | Who takes over; whether Windows builds are signed; what its update check sends; how reliable its nine-month-old conflict editor is. |
| Fork | Feature, purchase and licence pages; Mac and Windows release notes, including bundled Git updates; developer statements on its public issue tracker; NVD search. | Whether Fork updated its bundled Git without a release-note entry; activation and internet requirements; whether later major versions need a new purchase; what the app sends, beyond the developer’s 2024 statement; security contact and disclosure process. |
| GitHub Desktop | GitHub documentation, repository and licence, release list, build file, 3.6 announcement, security advisories, usage-data page, maintainers’ replies on two feature requests. | Blame and a built-in merge editor are undocumented; macOS 12 support conflict between release notes and installation page; bundled Git version in the latest release. |
| Other clients scored | Sourcetree, GitKraken Desktop, Sublime Merge, Tower, SmartGit, Git Cola, Gitnuro, GitButler, AngKorGit, GitWand: makers’ sites, documentation, pricing, release pages and changelogs, read October 20 and November 12, 2026. | Scores for Gitnuro, GitButler, AngKorGit and GitWand are estimates from their pages; SmartGit’s price; Tower’s and GitKraken’s renewal and cancellation terms. |
None of this establishes speed, merge correctness or security in use. Next substantive review is due December 18, 2026, or sooner after a price, licence or major release change. Found a changed price or behaviour? Contact the editors.
Sources and evidence
Sources were checked October 19, 2026 unless another date is given; GitComet, SourceGit, Nori and the other clients named were rechecked on November 12, 2026. Vendor material establishes documented features and published terms, not behaviour on your computer. Developer statements on issue trackers are attributed claims. Community posts are anecdotal, not representative samples.
- GitComet, November 12, 2026: site and editions; Pro edition; privacy policy, updated November 11, 2026; features; merge tool; line staging walkthrough; releases, v0.3.4, November 10, 2026; repository; issues; dependency lock file at v0.3.1; security page; AutoExplore on GitHub; launch post, March 2026; gitoxide advisories, including GHSA-6p9q-f2xg-6pr5 and GHSA-jrcm-326h-gpp8.
- Nori, November 12, 2026: site and features; pricing and platform requirements; release notes, 1.16.0, November 9, 2026; privacy policy, version dated October 16, 2026.
- SourceGit, November 12, 2026: repository, README and install notes; releases, 2026.24, November 9, 2026; hand-over announcement, issue 2722, September 18, 2026; release notes 2026.03 to 2026.12 and 2025.34 to 2026.02; first release tags, v1.0, July 3, 2020; README at 6.9, Windows only and at 8.0, Windows and macOS; licence; interface text; diff view source; picture-download code; issue 2415, line staging, June 2026; issue 2733, branch-switch dialog, September 2026; security page.
- Fork: features; purchase, US$59.99, rechecked November 12, 2026; licence; Mac release notes, 2.71, October 23, 2026; Windows release notes, 2.24, November 6, 2026; about the developers; issue 2247, privacy and compliance thread, 2024; issue 1657, team-licence discussion, 2022.
- GitHub Desktop: overview; repository and MIT licence; releases, 3.6.10, October 30, 2026; 3.6.10 build file, November 12, 2026; installation; connections; commits and diffs; managing commits; file history request, issue 11990, labelled not planned; interactive rebase request, issue 12354, closed June 4, 2026; 3.6 announcement, June 26, 2026; security advisories, including GHSA-f4gx-53p6-27gv, September 24, 2026, GHSA-3wgp-8x77-3jjx, November 11, 2025 and GHSA-36mm-rh9q-cpqq, January 15, 2025; usage data; GitHub privacy statement.
- Sourcetree: product page, rechecked November 12, 2026; download terms; install guide, last modified February 28, 2018; remote accounts; Mac release notes, 4.2.19, July 30, 2026; Windows release notes, 3.4.32, August 28, 2026; CVE-2026-21575, SRCTREE-8275, July 21, 2026; Atlassian privacy policy.
- GitKraken Desktop, November 12, 2026: pricing and plan table; plan feed loaded by the pricing page; release notes, 12.6.2; privacy policy, March 19, 2026; account and licence FAQ, April 2026; Axosoft notice to Massachusetts, April 25, 2026.
- Bundled Git and runtime checks: Electron release schedule and support dates, November 12, 2026; Fork release notes; Sourcetree Windows release notes; SmartGit 26.1 changelog; Tower Windows release notes; Sublime Merge changelog; GitHub Desktop bundled Git package; Git for Windows advisories GHSA-hv9c-4jm9-jh3x, GHSA-9j5h-h4m7-85hx and GHSA-xrpg-8j9v-v282.
- Other clients scored, November 12, 2026: Gitnuro, its releases and tags; GitButler and its releases; AngKorGit; GitWand; GeeTree; Sublime Merge store; Tower pricing; Git Cola downloads; SmartGit changelog; TortoiseGit and Git Extensions.
- Community: Hacker News discussion of Fork, 2022 and Reddit report on GitKraken private-repository classification, 2024, both last read September 6, 2026. Vulnerability searches used the National Vulnerability Database.
This is a researched comparison, not a product review. Method: evidence standard, editorial picks.