Hmm. I might consider adding a section for third-party archives and greatly emphasise the potential risks for this, or share some other way, or leave it here as-is.

The reason all of the archives in the big table source Wayback Machine is that, as far as I know, unprivileged users can only request for their servers to save a copy, which in a way ensures that the data hasn't been tampered with.

It is the reason I don't feel very comfortable sharing personal archives, since anyone who cannot manually verify them shouldn't even try using them for sake of security, and those who can would have a lot of work to do.

Thank you for sharing, however this can provide limited utility at best as it is more than likely that the older versions are half-functional, if at all.

Just to be clear, I don't mean to discard all your hard work archiving all these versions.

As of now there isn't a convenient way of verifying legitimacy of packages, but if I had a lot of free time, I would source SteamDB's SteamTracker commits and compare file hashes for packages. This does not cover most of your archives though, which consisted of compressing the entire Steam installation into an archive, which would be impossible to verify without sourcing someone else's package archives.

Because of all these reasons, I am highly sceptical of adding more user-submitted archives to the mix. The one I did add is much more straightforward to verify, so it made the cut, although even that was merely an exception.

Originally posted by lightwo:

Hmm. I might consider adding a section for third-party archives and greatly emphasise the potential risks for this, or share some other way, or leave it here as-is.

The reason all of the archives in the big table source Wayback Machine is that, as far as I know, unprivileged users can only request for their servers to save a copy, which in a way ensures that the data hasn't been tampered with.

It is the reason I don't feel very comfortable sharing personal archives, since anyone who cannot manually verify them shouldn't even try using them for sake of security, and those who can would have a lot of work to do.

Thank you for sharing, however this can provide limited utility at best as it is more than likely that the older versions are half-functional, if at all.

Well the modern (non-extracted) files are directly from Steam. They're file.zip.sha1. You can compare the SHA1 numbers of the files with the name and if you want more, the SHA2 numbers of the files in the SteamDB manifest archive.
https://github.com/SteamDatabase/SteamTracking/commits/master/ClientManifest/steam_client_win32