The project was accepted into the SignPath Foundation open-source code signing program in October 2026 and is currently testing the signing pipeline with the self-signed test certificate provided by SignPath. The Foundation issues the production certificate only after reviewing the setup. Windows installers released before then (including v2026.10.30 and earlier) remain unsigned, and files signed with the test certificate are never published as release assets. Check a specific file's Windows Properties → Digital Signatures and its signature validation result.
Once the production certificate is enabled, the signing acknowledgement will be:
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
- Committers and reviewers: margrop. External contributions are reviewed by the maintainer through pull requests.
- Signing approver: margrop. Each production signing request requires the maintainer's manual approval in SignPath. The API token may submit requests but must not approve them.
- Members who can change release code or approve signatures must enable multi-factor authentication on both GitHub and SignPath.
The Windows installer WrongNotebook-Win-Setup-<version>-x64.exe and portable package WrongNotebook-Win-Portable-<version>-x64.exe are built on GitHub-hosted runners from the public margrop/wrong-notebook repository. The project is derived from wttwins/wrong-notebook and preserves its license and attribution.
Only workflows for the public main branch and version tags may submit signing requests. SignPath must verify the GitHub build origin, enforce the product name WrongNotebook, and require matching product versions for both files. This integration signs the two package files; it does not re-sign embedded Electron, Prisma or other upstream binaries.
After downloading the signed files, the workflow checks their names, count, product names, product versions, trusted Authenticode signatures and timestamps. Only then are they uploaded using the existing package-desktop-windows-x64 artifact name. Release checksums are calculated from the final signed files. A signing failure stops publication without falling back to unsigned files.
See the privacy policy for question images, study records, account data and AI credentials. Self-hosted data remains on the user's selected instance. AI requests, cloud speech, MiniMax Code login and automatic check-in connect to the third-party services configured by the user or administrator.
The signing service receives build artifacts and provenance information, not an instance's study database or runtime configuration. See the setup guide and the Foundation's Code of conduct.