Is Jujutsu (jj) ready to replace git in 2026 — how actively maintained is it, and which forges support it?

Is Jujutsu ready to disrupt Git? Surprisingly, it already has active support from multiple repositories, with a promising maintenance track record. Here's a look at the current landscape.

Active Repositories Supporting Jujutsu

1. treq-dev/treq ✅

   • Stars: 4
   • Language: TypeScript
   • Maintenance: Actively maintained, last pushed recently (2026-09-27).
   • Latest Release: v0.2.0 (released 2026-08-09).
   • Open Issues: 9
   • License: Apache-2.0
   • Description: A Stacking Agent Development Environment designed to improve developer workflow with Jujutsu compatibility.

2. michaeldhopkins/jjpr ✅

   • Stars: 18
   • Language: Rust
   • Maintenance: Actively maintained, last pushed 2026-09-27.
   • Latest Release: v0.40.2 (released 2026-09-27).
   • Open Issues: 7
   • License: MIT or Apache-2.0
   • Description: Manages stacked pull requests for Jujutsu repositories, seamlessly integrating with GitHub, GitLab, and Forgejo.

3. kimleo5808/jujutsuinfinitecodes.app ✅

   • Stars: 0
   • Language: TypeScript
   • Maintenance: Actively maintained, last pushed 2026-09-27.
   • Open Issues: 0
   • License: N/A
   • Description: Focuses on leveraging Jujutsu within a modern web application framework, though specific details on functionality are absent.

How Actively Maintained?

• All three repositories demonstrate active maintenance: pushed changes recently, open issues are relatively low (the highest is 9), and they are not archived.
• Contributors vary from 2 to 4, suggesting a modest but engaged community, which is pivotal for ongoing development and support.

Support Across Forges

• The jjpr tool points out Jujutsu's capability to integrate with both GitHub and GitLab, reflecting its viability in well-established ecosystems.
• Treq focuses on being Git compatible while also utilizing Jujutsu under the hood, indicating a strategic approach to coexistence rather than overt replacement.

Verdict and Recommendation

Jujutsu appears to be a viable Git alternative, especially with its focus on enhancing pull request management through tools like jjpr. However, its successful replacement of Git in workflows will heavily depend on community adoption and integration depth.

Choose Jujutsu if you're interested in novel branching strategies or managing pull requests as part of a team initiative. However, stick with Git for established practices and extensive community support until Jujutsu proves itself in a wider array of use cases.

In summary, Jujutsu isn't just a passing trend; it's steadily paving its way in the version control landscape, but patience and observation will be key before any replacement decisions.