Hi,
We are using ABP Pro packages in our project and have made some modifications to the source code. Snyk has flagged the LGPL-3.0 license associated with these packages as a potential risk to our proprietary code.
We’d like to better understand from ABP’s perspective the implications of using these LGPL-3.0-licensed packages:
- What obligations do we have with respect to our proprietary code when using these packages?
- Are there any risks of the LGPL-3.0 license requirements extending to our proprietary application?
- Does ABP have any guidance or best practices for ensuring compliance while maintaining the proprietary nature of our code?
We want to ensure we remain compliant while protecting the intellectual property of our project. Any advice or clarification would be greatly appreciated!
Thank you, Kenny
1 Answer(s)
-
0
hi
If you're only extending and using the ABP Framework in your own commercial application, you do not need to publish your source code. If you modify the ABP Framework itself, you must make those modifications public under LGPL 3.0, but this does not apply to your proprietary or commercial code that interacts with it.
https://abp.io/support/questions/7834/Request-for-confirmation-on-ABP-framework-commercial-license
