Verify your download
Two quick checks prove the package came from us and was not changed on the way. Both take a few seconds.
1. Compare the checksum
Every release lists the SHA-256 of each file in SHA256SUMS. Download both into the same folder and run:
sha256sum -c SHA256SUMS --ignore-missing
It should print opentars_all.deb: OK. On macOS use shasum -a 256 -c SHA256SUMS; on Windows, Get-FileHash opentars_all.deb in PowerShell and compare it with the line in the file. The same number is on the download section of this site.
2. Check where it was built
Release files carry a GitHub artifact attestation, signed by GitHub Actions in our repository. With the GitHub CLI:
gh attestation verify opentars_all.deb --repo MastLLM/OpenTARS
A file that was changed after we published it fails this check.
The scripts and the models
The Windows, macOS and Linux install commands download the code from this repository over HTTPS. The models are checked on your computer: openTARS refuses any model file whose SHA-256 does not match the one written in the app. The engine, llama.cpp, is checked the same way.
Something does not match?
Do not install it. Write to projectopentars@gmail.com with where you downloaded it from and the checksum you got.