License label on repository homepage incorrectly displays "RSA Message-Digest License"

Summary

After upgrading our self-hosted Gitlab instance to v15.10.0-ee I noticed that all the repositories that contain a LICENSE.md file were displaying the License project button with label "RSA Message-Digest License". This is not even close to the correct license. Our license files start with # Proprietary. Prior to the upgrade I believe the label was simply "License" or some such.

At first I thought this behaviour was caused by starting the file with #. However, even after removing the # token, Gitlab was still displaying the "RSA Message-Digest License" text. I've also tried removing the .md extension from the file. This also did not have any effect.

Changing the LICENSE file contents to a 'known' license such as MIT updates the label to MIT, but all other 'non-standard' LICENSE files result in the RSA Message-Digest License label.

Steps to reproduce

• Create a repository with a LICENSE or LICENSE.md file with your own license text.
• View the repository in Gitlab and notice the License label is "RSA Message-Digest License"

Example Project

https://gitlab.com/Willem.ter.Berg/license-parsing-bug

What is the current bug behavior?

License is incorrectly displayed as "RSA Message-Digest License".

What is the expected correct behavior?

The correct label is displayed with a sensible fallback to "License" if the license could not be recognized.

Relevant logs and/or screenshots

n/a

Output of checks

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