FileCentipede

filecxx/FileCentipede

Cross-platform internet upload/download manager for HTTP(S), FTP(S), SSH, magnet-link, BitTorrent, m3u8, ed2k, and online videos. WebDAV client, FTP client, SSH client.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 18, 2026
4 days ago
Ship score
60/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 10,904 → 10,939 (Sep 8 – Oct 20, 2026)
+21 stars in the 28 days to 2026-10-20

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
10.9K
Forks
684
Open issues
264
Watchers
82
Primary language
C++
License
Unknown
Created
Mar 7, 2022
Owner
filecxx · User

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 31 startups in the directory ship primarily in C++.

Topics

#bittorrent-client#bt#download#download-manager#download-videos#ftp-client#http-client#libtorrent#m3u8#magnet#qt#remote-download#ssh-client#stream-downloader#torrent#transmission#video-downloader#webdav-client

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 71%, self-hostable 45%, hosted offering 20%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-18This is the badge for filecxx/FileCentipede, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/filecxx/FileCentipede.svg)](https://ossean.com/filecxx/FileCentipede)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.