git-bug

Why it's ranked here

The design is the reason to look. Instead of syncing a database, git-bug turns issue history into an operation log that merges like a CRDT (a data structure built to merge concurrent edits without conflicts), and the on-disk format is published as a separate specification so other tools can read it. It is GPLv3 or later, ships as one binary with signed release checksums, and is packaged for Arch, Nix, Homebrew, scoop and FreeBSD. CI runs a vulnerability scan on dependencies. The gaps are honest and documented: the web portal for outside reporters is unfinished.

What's good

Concurrent edits are handled with real care: commits whose logical clocks contradict the history graph are rejected, and ties are broken by a hash order that a participant cannot easily steer. Queries use a small, familiar filter syntax (status, author, label, title, sort by edit time) and IDs accept any unique prefix, the way git commits do. The GitHub and GitLab bridges import and export incrementally, resume from where they stopped, and have automated test suites. Releases come with a cosign-signed checksum file and documented verification commands, which is more than most developer tools offer.

Tradeoffs

The project's own feature matrix lists assignees and milestones as not implemented anywhere, and boards as partial. Comment deletion exists in the core but not in any interface. The Launchpad bridge imports only and cannot resume, and the Jira bridge has no automated test suite. No bridge carries attached media. Public key handling and identity protection are marked partial, so signed authorship is not yet enforced end to end. The web interface is labelled a work in progress, and building it needs Node.js and pnpm on top of Go. The GPLv3 license matters if you plan to embed the library.

How to use it well

A good fit for small teams or solo maintainers who already live in the terminal and want issues that travel with the code, survive a hosting outage, and work offline. It also works as a local, editable mirror of a GitHub or GitLab tracker, synced through a bridge. Use the command line or terminal interface for daily work, since the docs themselves recommend them over the web view. Look elsewhere if you need assignees, milestones, project boards, or a public intake page where outsiders can file reports without cloning the repository.

Observed

License

GPLv3 or later (logo under CC BY 4.0)

Language

Go, with a React web UI compiled into the binary

Interfaces

git subcommand CLI, terminal UI, local web UI, GraphQL API

Storage

Git objects under custom refs; no files added to the working tree

Bridges

GitHub, GitLab, Jira (import and export); Launchpad (import only)

Platforms

Linux, macOS, Windows, FreeBSD, OpenBSD, NetBSD

Packaging

Single binary; deb, rpm, apk, Arch, nixpkgs, Homebrew, scoop, FreeBSD pkg

Release verification

SHA-256 checksums signed with keyless cosign

Not implemented

Assignees, milestones, pull-request entities (per feature matrix)