Skip to main content


The official Apache Fury releases are provided as source artifacts.

For binary install, please see Fury install document.

The latest release

The latest source release is 0.5.1:

VersionDateSourceRelease Notes
0.5.12024-05-28apache-fury-0.5.1-incubating-src.tar.gz (asc, sha512)release notes

All archived releases

For older releases, please check the archive.

Verify a release

It's highly recommended to verify the files that you download.

Fury provides SHA digest and PGP signature files for all the files that we host on the download site. These files are named after the files they relate to but have .sha512/.asc extensions.

Verifying Checksums

To verify the SHA digests, you need the .tgz and its associated .tgz.sha512 file. An example command:

sha512sum --check apache-fury-incubating-0.5.1-src.tar.gz

It should output something like:

apache-fury-incubating-0.5.1-src.tar.gz: OK

Verifying Signatures

To verify the PGP signatures, you will need to download the release KEYS first.

Then import the downloaded KEYS:

gpg --import KEYS

Then you can verify signature:

gpg --verify apache-fury-incubating-0.5.1-src.tar.gz.asc apache-fury-incubating-0.5.1-src.tar.gz

If something like the following appears, it means the signature is correct:

gpg: Signature made Wed 17 Apr 2024 11:49:45 PM CST using RSA key ID 5E580BA4
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Good signature from "chaokunyang (CODE SIGNING KEY) <>"

You should also verify the key using a command like:

gpg --fingerprint 1E2CDAE4C08AD7D694D1CB139D7BE8E45E580BA4

It should output something like:

pub   rsa4096 2024-03-27 [SC]
1E2C DAE4 C08A D7D6 94D1 CB13 9D7B E8E4 5E58 0BA4
uid [ unknown] chaokunyang (CODE SIGNING KEY) <>
sub rsa4096 2024-03-27 [E]