Also there are other costs for the community like the increase of second level dependencies with redundant functionality.
So another criteria would be.. Is it a top level (appliance) project or is it one framework that would be used by many projects?
I would say more basic dependencies sould try to don't repeat themselves.
For the propietary software and componentware marketplace it is something different. I would say.. You have the right to push the market but if you don't contribute back to the opensource projects used, a lot of complexity might accumulate in your customizations and the manteniance costs will grow up to the stress point.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.