when fetching jsons I found the fallowing hashes are not valid. I found them using my archiver for mc java edition called mc ripper 2.

Log file prints out invalid hashes with the url on your web api domain. The badhashes.hash is a Map<BadHash, ActualHash> in sha1 format. The index.hash repsresents the entire archive of java edition known

For example:
`[2021-07-10T22:13:32.420Z] [Err]: hash mismatch expected hash:016674e6940d040efe6df3a459a4fe10faaa6a40 actual:7ab84bf3169e8f5e9e7c72b9c139496c990d7c2a from:mcripped/jsons/minor/release/1.7.10-016674e6940d040efe6df3a459a4fe10faaa6a40.json url:https://launchermeta.mojang.com/mc/game/016674e6940d040efe6df3a459a4fe10faaa6a40/1.7.10.json`

What this means:
SHA1 of what the json and URL says: 016674e6940d040efe6df3a459a4fe10faaa6a40
Actual file SHA1: 7ab84bf3169e8f5e9e7c72b9c139496c990d7c2a
URL: https://launchermeta.mojang.com/mc/game/016674e6940d040efe6df3a459a4fe10faaa6a40/1.7.10.json

if you look at the log it will spit out all of the urls. If you look at the badhashes.hash it will give you a map of all of them I found so far

Probable cause:
In all of the json files I observed that don't match their actual hash; The json is in pretty print format instead of condensed default format. when the api is probably computing the expected hash for non pretty print.