4 ms·
Not only does it require more steps, it also has to meet the following criteria[1]: * no other packages in the npm Public Registry depend on * had less than 3
by mjlawson 5y ago
Not only does it require more steps, it also has to meet the following criteria[1]:
* no other packages in the npm Public Registry depend on
* had less than 300 downloads over the last week
* has a single owner/maintainer
So while your point is taken that unpublishing is possible under some circumstances, it is not for popular packages that are in use today.
[1] https://docs.npmjs.com/policies/unpublish https://docs.npmjs.com/policies/unpublish
- throw_m239339 5y agoNone of these points have any legal standing, from a copyright perspective. https://news.ycombinator.com/item?id=29868199 https://news.ycombinator.com/item?id=29868199
- tomrod 5y agoDespite the need to keep it clear, copyright does not reign supreme.
- throw_m239339 5y ago> Despite the need to keep it clear, copyright does not reign supreme. neither do NPM TOS, or whatever Microsoft thinks they are entitled to, since NPM is owned by Microsoft.
- tomrod 5y agoWhich is not what I argued :^)
- mjlawson 5y agoYou are technically correct. The best kind of correct! In practical terms, it depends on the license used. Since most licenses used in open source will prevent you from making these kind of requests, this consequence isn't likely to have any practical implications.
- kd5bjo 5y agoYou are assuming that the true rights holders of all the code in the package actually agreed to the given license. Someone unrelated to the package development can still claim it includes an illegally-copied, unlicensed version of their code.