4 ms·
Things that was raised in the ipmjs repository that I don't feel the a package manager should solve > Prevent worm-like vulnerabilities when adding dependencie
by diggan 11y ago
Things that was raised in the ipmjs repository that I don't feel the a package manager should solve
> Prevent worm-like vulnerabilities when adding dependencies
> npm scripts, the good, the bad, and the dangerous
> Namespace all the things!
> Needs for frontend and backend package managers are different
> Involve the FSF
> Have you thought about malicious packages?
> Have you thought about copyright infringement?
> trademarking 'ipmjs' so we don't get kik'd
These are all issues I want to avoid. Also, I don't want to write yet another package manager, I'm trying to extend NPM and still allow the centralized way that we currently use today, but allow a optional offline-first approach.
Feel free to continue reading more about what I said in the ipmjs repository here: https://github.com/ipmjs/ipmjs/issues/13 https://github.com/ipmjs/ipmjs/issues/13