GetMerged

ory/docs - Open Source PR Review Scorecard

The Ory documentation

C-Rank Grade: B (Solid) - 47/100

External PR Merge Rate: 70%

Response Time: 8d

First Timer Success: 74%

Frequently Asked Questions

Is ory/docs welcoming to first-time open-source contributors?

ory/docs has a recorded first-timer success rate of 73.9%. Repositories ranked B 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 ory/docs respond to incoming external pull requests in approximately 186.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 47.3 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 47.3 places ory/docs in the B tier.

What is the external contributor pull request merge rate for ory/docs?

The external contributor pull request merge rate for ory/docs is 70.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in ory/docs?

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

ory
ory/docsB•Solid162
GitHub
Back to Explorer
ory

ory/docs

162
B•Solid(47/100)TypeScript

The Ory documentation

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 ory/docs.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •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
7 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
70.3%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
9 core
Highly collaborative maintainer core
Diagnostic Health HUD
70.3%
Merge Gauge
73.9%
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 ory/docs
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/ory/docs)](https://getmerged.abhishekco.de/ory/docs?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

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

View all good first issues directly on GitHub

Looking for more TypeScript beginner tasks?Explore TypeScript 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 ory/docs

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

Frequently Asked Questions - Contributing to ory/docs

01

Is ory/docs welcoming to first-time open-source contributors?

ory/docs has a recorded first-timer success rate of 73.9%. Repositories ranked Solid 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 ~7 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 47.3 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 47.3 places ory/docs in the Solid tier.

04

What is the external contributor pull request merge rate for ory/docs?

The external pull request merge rate is 70.3%. 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 ory/docs?

Yes, ory/docs currently has 3 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 ory/docs 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.