This repository is a full-featured web control panel for managing Xray-core proxy servers, known as 3x-ui. It provides a complete management interface for creating and configuring proxy inbounds (VLESS, VMess, Trojan, Shadowsocks, WireGuard, AmneziaWG, TUIC, Hysteria, MTProto, etc.), managing client accounts with traffic quotas and expiry, operating multi-node distributed setups, and generating subscription links (v2ray, Clash, JSON). The backend is written in Go using the Gin web framework and GORM for database access (SQLite or PostgreSQL), while the frontend is a React/TypeScript SPA with Ant Design and TanStack Query. The system includes sidecar supervision for Xray-core, MTProto (mtg), and TUIC binaries, a Telegram bot, Discord integration, email notifications, and an API token system. It features extensive automated testing (unit, integration, scale, mutation tests) and a documentation site built with Next.js and fumadocs.
FoxyProxy is a cross-browser extension (Chrome, Firefox, Edge) for advanced proxy management. It allows users to configure individual proxies, use pattern-based proxying (wildcard, regex, match patterns), set proxy per tab or container (Firefox), enable global exclude lists, and manage WebRTC settings. The codebase is highly modular, using ES modules and Manifest V3. It implements single proxy, PAC, and 'proxy by patterns' modes, with features like sync, import/export, a live log, pattern tester, and enterprise policy support. The architecture separates concerns clearly: background service worker handles proxy configuration via browser APIs, options page provides full UX, popup offers quick controls, and context menus add convenience. The code is well-structured, uses modern JavaScript (ES2022), and shows solid engineering practices. Reusable modules include pattern validation, file I/O, and flag display utilities.
Yet Another Surge Dashboard (YASD) is a React 19 single-page application for managing and monitoring Surge network proxy instances through their HTTP API. The application provides a web-based interface to configure Surge instances, view network traffic statistics, manage profiles and rules, and inspect request logs. Built with a modern tech stack including Vite, TypeScript, Redux Toolkit, SWR for data fetching, and shadcn/ui for components, it features internationalization (English/Chinese), mobile responsiveness, and PWA capabilities. The architecture follows React best practices with clear separation of concerns between components, hooks, state management, and API layers.
This repository is a web-based management panel for sing-box proxy servers, providing a Gin-based web UI and REST API for configuring inbounds, outbounds, clients, subscriptions, and traffic statistics. It includes custom protocol implementations for many proxy protocols (VMess, VLESS, Trojan, Shadowsocks, Hysteria, TUIC, etc.), session tracking, and subscription generation in multiple formats (plain, JSON, Clash). The architecture is modular with core, service, API, and sub packages, using SQLite for persistence and a cron job system for stats collection and maintenance. The codebase demonstrates strong engineering practices with reusable components like a session registry, graceful QUIC shutdown wrapper, and security middleware. However, it is tightly coupled to sing-box internals, requiring custom manager copies to preserve hot add/remove functionality that upstream dropped, and it has a history of migration-heavy schema evolution. The project is actively maintained with frequent commits, comprehensive testing, and multi-platform deployment support (Linux, Windows, Docker).
OpenClash is an OpenWrt/LuCI application that turns a router's admin interface into a full Clash/Mihomo proxy management system. The production code is mostly Lua CBI/controller modules, view templates with embedded JavaScript, and shell/Ruby orchestration scripts. It manages subscription downloads, YAML config generation and overwrite, core binary updates, GeoIP/GeoSite/China-route database updates, DNS/firewall integration, streaming-unlock probe and selection, and optional OIX managed-service integration. It also bundles the MetaCubeXD and zashboard single-page dashboards for live proxy monitoring and connection inspection. Architecturally, the project is an OpenWrt package: UCI configuration, an init.d service, and watchdog/procd lifecycle management. The LuCI controller exposes around 80 JSON/AJAX actions and uses low-level nixio fork/poll/pipe helpers for streaming subprocess output. The backend repeatedly combines shell scripts with Ruby-based YAML parsing and mutation to handle Clash configuration. External dependencies are significant: GitHub releases/CDNs for core and GEO data, subconverter services, the OIX API, and several IP-info services. Hardcoded URLs, vendored minified dashboard bundles, and multi-language shell/Ruby/Lua/C tooling are the main technical-drift risks. This is not a data-research repository; the data handled is operational proxy/node/routing state rather than analyzable datasets. No automated test suite is apparent in the tree; quality comes from defensive shell patterns (flock locks, ETag caching, retry loops) and feature depth rather than automated verification. The most reusable pieces are YAML.rb's merge/encryption layer, the server_url share-link parser widget, and the controller's streaming subprocess helpers.
Podkop is an OpenWrt package for traffic routing using sing-box as the proxy core. It provides a LuCI web interface (TypeScript frontend compiled to JavaScript) with tabs for Settings, Sections (proxy/VPN/block/exclusion), Dashboard (real-time traffic via Clash API WebSocket), and Diagnostic (checks for DNS, sing-box, nftables, FakeIP). The backend consists of shell scripts: /usr/bin/podkop (main entry), /etc/init.d/podkop (procd init), and libraries in /usr/lib/podkop/ (constants.sh, nft.sh, helpers.sh, sing_box_config_manager.sh, etc.). It uses nftables for traffic marking and TPROXY, dnsmasq for DNS hijacking with FakeIP, and downloads community domain/subnet lists from GitHub. It supports proxy protocols: VLESS, Shadowsocks, Trojan, SOCKS, Hysteria2. The architecture is monolithic: the frontend communicates with the backend via shell commands (exec) and WebSocket to the Clash API. The backend manages sing-box configuration, nftables rules, and list updates via cron. Key entry points include install.sh (installation), /usr/bin/podkop (service management), and the LuCI view files. External dependencies include sing-box, jq, curl, nft, coreutils-base64, bind-dig, and the diagnostic endpoints (ip.podkop.fyi, fakeip.podkop.fyi). The system is in beta, with breaking changes possible; users are advised to clear LuCI cache on updates. The codebase demonstrates solid engineering with modular shell libraries, a well-structured TypeScript frontend with unit tests for validators, and CI/CD pipelines. However, it has some drift risks: hardcoded version requirements, compiled JS committed to the repository, and reliance on external services. The frontend includes reusable components such as a reactive store service, WebSocket manager, and composable validators.
Hiddify-Manager is a comprehensive anti-censorship proxy/VPN management system designed for multi-user environments. It orchestrates a suite of proxy cores (Xray, Sing-Box, HAProxy, Nginx, WireGuard, etc.) via systemd services, a Flask-based web panel, and a CLI tool. The system supports over 20 protocols (VLESS, VMess, Trojan, Shadowsocks, Reality, Telegram proxies, DNS tunnels) and is optimized for regions with heavy internet censorship (Iran, China, Russia). It provides automated installation, configuration generation via Jinja2 templates, multi-node support, Docker deployment, and cloud-init/Terraform scripts for cloud provisioning. The codebase is actively maintained with frequent updates, but contains deprecated services and a large shell script surface that introduces maintenance complexity.
This repository contains the official documentation website for the Remnawave proxy management panel. Built with Docusaurus 3.9.x and React 19, it generates a static site that provides installation guides, configuration references, tutorials, and API documentation. The site features a landing page with custom React components (hero section, stats bar, feature highlights, project grids, client cards) and multilingual help articles covering authentication methods, editor templates, and page configurations. A Caddy server serves the built output with routing for the landing page and documentation paths. The repository also includes an awesome-remnawave page indexing community tools (backup scripts, bots, monitoring tools) and a curated list of proxy clients with data-driven card displays. While the actual Remnawave panel backend is hosted separately, this documentation site is a well-structured, actively maintained resource that follows Docusaurus best practices with custom theming, dark mode, and analytics integration.
Botright is a Python library built on Playwright that provides advanced browser automation with stealth features to evade bot detection. It includes proxy management, fingerprint spoofing using real browser profiles (chrome-fingerprints), human-like mouse movements, and CAPTCHA solving for hCaptcha, reCAPTCHA, and Geetest (though Geetest support is currently disabled). The library wraps Playwright's API with a custom layer that intercepts browser events, modifies user agent, platform, and other fingerprinting vectors, and injects anti-detection scripts. It supports both headless and headed modes, proxy rotation, and response caching. The codebase is well-structured but has commented-out modules indicating incomplete transitions (e.g., Geetest).
This is a production-grade web application for automated batch registration and management of OpenAI accounts. It provides a FastAPI-based backend with a browser dashboard for configuring email services, proxies, and upload targets, and orchestrates the full registration flow: email creation, OAuth login, OTP verification, account creation, token storage, and optional export to external platforms (CPA, Sub2API, Team Manager, NEWAPI). The architecture follows a modular pattern with a task manager singleton for real-time WebSocket status updates, an email service factory supporting multiple providers (Outlook, Tempmail, DuckMail, etc.), and a proxy management system with dynamic failover. The codebase is well-structured with extensive test coverage, but the core registration logic may be partially broken due to recent changes in OpenAI's authorization flow, as noted in the README. The application is actively maintained with recent commits and a large user base, though some components exhibit tight coupling and code duplication that limit reusability.
This repository is a production-ready Telegram bot that manages a multi-protocol VPN/proxy server infrastructure deployed via Docker Compose. It supports WireGuard, Xray (VLESS), Shadowsocks, OpenConnect, NaiveProxy, Hysteria, MTProto, and others, plus AdGuard Home for DNS filtering and split tunneling via PAC files. The bot handles user subscriptions, configuration generation, service restarts, IP banning, and automated maintenance (cron, log analysis, backups). The architecture is monolithic: a single large PHP script (app/bot.php ~5000 lines) processes Telegram webhooks and executes commands on Docker containers via SSH. The codebase is functional and actively used (500+ stars) but suffers from lack of tests, tight coupling, hardcoded infrastructure assumptions, and security concerns (Docker socket exposure, SSH in every container). Reusable components are limited, with app/calc.php (CIDR calculation) being a standout isolated utility.