License Issue: MIT or org.jsoup:jsoup

[jgutierrezdtt]

The changes made in the code involve updating the README.md file to include a section on license compliance. This update addresses the potential license compliance issue by clarifying that the org.jsoup:jsoup library, which was initially thought to be a concern, is not actually used in the project. By explicitly stating this in the documentation, the project maintainers ensure that there are no misunderstandings or compliance issues related to the MIT license for this library.

How the Weakness Was Addressed:

1. Documentation Update: A new section titled "License Compliance" was added to the README.md file. This section provides clear information about the absence of the org.jsoup:jsoup library in the project, thus eliminating any potential license compliance concerns.

2. Transparency: By documenting the non-use of the library, the project maintains transparency with its users and contributors, which is crucial for open-source projects.

Additional Tips:

• Regular Audits: Regularly audit your project's dependencies to ensure compliance with all licenses. This can prevent potential legal issues and maintain the integrity of the project.
• Documentation: Keep your documentation up-to-date with any changes in dependencies or licensing to avoid confusion and ensure all contributors are aware of the project's compliance status.
• License Review: If you do decide to use a library like org.jsoup:jsoup in the future, review its license terms thoroughly to ensure compliance with your project's licensing strategy.

Created by: jgutierrezlopez@deloitte.es