Code signing policy
Status: preparation, not acceptance. Gatit is preparing an application to SignPath Foundation and a separate Microsoft Store package. Neither route currently establishes that an existing download is signed. Check each release's verification receipts before installing.
If accepted, the planned acknowledgement is: “Free code signing provided by SignPath.io, certificate by SignPath Foundation.” No certificate or service sponsorship is claimed yet.
Proposed signing responsibilities
Author, reviewer and release approver: Yarin Barry. Foundation onboarding must verify repository control, MFA and this role assignment. External changes require maintainer review. Each signing request requires manual approval under the accepted policy.
Release checks
GitHub-hosted builds on the main branch produce the first-party app, recorder, installer and uninstaller. Their Windows signatures must identify the approved publisher and include a trusted timestamp. Upstream Whisper tools retain their own identity and are packaged without re-signing, with pinned source and verified hashes. On 17 October 2026, the owner also approved preserving five upstream installer helpers without signing them as Gatit's code: NSISdl.dll, StartMenu.dll, System.dll, nsDialogs.dll and nsis_tauri_utils.dll. Only the exact names and hashes in the pinned upstream record are allowed; changed bytes or additional helpers require fresh approval. Gatit's own executables still require signatures. macOS releases require Developer ID signing, notarization and stapling. Missing verification stops publication.
Microsoft Store certifies and signs its separate MSIX edition and manages its updates. Store signing does not sign the GitHub installer.
Read the privacy policy, technical signing documentation, and release details. Report unexpected warnings through the issue tracker.