{"action":"opened","issue":{"url":"https://api.github.com/repos/rust-lang/crates.io/issues/230","labels_url":"https://api.github.com/repos/rust-lang/crates.io/issues/230/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/crates.io/issues/230/comments","events_url":"https://api.github.com/repos/rust-lang/crates.io/issues/230/events","html_url":"https://github.com/rust-lang/crates.io/issues/230","id":120774167,"number":230,"title":"prevent leaking of credentials","user":{"login":"vks","id":33460,"avatar_url":"https://avatars.githubusercontent.com/u/33460?v=3","gravatar_id":"","url":"https://api.github.com/users/vks","html_url":"https://github.com/vks","followers_url":"https://api.github.com/users/vks/followers","following_url":"https://api.github.com/users/vks/following{/other_user}","gists_url":"https://api.github.com/users/vks/gists{/gist_id}","starred_url":"https://api.github.com/users/vks/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vks/subscriptions","organizations_url":"https://api.github.com/users/vks/orgs","repos_url":"https://api.github.com/users/vks/repos","events_url":"https://api.github.com/users/vks/events{/privacy}","received_events_url":"https://api.github.com/users/vks/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-12-07T13:28:48Z","updated_at":"2015-12-07T13:28:48Z","closed_at":null,"body":"It is very common to leak credentials (see [this](https://github.com/ChALkeR/notes/blob/master/Do-not-underestimate-credentials-leaks.md)). npm and github have precautions against leaking credentials:\r\n\r\n> 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.\r\n\r\nMaybe crates.io should implement something like this as well?"}}