Open-source, self-hosted customer support desk in a single binary. A lightweight alternative to Intercom, Zendesk, Chatwoot.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 62%
Response Time: 1d
First Timer Success: 50%
abhinavxd/libredesk 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 abhinavxd/libredesk respond to incoming external pull requests in approximately 33.1 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 55.7 places abhinavxd/libredesk in the A tier.
The external contributor pull request merge rate for abhinavxd/libredesk is 62.4%, based on public PR activity from non-core contributors.
abhinavxd/libredesk currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (72% positive review sentiment). Active code reviews with constructive guidance for new contributors in abhinavxd/libredesk.
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/abhinavxd/libredesk?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~21 hours (78% approval). Large PRs (>500 lines) take ~159 hours (28% 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 Go.
Vitess is a database clustering system for horizontal scaling of MySQL.
A collection of samples
资源定期浪费，可用于 Oracle 甲骨文保活。
It would be really nice if I could link from one ticket to another in private notes. Just like we can use @ to mention an agent or team, I would like to be able to use # to reference a specific conversation/ticket. Libredesk already keeps reference numbers on each conversation, so being able to type something like: Please look at #108 for more details into a private note would be great.
On your left sidebar, where you see the views - Having the number of open tickets visible there is nice. Then agents don't need to click into each one in order to see if there is anything to go through!
The widget API already exposes the field unread_message_count, so I suppose Libredesk already knows which chats are unread by the customer. Can we get some sort of indicator in Libredesk that a chat has not been read? I assume this one checkmark means the message was successfully sent to libredesk But for example a second checkmark where the second checkmark means its read by the customer would be a great addition.
The widget uploads attachments immediately after a file is selected, instead of letting users select multiple files or send them along with a message.
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 abhinavxd/libredesk, 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 abhinavxd/libredesk acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.4% were successfully merged into the primary branch.
abhinavxd/libredesk 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 ~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 55.7 places abhinavxd/libredesk in the Welcoming tier.
The external pull request merge rate is 62.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, abhinavxd/libredesk currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for abhinavxd/libredesk 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.