A package index for the Haskell ecosystem
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 91%
Response Time: 4d
First Timer Success: 67%
flora-pm/flora-server has a recorded first-timer success rate of 66.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in flora-pm/flora-server respond to incoming external pull requests in approximately 86.8 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 72.0 places flora-pm/flora-server in the S tier.
The external contributor pull request merge rate for flora-pm/flora-server is 91.5%, based on public PR activity from non-core contributors.
flora-pm/flora-server currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in flora-pm/flora-server. Prompt code reviews with positive guidance for new contributors.
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/flora-pm/flora-server?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~56 hours (96% approval). Large PRs (>500 lines) take ~417 hours (41% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Haskell.
Symbolic formula representation and solver interaction library
The official formatter for Nix code
An experimental proof assistant based on a type theory for synthetic ∞-categories.
We use a naïve List.find when normalising categories, which is linear in complexity. We can probably use a Map instead.
We only use blue/red messages when starting the executables, we should vendor those.
Today, iso8601-time is only used for parseISO8601, but we already use iso8601ParseM from the time library elsewhere, so no need for an extra dep.
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 flora-pm/flora-server, 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 flora-pm/flora-server acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.5% were successfully merged into the primary branch.
flora-pm/flora-server has a recorded first-timer success rate of 66.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 72.0 places flora-pm/flora-server in the Elite tier.
The external pull request merge rate is 91.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, flora-pm/flora-server currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for flora-pm/flora-server 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.