Clipboard manager with advanced features
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 82%
Response Time: -
First Timer Success: -
hluk/CopyQ has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in hluk/CopyQ 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 59.8 places hluk/CopyQ in the A tier.
The external contributor pull request merge rate for hluk/CopyQ is 81.8%, based on public PR activity from non-core contributors.
hluk/CopyQ currently has 18 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in hluk/CopyQ. Ensure PR scope matches issue requirements closely before requesting review.
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/hluk/CopyQ?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11: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 (37% approval). Keep your diff compact for rapid review.
Describe the bug The AppImage fails on my GNU/Linux install, visibly due to an undeclared dependency on glibc >= 2.43. To Reproduce Download https://github.com/hluk/CopyQ/releases/download/v17.0.0/CopyQ-17.0.0-x86_64.AppImage Follow the instructions from the README's Other Linux Distributions section. Expected behavior Workrave to be successfully upgraded, and a completion without errors Actual behavior The last command displays errors, and CopyQ remains at the previously installed version: $ chmod +x CopyQ-*.AppImage chealer@ASUSvinci:~/Téléchargements$ ./CopyQ-17.0.0-x86_64.AppImage /tmp/.mount_CopyQ-gombDH/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /tmp/.mount_CopyQ-gombDH/AppRun.wrapped) /tmp/.mount_CopyQ-gombDH/AppRun.wrapped: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.43' not found (required by /tmp/.mount_CopyQ-gombDH/usr/bin/../lib/libQt6Gui.so.6) /tmp/.mount_CopyQ-gombDH/AppRun.wrapped: /lib/x86_64-linux-gnu/libc.so
Describe the bug A blank screen stay on windows 11 Pro. Even the app minimized the screen still stay there. Can't even close To Reproduce Version, OS and Environment Windows 11 PRO CopyQ 17 Additional context
Is your feature request related to a problem? Please describe. CopyQ is often opened briefly as a compact clipboard-history popup. On Windows, the native title bar and the application menu bar (File / Edit / Item / Tabs / Help) consume a noticeable amount of vertical space, particularly in a narrow popup-style window. CopyQ already has most of the underlying capabilities, but they are difficult to discover and do not form a complete Windows workflow: The menu bar can be visually hidden only by editing the theme and adding height: 0 to menu_bar_css. The title bar can be removed with copyq config frameless_window true. These options are not exposed clearly in Preferences. As discussed in #2570, a frameless CopyQ window is difficult or impossible to move normally on Windows because there is no dedicated draggable region. This makes the current options feel like advanced workarounds rather than a supported compact interface. Describe the solution you'd like Please add a discoverable Comp
Request to provide .zsync file for AppImage delta updates. Updating will take less amount of data and time due to downloading only diff. info: https://github.com/AppImageCommunity/AppImageUpdate#update-information-overview https://github.com/AppImage/AppImageSpec/blob/master/draft.md#update-information https://github.com/ivan-hc/AppImage-tips#how-to-add-delta-updates This is a common standard for updating AppImages. AppImage having update information would also recognized by other software e.g. AppImageLauncher, AppImageUpdate, AppManager, AM etc... Lots of projects already support updating AppImage e.g: LibreWolf, KeePassXC, Sigil etc.
Describe the bug After unclear amount of time CopyQ starts to take 100% of one core usually right after start. To me it looks like some thread hangs and becomes zombie. The only solution is to exit CopyQ. To Reproduce Nothing special. I have an extension appIndicator and KstatusNotifierItem to support CopyQ running in the as icon in the top bar. CopyQ is started right after login. Expected behavior CopyQ to take only thread/core when needed. Screenshots Version, OS and Environment I have debian forky (testing): GNOME Shell 50.3, 50.4, System: Kernel: 7.1.6+deb14-amd64 arch: x86_64 bits: 64 HP EliteBook 850 G5 ( Info: quad core model: Intel Core i5-8350U) Diagnostic Information CopyQ 16.0.0 Arch: x86_64-little_endian-lp64 Audio: miniaudio 0.11.25 Compiler: GCC DISPLAY: :0 KNotifications: 6.23.0 KStatusNotifierItem: 6.23.0 OS: Debian GNU/Linux forky/sid QCA: 2.3.10 Qt: 6.10.2 QtKeychain: 0.16.0 WAYLAND_DISPLAY: wayland-0 XDG_CURRENT_DESKTOP: GNOME XDG_SESSION_DESKTOP: gnome XDG_S
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 hluk/CopyQ, 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 hluk/CopyQ acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.8% were successfully merged into the primary branch.
hluk/CopyQ has a recorded first-timer success rate of 0.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 59.8 places hluk/CopyQ in the Welcoming tier.
The external pull request merge rate is 81.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hluk/CopyQ currently has 18 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for hluk/CopyQ 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.