Code-signing your software releases — and dating the files you ship

Flat illustration of a monitor with source code, a locked server and a calendar with the release date, with a timestamp badge

When someone downloads your installer, they are asked to trust that it came from you and that it was not altered on the way. A code-signing certificate is how operating systems decide whether to show a warning or your publisher name. That is a different job from showing when the source, the build, or the release archive existed. A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. The fingerprint is made in the browser, and the file stays on your device. It does not identify you as the publisher, and a code-signing signature does not, by itself, show when the code was written. This is general practice information, not legal advice.

Some links to other tools on this page are affiliate links, marked “affiliate link”. If you buy through one, TimeBinder may earn a commission, at no extra cost to you. Tools are chosen on merit, with caveats. See our affiliate disclosure.

Table of Contents

What a code-signing signature actually shows

A certificate authority (CA) checks aspects of a publisher’s identity and issues a certificate. You sign the built binary, installer, script, or driver with the private key. The operating system (or the browser, or the plugin host) then checks:

  • That the signature is valid and chains to a trusted CA.
  • That the certificate has not been revoked.
  • That the file has not been changed since it was signed.

Sectigo’s official explanation is a fair summary of the industry model: the signature binds a package to a verified publisher identity, and if the signature is missing, invalid or untrusted, the user sees a warning. That is why unsigned Windows installers still trigger SmartScreen-style prompts, and why many developers treat signing as a release requirement rather than a nice-to-have.

What the signature does not show:

  • When you first wrote the source, opened the repository, or invented the idea.
  • That every dependency in the build is benign.
  • That the private key is still only in your hands — if the key is stolen, an attacker can sign malware in your publisher name until the certificate is revoked.
  • Instant reputation on Windows SmartScreen. Official CA materials are explicit that neither OV nor EV signing guarantees that.

Git commit dates are also a weak substitute for a dated release file. They can be rewritten in a local repository. See are git commit dates proof of when code existed?.

OV, EV, and the hardware key

Public CAs currently issue Organisation Validation (OV) and Extended Validation (EV) code-signing certificates. Official Sectigo guidance, which tracks the CA/Browser Forum baseline requirements, is a useful orientation:

  • Both types involve identity checks and, in current public issuance, delivery of the private key on a hardware token rather than as a freely copyable file.
  • EV uses a stricter check of the organisation and is the type Microsoft requires for Windows driver submissions.
  • OV is commonly used for general application signing, including by some individual publishers where the CA allows it.
  • Certificates are valid for a limited term (Sectigo currently states up to 459 days for these products). Official pages also describe a signature timestamp: if you timestamp the signature at signing time, the signature can remain verifiable after the certificate itself expires.

Protect the token and its PIN the way you would protect the keys to a store account. If you lose control of the key, revoke first and notify users if signed malware may have gone out. Signing is only as strong as the key ceremony around it.

A release routine that covers both jobs

You can treat signing and dating as two steps in the same release checklist.

  1. Freeze the release artefacts. The source tag, the compiled binaries, the installer, the checksums file, and any SBOM or notes you publish should be exported to a release folder and not rebuilt “the same way” later if you want to point to those exact bytes.
  2. Date the artefacts you will keep. Fingerprint the installer, the archive, and, if it helps, a source snapshot (for example a .zip of the tagged tree). Click here to start. Your first Pooled TimeBind is free; after that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. See how to timestamp a file, prove source code existed before a date, and timestamp your code before you open-source it.
  3. Sign the binaries with your code-signing certificate, including a signature timestamp so verification can outlive the certificate term.
  4. Publish checksums (SHA-256) next to the download. People can confirm a download without having to trust a screenshot of your site.
  5. Keep a release pack offline: the exact artefacts, the TimeBind certificate, the checksums, and a note of the certificate serial and the signing date.

For the developer-facing hub, see developer timestamping and source code timestamping. If you also hand builds to a client before payment, see freelance code delivery.

Signing and dating complement each other in a slightly different way from TimeBinder vs Sigstore. Sigstore is a public, mostly keyless signing and transparency approach used widely in open-source ecosystems. A commercial CA certificate is still what many Windows and macOS desktop installers need to look trusted to ordinary users. You can use both: Sigstore or a CA signature for publisher identity and integrity at install time, and a TimeBind for an independent date on the files you shipped.

Open-source releases and private source

If you are opening a repository, date a snapshot before the first public push if the date of the private work matters to you. Once the repo is public, later clones will not reconstruct a pre-publication private history by themselves. See timestamp your code before you open-source it.

If the project stays closed, still date the artefacts you send to a customer, an app store, or a lab. Store listings and git tags are useful context. They are not a fingerprint of the binary you shipped.

Inventors who are tracking design files and notes alongside code may also want the inventor timestamping hub and how to show when you had an invention. A TimeBind does not create a patent or prove inventorship.

Mistakes that undermine a signed release

  • Signing a build you did not keep. If you cannot produce the exact bytes, a user who has a tampered copy has nothing honest to compare it with.
  • Skipping the signature timestamp. When the certificate expires, some verifiers will treat an untimestamped signature as stale.
  • Leaving the hardware token unattended, or sharing the PIN in a chat. Revocation is slow relative to how fast a signed fake update can spread.
  • Dating only the git tag. Date the artefact you actually distributed.
  • Rebuilding from source years later and calling it the same release. Compilers, dependencies and timestamps inside the build will usually change the hash.

Frequently Asked Questions

  1. Does code signing prove when I wrote the software?

    No. It shows who the certificate identifies as the publisher, and that the signed file has not been changed since signing. Date the source snapshot or the release archive if the date matters.

  2. Do I still need a TimeBind if the signature is timestamped?

    A signature timestamp supports long-term signature validity. A TimeBind is an independent dated record of an exact file you keep. They answer different questions, and many release checklists use both.

  3. Can I use Sigstore instead of a commercial CA?

    For many open-source packages, yes, that is now a normal path. For a Windows or macOS installer aimed at non-technical users, a CA-issued code-signing certificate is still commonly needed to avoid OS warnings. Check current platform rules.

  4. What should I date — the source zip or the installer?

    Date the artefacts you may need to point to later. For a public download, that is usually the installer or archive you shipped. For a priority dispute about when the work existed, a source snapshot matters too.

  5. Does TimeBinder replace Sigstore or a CA?

    No. TimeBinder does not issue certificates and does not attest publisher identity. See TimeBinder vs Sigstore.

Date the next release artefact free

Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Click here to start, or see plans and pricing.