It this case, this is more like a foster parent; Oya started as a part-time open source project, then Tooploox sponsored further development after having used it internally.
It was created as an independent open source project, then used internally @ Tooploox, then development got sponsored by Tooploox so it does make sense from our (very subjective) pov.
But I agree AFTER it got moved to Tooploox Github it looks kinda self-serving.
Not everybody uses JavaScript. There are many language-specific task runners (e.g. Rake, Mage etc.). Oya is aiming to be language agnostic and lightweight (not require a ton of dependencies).
You're not being negative, that's super useful feedback. We're using Oya internally but are still struggling with making it 100% (or even 80%:) clear what it is that it does. :)
Scaffolding is just a part of what Oya. The purpose is not just creating new projects but also making managing them easier with focus on devops.
You can:
1. Create bash-based tasks similar to what Makefiles do.
2. You can parametrize these tasks AND templates using YAML files such as values.oya (they can be encrypted).
3. You can share/reuse your scripts by just pushing them to Github and tagging using a version and then import them into your Oyafile (`oya import github.com/bilus/mypack`)