SECURITY AND VERIFICATION

Is this file really the one built from the source, and what does the program do with your data.

Status: the releases are not code-signed, so Windows may show a SmartScreen warning ("Windows protected your PC") the first time you run a new version. Press More info, then Run anyway. A code signing certificate for a free tool is not worth the cost, and the free open source signing program has not accepted the project yet. The checks below prove where the file comes from without it.

Check your download

  1. SHA-256. Every release has RoboXCopy.exe.sha256. In PowerShell, run Get-FileHash RoboXCopy.exe and compare the hash with the one in that file.
  2. Build attestation. Every release is built by a GitHub Actions workflow from the public source, which records a signed provenance statement. With the GitHub CLI: gh attestation verify RoboXCopy.exe --repo Skyflash/RoboXCopy. If it succeeds, the file was built by .github/workflows/release.yml in github.com/Skyflash/RoboXCopy.
  3. Build it yourself. The program is MIT licensed and has few dependencies: cargo build --release in a clone of the repository gives you your own exe.

How a release is made

  1. Changes are committed to the public repository by the maintainer, Cristian Castellari.
  2. A version tag (vX.Y.Z) starts the release workflow on GitHub-hosted runners: tests, build, SHA-256, attestation.
  3. The exe, its SHA-256 and the notes from CHANGELOG.md are published as a GitHub release.

Privacy policy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

Reporting a problem

If you think a file is not what this page describes, or you found a security problem, tell us on GitHub issues.