Spring Cloud Alibaba provides a one-stop solution for application development for the distributed solutions of Alibaba middleware.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 58%
Response Time: 1d
First Timer Success: 40%
alibaba/spring-cloud-alibaba has a recorded first-timer success rate of 40.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in alibaba/spring-cloud-alibaba respond to incoming external pull requests in approximately 27.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 59.1 places alibaba/spring-cloud-alibaba in the A tier.
The external contributor pull request merge rate for alibaba/spring-cloud-alibaba is 57.7%, based on public PR activity from non-core contributors.
alibaba/spring-cloud-alibaba currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in alibaba/spring-cloud-alibaba. Maintains strict focus on technical quality and test standards.
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/alibaba/spring-cloud-alibaba?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~18 hours (72% approval). Large PRs (>500 lines) take ~130 hours (26% approval). Keep your diff compact for rapid review.
Which Component Nacos Discovery (spring-cloud-starter-alibaba-nacos-discovery) Describe the bug PR #4350 has been merged into 2025.1.x and fixes the network-interface address selection problem reported in #4342. However, the latest 2025.0.x branch at the time of verification (b8403af4b2d94460e54dd53552d2e87c7f6265c0) still contains the same condition in NacosDiscoveryProperties.init(): if (currentAddress instanceof Inet4Address || currentAddress instanceof Inet6Address && !currentAddress.isLoopbackAddress()) { ip = currentAddress.getHostAddress(); break; } Because && has higher precedence than ||, Java parses this as: currentAddress instanceof Inet4Address || (currentAddress instanceof Inet6Address && !currentAddress.isLoopbackAddress()) Therefore, the loopback check applies only to IPv6 addresses. When spring.cloud.nacos.discovery.network-interface is configured, an IPv4 loopback address such as 127.0.0.1 may be selected as the service registrat
Background AI coding tools (Cursor, Copilot, Qoder, etc.) are becoming part of everyday development workflows. These tools rely on an AGENTS.md file in the repository root to understand project-specific context — build commands, conventions, debugging tips, and architectural decisions that aren't obvious from code alone. Adding an AGENTS.md to Spring Cloud Alibaba will help community contributors use AI tools more effectively when submitting PRs, fixing bugs, and diagnosing issues. Proposal Create and maintain an AGENTS.md at the repository root, built collaboratively by the community. Below are the proposed sections with example content to illustrate the expected depth and style. 1. Project Structure & Module Layout Describe the high-level directory structure, what each top-level module is responsible for, and how modules relate to each other. This section should evolve as the project adds or removes modules. Example: spring-cloud-alibaba/ ├── spring-cloud-alibaba-starters/
Hi, I have a question about this fix: #3644 While checking the code in 2025.1.0.0, it seems the logic introduced by this fix may not be triggered. I'm not sure if I missed something. Could you confirm whether this fix is included and expected to work in 2025.1.0.0? Thanks! Which Component Nacos Config
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 alibaba/spring-cloud-alibaba, 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 alibaba/spring-cloud-alibaba acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.7% were successfully merged into the primary branch.
alibaba/spring-cloud-alibaba has a recorded first-timer success rate of 40.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 59.1 places alibaba/spring-cloud-alibaba in the Welcoming tier.
The external pull request merge rate is 57.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, alibaba/spring-cloud-alibaba 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 alibaba/spring-cloud-alibaba 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.