Sub-Store is a Node.js backend service for managing and converting proxy configurations across multiple platforms (QX, Loon, Surge, Stash, Shadowrocket, etc.). It provides RESTful APIs for subscription management, collection grouping, artifact processing, file handling, settings, logging, token-based sharing, and synchronization with remote storage (e.g., GitHub Gist). The system features a modular architecture with a central `$` object for shared state (caching, logging, HTTP client, environment), a proxy processing pipeline (parse β preprocess β process operators β produce), and platform-specific producers/parsers. Key capabilities include format conversion between proxy schemes (URI, Clash, Surge, Loon, QX, sing-box), rule-based traffic filtering, scriptable configuration manipulation, age-encrypted secure sharing, and automated cron jobs for tasks like artifact sync and MMDB updates. The codebase demonstrates strong engineering practices through separation of concerns, extensive test coverage (Mocha/Chai), and reusable utility patterns. Notable components include age encryption for secure data sharing, configurable caching layers with TTL and auto-cleanup, request concurrency control for external API limits, and a migration system for schema evolution. However, the reliance on `eval` for environment variable handling and dynamic imports introduces runtime fragility, and the extensive platform-specific logic (numerous producers/parsers) increases maintenance complexity. Despite these challenges, the project is actively maintained with recent commits and shows commitment to quality via structured error handling, validation patterns, and dependency management via pnpm.
This is a curated content hub for Shadowrocket, an iOS network proxy app, hybrid in nature: its user-facing value is a Chinese-language README catalog of installable resources (original .sgmodule modules for ad-blocking, traffic-splitting policies for DeepSeek/Emby/Wi-Fi Calling, DNS overrides for CMCC IPTV; .list rule sets; a lazy configuration; 30+ original color themes encoded as shadowrocket://color URL schemes), while its only executable surface is a scheduled data-aggregation pipeline. The live GitHub Pages site referenced throughout the README (redirect.html, theme.html, images) is not present in this branch's file tree β only README.md, a generated modules.json, a CI workflow, and one build script are visible, so the repo-as-code is essentially an ETL job, not a runtime service. The functional core is scripts/build-modules.js, a dependency-free Node.js script executed by GitHub Actions every 6 hours. It parses the repo's own README for .sgmodule/.srmodule/.module URLs, enumerates module files from community repos (fmz200/wool_scripts, zirawell/R-Store) via the GitHub Trees API, probes each module's first 2KB using HTTP Range requests to extract #! metadata (name, description, icon), enriches entries with icons resolved from three icon libraries using Chinese/English app-alias matching, deduplicates and pins key tools (Script-Hub, Sub-Store, BoxJs), then writes modules.json β the feed consumed by the ShadowStore module directory (shadowstore.dpdns.org). External dependencies are GitHub API endpoints, raw.githubusercontent.com, and a GITHUB_TOKEN for API rate limits; there is no package.json or npm dependency graph. There are no unit tests and the script is tuned to Shadowrocket/Surge file formats, but it demonstrates transferable engineering patterns: github.com/blob to raw.githubusercontent.com URL normalization, partial-content fetch for cheap metadata extraction, 404/invalid-content detection, a bounded-concurrency worker pool with progress logging, and alias-based fuzzy icon resolution. Maintenance is genuinely active (automated syncs commit modules.json regularly; last commit 2026-09-04), and technical drift is low β Node 22 LTS, current GitHub Actions checkout/setup-node v5, modern JS syntax (global fetch, AbortController, nullish coalescing).
This repository contains a comprehensive Bash script (sing-box.sh) for deploying and managing the sing-box proxy server with multi-protocol support (VLESS, Hysteria2, TUIC, ShadowTLS, Shadowsocks, Trojan, VMess/VLess over WebSocket, H2/gRPC Reality, AnyTLS, NaiveProxy) and integrated Cloudflare Argo Tunnel for inbound connectivity. The script automates installation, configuration generation, service management (systemd/OpenRC), subscription output for various clients (V2rayN, Clash, ShadowRocket, Throne, Sing-box), and provides an interactive menu for ongoing operations. It supports both interactive and non-interactive (parameterized or config-file) deployment modes, and includes a Dockerfile for containerized deployment. The architecture is a monolithic Bash script with functions for system detection, dependency installation, certificate generation, JSON config creation, firewall management, and traffic statistics via clash_api. External dependencies include sing-box, cloudflared, jq, qrencode, nginx, and openssl. The script is widely used (5559 stars) and actively maintained, with recent commits addressing bug fixes and feature additions.
This repository provides curated, daily-updated rule lists for the Shadowrocket iOS proxy application. It contains three main rule modules: DIRECT (domains that should bypass the proxy), PROXY (domains that should be routed through the proxy), and REJECT (domains to block, primarily for ad/tracker blocking). The rules are generated from multiple upstream sources (dnsmasq-china-list, v2fly domain list, gfwlist, adblock lists, etc.) and are built automatically via an unseen CI pipeline. The repository also includes a 'factory' directory with append/exclude text files that allow users to customize the generated lists by adding or removing specific domains. While the repository is not a software application, it serves as a valuable data asset for anyone using Shadowrocket or similar proxy tools, providing a comprehensive and well-maintained set of routing rules. The data is presented in Shadowrocket's module format, making it easy to integrate.
This is a configuration-only repository for Shadowrocket, an iOS VPN/proxy application. It provides dozens of pre-built rule sets that control how network traffic is routed (direct vs. proxy) and includes ad-blocking rules compiled from multiple public sources such as GFWList, EasyList, and community-maintained domain lists. The repository does not contain any application code, libraries, or data processing pipelines; it is solely a collection of static `.conf` files. The build process that generates these configurations resides in a separate `build` branch (not included in the release branch), using Python scripts to merge and format rules daily via GitHub Actions. Users import these configuration files directly into Shadowrocket for automatic traffic splitting and ad filtering. The rules are continuously updated (daily cron) and include specialized modes like whitelist, blacklist, China-only, and lazy configurations with proxy groups for fine-grained control.
This repository contains a collection of deployment and management scripts for setting up and maintaining a multi-protocol proxy server (sing-box) on VPS and free hosting platforms (Serv00/Hostuno). The system automates the installation of five proxy protocols (Vless-reality, Vmess-ws, Hysteria-2, Tuic-v5, Anytls), generates TLS certificates, configures Cloudflare Argo tunnels for CDN proxying, and provides keep-alive mechanisms via cron, GitHub Actions, Cloudflare Workers, and a Node.js web server to prevent service downtime on free hosts. The primary entry points are interactive bash scripts (`sb.sh` for VPS, `serv00.sh` for Serv00) and a non-interactive keep-alive script (`serv00keep.sh`). The architecture is a set of loosely coupled shell scripts and a small Express.js application, not a monolithic service. External dependencies include sing-box, cloudflared, and standard Linux utilities. The code is functional and widely used (10k+ stars) but exhibits typical script-level craftsmanship: long monolithic functions, global variable usage, and tight coupling to specific hosting environments. The last commit date (2026-10-13) appears anomalous and likely a data error, but the repository shows active maintenance with recent stars and forks.
This repository is a massive, curated collection of network proxy routing rules (εζ΅θ§ε) for multiple proxy tools including Surge, Loon, QuantumultX, Shadowrocket, Clash, Stash, and AdGuard. The rules are auto-generated by an internal 'RULE GENERATOR' from public data sources (e.g., LM-Firefly/Rules, ACL4SSR, kr328.app) and cover thousands of servicesβfrom streaming platforms and social media to banking and gaming. Each rule set is provided in multiple formats (`.list`, `.yaml`, `.sgmodule`, `.plugin`) and distributed via daily-updated master and irregular release branches with CDN mirrors. The repository also includes a smaller set of automation scripts (JavaScript) that run inside proxy clients, performing tasks such as ad removal, cookie harvesting, daily check-ins, and TestFlight beta joining. These scripts rely on a custom cross-platform framework called MagicJS, which abstracts the APIs of Surge, Loon, QuantumultX, and Node.js. While the primary character is data aggregation and transformation (rule generation), the presence of application-like automation scripts makes it a hybrid repository. The rule sets are the core deliverable and are widely used by the proxy tool community. The automation scripts are secondary but demonstrate non-trivial engineering for multi-account session management and persistent storage. The repository is actively maintained (last commit 2026-08-21, though some rule sets show stale timestamps from 2024) and has a large user base (27k stars). However, technical drift is medium due to reliance on external data sources, embedded library duplication, and lack of automated testing. Reproducibility is low because the rule generator is not publicly available, and the scripts require specific proxy tool environments and MITM setup.
This repository is a comprehensive collection of ad-blocking filter lists, CSS styles, JavaScript scripts, and configuration files for proxy tools (Surge, QuantumultX, Shadowrocket, Clash) and browser extensions (uBlock Origin Lite, Tampermonkey). It targets both international and Chinese websites, with a strong focus on streaming, adult, and content farm sites. The core functionality is delivered through platform-specific rule lists (`.list`, `.conf`, `.sgmodule`, `.yaml`) and a set of userscripts that inject CSS/JS into web pages via MITM proxy or browser script managers. The repository also includes a large set of pre-compiled uBlock Origin Lite scriptlets that implement advanced ad-blocking techniques such as cookie removal, attribute removal, eval blocking, and timer manipulation. The project is community-driven, with issue templates for reporting new ad locations. While primarily a configuration/rule collection, it contains substantial JavaScript code that demonstrates client-side ad-blocking patterns.
This repository is a static collection of proxy subscription links and configuration files for V2Ray and Clash proxy clients. It contains a README.md with promotional material for various VPN services, a list of free proxy URIs in v.txt, a Clash YAML configuration file (c.yaml) with hundreds of proxy entries, and a vpn.md with a promotional link. The repository serves as a free source of proxy configurations for circumventing internet censorship. It does not contain any original software code. The architecture is trivial: it is a file-based subscription endpoint. The primary data flow is users downloading these files and importing them into proxy clients.
This repository is a binary distribution hub for the Android VPN client 'Shadowrocket for Android'. It contains no source code, build scripts, or development artifacts. The only substantive content is a README file with download links for pre-built APK files targeting different CPU architectures (arm64-v8a, armeabi-v7a, x86_64, x86), along with translations of that README into 32 languages. The repository serves solely as a release channel for the closed-source Shadowrocket application; there are no entry points, data flows, or external dependencies to analyze. From a software engineering perspective, this is not a codebase but a static file index. No components are reusable because no code exists to extract.