C-Rank Grade: B (Solid) - 56/100
External PR Merge Rate: 89%
Response Time: 8d
First Timer Success: 100%
pluk-inc/himekuri has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pluk-inc/himekuri respond to incoming external pull requests in approximately 194.9 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 56.0 places pluk-inc/himekuri in the B tier.
The external contributor pull request merge rate for pluk-inc/himekuri is 88.9%, based on public PR activity from non-core contributors.
pluk-inc/himekuri currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Swift project in pluk-inc/himekuri welcoming community pull requests and bug fixes.
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/pluk-inc/himekuri?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 03:00 UTC (03: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 ~127 hours (96% approval). Large PRs (>500 lines) take ~935 hours (40% approval). Keep your diff compact for rapid review.
The pad's window frame is autosaved (HimekuriWindow) and the falling-page overlay in himekuri/Views/Falling/FallingPageOverlay.swift sizes itself from main.screen ?? NSScreen.main. None of this has been exercised across multiple displays, or when a display is disconnected while the pad is sitting on it. Known-unknowns worth checking: Does the pad come back onto a valid screen after the display it lived on goes away? showCalendar() re-centres only when the frame no longer intersects NSScreen.main.visibleFrame, which may not cover every case. Does a page torn on a secondary display fall down that screen, or the main one? Does "Pin to Desktop" behave on a second display, where the desktop-icon window level differs?
This is the part of Himekuri I'm least happy with, and the main reason the repo is open. If you know SpriteKit, Metal, SwiftUI performance, or — best of all — the actual aerodynamics of falling paper, I'd love the help. You don't need to take the whole thing. Each bullet below stands on its own. The fall is hand-authored, not simulated himekuri/Views/Falling/FallPlan.swift is four tracks of tuned waypoints — x, y, rotation, tilt — played back by a KeyframeAnimator (or interpolated by hand on macOS 13 and below). It knows nothing about the sheet's mass, the air, or the shape of the torn piece, so every page falls the same way and it reads as swaying rectangle rather than paper. The falling-plate / tumbling-card literature has models cheap enough to run per-frame that would beat my hand-tuned numbers easily. Even a 2-DOF flutter model driven by the throw velocity would be a real improvement. The ripple is a sine wave himekuri/Paper/PaperShaders.metal waves the falling sheet with
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 pluk-inc/himekuri, 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 pluk-inc/himekuri acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.9% were successfully merged into the primary branch.
pluk-inc/himekuri has a recorded first-timer success rate of 100.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 56.0 places pluk-inc/himekuri in the Solid tier.
The external pull request merge rate is 88.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pluk-inc/himekuri 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 pluk-inc/himekuri 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.