We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The bundled Bitwarden license is outdated.
While all refer to version 1 released in 2020, there have been two new versions in the meantime:
See the corresponding commit history at https://github.com/bitwarden/server/commits/main/LICENSE_BITWARDEN.txt for more details.
Match https://scancode-licensedb.aboutcode.org/bitwarden-1.0.html with https://github.com/bitwarden/server/blob/main/LICENSE_BITWARDEN.txt
The text was updated successfully, but these errors were encountered:
What a shame that the bitwarden server team does not understand license versioning. The revised license text at https://github.com/bitwarden/server/blob/main/LICENSE_BITWARDEN.txt still begins with:
BITWARDEN LICENSE AGREEMENT Version 1, 4 September 2020
Not helpful at all. When you revise a license you really need to create a new version and put a meaningful date on it.
We can address this by creating a new one that assigns a meaningful license key suffix. Work in progress.
Sorry, something went wrong.
@stefan6419846 thanks for opening the new issue in bitwarden/server and providing all the pertinent details.
DennisClark
No branches or pull requests
Description
The bundled Bitwarden license is outdated.
While all refer to version 1 released in 2020, there have been two new versions in the meantime:
See the corresponding commit history at https://github.com/bitwarden/server/commits/main/LICENSE_BITWARDEN.txt for more details.
How To Reproduce
Match https://scancode-licensedb.aboutcode.org/bitwarden-1.0.html with https://github.com/bitwarden/server/blob/main/LICENSE_BITWARDEN.txt
The text was updated successfully, but these errors were encountered: