qjfoidnh/baidupcs-go

iikira/BaiduPCS-Go原版基础上集成了分享链接/秒传链接转存功能

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 12th, 2026
Created on November 6th, 2020
Open Issues & Pull Requests: 234 (+0)
GitHub issues: Enabled
Number of forks: 691
Total Stargazers: 5,615 (+1)
Total Subscribers: 36 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 110
New in 7 days: 3
Closed in 7 days: 0
Avg open age: 456 days
Stale 30+ days: 99
Stale 90+ days: 88

Recent activity

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

Top labels

  • bug (2)
  • documentation (1)

Detailed Description

baidupcs-go is a command-line client for Baidu Cloud Storage that emulates Linux shell file handling commands.

The tool addresses the need for programmatic access to Baidu Cloud Storage through a terminal interface. It works by implementing shell-like commands for common file operations—listing directories, uploading, downloading, copying, moving, and deleting files. A distinguishing feature is its integration of share link and instant transfer (秒传) functionality for saving files from shared sources directly to the user's cloud storage, built on top of the original iikira/BaiduPCS-Go foundation.

The project suits developers and power users who prefer command-line workflows over graphical interfaces and need to automate Baidu Cloud Storage operations. It runs on Windows, macOS, Linux, and mobile devices. The tool does not provide download acceleration beyond what the official Baidu client offers; users seeking performance tuning should consult the configuration documentation. Those evaluating adoption should note that this is a fork extending the original BaiduPCS-Go with transfer capabilities rather than a completely independent implementation.

Development activity shows consistent maintenance with regular updates addressing user-reported issues and feature requests. The project maintains active engagement with the community through documented known issues and a TODO list, indicating ongoing refinement of functionality and bug fixes.