I am running http://www.versioneye.com. Currently don't earn much with it. Most people are using it for open source projects. Still thinking about how to monetise it right. Any ideas?
As it is, I find it hard. If you stick to bundler/npm/etc would there be benefit it not only notifications but an automatic update feature? Tie it to git where possible to have a "newest" branch that keeps this out of master and/or tie it with the likes of Travis CI to make sure things didn't break. There's almost too many moving parts but I see high value in keeping a project on the latest dependencies without much involvement from myself. Its not foolproof though and may be too error prone to pull anything off without pulling your hair out.
Thanks for your feedback. I know what you mean. VersionEye has already a pretty good GitHub integration. Currently we are working on automated change logs. And I want to work together with TravisCI and CodeShip to run tests against newest versions. I think together with automated testing it can be very valuable.
I maintain a couple open source projects by myself. And I don't release new versions just for fun. Releasing a new version is a lot of work. If I do it than there is always a very good reason for it. For example BugFixes, SecurityFixes, New Features or Speed & Memory Optimisation. And I think if somebody else is releasing a new version of an open source project he has the same reasons. And that are all good reasons for me to update. That's why I started VersionEye.