Skip to content

lGPLv3 not recognized as valid OSS license

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

In my open source projects, I've selected the lGPLv3 as the license for all projects. Recently this license was added by GitLab to the license templates but now the license is not recognized as a valid OSS license.

In the project's main page, in the right sidebar you see the license saying just LICENSE without a specific type.

When you view the license page it says "This project is licensed under the Other".

Steps to reproduce

  1. Create a new project on gitlab.com
  2. Add a file via the UI or click on the "+LICENSE" link on the right sidebar of the main page.
  3. Type in LICENSE for the filename
  4. Select GNU Lesser General Public License v3.0 as the template for the license
  5. Commit the changes to main

Example Project

https://gitlab.com/balean-oss/devops-tools/gitlab-cicd-components/

What is the current bug behavior?

Once you created the license file, the page showing the license shows the message "This project is licensed under the Other". See screenshot below.

In the project's right sidebar you see LICENSE but no specific license type is indicated. See screenshot below

What is the expected correct behavior?

The expected behavior is that GitLab will show the name of the chosen license in the right sidebar as in this project

Relevant logs and/or screenshots

Line on LICENSE page:

Screenshot_2025-05-19_at_17.48.31

Right sidebar:

Screenshot_2025-05-19_at_17.47.33

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖