Thanks! The changes look good to me and I'm looking forward to merge them soon.

an option which is not even mentioned in then install documentation

Would you care to add it to the README? :) Also, perhaps providing some rationale as to why/when to install via composer would be much appreciated.

Thanks!

Well, TBH, actually I'm not quite sure if what I am proposing here makes sense at all...

A use case might be if you want to hack the graph-composer code to fit a particular project.
Also - installation is "cheap" (just adiing graph-composer to the composer.json file).
Updates may (or may not) be easier running composer update.

Looking at your other projects related to Composer, phars and stuff, it seems that you know when to recommend a phar installation so, feel free not to merge this if it's not useful.

Any news here?
Just installed it via composer, and it does not work out of the box:

$ graph-composer
ERROR: Composer not properly set up! Run "composer install" or see README.md for more details

Thanks @elkuku, I've finally merged this feature and am looking towards releasing it with a v0.2.0 eventually 👍

Also, I've streamlined the readme a fair bit and added a remark to the changelog. As much as I encourage automating common tasks, I'd rather try to not prefer a single tool (Apache Ant) in the readme. Nontheless your input has proven valuable in communicating your usecase, so I really appreciate your input!

Has been a pleasure 😉