[actualprogram]

The irony of this question should be apparent if you search for packages on npm today. How many "new projects" are there?

In answer, why not create a new project? NPM INC controls npm, hasn't contributed it to the node foundation (despite playing a pivotal role in creating said foundation), and hasn't been especially good at taking contributions recently.

A new project dodges all those existing problems, demonstrates alternate approaches are both feasible and compatible, and destroys the myth that npm is fundamental to node, rather than simply the first of many package management systems that take advantage of node's import semantics.

[randylahey]

I wonder what reasons there are for not putting npm in a foundation in the same way that happened to Node itself? Surely such a critical piece of Node infrastructure shouldn't be controlled by a single (for-profit) company.