What does the 49.8 C-Rank™ score (B 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 49.8 places PLFJY/ContextMenuMgr in the B tier.

Are there Good First Issues available in PLFJY/ContextMenuMgr?

PLFJY/ContextMenuMgr currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

Back to Explorer

PLFJY/ContextMenuMgr

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

Maintainers in PLFJY/ContextMenuMgr respond to incoming external pull requests in approximately 9.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

Q: What is the external contributor pull request merge rate for PLFJY/ContextMenuMgr?

The external contributor pull request merge rate for PLFJY/ContextMenuMgr is 100.0%, based on public PR activity from non-core contributors.

3,169

B•Solid(50/100)C#

Context Menu Manager Plus 是一个强大的实用程序，它可帮助您管理 Windows 上的右键菜单，并避免第三方向你的右键菜单里塞屎

Compare•

Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Mentor

Warmth Score

7.8/10

Patience Score

8.2/10

Nitpick Rate

25%

Responsive & active maintainer team in PLFJY/ContextMenuMgr. Reviews pull requests with focus on project architectural goals.

Top PR Submission Do's

•Verify all existing package test suites run cleanly
•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

9 hours

Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency

100.0%

High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success

0.0%

No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers

CRITICAL BUS FACTOR

Single maintainer

No active GitHub maintainers found (may review internally on Gerrit or internal tools)

Diagnostic Health HUD

100.0%

Merge Gauge

0.0%

1st-Timer

Community Vibe63/100

Embed C-Rank Badge

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

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

90-Day C-Rank Trajectory

10 snapshots

Historical health & responsiveness evolution

37.7/100C

Aug 28

-19.5

Aug 11Range: 37.7 – 62.1 ptsAug 28

PR Acceptance & Review Speed Forecast

Run Pre-flight PR CheckPrecomputed via Live PR Events

Overall Merge Odds

100.0%

External PR acceptance

First-Timer Rate

N/A

First PR success rate

Median Response (p50)

10h

50% receive response in

Tail Latency (p90)

N/A

90% receive response in

Active Maintainers: 0

Optimal PR Submission Window

Maintainer review activity heatmap & prime window prediction

Tuesday - ThursdayConfidence: NaN%

Peak Review Hour

14:00 UTC

Calculating local time...

Primary Window

14:00 - 18:00 UTC

Calculating local time...

Active Maintainers

Heuristic Estimate

Detected: UTC

24-Hour Maintainer Activity Heatmap (UTC)

LowPeak

00:0006:0012:0018:0023:00

Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).

PR Size vs Review Speed

Best Pull Request Size for PLFJY/ContextMenuMgr

Sweet Spot: < 150 lines

Small (<150 LOC)Recommended

6havg review

96% Merge Approval

Medium (150–500 LOC)Normal

15havg review

95% Merge Approval

Large (>500 LOC)Slow

2.0davg review

45% Merge Approval

Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (96% approval). Large PRs (>500 lines) take ~47 hours (45% approval). Keep your diff compact for rapid review.

Interactive Test: Test your planned branch diff against PLFJY/ContextMenuMgr's ~150 LOC sweet spot before opening a PR.

PR Merge Doctor · Pre-Submission Diff Check

Simulate Your PR Merge Speed

Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.

⚡ Sweet spot: ~150 LOC

Active Good First Issues (1)

View on GitHub

This repository currently has 1 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

Looking for more C# beginner tasks?Explore C# 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 PLFJY/ContextMenuMgr

When evaluating whether to contribute to PLFJY/ContextMenuMgr, 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 PLFJY/ContextMenuMgr acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to PLFJY/ContextMenuMgr

Is PLFJY/ContextMenuMgr welcoming to first-time open-source contributors?

PLFJY/ContextMenuMgr has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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?

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

What does the 49.8 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 49.8 places PLFJY/ContextMenuMgr in the Solid tier.

What is the external contributor pull request merge rate for PLFJY/ContextMenuMgr?

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

Are there beginner Good First Issues open in PLFJY/ContextMenuMgr?

Yes, PLFJY/ContextMenuMgr currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for PLFJY/ContextMenuMgr 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.