E-Ink Display with a Raspberry Pi and a Web Interface to customize and update the display with various plugins
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
fatihak/InkyPi has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in fatihak/InkyPi respond to incoming external pull requests in approximately 0.3 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 21.2 places fatihak/InkyPi in the D tier.
The external contributor pull request merge rate for fatihak/InkyPi is 0.0%, based on public PR activity from non-core contributors.
fatihak/InkyPi currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in fatihak/InkyPi. Reviews community pull requests with focus on project quality.
Discussions in fatihak/InkyPi focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/fatihak/InkyPi?utm_source=github&utm_medium=badge)
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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~1 hours (29% approval). Keep your diff compact for rapid review.
This is more a question than a bug. My InkyPi looses connection after some time, about a week. It can update it self, with calendar, count down, comics etc. so it has internet connection, but I cannot connect to it either over http nor ssh. I have tried to figure out what the problem is,but not succeeded so far. Any suggestions?
Prerequisites Please confirm the following: [ X] I have searched open and closed issues to make sure it isn't already reported [X ] I reviewed the troubleshooting guide [ X] I reviewed InkyPi service logs and will paste any relevant logs below Describe the bug downloadable WS epd drivers linked in package do not work for a specific model of WS screen, despite being listed as the same model. Expected behavior the screen updates when the software tells it to To Reproduce Steps to reproduce the behavior: 1 buy/own the "RPI Zero Photopainter" model of the display "https://www.waveshare.com/rpi-zero-photopainter-acce.htm" 2 attempt to install the project using the instructions provided Additional context OK with the basic pre-reqs out of the way I can speak a bit more freely. I set up and installed the package on the RPI zero "photopainter" version of the Waveshare epd screen. its a 7.3in "e" display, and the pi is connected directly to it using the "hat+" standard according to their w
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 fatihak/InkyPi, 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 fatihak/InkyPi acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
fatihak/InkyPi has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 21.2 places fatihak/InkyPi in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, fatihak/InkyPi 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 fatihak/InkyPi 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.