johang/btfs

A bittorrent filesystem based on FUSE.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 33 minutes ago
Added to GitGenius on September 17th, 2026
Created on July 26th, 2015
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 147
Total Stargazers: 3,968 (+0)
Total Subscribers: 49 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 hours
Mean response time: 23.7 days
90th percentile: 105.6 days
Tracked items: 11

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 595 days
Stale 30+ days: 8
Stale 90+ days: 7

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

BTFS is a FUSE-based filesystem that mounts torrent files and magnet links as read-only directories.

The tool solves the problem of accessing torrent content without downloading entire files upfront. It works by mounting a .torrent file or magnet link into the filesystem, then downloading file contents on-demand as applications read them. Standard Unix tools like ls, cat, and cp work transparently, and media players like VLC and mplayer can stream video directly from the mounted torrent without modification.

BTFS suits users who want to stream or selectively access torrent content without committing disk space to full downloads beforehand. It works on Linux, macOS, and other Unix-like systems where FUSE is available. The tool is available through package managers on Debian, Ubuntu, Arch, Gentoo, Fedora, openSUSE, and macOS via Homebrew, making installation straightforward across major distributions.

The project receives infrequent commits with long gaps between updates. Pull requests are rarely merged, indicating a low rate of external contribution acceptance. Issues are typically not addressed or closed, suggesting minimal active maintenance and responsiveness to bug reports or feature requests.