Why is MD5 unsafe in the SHA-256 era?
Practical MD5 collisions are affordable now; use SHA-256 for integrity checks and bcrypt/argon2 for passwords.
The scenario
An old project is still using MD5 for checksums or as "fake encryption".
MD5 has practical collisions, which makes it unsuitable for integrity checks and even less suitable for passwords. This site's hash calculator covers the SHA family and does not compute MD5. For passwords, use a KDF such as bcrypt or argon2.