There was a time when it was considered ok to have the salted and MD5-hashed password available to all users.
Then people learned to bruteforce the password and so the hash itself was moved to shadow file but passwd was left because a lot of platform software and scripts depended on it.
This may shock people nowadays but back then this was fine. I remember having to explain to the users (and sometimes loosing) the need to have a password at all.
The confusion rests on the name of the file I think. If it were named "accounts" (closer to its use) people wouldn't be too surprised it was readable. Then shadow could have been named "passwords."
With a user who's lost multiple accounts to weak passwords.
Or should I say, the same weak password. Which they still use in some contexts....
I'm of the opinion that allowing users free choice in passwords is no longer viable. At a bare minimum reuse of any known-compromised password must be rejected.
"but passwd was left because a lot of platform software and scripts depended on it."
It is pretty comical when people who do not know basics of how the system permissions work wax about authentication and authorization used by the same systems.