vernesong/openclash

A Clash Client For OpenWrt

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 50 minutes ago
Added to GitGenius on September 2nd, 2026
Created on May 29th, 2019
Open Issues & Pull Requests: 75 (+0)
GitHub issues: Enabled
Number of forks: 4,019
Total Stargazers: 27,412 (+1)
Total Subscribers: 203 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.3 hours
Mean response time: 3.6 days
90th percentile: 6.2 days
Tracked items: 934

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Almost all tracked open issues have seen activity in the last three months. Only 8% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 58
New in 7 days: 6
Closed in 7 days: 9
Avg open age: 77 days
Stale 30+ days: 27
Stale 90+ days: 0

Recent activity

Opened in 7 days: 6
Closed in 7 days: 8
Comments in 7 days: 5
Events in 7 days: 10

Top labels

  • bug (745)
  • Stale (626)
  • enhancement (223)
  • duplicate (1)
  • help wanted (1)
  • invalid (1)
  • question (1)
  • wontfix (1)

Detailed Description

OpenClash is a Clash client for OpenWrt that runs the Mihomo proxy engine on router devices.

The tool solves the problem of routing traffic through proxy protocols on OpenWrt systems. It implements policy-based routing by accepting configuration rules that determine which traffic flows through which proxy servers. The project supports multiple proxy protocols including Shadowsocks, ShadowsocksR, Vmess, Trojan, and Snell, allowing users to define flexible rules for traffic handling across their network.

OpenClash suits users who run OpenWrt on routers and want centralized proxy management for all connected devices. It is appropriate for those comfortable with router-level configuration and who need to route different traffic types through different proxy servers based on custom rules. The tool requires a substantial dependency chain including luci, dnsmasq-full, bash, curl, iptables modules, and ruby with yaml support, so adoption depends on having sufficient router resources and the ability to satisfy these prerequisites.

The project maintains active development with regular updates to the codebase. The tool receives ongoing refinement and bug fixes across its core functionality. Documentation is provided through a wiki guide to help users configure and operate the system.