&gt; Project owners update projects and don&#x27;t bump the version. New bugs &#x2F; security problems could be injected even though we haven&#x27;t changed a thing internally.<p>You can&#x27;t update a crate on crates.io without bumping the version. Once a version is published, it cannot be removed. (It can be &quot;yanked,&quot; but even yanking it does not make it completely inaccessible.)<p>&gt; These ensure all projects are built from known sources. We _know_ we can get consistent builds.<p>Cargo isn&#x27;t coupled to crates.io. You can run your own registry index. (Note the `[registry]` config section: <a href="http:&#x2F;&#x2F;doc.crates.io&#x2F;config.html" rel="nofollow">http:&#x2F;&#x2F;doc.crates.io&#x2F;config.html</a>) --- All of the code that powers crates.io is open source. On top of that, crate dependencies can be specified via git URLs or locations on disk. Repeatable builds are well supported IMO.