v2rayNG is a production-grade Android VPN/proxy client that provides a comprehensive interface for managing V2Ray and Xray proxy configurations. It supports multiple proxy protocols (VMess, VLESS, Shadowsocks, Trojan, WireGuard, Hysteria2, SOCKS, HTTP), subscription management with auto-update, routing rules, per-app proxy, and backup/restore via local files or WebDAV. The app runs in three modes: VPN (TUN), proxy-only (local SOCKS/HTTP), and root (iptables transparent proxy). It uses native cores (Xray or v2fly) via JNI and manages complex configuration generation, including DNS segmentation, observatory-based load balancing, and fragment settings. The architecture follows standard Android patterns with Compose UI, ViewModels, and background services in separate processes. The codebase is actively maintained with a large community, though some modules (e.g., CoreConfigManager) are monolithic and could benefit from further decomposition.
Algo VPN is a deployment tool that automates the setup of a personal VPN server on cloud providers or local Ubuntu machines. It uses Ansible to provision a hardened server running strongSwan (IKEv2/IPsec) and WireGuard, with optional DNS encryption via dnscrypt-proxy and privacy enhancements like log rotation and history clearing. The architecture is a set of Ansible playbooks and roles, orchestrated by a shell script entry point (`algo`) that invokes `ansible-playbook`. Cloud provisioning is handled by provider-specific roles (AWS EC2, DigitalOcean, Azure, GCE, etc.), while server configuration roles handle system hardening, PKI certificate generation, VPN service configuration, and client profile generation (mobileconfig, WireGuard .conf, QR codes). The system is designed for security and privacy: it uses strong crypto defaults (ECC secp384r1), minimal logging, and unattended upgrades. External dependencies include Ansible, community.crypto collection, cloud provider SDKs, and the dnscrypt-proxy package. The primary data flow is: user edits `config.cfg` → Ansible playbook runs → cloud VM is created → server is configured with VPN services → client configuration files are generated and stored locally. User management (add/revoke) is handled by a separate playbook. The repository includes extensive unit, integration, and end-to-end tests, with Docker-based integration testing and CI/CD via GitHub Actions.
Oblivion is a cross-platform VPN/tunneling application that provides secure internet access through Cloudflare Warp technology (unofficially) and supports Zero Trust authentication. The application uses a hybrid architecture with a Flutter frontend for the UI and a Rust core for tunnel logic, communicating via FFI on desktop and platform channels on mobile. It supports multiple tunneling protocols (MASQUE over QUIC/HTTP-3, WireGuard) and includes features like split tunneling, traffic obfuscation, and geo-location-based exit node selection. The codebase demonstrates strong engineering practices in platform abstraction, configuration management, and privilege separation, though build complexity and dependency management introduce maintenance challenges.
This is an Electron desktop application (branded 'Clash Party' / 'mihomo-party') that serves as a full-featured GUI manager for the Mihomo (Clash Meta) proxy core. It manages proxy subscriptions, profiles, rules, DNS, TUN, system proxy, connections, traffic logging, and provides both a standard mode and a simplified 'simple mode' for configuration. A standout feature is its custom plugin system (cpx-plugin/2) that enables third-party proxy providers to integrate via OAuth, Ed25519-signed discovery, and encrypted vault storage, with a reference gateway server included in the repository. The application also includes traffic usage analytics (SQLite database with multi-resolution aggregation), a smart core integration using LightGBM models for routing, and extensive platform-specific support (Windows, macOS, Linux, AUR packages). While primarily an application, it contains data engineering elements in its traffic recording and model download pipelines. The codebase is well-structured with extensive unit tests, reusable patterns (atomic writes, operation budgets, SSRF guards), and a large IPC surface. However, it has a very large feature surface, mixed-language comments, and some legacy build paths that increase maintenance complexity.
This repository provides a collection of shell scripts to automate the setup and management of an IPsec VPN server on Linux. It supports multiple VPN protocols (IPsec/L2TP, IPsec/XAuth, IKEv2) and a wide range of Linux distributions including Ubuntu, Debian, CentOS, Rocky Linux, AlmaLinux, Oracle Linux, and Alpine Linux. The main entry point is `vpnsetup.sh`, which detects the OS and runs the appropriate installer. The project also includes helper scripts for user management, IKEv2 certificate handling, upgrades, and uninstallation. Additionally, it offers an Azure ARM template for cloud deployment. The code is well-structured with OS-specific installers, common bash utility functions, and extensive documentation in multiple languages. It is a mature, widely-used DevOps tool for system administrators.
This repository contains the official IVPN desktop client, a multi-platform VPN application supporting Windows, macOS, and Linux. It is composed of three main components: a privileged Go daemon that manages VPN connections (OpenVPN, WireGuard, V2Ray), firewall (kill switch), DNS (including DNSCrypt-proxy for DoH), split tunneling, and WiFi trusted networks; a Go CLI for command-line control; and an Electron/Vue.js UI for graphical interaction. The daemon and clients communicate over a local TCP JSON protocol with authentication and event push. The codebase demonstrates strong engineering practices: platform abstraction via build tags, a custom ICMP ping library, a reusable logger, a type-safe IPC client library documented for third-party integration, and Windows WFP wrappers for firewall and split tunneling. Build scripts and native projects (Windows kernel driver, macOS helpers) handle cross-platform packaging and signing.
This repository implements a Linux desktop GUI for managing WireGuard VPN profiles. It is built using the Tauri v2 framework, combining a Rust backend for system-level operations (connection management, encryption, file I/O) with a Next.js 16 (React 19) frontend for the user interface. The application allows users to create, import, export, connect, and disconnect WireGuard tunnels, and provides optional at-rest encryption for profile data using a user-defined PIN. The architecture follows a clean IPC-based separation of concerns. The frontend communicates with the Rust backend exclusively through typed Tauri commands defined in `lib/effects.ts`. The backend in `src-tauri/src/main.rs` manages application state, executes WireGuard commands via shell scripts (`wg.sh`), and handles encryption via a dedicated security module. The UI is built from a comprehensive library of ~40+ composable, accessible components in `components/ui/`, demonstrating a strong commitment to frontend architecture and design system principles. The most reusable assets are the Rust security module (`security.rs`), which implements PIN-based encryption using Argon2id and XChaCha20-Poly1305 in a self-contained manner, and the typed IPC service layer (`lib/effects.ts`), which cleanly decouples the UI from the backend. The UI component library, while styled for this project, follows an architectural pattern (atomic, composable primitives) that is directly transferable to other React projects. The project is actively maintained with CI/CD, E2E testing, and semantic versioning, though it carries some technical drift in its Nix build configuration (targeting Tauri v1) and deprecated plugin permissions.
Hiddify is a cross-platform proxy/VPN client built with Flutter and a Go core (Sing-box). It supports multiple proxy protocols (Vless, Vmess, Reality, TUIC, Hysteria, WireGuard, SSH, etc.), subscription management, per-app proxy, routing rules, chain configuration, and advanced features like Warp, Psiphon, and TLS tricks. The architecture is a Flutter frontend communicating with a Go backend via gRPC/protobuf over a local socket. The app uses Riverpod for state management, drift for local SQLite storage, freezed for immutable models, and go_router for navigation. It has platform-specific native code for Android (Kotlin), iOS/macOS (Swift), Windows (C++), and Linux (C). The codebase is well-organized into feature modules, core infrastructure, and generated protobuf bindings. It is actively maintained with CI/CD pipelines and multi-platform releases, though it contains some commented-out code and generated file churn.
Everywhere is an iOS VPN/proxy client that lets users choose between three open-source proxy cores—Xray, sing-box, and mihomo—to route device traffic through custom configurations. The app uses Apple's Network Extension framework (NEPacketTunnelProvider) to establish a VPN tunnel, with the selected core executed inside the tunnel process. Configurations can be imported, subscribed to, or edited directly within a SwiftUI interface, and a bundled web dashboard (zashboard) provides real-time monitoring and control via the Clash API.
Se7en Pro is a Windows 10/11 anti-censorship VPN client that aggregates eleven circumvention protocols into one desktop application. In production it runs a Flutter glassmorphic GUI (Se7enFlutter) that talks over authenticated named pipes to a .NET 8 daemon (Se7enCore), which orchestrates child processes for Psiphon, Tor, Xray/sing-box, Aether (MASQUE/WireGuard/WARP), and SHARD (Cloudflare TLS fragmentation over VLESS/Trojan nodes). Chained multi-hop modes (Psiphon-over-WARP, Tor-over-V2Ray, etc.) are first-class features, and a Wintun/tun2socks TUN adapter provides system-managed routing with split tunneling by app, domain, and IP along with a kill switch, system proxy, DNS handling, LAN sharing, and admin elevation. Architecturally the daemon's ConnectionManager selects active engines behind an IConnectionEngine abstraction; LocalSocksEngineBase supplies a shared process-spawn/SOCKS5-probe/auto-restart lifecycle for every engine. The Flutter side is a Riverpod-driven dashboard with live speed/ping telemetry, engine-filtered log viewing, region picking, and a large settings surface. Primary data flows are: UI command → PipeCoreClient → IpcDaemonService JSON dispatch → ConnectionManager → engine process → local SOCKS5/HTTP proxy → system proxy or TUN; status and logs stream back over the same pipe. The daemon persists settings to settings.json, caches Aether edge pools, and fetches SHARD node lists from GitHub. The repo is hybrid in a narrow sense: it bundles curated operational datasets (Akamai/Cloudflare/Fastly IP ranges, Akamai seed IPs, SHARD seed nodes, Tor bridge strings) used at runtime for CDN fronting and edge discovery. These are static resource inputs to the application machinery, not research artifacts or pipeline outputs, so the dominant character is application. Craftsmanship is solid but uneven. The engine abstraction, IPC layer, Authenticode trust checks, DPAPI secret storage, and route-pinning logic are genuinely reusable. However, multi-thousand-line widget files (settings_page.dart ~2200 lines, split_tunnel_section.dart ~1200 lines), incomplete i18n coverage with hardcoded English/Chinese/Russian strings, version drift (UI reports v1.0.4 while the engine UA says 1.1.0), brittle relative resource paths, and bundled third-party binaries with limited update channels create real maintenance friction. Test coverage is thin (a few model/round-trip widget tests).
This repository is a stub. The current file tree contains no application source code—only a README and seven screenshots. The README explicitly states that the open-source project has been discontinued and transitioned into a commercial service at tunnl.to. There are no entry points, no executable files, no build configuration, and no code to analyze; the repo exists primarily as a notice and redirect for former users. The README explains that the old open-source version is still available for personal use but is not licensed for commercial use, and that the source was removed to avoid misleading users now that the application is closed-source. It also describes the rationale for the new UI, but none of that functionality exists in this repository. From a software engineering perspective, this is not a usable or reusable codebase; it is a deprecated project marker with screenshots and marketing/FAQ content.