vernesong/OpenClash
Some data may be outdated — see provenance labels.
A Clash Client For OpenWrt observed · 2026-10-02
Health v2 · maintenance only
95/100
- Activity 97
- Release rhythm 90
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: 18
- age_days: 2701
- days_rel: 71
- days_push: 20
- n_releases_24m: 8
Adoption not part of the score
27664 stars · 4024 forks observed · 2026-10-02
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
OpenClash is a LuCI plugin that runs the Mihomo (Clash) proxy client on OpenWrt routers. It supports protocols like Shadowsocks, VMess, Trojan, and Snell with flexible rule-based policy routing.
Use cases
- run clash proxy on my openwrt router
- route traffic through shadowsocks or vmess on a router
- rule-based traffic splitting for the whole home network
- manage mihomo proxy via a web interface
- bypass censorship at the router level
When to choose
- you run OpenWrt and want transparent, whole-network proxying
- you need a LuCI-managed Clash client with rule-based routing
- you want support for many proxy protocols on a router
When to avoid
- you need a proxy client on desktop or mobile rather than a router
- your router does not run OpenWrt or lacks required kernel modules
- you want a simple single-device proxy without router configuration
Facets
plugin · maturity active
proxy networking security privacy routing networking privacy self-hosted security self-hosted embedded clash openwrt luci mihomo shadowsocks vmess trojan proxy-client router linux
1 source
- readme: https://github.com/vernesong/OpenClash · fetched 2026-10-02 · 01f61512de32
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| vernesong/OpenClash | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="vernesong/OpenClash")
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem