> All in all your points are mostly valid (i don't fully understand all your arguments about versions as integrity should be handled by git) If you depend on g

> All in all your points are mostly valid (i don't fully understand all your arguments about versions as integrity should be handled by git) If you depend on github.com/owner/foo@1.0.0, there's nothing stopping owner from force pushing to foo to override an existing version. The way it can be mitigated is if your dependency declaration contains a hash, so Cargo.toml files would be closer to foo = { url = "github.com/owner/foo", tag = "1.0.0", hash ="$HASH$" }. > there no reason on the world everybody writing rust should be trusting the same entity Note that you can today depend on git repos, local paths, or on alternative crate repositories. In practice the only people doing so are either applications (for the former) or large air-gaped organizations (for the later).