Browser plugin for sending documents and raw commands to a printer or attached device.
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 54%
Response Time: 1d
First Timer Success: 50%
qzind/tray has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in qzind/tray respond to incoming external pull requests in approximately 35.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 53.7 places qzind/tray in the B tier.
The external contributor pull request merge rate for qzind/tray is 53.6%, based on public PR activity from non-core contributors.
qzind/tray currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active Java repository in qzind/tray with ongoing community development and issue triage.
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/qzind/tray?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~23 hours (67% approval). Large PRs (>500 lines) take ~172 hours (24% approval). Keep your diff compact for rapid review.
Screen.Recording.2026-09-21.at.2.49.42.AM.mov Assigning to @IdelsTak, should be pretty straightforward.
This question came in from a customer: Is there a way for a front-end application to know if they have connected to the REAL QZ Tray versus something that is Company Branded [...]? Currently, we offer a JSON endpoint that helps with this: fetch('https://localhost:8181/json') .then(response => response.json()) .then(data => console.log([data.product.title, data.product.vendor])) .catch(error => console.error('Error:', error)); Which shows [ "QZ Tray", "QZ Industries, LLC" ], however for a branded version, this would return a different app name and vendor. We should add an official API call that allows the fetching of these values.
Improve the System Tray handling for Linux Desktops, possibly through a D-Bus bridge. The current implementation uses a JPopupMenu attached to a 1px x 1px JFrame that attempts to appear when the Task Launcher is clicked. @IdelsTak will be creating a proof of concept using D-Bus. Target desktops: Gnome KDE XFCE COSMIC Pantheon Stretch goals: Support "symbolic" icon types https://gitlab.gnome.org/GNOME/gtk/-/work_items/1762 Update notification system to be "native" as well Allow "symbolic" icons to change color based on QZ Tray status (red, yellow)
While testing 2.2.6, I realized that with a faulty USB-Serial adapter, it's possible to coerce QZ Tray into a schrodinger's cat state where the port is neither open nor closed. Attach USB-Serial adapter Open port Send data Close port Expected: Port closes and can be reopened Actual Port claims it's not open This suggests that there may be a wait or a lock that's preventing the close from occurring. This is difficult to reproduce because it requires a faulty cable. The cable was crimped by me and it works sometimes, but not others due to a bad connection at the RJ11 end. Worth nothing, I was impatient and did NOT wait for the TIMEOUT to fire. tray/src/qz/communication/SerialIO.java Line 24 in 001d1dd private static final int TIMEOUT = 1200; I suspect that there's an opportunity in code for some form of atomic flag to indicate QZ Tray's serial port should close -- eve
Enhancement request to add NFC/smart card reader support. TODO: File upstream bug for macOS issue (Done via QZ-29 private bug report).This is already fixed in JDK17+ Collect use-case from customer Develop API, e.g. qz.nfc.listDevices, etc. Milestone Document Release WIP: package com.company; import javax.smartcardio.*; import java.util.List; public class Main { public static void main(String[] args) { try { // FIXME: macOS: Force the library path inside the code // System.setProperty("sun.security.smartcardio.library", "/System/Library/Frameworks/PCSC.framework/PCSC"); TerminalFactory factory = TerminalFactory.getDefault(); CardTerminals terminalManager = factory.terminals(); // List ALL terminals, even if no card is present List<CardTerminal> terminals = terminalManager.list(CardTerminals.State.ALL); if (terminals.isEmpty()) { System.out.println("Java still can
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 qzind/tray, 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 qzind/tray acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.6% were successfully merged into the primary branch.
qzind/tray has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 53.7 places qzind/tray in the Solid tier.
The external pull request merge rate is 53.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, qzind/tray currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for qzind/tray 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.