Both builds carry their own Python runtime — the host needs
neither python3 nor python3-tk. Both are
unsigned; checksums are how you verify them.
--appimage-extract-and-run (below)chmod +x verjuice-x86_64.AppImage
./verjuice-x86_64.AppImage # GUI
./verjuice-x86_64.AppImage detect # or any CLI command
On a host without libfuse2:
./verjuice-x86_64.AppImage --appimage-extract-and-run
First run: verjuice install lists exactly what is missing
(umu, a Proton build, Wine, …), fetches each only after you confirm, and
checksum-verifies every download. Offline, it tells you what it would
fetch and changes nothing.
unzip Verjuice-macos-arm64.zip
mv Verjuice.app /Applications/
First launch opens the GUI. The same bundle works from a terminal:
/Applications/Verjuice.app/Contents/MacOS/verjuice plan "portal 2".
Verify before running — one line per artifact:
shasum -a 256 verjuice-x86_64.AppImage Verjuice-macos-arm64.zip
| Artifact | SHA-256 |
|---|---|
verjuice-x86_64.AppImage |
0766a2ebf8ca2e9f2ca82c1136cba7391cd31662e36dd7c0f2379f3c278beba3 |
Verjuice-macos-arm64.zip |
07fa53c93bd4279d7667ac06220a23d0cfdca726bc17cfe3fbb105b3d147bf25 |
The digests above are published with the release and never change for a given file; if your download's digest disagrees, do not run it — re-download, then report it.
Verjuice is proprietary but free for personal use — no payment, no account. Modifying, redistributing, and reselling are not permitted; the full text ships inside every artifact and is the entire agreement. The tools Verjuice wraps (Wine, Proton, umu, DXVK, VKD3D, DXMT, MoltenVK, legendary) keep their own open licenses, attributed in the third-party notices that ship with each build.