Not very urgent though.

I would love to work on this issue. Can you please elaborate more on it?

Currently we use MD5 hashes of assets that are fetched e.g. during the build process, and I think it'd be nice to upgrade them to SHA256.

That would naturally mean not just changing the hashes themselves but also adjusting the things that check the hashes. Most (all?) of the related stuff is in CMake files I guess, but there might be stuff in the C++ code, for example related to plugins.

This doesn't just apply to this repository but also to all the OpenChemistry submodules.

Issues don't get assigned, if you want to contribute just make some changes and open pull requests. There's a build guide at https://two.avogadro.cc/develop/build.html

The files to start (e.g., for the thirdparty modules) are

• This has the EXPECT_MD5
  https://github.com/OpenChemistry/openchemistry/blob/master/cmake/download_all.cmake

• This has the individual downloads:
  https://github.com/OpenChemistry/openchemistry/blob/master/cmake/projects.cmake

And there's a guide to the relevant CMake bits:
https://cmake.org/cmake/help/latest/command/file.html