Verify a release with its live report

After installers are published, our release workflow submits them to VirusTotal. When the current report is available, the results, file hashes and report links appear below; otherwise this page says that results are unavailable.

Files and checksums

These are the exact files the download buttons serve. Compare the SHA-⁠256 of your download with the value here: if they match, you have the file we published.

Check it yourself

A matching hash means the file on your disk is exactly the one we published — wherever you downloaded it from.

  1. Take the file — The installer you downloaded — from this site or from anywhere else.
  2. Run one command — It prints the file’s SHA-⁠256: 64 characters that change completely if a single byte does.
  3. Compare — Paste the result below, or check it against the list of files above.

shasum -a 256 ~/Downloads/<file> · sha256sum ~/Downloads/<file> · (Get-FileHash "$HOME\Downloads\<file>").Hash

All checksums as one file

No number here is typed by hand

The verdict travels from VirusTotal to this page without anyone copying it over.

  1. Published — A new version’s installers go up on updates.more-ai.net, with the update packages the app installs by itself.
  2. Sent to VirusTotal — Our release workflow submits every one of those files, and VirusTotal runs each past dozens of antivirus engines.
  3. Report beside the files — Verdicts, engine counts, SHA-⁠256 hashes and links are written to one report file, published next to the installers.
  4. Read live — This page and the badge under every download button load that file when they open — the result is never frozen into the page.

What this proves, and what it does not

  • VirusTotal is an independent Google service that runs a file past 70+ antivirus engines at once. We publish whatever comes back, detections included.
  • A fresh installer sometimes trips one or two engines on heuristics alone: it is new, it is signed by us rather than by a household name, and it ships a coding agent that runs commands. When that happens we name the engine and link the report instead of rounding the number down.
  • The macOS build is signed with our own certificate rather than an Apple Developer one, so the first launch shows a Gatekeeper warning. That is about the signature, not about the scan.
  • A matching hash proves the file is byte-for-byte the one we published. It is the check worth doing whenever you downloaded from anywhere but this site.

Seen the report? Get the app

Free for macOS, Windows and Linux. Every new release goes through the same check.

Back to home