Question about checksum verification UX

[damonzwicker]

Quick question about the verification step in bat releases—

When downloading a binary, people run shasum/sha256sum and then compare hashes. That last step—comparing 64-character hashes by eye—is where things tend to break down (either skipped or done loosely).

I put together a minimal example that keeps the same checksum model but removes that comparison:

npx verafile verify file proof.json → VALID / INVALID

Example:
https://github.com/damonzwicker/verafile/tree/main/examples/open-source-release

Not about replacing signing—just turning verification into a clear result instead of a manual check.

Would simplifying that step increase how often people actually verify downloads?