Skip to content

Code signing policy

Code signing lets Windows show who published a program and that nobody has changed it since. This page explains how Keymotion’s releases are built, signed and checked.

Keymotion comes two ways. The Microsoft Store copy is signed by Microsoft, so it installs without a warning. The installer on GitHub is not code-signed yet, so Windows may warn you when you run it; Installing Keymotion shows how to continue.

On 15 November 2026 the project applied to SignPath Foundation, which offers free code signing to open-source projects. SignPath declined for now, because the project is still new, and invited it to apply again once it is better known. The project will.

In the Microsoft Store, Microsoft checks every package before it publishes it and signs it. The Store’s package holds the same program as the GitHub installer, built by GitHub Actions from the same version tag.

  • Every release is built by GitHub Actions from the source code of its version tag, by the workflow in .github/workflows/release.yml. Release files are never built or uploaded from a personal computer.
  • The workflow puts the release on GitHub as a draft. The maintainer reviews it and publishes it.
  • The release page lists the installer’s SHA-256 checksum, so you can check that your download is the published file.

To compare the checksum:

  1. Open the folder where you saved the installer, for example Downloads.
  2. Right-click an empty space in the folder and choose Open in Terminal.
  3. Type Get-FileHash followed by the installer’s name, for example Get-FileHash .\Keymotion_0.1.0_x64-setup.exe, and press Enter.
  4. Compare the long code it shows with the SHA-256 on the release page. They must be the same.

The Keymotion 0.1.0 installer was scanned on VirusTotal on 15 November 2026. 70 of the 71 antivirus engines found nothing, Microsoft Defender included.

One engine, Trapmine, flags it with a machine-learning score (“Malicious.high.ml.score”), and gives the app inside the installer a low score from the same model. This is a guess the engine makes about new, unsigned files, not a match with known malware. We reported it to Trapmine as a false positive on 15 November 2026. Signed releases should make guesses like this rarer.

Each installer is also signed with Keymotion’s own update key. The key has two halves:

  • the private half stays secret with the project, and the release workflow uses it to sign each installer;
  • the public half is built into Keymotion.

When Keymotion downloads an update, it checks the download against the public half. If the signature doesn’t match, it doesn’t install the update and says “The download couldn’t be verified, so it wasn’t installed.” So Keymotion installs only updates signed with the project’s key.

Once signing is set up, every signing request will be approved by hand by an approver before anything is signed.

Keymotion collects no usage data. It goes online only to read the calendars you add and to check GitHub for a new version. See the privacy policy.