Homebrew cask scheduled for disablement (fails Gatekeeper check)

[stefan2904]

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 it, although the disabling is not in effect yet:

Desktop (please complete the following information):

• OS/Distribution: Mac OS
• Version 15.7.7
• CPU: Apple M2

Additional context

The cask adds disable! date: "2026-09-01", because: :fails_gatekeeper_check, so
QtPass may stop being installable via Homebrew unless the macOS release artifact is
properly signed/notarized.

Homebrew/homebrew-cask#225498

Related historical discussion: #149, but I could not find a current dedicated issue for this Gatekeeper/Homebrew disablement.

Thanks everyone for your work and effort!

[annejan]

Thanks for the warning @stefan2904 . .

Funniest thing is that QtPass started as a read-only MacOS app to get management onboard with using pass.

Unfortunately (or fortunately, depends on POV) I have stopped using MacOS some 5 years ago.
Hence me not being as sharp on the Mac side of things, same with Windows really.

I'll have a look at this issue somewhere coming week and should have it resolved way before september.

[nogeenharrie]

Thanks for the detailed report and the heads-up on the September deadline.

Unfortunately I no longer have access to a macOS machine or an Apple Developer account, so I can't sign and notarize the release artifact myself. Code-signing requires a paid Apple Developer ID certificate (~$99/year) and a macOS machine to run codesign + xcrun notarytool.

Calling for a volunteer!

If you're a QtPass user on macOS and have an Apple Developer account, we'd love your help. What's needed:

• An Apple Developer ID Application certificate
• Willingness to add the certificate + app-specific password as GitHub Actions secrets so signing/notarization happens automatically on each release
• About 30–60 minutes of one-time setup

The actual per-release work would be fully automated in CI after that.

In the meantime, users can bypass Gatekeeper manually after downloading:

xattr -d com.apple.quarantine /Applications/QtPass.app

or right-click → Open the first time macOS prompts you.

If no volunteer steps forward before 2026-09-01, the Homebrew cask will be disabled — we'd then recommend macOS users build from source or install via MacPorts if available.

Please comment here if you're able to help!

[stefan2904]

Unfortunately (or fortunately, depends on POV) I have stopped using MacOS

I am also primarily a Linux user, and I only use Mac OS for a project now. So unfurtuantely I cannot help with expertise or a dev cert..

Thanks for the detailed report and the heads-up

Homebrew apparently set the September 2026 deadline already in August 2025. It's interesting that there is no warning whatsoever to developers/maintainers ...