MerlinKodo/clash-rev
Continuation of Clash core project observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 73
Flags: archived no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 1029
- days_rel: n/a
- days_push: 1007
- n_releases_24m: 0
Adoption not part of the score
1802 stars · 111 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A continuation of the Clash proxy core, a rule-based tunnel/proxy client supporting multiple protocols. The repository is now archived and users are directed to its successor, MetaCubeX/mihomo.
Use cases
- route traffic through proxy servers with rule-based routing
- bypass network censorship with clash-compatible proxy core
- run a local proxy client supporting vmess, trojan, and ss
- self-host a clash core for multi-protocol tunneling
- chain and load-balance proxy connections
When to choose
- you need a clash-compatible core for legacy setups or tooling
- you want a lightweight rule-based proxy client
When to avoid
- starting a new project - use mihomo (MetaCubeX/mihomo) instead
- you need ongoing updates or security fixes, since the repo is archived
Facets
application · maturity abandoned
proxy vpn networking privacy networking privacy censorship-circumvention self-hosted cross-platform windows cli clash-core proxy-server rule-based-routing archived successor-mihomo linux macos
1 source
- readme: https://github.com/MerlinKodo/clash-rev · fetched 2026-08-28 · 756770e60e53
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| MerlinKodo/clash-rev | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="MerlinKodo/clash-rev")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem