When I clicked to DL my version, all I saw was a "click here to see hash" that needed me to enable JS. Just sha256, which is good btw, more is not better when it comes to hashes - sha256 is sufficient.
Many open source projects provide all these on 1 page, rather than rely on complex code to deliver the info or display it on the DL page.
I totally understand. Back in grad shool I focused on usable security, and usually less clicks to get to something means more likely people will use the info.
I always wondered what purpose these hashes shown on dl pages serve. If someone can hack your website to change out the .exe or whatever, surely they could also just change the hash displayed?
Reproducible builds + a signed list of hashes would be a nice move for security.