Loyalsoldier/clash-rules

🦄️ 🎃 👻 Clash Premium 规则集(RULE-SET),兼容 ClashX Pro、Clash for Windows 等基于 Clash Premium 内核的客户端。

28.8k stars · 2.2k forks

This repo isn't software code, so code checks are limited.

Healthy

Healthy: maintained by 1 person in the last 90 days, no known risks.

Why

No rule fired.

What would change this

Maintenance

Complete

Steady

Human commits, 30 days
0
Human commits, 90 days
1
Human commits, 365 days
4
Bot share of commits, 365 days
43%
Last commit
Jul 28, 2026 (2 months ago)
Last human commit
Jul 28, 2026 (2 months ago)
Authors, 90 days
1
Last release
Oct 13, 2026 (1 day ago)
Median PR merge time
2 hours

Responsiveness: of 5 recent issues, 20% got a maintainer reply. Median first response: 3 hours.

Sources: Commits, Releases, Merged pull requests, Issues

People

Partial
Owner
Personal account
Commits sampled
4 since Oct 14, 2025
Authors for half of commits
1
Authors for 80% of commits
1
Contributors
3

Top committers

Sources: Commits, Contributors

Stars

Complete

Organic, confidence high

Stars per week, 2020-07-26 to 2026-10-11. 8 weeks overlap a burst.Peak 758 a week2020-07-262026-10-11
Bars show stars gained each week. Orange bars overlap a burst.

Bursts

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

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: Loyalsoldier/clash-rules

Badge

Add this to a README to show the current verdict:

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

Earlier verdicts

Computed 10 hours ago · method 2026.10.2