QtPass is a multi-platform GUI for pass, the standard unix password manager.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 42%
Response Time: 1h
First Timer Success: 67%
IJHack/QtPass has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in IJHack/QtPass respond to incoming external pull requests in approximately 1.4 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 69.3 places IJHack/QtPass in the A tier.
The external contributor pull request merge rate for IJHack/QtPass is 41.9%, based on public PR activity from non-core contributors.
IJHack/QtPass currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in IJHack/QtPass. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in IJHack/QtPass 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/IJHack/QtPass?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (52% approval). Large PRs (>500 lines) take ~7 hours (19% approval). Keep your diff compact for rapid review.
An experiment: can QtPass run on Android, and how would it talk to GnuPG there? Building: works A probe on a fork (annejan/qtpass android-probe, run) builds src and main with Qt 6.8.3 for android_arm64_v8a (NDK r26b, API 35) and packages a debug APK (18.5 MB) with androiddeployqt. The only change needed: Android's qmake adds the ABI to the static library's name (libqtpass_arm64-v8a.a), while main.pro links libqtpass.a. The probe copies it; a real fix belongs in main.pro. Notes for the install step: Qt 6.7 and later list their Android packages under host all_os (not linux), and autodesktop: true brings the host tools along. Not tried yet: running the APK. The Widgets UI is the desktop one, so on a phone it will be small and mouse-shaped; a usable phone UI is a separate (big) question. GnuPG: the real problem QtPass runs gpg, git and pass as processes through Executor. On Android: An app cannot run binaries from its own writable storage (since Android 10). Binaries shipped as lib*.so
Why OpenSSF Scorecard Code-Review is 1/10: 3 of the last 20 merged changesets had a human approval. Most PRs get CodeRabbit's automated review and are then merged by their author. That's allowed by CONTRIBUTING (#1979) and stated on qtpass.org/code-signing, but Scorecard only counts approvals by people. Branch-Protection goes up too when main requires at least one approval. That isn't possible while a single maintainer merges their own work. Options A second maintainer from the IJHack team reviews and approves PRs, even briefly, at least those touching src/ or workflows. Require 1 approval in the main ruleset (id 24859572) only once there are enough reviewers, so no PR gets stuck. Keep it as it is and accept the score; the policy page describes the process accurately. This is a decision for the team, not a code change. 🤖 Generated with Claude Code
Problem The Windows installer built by .github/workflows/release-installers.yml (iscc qtpass.iss) is not Authenticode-signed. There is no signtool step and no certificate in the repository secrets. Consequence for users: on first run Windows shows the SmartScreen dialog "Windows protected your PC" and the installer only runs after More info → Run anyway. SmartScreen reputation is built per file hash, so every new release starts nagging again. Unlike the macOS situation (#1542) nothing is blocked: Chocolatey (1.7.0, approved, tests passing) and winget (1.7.0) both accept unsigned installers. This is a polish/trust issue, not a distribution outage. Options SignPath Foundation (recommended) — free Authenticode code signing for open source projects. Certificate stays in their HSM; signing happens from CI via the signpath/github-action-submit-signing-request action. Cost: €0. Needs an application and approval (takes a few weeks), then one extra step in release-installers.yml. https:/
Describe the bug Homebrew disabled the QtPass package (effective 2026-09-01): Homebrew/homebrew-cask@16a1509 To Reproduce Steps to reproduce the behavior: brew install --cask qtpass ==> Would install 1 cask: qtpass ==> Fetching downloads for: qtpass Warning: qtpass has been deprecated because it does not pass the macOS Gatekeeper check! It will be disabled on 2026-09-01. ✔︎ Cask qtpass (1.7.0) Verified 25.4MB/ 25.4MB Warning: qtpass has been deprecated because it does not pass the macOS Gatekeeper check! It will be disabled on 2026-09-01. ==> Installing Cask qtpass Expected behavior After installing the app, I expected I can start it. I also assumed that I can use it after 2026-09-01 (Or at least any hint if that problem is known/taken care of/a WONTFIX.) Screenshots: I don't know is this is related, but I can also not start
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 IJHack/QtPass, 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 IJHack/QtPass acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 41.9% were successfully merged into the primary branch.
IJHack/QtPass has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 69.3 places IJHack/QtPass in the Welcoming tier.
The external pull request merge rate is 41.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, IJHack/QtPass 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 IJHack/QtPass 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.