wnlen/clash-for-linux - Open Source PR Review Scorecard

🐧 一个更完整、更优雅的 Linux Clash / Mihomo 代理运行平台

C-Rank Grade: A (Welcoming) - 58/100

External PR Merge Rate: 88%

Response Time: 22d

First Timer Success: 50%

Frequently Asked Questions

Is wnlen/clash-for-linux welcoming to first-time open-source contributors?

wnlen/clash-for-linux has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in wnlen/clash-for-linux respond to incoming external pull requests in approximately 516.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 57.9 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.9 places wnlen/clash-for-linux in the A tier.

What is the external contributor pull request merge rate for wnlen/clash-for-linux?

The external contributor pull request merge rate for wnlen/clash-for-linux is 88.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in wnlen/clash-for-linux?

wnlen/clash-for-linux does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

wnlen
wnlen/clash-for-linuxAWelcoming5.9k
GitHub
Back to Explorer
wnlen

wnlen/clash-for-linux

5,875
AWelcoming(58/100)Shell

🐧 一个更完整、更优雅的 Linux Clash / Mihomo 代理运行平台

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in wnlen/clash-for-linux.

Top PR Submission Do's

  • Add unit tests with >80% coverage for modified code paths
  • Use conventional commit messages and clean branch names
  • Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without referencing an existing issue
  • Do not mix refactoring and feature logic into a single commit
  • Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
21 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
88.2%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
9 core
Highly collaborative maintainer core
Diagnostic Health HUD
88.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe50/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for wnlen/clash-for-linux
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/wnlen/clash-for-linux)](https://getmerged.abhishekco.de/wnlen/clash-for-linux?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for wnlen/clash-for-linux.

View all good first issues directly on GitHub

Looking for more Shell beginner tasks?Explore Shell GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for wnlen/clash-for-linux

When evaluating whether to contribute to wnlen/clash-for-linux, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of wnlen/clash-for-linux acknowledge new external contributions in approximately 21 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to wnlen/clash-for-linux

01

Is wnlen/clash-for-linux welcoming to first-time open-source contributors?

wnlen/clash-for-linux has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~21 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.9 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.9 places wnlen/clash-for-linux in the Welcoming tier.

04

What is the external contributor pull request merge rate for wnlen/clash-for-linux?

The external pull request merge rate is 88.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in wnlen/clash-for-linux?

wnlen/clash-for-linux does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for wnlen/clash-for-linux are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.