Kurrier is a modern, self-hosted workspace for email, calendar, contacts and storage.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 47%
Response Time: 18h
First Timer Success: 67%
kurrier-org/kurrier has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kurrier-org/kurrier respond to incoming external pull requests in approximately 18.2 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 65.4 places kurrier-org/kurrier in the A tier.
The external contributor pull request merge rate for kurrier-org/kurrier is 47.4%, based on public PR activity from non-core contributors.
kurrier-org/kurrier currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Kurrier is a modern, self-hosted workspace for email, calendar, contacts and storage.
Active TypeScript repository in kurrier-org/kurrier with ongoing community development and issue triage.
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/kurrier-org/kurrier?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (59% approval). Large PRs (>500 lines) take ~87 hours (21% approval). Keep your diff compact for rapid review.
Description Add documentation for contributing and maintaining translations in Kurrier. The guide should cover: How to add a new language/locale Where translation dictionaries live and how they are structured Updating the locale list and dictionary loader Day.js/Mantine locale setup where required Updating the language selector Using the translation glossary for consistent terminology How to check that translation keys match the English dictionaries What to do when new English strings are added Basic testing/validation before submitting a PR This should give contributors a single reference when adding a new language or updating an existing translation.
Add support for aliases and catch-all addresses for domain identities. Requirements: Create multiple aliases for an existing email identity Incoming mail to an alias is delivered to the target identity/mailbox Allow sending/replying from an alias Support a domain-level catch-all (*@example.com) Configure which identity receives catch-all mail Prevent duplicate/conflicting aliases Manage aliases and catch-all from identity/domain settings Reuse the existing inbound/outbound mail pipeline
Add support for automatically forwarding incoming emails using the existing mail rules system. Requirements: Add a forward mail rule action Configure one or more destination email addresses Forward messages matching existing rule conditions Optionally keep the original message in Kurrier Preserve the original message/attachments when forwarding Prevent forwarding loops Use the identity’s existing outbound provider/SMTP configuration Support combining forwarding with other rule actions where appropriate Reuse the existing mail rules and inbound/outbound processing pipelines rather than creating a separate forwarding system.
Add vacation/out-of-office automatic replies for email identities. Requirements: Enable/disable per identity Configure subject and message Optional start/end date Automatically reply to incoming mail Reply only once per sender during the active period Ignore mailing lists, automated messages, bounces, and other auto-replies Prevent reply loops Use the identity’s existing outbound provider/SMTP configuration Add configuration under the identity settings and reuse the existing inbound/outbound mail pipeline.
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 kurrier-org/kurrier, 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 kurrier-org/kurrier acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.4% were successfully merged into the primary branch.
kurrier-org/kurrier has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 hours. 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 65.4 places kurrier-org/kurrier in the Welcoming tier.
The external pull request merge rate is 47.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kurrier-org/kurrier currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for kurrier-org/kurrier 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.