Bitwarden SDK relicensed from proprietary to GPLv3 (github.com)

Article summary

Bitwarden has relicensed its SDK from a proprietary license to GPLv3. The change was made in response to concerns raised by users and developers. The company had previously been criticized for including proprietary code in its open-source client. The relicensing of the SDK aims to address these concerns and ensure that the software remains open and accessible to the community.

Main themes

• Open source licensing
• Password management
• Software development
• Community concerns
• Proprietary code
• GPLv3 license

What commenters say

• The relicensing of Bitwarden's SDK to GPLv3 is a positive step towards transparency and community trust.
• Some users are still wary of Bitwarden's intentions and worry about potential future restrictions on the software's use.
• The use of GPLv3 licensing may give an unfair advantage to companies offering software as a service, rather than those selling commercially supported hardware.
• The controversy surrounding Bitwarden's licensing highlights the importance of careful consideration and transparency in open-source software development.
• Some commenters believe that the AGPL license would be a better choice for Bitwarden's SDK, as it would provide additional protections for users.
• Others argue that the GPLv3 license is sufficient and that the controversy was overblown.
• The decision to relicense the SDK was likely driven by community pressure and a desire to maintain a positive reputation.
• Some users are considering alternative password management solutions, such as Apple Keychain or Vaultwarden, due to concerns about Bitwarden's licensing and potential future changes.