Closed
Description
It is very common to leak credentials (see this). npm and github have precautions against leaking credentials:
So, the solution for this problem is to: [...] On npm and GitHub side — automatic search for their auth data in public packages/repositories at the time of publishing/committing/making a private repo public, then revoking the leaked tokens and resetting leaked passwords.
Maybe crates.io should implement something like this as well?