rakshasa/rtorrent

rTorrent BitTorrent client

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on October 3rd, 2011
Open Issues & Pull Requests: 391 (+0)
GitHub issues: Enabled
Number of forks: 484
Total Stargazers: 4,864 (+0)
Total Subscribers: 146 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.0 hours
Mean response time: 80.9 days
90th percentile: 28.3 days
Tracked items: 382

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 94% of issues opened in the past year have since been closed. Three people close 81% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 42
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 1,556 days
Stale 30+ days: 39
Stale 90+ days: 33

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

rTorrent is a command-line BitTorrent client built for high performance using ncurses.

The tool addresses the need for an efficient, terminal-based torrent client suitable for server environments and power users who prefer keyboard-driven interfaces over graphical applications. It operates as a lightweight ncurses interface that communicates with the underlying libtorrent library, which handles the actual BitTorrent protocol implementation and peer management. This separation of concerns allows rTorrent to remain responsive even when managing large numbers of torrents or transfers.

Developers and system administrators managing torrents on headless servers or preferring command-line workflows should consider rTorrent. It suits scenarios where minimal resource overhead is critical or where remote access via SSH is the primary interaction method. The project maintains tight version coupling with libtorrent, requiring both to be built from the same version, which means adopters need to manage this dependency relationship carefully during installation and updates.

Development activity shows consistent maintenance with regular updates addressing bugs and compatibility issues. The project accepts contributions through standard pull request workflows and maintains active issue tracking. Documentation is centralized in the project wiki rather than embedded in the repository, directing users to external resources for learning and troubleshooting. The maintainer has established multiple funding channels, indicating sustained commitment to the project's continued development.