bitwarden / bitwarden/server

Wrong versioning of LICENSE_BITWARDEN.txt

Open
#5,115 2 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C#
Stars
20.1k
Forks
1.8k
Avg merge
4d 8h
Merged PRs (30d)
75

Description

### 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: https://github.com/bitwarden/server/blob/0e32dcccadd759e938542dc8069bc7be9b4e297b/LICENSE_BITWARDEN.txt#L1-L2

### 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 https://github.com/aboutcode-org/scancode-toolkit/issues/4002.

### Build Version

main

### Environment

Cloud (bitwarden.com)

### Environment Details

_No response_

### Issue Tracking Info

- [X] 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.