Using Asset Transparency (and tl) for increased download security

I have been using sops and am a huge fan, thanks!

We are developing a system called Asset Transparency which is designed to improve the UX around validating web content integrity. Think sha256sum or gpg —verify, but more automated:

$ tl get https://github.com/mozilla/sops/releases/download/v3.6.0/sops-v3.6.0.linux
fetched note: https://beta-asset.transparencylog.net/lookup/github.com/mozilla/sops/releases/download/v3.6.0/sops-v3.6.0.linux
validated file sha256sum: 280ca39d21e6740dfa5332b12ef41698acf014e5f277c5c296c61e83b4ccad21
Download validated and saved to sops-v3.6.0.linux
$
$
$ tl verify https://github.com/mozilla/sops/releases/download/v3.6.0/sops-v3.6.0.linux sops-v3.6.0.linux 
fetched note: https://beta-asset.transparencylog.net/lookup/github.com/mozilla/sops/releases/download/v3.6.0/sops-v3.6.0.linux
validated file sha256sum: 280ca39d21e6740dfa5332b12ef41698acf014e5f277c5c296c61e83b4ccad21

Since this project is security focused we would love you to both:

1. If you suggested using tl get or tl verify in installation docs
2. Enabled the Asset Transparency GitHub Action to automatically register your release assets to the system on every release.

More background on Asset Transparency can be found here: https://www.transparencylog.com

The issue names no repository files or tests; start by locating the installation documentation and release workflow, then review the linked Asset Transparency GitHub Action. Done would mean documenting the requested tl commands and enabling the action to register release assets, subject to maintainer agreement.