clash-verge-rev/clash-verge-rev

A modern GUI client based on Tauri, designed to run in Windows, macOS and Linux for tailored proxy experience

151.3k stars · 10.9k forks · Rust

Healthy

Healthy: actively maintained by 36 people, no known risks.

Why

No rule fired.

What would change this

Partly checked: maintenance (Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.)
A dormant maintenance status, a deprecated or archived package, a successor link, or a critical advisory would change this.

Maintenance

Partial

Active

Human commits, 30 days: 116
Human commits, 90 days: 314
Human commits, 365 days: 1.4k
Bot share of commits, 365 days: 16%
Last commit: Oct 14, 2026 (1 day ago)
Last human commit: Oct 14, 2026 (1 day ago)
Authors, 90 days: 36
Last release: Oct 9, 2026 (6 days ago)
Median PR merge time: 11 hours

Responsiveness: of 29 recent issues, 76% got a maintainer reply. Median first response: 2 hours.

Commit counts are estimated: the commit sample stops before the window start, so GitHub's totals were scaled by the sampled bot share.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete

Owner: Organization
Commits sampled: 419 since Oct 14, 2025
Authors for half of commits: 2
Authors for 80% of commits: 4
Contributors: 174

Top committers

wonfen: 36% of commits
Tunglies: 33% of commits
oomeow: 10% of commits
Dragon1573: 7% of commits
wysha-object: 2% of commits

Shares come from the newest sampled commits, since the commit sample is capped.

Sources: Commits, Contributors

Stars

Complete

Organic, confidence high

Bars show stars gained each week. Orange bars overlap a burst.

Bursts

Jan 21, 2024 to Jan 25, 2024: about 361 more stars than usual, peak 208 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Feb 5, 2024 to Feb 6, 2024: about 249 more stars than usual, peak 268 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Apr 25, 2024 to Apr 27, 2024: about 293 more stars than usual, peak 242 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Jun 17, 2024 to Jun 20, 2024: about 350 more stars than usual, peak 221 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Nov 24, 2024 to Nov 28, 2024: about 475 more stars than usual, peak 228 in one day, a spike that tapers off. Outside explanation: a jump in forks, a jump in issues and pull requests.
Mar 1, 2025 to Mar 6, 2025: about 462 more stars than usual, peak 245 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
Nov 19, 2025 to Nov 20, 2025: about 234 more stars than usual, peak 263 in one day, a spike that tapers off. Outside explanation: a jump in issues and pull requests.
Nov 23, 2025 to Nov 26, 2025: about 568 more stars than usual, peak 339 in one day, a shape we can't classify. Outside explanation: a jump in issues and pull requests.
Sep 20, 2026 to Sep 23, 2026: about 575 more stars than usual, peak 389 in one day, a flat block of stars. Outside explanation: a jump in issues and pull requests.

18 stars GitHub has since removed (tracked since Oct 13, 2026).

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

The star history looks organic.

Sources: How star history is analyzed

Risk

Complete

Flags

No risk flags.

License

Now: GPL-3.0 (OSI-approved)
A year ago: GPL-3.0 (OSI-approved)

Packages

No published packages found.

Sources: GitHub: clash-verge-rev/clash-verge-rev

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/clash-verge-rev/clash-verge-rev/badge.svg)](https://reporadar.ai/clash-verge-rev/clash-verge-rev)

Earlier verdicts

Oct 14, 2026: Healthy
Oct 13, 2026: Healthy
Oct 13, 2026: Healthy

Computed 20 hours ago · method 2026.10.2