I have a specific question with respect to using a project which is licensed under MIT/Apache 2.0 in a SAAS product (proprietary). The open source project have multiple dependencies, if any of the dependency is restrictive (AGPL, GPL) what happens to my SaaS product license or do I have to open source my SaaS product code is the question here.
Product: Integrate an open source form builder to integrate with my SaaS product offering for my customers.
For eg., webiny-js (form builder library)
webiny-js library has 10 obligations - (e.g., Disclose source for projects)
My SaaS product directly calls the 'form builder service' in its code workflow.
Form builder service is not directly integrated to my SaaS app, but it gets used seperately and it redirects to my SaaS app. (and no api calls from my SaaS app)
Is there any possibility where I have to open source my proprietary application code in any case, when I use open source (MIT/Apache) software which in-term uses dependency libraries (which are restrictive) as in the above example?
Does the above usage scenarios have a difference, with respect to (1) based on the type of restrictive license.
I would love to hear your experience and knowledge on this.