Self-hosted AI agent platform built on OpenClaw. Enterprise-ready, offline-capable, open source. 🦞
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 95%
Response Time: -
First Timer Success: 100%
heypinchy/pinchy has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in heypinchy/pinchy respond to incoming external pull requests in approximately 0.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 56.2 places heypinchy/pinchy in the A tier.
The external contributor pull request merge rate for heypinchy/pinchy is 94.9%, based on public PR activity from non-core contributors.
heypinchy/pinchy currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Self-hosted AI agent platform built on OpenClaw. Enterprise-ready, offline-capable, open source. 🦞
Collaborative maintainer environment in heypinchy/pinchy. Reviews community pull requests with focus on project quality.
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/heypinchy/pinchy?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 05:00 UTC (05: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 ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (43% approval). Keep your diff compact for rapid review.
Symptom When the browser window is short (small height), a modal whose content is taller than the viewport overflows both above and below the window and the clipped parts are unreachable — there is no scroll. Surfaced during release testing in the IMAP connect wizard: with the SMTP port-block diagnostic banner shown (Port 465 is commonly blocked … we can reach port 587 …), the Add-Integration modal grows tall enough that in a short window the top (title/fields) and/or the "Switch to 587 / Save" action at the bottom get cut off. See attached screenshot: the modal extends past the top and bottom edges of the viewport. Root cause (affects ALL modals, not just IMAP) The shared DialogContent in packages/web/src/components/ui/dialog.tsx (~line 56) constrains width but not height, and is vertically centered: fixed top-[50%] left-[50%] … w-full max-w-[calc(100%-2rem)] translate-x-[-50%] translate-y-[-50%] … sm:max-w-lg There is no max-h-* and no overflow-y-auto. Because the content
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 heypinchy/pinchy, 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 heypinchy/pinchy acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 94.9% were successfully merged into the primary branch.
heypinchy/pinchy has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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.2 places heypinchy/pinchy in the Welcoming tier.
The external pull request merge rate is 94.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, heypinchy/pinchy currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for heypinchy/pinchy 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.