Documentation for Stellar
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 35%
Response Time: -
First Timer Success: 50%
stellar/stellar-docs 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.
Maintainers in stellar/stellar-docs respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 61.7 places stellar/stellar-docs in the A tier.
The external contributor pull request merge rate for stellar/stellar-docs is 35.4%, based on public PR activity from non-core contributors.
stellar/stellar-docs currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in stellar/stellar-docs welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/stellar/stellar-docs?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (44% approval). Large PRs (>500 lines) take ~115 hours (16% approval). Keep your diff compact for rapid review.
Make sure people are aware of access control as this is a frequently asked question or frequently missed package https://tech.spiko.io/posts/stellar-integration/
What problem does your feature solve? Developers building on Soroban need guidance on how to handle data migrations when their contract storage schema needs to change. While upgrading contract code is documented, migrating existing storage data is not covered. Reference: https://discord.com/channels/897514728459468821/966788672164855829/1463250846123819203 cc @tupui What would you like to see? Documentation covering data migration strategies for Soroban smart contracts, including: How to perform data migrations today (e.g., deploying a new contract version with migration code, running the migration, then potentially deploying another version to remove migration-only code) Best practices and patterns for structuring migration logic Reference to how other chains handle data migrations may be helpful (separate from any existing docs about migrating contracts from other chains to Soroban) What alternatives are there? Developers could figure this out on their own?
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to stellar/stellar-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 stellar/stellar-docs acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 35.4% were successfully merged into the primary branch.
stellar/stellar-docs 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.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 61.7 places stellar/stellar-docs in the Welcoming tier.
The external pull request merge rate is 35.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, stellar/stellar-docs currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for stellar/stellar-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.