The Scala Package Index
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 29%
Response Time: -
First Timer Success: 60%
scalacenter/scaladex has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in scalacenter/scaladex 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 60.2 places scalacenter/scaladex in the A tier.
The external contributor pull request merge rate for scalacenter/scaladex is 28.9%, based on public PR activity from non-core contributors.
scalacenter/scaladex does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Growing Scala project in scalacenter/scaladex 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/scalacenter/scaladex?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~41 hours (36% approval). Large PRs (>500 lines) take ~304 hours (15% approval). Keep your diff compact for rapid review.
Motivation Recently Scaladex has been receiving unusually many requests, which has caused unresponsiveness. These requests may come from legitimate users or AI assistants, but it may also be malicious scraper bots. Either way, there is a need to distribute server's resources fairly and evenly. Identified Obstacles The public API doesn't seem to have any authentication or rate limiting. Therefore, a carelessly written script can flood the server with requests completely by accident. Implementation Guideline I propose to implement rate limiting for the public API. An optional authentication by Github token may be worth considering. Expectations The rate limit would make accidental flooding very unlikely, and purposeful DoS attacks harder to orchestrate. Authenticated users could enjoy an increased rate limit; potentially it would be possible to identify the users which abuse the server.
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 scalacenter/scaladex, 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 scalacenter/scaladex acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 28.9% were successfully merged into the primary branch.
scalacenter/scaladex has a recorded first-timer success rate of 60.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 60.2 places scalacenter/scaladex in the Welcoming tier.
The external pull request merge rate is 28.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
scalacenter/scaladex does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for scalacenter/scaladex 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.