What code signing proves
A code signature attaches a certificate and a cryptographic signature to a file. The operating system checks two things: the file has not changed since signing, and the certificate belongs to a named publisher that a certificate authority verified. That is all. It does not prove the software is safe, and it does not make a brand-new publisher trusted.
For a seller, the effect shows up at install time. An unsigned installer meets a stronger warning, or is blocked, depending on the platform and its settings. A signed one shows your name as the publisher. On macOS, signing is the first step, and notarization by Apple is the second. That has its own article: distributing Mac apps and notarization.
The four signatures in a licensed app
A paid desktop app can carry four different signatures, made by different parties with different keys. Mixing them up is the main source of confusion in this area.
| Signature | Made by | Checked by | Answers |
|---|---|---|---|
| Code signature (Authenticode, Developer ID) | You, with a certificate from a CA or Apple | Windows or macOS at install and launch | Who published this file, and was it altered |
| Notarization (macOS) | Apple, after you submit the build | macOS Gatekeeper | Has Apple scanned this build |
| Update signature (Sparkle EdDSA, Tauri signer) | You, with an update key | Your updater, before installing | Is this update from me |
License token (sgt1, Ed25519) |
The licensing service | Your app | Did this customer pay, and for which product |
Only the first two involve a certificate authority. The update key and the license token key are plain Ed25519 key pairs. Losing a certificate is an inconvenience. Losing the Tauri updater’s private key means, in Tauri’s own words, that you cannot publish new updates to users who already have the app. Treat the keys differently, store them separately and back them up.
Signing also affects other features. Electron’s documentation says an application must be signed for automatic updates on macOS, and that safeStorage behaves consistently only for a signed app, because without a stable signature macOS may not treat different builds as one app. If your license check keeps its key in safeStorage, an unsigned build can lose it between versions.
Windows
What SmartScreen looks at
Microsoft’s documentation says SmartScreen evaluates two signals when a user downloads and runs a file: publisher reputation, meaning whether the file is signed by a known and trusted publisher, and file hash reputation, meaning whether this exact file has been downloaded without signs of malicious behavior. A newly built binary can still show a warning even when it is signed, until enough clean downloads accumulate.
What EV certificates no longer do
Years ago an Extended Validation certificate gave positive SmartScreen reputation by default. Microsoft’s current page states that this behavior no longer exists, that EV certificates may matter for enterprise procurement but no longer affect SmartScreen, and that paying a premium for EV only to avoid warnings is no longer justified. A self-signed certificate behaves like no signature.
Options for getting a certificate
| Route | Notes, as of November 2026 |
|---|---|
| Artifact Signing (Microsoft; earlier called Trusted Signing) | Basic plan $9.99 a month for up to 5,000 signatures, Premium $99.99 for up to 100,000. Organizations in the United States, Canada, the EU, the United Kingdom, Australia, New Zealand, Japan, South Korea, Singapore, Switzerland, Norway and Israel can use the public trust option. Individual developers must be located in the United States or Canada. You cannot choose a custom common name: it must be your validated legal name |
| A certificate from a commercial CA | A hardware token or a cloud key service, plus identity validation. Pricing varies by CA |
| Microsoft Store | Store-distributed apps are re-signed by Microsoft and are not subject to SmartScreen |
Certificate lifetime and hardware keys
The CA/Browser Forum’s ballot CSC-31 lowered the maximum validity of publicly trusted code signing certificates from 39 months to 460 days, effective 1 March 2026. Certificates issued before then keep their original period. Plan a yearly renewal and put it in a calendar.
The forum’s code signing requirements also say the private key must be generated, stored and used in a hardware cryptographic module meeting FIPS 140-2 level 2 or Common Criteria EAL 4+ or better. In practice you get a USB token, a cloud signing service, or a managed service such as Artifact Signing, and you cannot export the key to a file on a build server.
Always sign with a trusted timestamp. Microsoft’s documentation says that without a timestamp the signature becomes invalid when the signing certificate expires and Windows treats the binary as unsigned. With one, signatures stay verifiable after the certificate expires.
macOS
Distributing a Mac app outside the Mac App Store means signing with a Developer ID certificate from Apple and submitting the build for notarization. The Apple Developer Program costs 99 USD per membership year, as of November 2026, and Apple lists a fee waiver for eligible nonprofits, educational institutions and government entities. Enrol as an individual or as an organization. The notarization workflow is in the Mac notarization article, and the Windows side is in selling Windows software directly.
Doing it in a build pipeline
A short, durable setup:
- Keep signing credentials in the CI system’s secret store, never in the repository.
- Use a cloud or token-based key, so no signing key exists as a file on a build machine.
- Sign every installer and the main executable, and apply a timestamp.
- Verify after signing, on a clean machine, by running the installer and checking the publisher name.
- Calendar the certificate expiry and the Apple membership renewal.
- Keep the update key and the license verification code out of this pipeline’s responsibilities: they are separate.
What to do first
For a new product, start with a verified publisher identity, because that takes the longest. Then choose the lowest-effort route that fits your location: Artifact Signing if you are in a supported region, a commercial certificate otherwise. Sign before the first public download, because file reputation starts accumulating from the first file people run.
Doing this with Clavem
Clavem does not sign your builds and does not need to. It stores the signed installers you upload and delivers them with expiring links, and it signs license tokens with its own key. Code signing sits in your build, and the guides show how the license check fits in an app that is already signed.
Questions
Do I need an EV certificate to avoid Windows SmartScreen warnings?
No. Microsoft's documentation says EV certificates no longer bypass SmartScreen, and that paying a premium for EV only to avoid warnings is no longer justified. Reputation builds from signed publishers and from downloads of the specific file.
How long can a code signing certificate last?
Under the CA/Browser Forum rule effective 1 March 2026, certificates issued on or after that date may be valid for at most 460 days, down from 39 months. Plan to renew about once a year.
Is a license token the same as a code signature?
No. The operating system checks a code signature to decide whether to trust an installer or program. Your app checks a license token's signature to decide whether a customer paid. Different keys, different checkers.
Sources
- Microsoft, SmartScreen reputation for Windows app developers (as of November 2026)
- Microsoft Learn, Artifact Signing quickstart, supported regions (as of November 2026)
- Microsoft Azure, Artifact Signing pricing (as of November 2026)
- CA/Browser Forum ballot CSC-31, maximum validity reduction to 460 days (as of November 2026)
- CA/Browser Forum code signing baseline requirements, hardware key storage (as of November 2026)
- Apple Developer Program enrollment, 99 USD per membership year (as of November 2026)
- Microsoft, time-stamping Authenticode signatures (as of November 2026)
- Tauri v2 updater plugin, signing updates (as of November 2026)
- Electron safeStorage and autoUpdater documentation (as of November 2026)