Code Signing Policy
Updated 10 November 2026. Applies to official Open Manuscript Studio binaries,
built from the MIT-licensed open-manuscript-initiative/open-manuscript-studio
repository.
Windows distribution channels
| Channel | Current policy and status |
|---|---|
| Microsoft Store MSIX | The publisher received a Microsoft notification on 10 November 2026 that its submission had been processed and the app was available in Microsoft Store (customer visibility may take up to two hours). GitHub produced the unsigned submission candidate; Store-managed signing applies to certified distribution. The exact published package signature and real-device installation/update acceptance have not yet been independently recorded. |
| Direct EXE/MSI | Existing Tauri installers remain a separate channel. No active public-trust signing integration is established; the Store does not sign these files. |
| Local development | Test certificates are restricted to explicitly trusted test environments and do not establish public release trust. |
The publisher also received an IARC live-rating notice on 10 November about a questionnaire submitted on 9 November 2026. The screenshots do not show the age-category outcome; no numerical or regional age rating is asserted here. A canonical public Microsoft Store product URL has not yet been verified, so a product-specific download link is intentionally withheld.
The owner reports that the earlier SignPath Foundation application was declined. SignPath is not an active signing provider; no SignPath sponsorship or certificate is claimed. The Store-only workflow requires neither Azure nor private signing credentials. See RC status and verified build.
Provenance and release approval
- Use official public source and GitHub-hosted approved build workflows.
- Bind exact source revision, package identity/version, build run and SHA-256.
- Submit the reviewed candidate through the approved distribution channel; any deliberate rebuild or repackaging requires new byte identity and review.
- Verify signing authority, signature integrity and actual install/update/data preservation before claiming signed distribution.
- Keep signing credentials and service secrets out of Git, logs and binaries. Limit CI/release access and use MFA.
- Obtain explicit release-owner approval; a green build is not certification or an approved stable release. Preserve Store-managed update behavior for Store-installed packages.
MSIX archive digests, package hashes and Microsoft signatures are distinct evidence. The separate Store artifact does not silently replace the existing seven-file RC receipt or its 14 manual acceptance gates.
The designated maintainer, reviewer and release approver is
vargaijanos. Roles may overlap in this small
project, but release approval remains explicit. Suspend signing/publication if
credentials or provenance are suspected compromised; investigate, revoke/rotate
affected credentials and identify affected releases before resuming.
Privacy and reports
Microsoft and GitHub process account/build/submission metadata under their own terms. Manuscript content, user credentials, database contents and server secrets must never be included in signing or Store submission artifacts. Database/server operation remains outside this signing boundary. See Privacy Policy. Report security issues privately to the maintainers.
Material changes to provider, certificate ownership, trusted build, access or approval must be reviewed and documented before production use.