2 ms·
> In theory the same things could happen for PIP, Maven, Gradle, their Rust and Go counterpart and any such package manager. Any data on this? Rust employs ver
by smoldesu 5y ago
> In theory the same things could happen for PIP, Maven, Gradle, their Rust and Go counterpart and any such package manager. Any data on this?
Rust employs version locking for it's builds, so you'll only be able to propagate malware with it if:
0. The developer's cargo definition auto-grabs the latest dependencies (trust me, very few do this)
1. The developer has deliberately updated the version of their dependency
2. The developer doesn't notice any significant changes when debugging/staging the new release
3. The package passed through testing without identifying any malware or malicious changes
In theory, it's possible to distribute malware with Rust's dependency system, but doing so would be pretty difficult. I'd say there's some pretty good roadblocks in place to prevent it from happening.
- stonemetal12 5y agoThe only real change from the NPM case is speed of distribution of the end results, users don't need to consciously update. NPM has package and package-lock just like there is cargo and cargo-lock, so devs are just as in control of the dependency versions they are shipping.