Elegant open source project tracking. Self-hosted Kanban for teams — free Community edition, with PLANKA Pro for organisations.
C-Rank Grade: B (Solid) - 43/100
External PR Merge Rate: 11%
Response Time: 8d
First Timer Success: -
plankanban/planka has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in plankanban/planka respond to incoming external pull requests in approximately 192.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 42.8 places plankanban/planka in the B tier.
The external contributor pull request merge rate for plankanban/planka is 11.4%, based on public PR activity from non-core contributors.
plankanban/planka currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Elegant open source project tracking. Self-hosted Kanban for teams — free Community edition, with PLANKA Pro for organisations.
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in plankanban/planka.
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/plankanban/planka?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~125 hours (14% approval). Large PRs (>500 lines) take ~922 hours (15% approval). Keep your diff compact for rapid review.
Where is the problem occurring? I encountered the problem while using the application (Frontend) What browsers are you seeing the problem on? Firefox Current behavior When deploying Planka with ingress-nginx, error 400 are logged in the controller and the load circle spince for ever. 10.233.66.42 - - [05/Mar/2026:09:09:07 +0000] "GET /socket.io/?__sails_io_sdk_version=1.2.1&__sails_io_sdk_platform=node&__sails_io_sdk_language=javascript&EIO=4&transport=websocket HTTP/1.1" 400 11 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0" 1031 0.002 [planka-planka-1337] [] 10.233.69.185:1337 11 0.002 400 acbc2fc1ef76abbbea871774185630f3 the issue is not limited to Firefox, chrome as well Desired behavior It worked before Steps to reproduce Deploy using helm chart with private certificate on kubernetes cluster. Open browser and login, then the spinning will comes in there forever and the above error is generated every 5 sec in nginx-ingress controller Othe
Hi. First of all, congratulations on the v2.0.0 release. We were particularly looking forward to the @mentions. After successfully upgrading, I hade some issue with mailing updates and mentions. We run planka together with some other tooling on our private cloud and have an exchange connector (direct mail sending via port 25) to allow mails being sent from internal services. I've done the following things: Whitelisted the outlook mail host. Removed SMTP vars from container file (podman) Added the SMTP settings via the GUI. This allowed me to send a test message. (this works) Then I went to a card and did a @mention and then it doesn't send, I see this error: 2026-02-16 19:00:39 [E] Error sending email: Error: Can't send mail - all recipients were rejected: 550 5.4.1 Recipient address rejected: Access denied. For more information see https://aka.ms/EXOSmtpErrors Subsequently I also added azure:// to apprise but that also doesn't seem to work, also not using the test button, I get e
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 plankanban/planka, 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 plankanban/planka acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 11.4% were successfully merged into the primary branch.
plankanban/planka has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 42.8 places plankanban/planka in the Solid tier.
The external pull request merge rate is 11.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, plankanban/planka 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 plankanban/planka 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.