Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create LICENSE file for CC0 #36

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

hkong-mitre
Copy link
Collaborator

Adding a license file to the repository

@pombredanne
Copy link

I thought that there was already a different license for this data... I have documented this here https://github.com/nexB/vulnerablecode/blob/37fdd7dcabc8187e855292d1e681d3852a87cf52/vulnerabilities/importers/nvd.py#L32

It is fine if you switch to a CC0-1.0 license but has this be vouched for by MITRE legal?

@pombredanne
Copy link

See in particular https://www.cve.org/Legal/TermsOfUse

@pombredanne
Copy link

gentle ping

@eslerm
Copy link

eslerm commented Apr 17, 2024

I would love for this to be CC0, but the attribution clause in the terms of use page implies CC BY 4.0 or similar:

Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Of course, MITRE could remove this clause.

@pombredanne
Copy link

@hkong-mitre gentle ping. I see @rbrittonMitre is missing as a reviewer? Note that until you clarify the license, the Mitre ToU at https://www.cve.org/Legal/TermsOfUse apply and any fork or release you make is immediately non-compliant because this license at https://www.cve.org/Legal/TermsOfUse states:

"Any copy you make for such purposes is authorized provided that
you reproduce MITRE's copyright designation and this license in any
such copy."

It would be nice to make it easy on users by providing a proper license text in the repo.

@pombredanne
Copy link

I submitted this PR #65 to add the missing current license text until that CC0 PR can be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants