Proof of authorship for developers

To prove you wrote code, timestamp snapshots of the source and your release artifacts. Archive the repository (for example with git archive), register the ZIP with SecureAuthor and keep the certificate. Its SHA-256 hash is anchored on the Polygon blockchain. Automate it with the free API in your CI pipeline.

Get a free API key

REST API · Swagger docs

When developers need proof

  • Freelance work where the client disputes who wrote the code;
  • leaving a job and proving which side projects pre-date it;
  • open-source projects copied into closed products;
  • prior-art evidence for an algorithm or a design.

Manual

git archive --format=zip -o myapp-v1.2.0.zip v1.2.0

Upload myapp-v1.2.0.zip online and keep the certificate with the release.

In CI

git archive --format=zip -o release.zip "$CI_COMMIT_TAG"
curl -sS -X POST \
  "https://api.secureauthor.com/api/recipient/user-api/create-with-pdf?api-key=$SECUREAUTHOR_API_KEY" \
  -F "media=@release.zip"

Store the API key as a secret variable. Full API reference →

Frequently asked questions

Isn't Git history enough?

Git timestamps are set by the committer's machine and can be rewritten. A blockchain timestamp of a snapshot is independent and cannot be backdated.

What should I register — the repo or the build?

Both: a source snapshot (git archive of a tag) and the release artifacts you distribute.

Can I register only a commit hash?

The current API accepts files. Register a small text file containing the commit hash and tag, or the archive of the tag itself.

Is the code uploaded?

The file is sent over HTTPS to calculate the hash and is not stored.

Is source code protected by copyright?

Yes. Source code is protected as a literary work from the moment it is written. The algorithms and ideas behind it are not.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file