thehardwarestore.ai

FlClash is a production multi-platform proxy/VPN client that embeds and manages the mihomo (Clash.Meta) Go core. The Dart/Flutter app (Riverpod, Drift, freezed) drives a real core lifecycle: profile/subscription import and validation, proxy group and rule management, TUN/VPN on Android, system proxy on desktop, live connections/requests/DNS views, latency probing, streaming-service availability checks, and WebDAV backup/restore. The Go core exposes a method-dispatch IPC contract (updateConfig, changeProxy, getConnections, watchRoute, probe, serviceCheck, etc.) consumed through an Android cgo bridge and a desktop helper process. This is a full application, not a library or data project — no notebooks, no research pipelines. The architecture is layered: Flutter UI → manager/provider layers → core controller → framed JSON IPC → Go mihomo core. Desktop builds add a Rust privileged helper service (systemd unit / Windows SCM, Unix socket with peer-credential auth) and Rust plugins for global hotkeys, QuickJS evaluation of script-based profile overrides, and a rope-backed code editor (code_forge). Native integration plugins for system tray, window management, system proxy, and WiFi SSID are shipped as separate Dart packages with per-OS implementations in C++/Swift/Kotlin. A custom build-hook system compiles and SHA-256-fingerprints the Go core and Rust helper artifacts with file-locking to make native builds cacheable and idempotent. The codebase is unusually disciplined. Test/ subdirectories include contract tests that parse Go structs from the mihomo submodule to verify DNS-override parity, AST-parsing tests verifying every core method is dispatchable, architectural lint tests (platform layering, dead-file detection, UI tooltip enforcement, Material-icon bans), plus unit and widget tests across every layer. Concurrency is handled deliberately: priority message batching between core and UI, serial task scheduling, claim/cancel semantics for GEO/probe updates, and an Android service state machine with newest-request-wins arbitration. Release tooling generates changelogs from conventional commits and a CI pipeline produces deb/rpm/AppImage/DMG/Inno packages. Caveats: the polyglot stack (Dart, Go, Rust, Kotlin, C++, Swift) and tight coupling to mihomo internals via a git submodule make wholesale extraction impractical, and large amounts of generated code (freezed, riverpod_generator, Drift, flutter_rust_bridge) require coordinated regeneration. Browser-platform and TV branches add conditional complexity, and some UI tests assert precise pixel/animation timings that are brittle. The genuinely reusable value lives in the standalone patterns — IPC framing and batching, the rope data structure, fractional indexing, async utilities, and the fingerprinted build cache — plus the independent plugin packages themselves.

Neko Master is a production-grade traffic analytics platform for Clash/Mihomo and Surge proxy gateways. It collects real-time connection data via WebSocket or HTTP polling, aggregates it in SQLite (always) and optionally ClickHouse, and serves a rich dashboard built with Next.js 16, React 19, and Tailwind CSS. The system supports both direct collector-to-gateway mode and a Go-based agent mode for remote or isolated networks. The backend is a Fastify 5 server with WebSocket push, repository-patterned database access, in-memory realtime store, and health-aware dual-write routing. The frontend provides per-domain, per-IP, per-proxy, per-rule, per-country, and per-device statistics with time-range filtering, pagination, charts, and interactive visualizations including a DAG rule-chain flow. The project is a monorepo with pnpm and Turborepo, including a shared TypeScript types package and extensive CI/CD. While primarily an application, it has strong data-engineering aspects: batch buffering, time-series aggregation, GeoIP enrichment, and ClickHouse integration for large-scale deployments.

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.

Clash Verge Rev is a cross-platform desktop proxy management GUI built with Tauri 2 (Rust backend) and React 19 (TypeScript frontend). It serves as the control interface for the mihomo (Clash Meta) proxy core, enabling users to manage proxy subscriptions, switch proxy groups, toggle system proxy and TUN mode, view real-time traffic and connection details, and configure advanced settings like DNS overrides, script enhancements, and backup to WebDAV. The architecture is modular: a Rust backend handles core lifecycle, config management (using a unique 'Draft' transactional pattern), system integration (tray, hotkeys, auto-launch), and IPC with a privileged service on Windows. The frontend uses MUI, SWR, and virtual lists for a responsive UI with drag-and-drop profile/group editing, a built-in Monaco editor for YAML/JS configs, and real-time WebSocket-based data visualization. The repository also includes a Rust workspace with several crates (media unlock checker, i18n, logging, signal handling, rate limiter, system info plugin) that could be extracted and reused in other Tauri applications.

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.

ArgoX is a comprehensive bash-based deployment and management tool for setting up Xray proxy servers with Cloudflare Argo tunnels on VPS. It supports 12 proxy protocols (VLESS, Hysteria2, Shadowsocks, etc.) and provides interactive and non-interactive installation, automated configuration generation, firewall management, subscription output for multiple clients (Clash, V2rayN, Sing-box, etc.), and hot-reload via Xray gRPC API. The script handles complex tasks like deriving X25519 keys, managing Cloudflare tunnels via API, selecting optimal CDN proxies, and implementing Hysteria2 Realm for NAT traversal. It is actively maintained with frequent updates and extensive error handling.

This repository contains a collection of scripts and configurations for merging and generating proxy subscriptions, primarily for Clash and Sing-box. It aggregates various proxy nodes from different sources and compiles them into a unified subscription.

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.

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.

This repository is a comprehensive collection of proxy routing rule sets and configuration files for multiple proxy clients (Surge, Loon, Quantumult X, Stash, Shadowrocket, mihomo, sing-box, Egern). It provides pre-curated domain/IP lists for services (e.g., Netflix, Telegram, OpenAI), ad-blocking (e.g., Ads_AWAvenue, EasyListChina), and China network identification (e.g., ChinaASN with 5076 entries). The rules are duplicated across platforms with format adaptations, and the repository includes full client configuration templates and server deployment examples (e.g., sing-box Hysteria2, AnyTLS). A few Surge panel scripts (Peekabo, Aliyun ECS CDT, Lightsail) demonstrate self-contained HTTP API client patterns with HMAC signing and caching. While not a software application itself, the repository is a dependency for proxy clients and includes several reusable script components.

This repository provides a transparent proxy package for OpenWrt using Mihomo (a clash-compatible rule-based proxy core) as the backend. It is a full LuCI application that allows users to configure proxy modes (redirect, TPROXY, TUN), manage subscriptions, define access control rules, and monitor logs through a web interface. The system is designed for OpenWrt ≥24.10 with firewall4 (nftables) and kernel ≥5.13. The architecture consists of three OpenWrt packages: `nikki` (main service and scripts), `mihomo-meta` (stable core), and `mihomo-alpha` (alpha variant). The service is managed via procd init script (`nikki.init`), which handles starting/stopping Mihomo, setting up routing rules and nftables tables, and scheduling tasks. Configuration is stored in UCI (OpenWrt's standard configuration system) and processed through a pipeline: UCI options → `mixin.uc` (ucode script) generates a JSON overlay → `yq` merges it with a base profile → final Mihomo config. Traffic interception rules are generated dynamically from a utpl template (`hijack.ut`) that produces nftables rulesets. Key entry points include the LuCI views (`app.js`, `profile.js`, `mixin.js`, `proxy.js`, `editor.js`, `log.js`) for web-based management, the init script for service lifecycle, and shell scripts for installation/upgrade. External dependencies are Mihomo core, `yq` for YAML processing, and standard OpenWrt tools (procd, nftables, ucode). The repository also includes a large hardcoded nftables set of Chinese IP prefixes (`geoip_cn.nft`) for bypassing mainland China traffic.

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 is a proxy subscription aggregation and distribution system. It periodically collects free proxy subscription links (Clash YAML and V2Ray URI formats) from multiple public sources, merges them, classifies nodes by TCP connectivity (reachable/unreachable/untested), and serves the resulting files via a Cloudflare Worker. The system is driven by a GitHub Actions workflow that runs every 12 hours, executing Python scripts to fetch, process, and commit updated subscriptions. The architecture is a data pipeline application with a serverless serving layer. Key entry points include main.py (orchestrating collection and merging), check_nodes.py (TCP connectivity classification), and worker/sub.mjs (Cloudflare Worker for serving with caching and ETag). External dependencies include requests, PyYAML, and the Cloudflare Workers runtime. The repository also includes a weekly commit history cleanup workflow to keep repository size small. The project is actively maintained with frequent updates and tests, though it relies on unstable external proxy sources.

This is a LuCI application package for OpenWrt routers that provides a full web-based management interface for Clash/Mihomo proxy services. It handles the complete proxy lifecycle: service management via procd, transparent proxy setup (TPROXY/TUN/MIXED modes), DNS manipulation, firewall rule generation via nftables/iptables, subscription management, and a real-time log viewer. The package installs to /opt/clash/ and integrates deeply with OpenWrt's hotplug, UCI, and LuCI systems. A separate Vue-based SPA dashboard (zashboard) is bundled for advanced features like Tailscale management, network diagnostics (bandwidth tests, STUN NAT detection), and an embedded SSH terminal. The architecture is a classic OpenWrt package: shell scripts for service and firewall management (/etc/init.d/clash, /opt/clash/bin/clash-rules), LuCI JavaScript views for the admin UI (config, settings, rulesets, log), hotplug scripts for network events, and a vendored Ace editor for YAML editing. The firewall engine is the most substantial component — roughly 1400 lines of modular shell that generates nftables/iptables rules, manages subscription IP caches with locking, and auto-generates fake-IP whitelists from rule providers. The init script includes rollback logic that restores DNS/firewall state on failure, preventing bricked router connectivity. The repository is explicitly legacy: the README states active development has moved to SSClash-Go (a single static binary with built-in web UI). This repo receives bugfix maintenance only. Technical drift is medium — the vendored Ace editor is an old version (1.5.0), the shell scripts use fragile heuristics for YAML transformation, GitHub API calls for kernel downloads lack caching, and the dual configuration (config.yaml plus /opt/clash/settings) can confuse users. However, the CI pipeline is maintained and the package builds for current OpenWrt versions (both ipk and apk formats). For reuse, the most valuable components are the modular firewall engine pattern (nft/iptables abstraction with idempotent rule generation), the procd init script with rollback logic, and the LuCI view utilities (chunked file writing, service polling). These could be extracted for other OpenWrt proxy/VPN services with minimal modification. The repo serves as a solid reference for OpenWrt package structure, LuCI app development, and transparent proxy integration, though new projects should target the successor SSClash-Go instead.

This repository is a curated collection of proxy rule configurations for multiple proxy clients (Clash, Stash, Shadowrocket, Surge, Surfboard, QuantumultX, Egern). It provides pre-built rule sets for routing traffic for specific services (YouTube, Netflix, Disney+, Bilibili, TikTok, HoYoGames, etc.), ad blocking via MITM rewriting, DNS configuration, and various utility overrides (e.g., cron scripts for JD sign-in, Bilibili manga, Epic free games). The repository is essentially a personal configuration template set, with the actual logic and maintenance delegated to external upstream rule repositories (e.g., blackmatrix7/ios_rule_script, NobyDa, app2smile). The code (configs) is well-organized by tool and purpose, with clear Chinese comments. It demonstrates a thorough understanding of proxy tool capabilities, especially Stash's override system for advanced MITM rewriting and ad blocking. However, it is not a reusable software library or application; it is a static configuration archive. The primary value is for users of these proxy tools who want an out-of-the-box rule set with minimal customization.

This repository provides a Chinese localization (汉化) of Clash for Windows, a popular proxy client. It contains modified app.asar files (renderer.js and main.js) with translated UI strings, build scripts for packaging the modified Electron app, and installers. The core functionality is string replacement via regex-based translation tables. The repo also includes the original Clash core binaries and static assets. It is not a standalone software project but a patch set; the code quality is functional but unremarkable, with boilerplate build scripts and tightly coupled modifications. The primary value is the translation effort, not software craftsmanship.

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 promotional landing page for the 'mojie' VPN service (魔戒机场). It contains no application source code, libraries, or data pipelines. The core content consists of multilingual README files (Chinese, English, Russian, Persian) that list VPN subscription plans, pricing, invitation codes, affiliate links, and server status tables, along with a handful of performance test screenshots in the mojie/ directory. The only functional component is a GitHub Actions workflow (.github/workflows/daily-sync.yml) that runs nightly to update the date in all README headers and forces pushes the repository to GitLab (Gitee sync is commented out). This is primarily a marketing and affiliate revenue vehicle, not a software project. Because there is no software to evaluate, the quality score reflects the minimal engineering effort: a trivial cron-based workflow with dated bash/perl commands. It is actively maintained in the sense that the date is refreshed daily, but there is no meaningful code craftsmanship or reusability.