Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong versioning of LICENSE_BITWARDEN.txt #5115

Open
1 task done
stefan6419846 opened this issue Dec 5, 2024 · 0 comments
Open
1 task done

Wrong versioning of LICENSE_BITWARDEN.txt #5115

stefan6419846 opened this issue Dec 5, 2024 · 0 comments
Labels

Comments

@stefan6419846
Copy link

Steps To Reproduce

View https://github.com/bitwarden/server/blob/main/LICENSE_BITWARDEN.txt and its history at https://github.com/bitwarden/server/commits/main/LICENSE_BITWARDEN.txt

Expected Result

The updates to the actual license text should be versioned. This especially holds true for the change from 26 March 2021 which added section 2.5 about trademarks. The change from 24 January 2024 might qualify for a new version as well.

Actual Result

Although there has been at least one relevant change to the license text itself after the documented date, the license still states the original version and date:

BITWARDEN LICENSE AGREEMENT
Version 1, 4 September 2020

Screenshots or Videos

No response

Additional Context

This is relevant for managing software licenses, as this usually requires specifying unique license identifiers which only match a specific flavor/text. Additionally, this yields to missing transparency about relevant license changes. Disclaimer: IANAL.

For reference: I initially stumbled upon this as part of aboutcode-org/scancode-toolkit#4002.

Build Version

main

Environment

Cloud (bitwarden.com)

Environment Details

No response

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant