Complex license file incorporating multiple license is misidentified as the SSPL 1.0
Summary
The wine-staging project [1], hosted on gitlab, is a complex collection of software, different parts of which are distributed under the terms of different licenses. It uses a file called LICENSE.md which contains the full text of all of those licenses, as well as a description of each license.
Gitlab identifies the project as being under the "Server Side Public License, v 1". This is incorrect not only because the project is not distributed under the terms of any single license, but because none of those licenses are in fact the SSPL. The closest is the GPL v3, which (from brief research) differs from the SSPL v1 by one section.
The misidentification of one license as another is somewhat disturbing, partly because the license is missing the SSPL's characteristic clause, but also because I should imagine that gitlab should not automatically detect any license whose full text is not a perfect match for one in the database, nor automatically report a license for project which contains more than one license in the same LICENSE file, or more than one LICENSE file.
[1] https://gitlab.winehq.org/wine/wine-staging
Steps to reproduce
I have not tried to reproduce this, since the exercise seems academic, but I cannot imagine that it would be any more difficult than creating an empty project and adding the same license file from wine-staging to that project.
Example Project
The project is linked above.
What is the current bug behavior?
The license is automatically identified as the "Server Side Public License, v 1".
What is the expected correct behavior?
The license should probably not be automatically identified at all.