Short answer: a release evidence routine layers three different things: git history (what changed), a signature (who signed it, and that it was unchanged afterwards) and an independent timestamp (that the exact release files existed no later than a recorded time). Each answers a different question. None of them shows that the code is safe, original or yours.
Last checked 12 November 2026. General information, not legal or security advice.
Table of Contents
Three questions, three tools
When someone later asks about a release, they usually mean one of three things: what exactly was in it, who published it, and when did it exist. No single tool answers all three well.
- Git records content and history. Its dates are not independent: the
git commitdocumentation lets the author set the date with--date, and history can be rewritten before it is shared. See git commit dates as proof. - Signatures tie a commit, tag or artifact to a key or identity. GitHub marks a commit “Verified” when its GPG, SSH or S/MIME signature can be checked against a key on the account. A signature shows who held the key, not when the work was done.
- An independent timestamp shows an exact file existed no later than a recorded time. It does not show who made it. See TimeBinder vs Sigstore.
The routine, step by step
- Tag the release. Use a signed tag where your team already signs, and keep the tag name and commit hash in your release notes.
- Build once, from the tag. Produce the release files (archives, binaries, container image) from that tag in a clean build. Do not rebuild and replace files afterwards.
- Write a checksum file. List a SHA-256 fingerprint for each release file (
sha256sumon Linux or macOS, or PowerShell’sGet-FileHash, which uses SHA-256 by default). The free SHA-256 hash checker does the same in your browser. - Sign the artifacts if you have a signing process. Sigstore’s Cosign can sign release files and container images, and it records signing events in a public transparency log. That adds identity and tamper-evidence. It is a separate tool and TimeBinder does not replace it.
- Date the release files. Create a TimeBind for the release archive and the checksum file (up to 10 files per TimeBind). The files stay on your machine; only their fingerprints are anchored to the Bitcoin blockchain.
- Store the record with the release. Keep the certificate, the checksum file and the tag hash together, outside the repository as well as in it.
See timestamping for developers for the wider picture, why git author names are just text for the commit-identity side, or the Guides hub for evidence routines in other fields.
When this helps, and when it does not
It can help if you later need to show what you shipped before a public disclosure, a licence dispute, an audit or a customer question about which build they received. It does not show that you wrote the code, that the licence terms are what you intended, or that the release is free of vulnerabilities. If a dispute is real, take advice from a qualified professional in your jurisdiction.
Timing note: a Pooled TimeBind is batched and confirmed on the Bitcoin blockchain later; an ASAP TimeBind is sent on its own transaction. See pricing.
Tools that can help
The free options above (git, sha256sum, Sigstore) cover most of this routine and none is an affiliate link. We have no affiliate arrangement with any code-signing or release tool, so this page contains no affiliate links.
Frequently Asked Questions
-
Is a git commit date proof of when I wrote code?
Not on its own. The author date can be set by the author and history can be rewritten before it is shared. It is useful evidence alongside other records, and an independent timestamp adds a date you do not control.
-
Do I need Sigstore and a timestamp?
They answer different questions. Sigstore signs artifacts against an identity and records the signing in a public transparency log. A timestamp shows that exact files existed no later than a recorded time. Many teams will only need one.
-
Does TimeBinder see my code?
No. The fingerprint is calculated in your browser and only the fingerprint is recorded. The files stay on your device.
-
Does a TimeBind prove I own the code?
No. It shows an exact file existed no later than a recorded time and still matches. It does not show authorship, ownership or originality.
Sources checked
- Git documentation, git-commit (the
--dateoption). - GitHub Docs, About commit signature verification.
- Sigstore, Overview (Cosign, Fulcio, Rekor transparency log).
- Microsoft Learn, Get-FileHash.
Date your release files
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.







