sub-store-org/sub-store

Advanced Subscription Manager for QX, Loon, Surge, Stash, Egern and Shadowrocket!

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 19th, 2020
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 1,352
Total Stargazers: 10,426 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.2 hours
Mean response time: 2.4 days
90th percentile: 7.0 hours
Tracked items: 235

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 13% of issues opened in the past year have been closed. Three people close 69% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 3
Closed in 7 days: 3
Avg open age: 471 days
Stale 30+ days: 10
Stale 90+ days: 10

Recent activity

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

Top labels

  • enhancement (11)
  • bug (2)
  • documentation (1)

Detailed Description

Sub-Store is an advanced subscription manager for proxy applications including QX, Loon, Surge, Stash, Egern, and Shadowrocket.

The tool addresses the challenge of managing proxy subscriptions across multiple incompatible client applications. It works by converting subscription formats between different proxy protocols and clients, allowing users to aggregate multiple subscription sources into a single URL, and providing the ability to host and modify subscriptions or configuration files. This centralized approach eliminates the need to manually configure each client separately.

Developers and users managing proxy configurations across multiple platforms should consider Sub-Store when they need format conversion capabilities, subscription aggregation, or the ability to apply transformations to subscription data. The project supports various proxy protocols including Shadowsocks, ShadowsocksR, Trojan, and VMess. The tool can be deployed as a Node or server instance, or integrated as a module within proxy applications, with configurable CORS allowlisting to control which browser origins can access the backend API.

The project maintains active development with regular updates to support new proxy protocols and client applications. The maintainers have documented security considerations around the sub.store domain used for module rewrites, acknowledging potential data leakage risks and providing mitigation strategies such as local DNS mapping. The team has chosen to retain the current domain despite these concerns rather than migrate to a new one, indicating a pragmatic approach to balancing usability against theoretical risks. Documentation is maintained through a project wiki, and the official frontend is hosted separately from the backend infrastructure.