clearlydefined / clearlydefined/crawler

Incorrect resolution of SPDX license expression

Open
#401 2 comments 1 reaction 0 assignees View on GitHub
bug Discovered License Issue reproducible
Dominant language
JavaScript
Stars
60
Forks
38
Avg merge
1h 49m
Merged PRs (30d)
1

Description

Issue Type: Bug
Issue Description:

I was looking at [https://clearlydefined.io/definitions/git/github/eclipse-ee4j/mail/4c092797479f6fb05576e723a6855a7e116ed027](https://clearlydefined.io/definitions/git/github/eclipse-ee4j/mail/4c092797479f6fb05576e723a6855a7e116ed027) and noticed that there are lots of cases where files with SPDX: "EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0" resolve to "EPL-2.0 OR NOASSERTION".

One random example of such a case is the file https://github.com/eclipse-ee4j/mail/blob/4c092797479f6fb05576e723a6855a7e116ed027/gimap/src/main/java/com/sun/mail/gimap/protocol/GmailProtocol.java.

If you look at line 30899 in the raw data of the definition, looks like the tools have got the license expression correct for this file: "epl-2.0 OR gpl-2.0 WITH classpath-exception-2.0".

However, when you look under "Files", the reported license for the same file appears as "EPL-2.0 OR NOASSERTION".

![image](https://user-images.githubusercontent.com/31491646/88727697-f634d580-d0e4-11ea-8373-f9c57908aba5.png)

It looks to be that ScanCode is detecting the license correctly, but the same information is not showing in ClearlyDefined.

Thanks,

Brian

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.