OrchardCMS/OrchardCore - Open Source PR Review Scorecard

Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.

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

External PR Merge Rate: 73%

Response Time: 2d

First Timer Success: 62%

Frequently Asked Questions

Is OrchardCMS/OrchardCore welcoming to first-time open-source contributors?

OrchardCMS/OrchardCore has a recorded first-timer success rate of 61.9%. 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 OrchardCMS/OrchardCore respond to incoming external pull requests in approximately 47.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 60.1 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 60.1 places OrchardCMS/OrchardCore in the A tier.

What is the external contributor pull request merge rate for OrchardCMS/OrchardCore?

The external contributor pull request merge rate for OrchardCMS/OrchardCore is 72.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in OrchardCMS/OrchardCore?

OrchardCMS/OrchardCore does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

OrchardCMS
OrchardCMS/OrchardCoreA•Welcoming8.2k
GitHub
Back to Explorer
OrchardCMS

OrchardCMS/OrchardCore

8,195
InactiveA•Welcoming(60/100)C#

Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
6.0/10
Patience Score
6.7/10
Nitpick Rate
52%

Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in OrchardCMS/OrchardCore.

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
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
72.5%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
61.9%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
28 core
Highly collaborative maintainer core
Diagnostic Health HUD
72.5%
Merge Gauge
61.9%
1st-Timer
Community Vibe48/100

Embed C-Rank Badge

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

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

Active Good First Issues (3)

View on GitHub

Describe the bug When you open the three-dot menu of Media files, the menu items show the standard pointer (if hovering the icons) or the insert text cursor (when hovering the texts). However, these all should show the hand cursor, indicating that they're clickable. Orchard Core version Latest main (4306c07). To Reproduce Just open the menu. Expected behavior The hand cursor is displayed. Logs and screenshots 2026-09-13_23h15_12.mp4

📅 Opened Sep 13, 2026💬 0 comments
Quality: 90/100Contribute

Is your feature request related to a problem? When you highlight (select) files in the Media Library, it shows as a thin blue border (the middle file is highlighted): This is easy to miss, especially if you have a lot of files (even more if they have darker or blue colors). With the dark theme it's a bit more visible, but not by much: Describe the solution you'd like Use a more visible highlighting approach, possibly by using the bottom of the thumbnail (at first, I actually thought that meant an item was highlighted): Not sure about the dark theme, perhaps like this? And the border can also remain. Describe alternatives you've considered Have a thicker border, like:

📅 Opened Sep 12, 2026💬 3 comments
Quality: 90/100Contribute

Is your feature request related to a problem? The v3 Media Library displays a View link when you hover a file: This is useful if you want to check the file, primarily an image or PDF, in the full window. The current Media Library doesn't have this feature: you can only download files from the three-dot menu, or use the grid layout to see small thumbnails of the files. Describe the solution you'd like Add a View link under the three-dot menu. Describe alternatives you've considered Displaying a link on hover/click, but that would be out of place.

📅 Opened Sep 12, 2026💬 5 comments
Quality: 90/100Contribute
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 OrchardCMS/OrchardCore

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

Frequently Asked Questions - Contributing to OrchardCMS/OrchardCore

01

Is OrchardCMS/OrchardCore welcoming to first-time open-source contributors?

OrchardCMS/OrchardCore has a recorded first-timer success rate of 61.9%. 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.1 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 60.1 places OrchardCMS/OrchardCore in the Welcoming tier.

04

What is the external contributor pull request merge rate for OrchardCMS/OrchardCore?

The external pull request merge rate is 72.5%. 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 OrchardCMS/OrchardCore?

OrchardCMS/OrchardCore 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 OrchardCMS/OrchardCore 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.