4 ms·
> The problems mentioned are relevant to other package managers and languages, but they’re obvious problems that other package managers solved 20+ years ago.
by K0nserv 7y ago
> The problems mentioned are relevant to other package managers and languages, but they’re obvious problems that other package managers solved 20+ years ago.
Which package mangers and how? The ones I can think of[0] and are familiar with suffer from the same or very similar problems[1].
0: Bundler, Cargo, CocoaPods, Composer, Pip(to a lesser extent)
1: Name squatting, typo squatting, malicious versions via compromised accounts/publishing credentials, compromises to the delivery infrastructure(AFAIK NPM protects against this with the integrity field in package-json.lock)
- danShumway 7y agoMore to the point, if a package maintainer turns malicious, as it appears was the case here, none of the changes this article is suggesting will help at all. 2FA means nothing if you can't trust the person publishing the package.