Hacker News new | ask | show | jobs
by qchris 2078 days ago
It's also worth pointing out that once a version is published to crates.io, it can't be altered, specifically to prevent social engineering attacks. If you're worried about it, that means you can audit the frozen codebase for any given version from a top-level crate down through the dependencies, and once that trust is established, it can't be leveraged for a silent dependency change later on, which can only happen through a version update on the end-user's side.
1 comments

What if I audit something down a few levels and find it lacking - how do I force update everything to not use the bad version?