I appreciate the feedback, but you're not really contradicting anything I said.
Most companies have private projects, so you end up having to pay for Gemnasium. And you do have to somehow upload stuff to your service to make use of it.
Like the grandparent, I just want a command-line tool to document updates to NPM modules as part of Git commits.
> Modern projects use more than one package manager
Our projects are very modern indeed, and we use just one package manager per project. Node.js projects use NPM (for server and front end packages), Ruby projects use Rubygems, etc.
Agreed. But why do I need to share anything at all when a local command-line program already has all the information (or can gather it from npmjs.com or whatever)?
Most companies have private projects, so you end up having to pay for Gemnasium. And you do have to somehow upload stuff to your service to make use of it.
Like the grandparent, I just want a command-line tool to document updates to NPM modules as part of Git commits.
> Modern projects use more than one package manager
Our projects are very modern indeed, and we use just one package manager per project. Node.js projects use NPM (for server and front end packages), Ruby projects use Rubygems, etc.