-
Notifications
You must be signed in to change notification settings - Fork 207
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
base: main
Are you sure you want to change the base?
Conversation
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? |
See in particular https://www.cve.org/Legal/TermsOfUse |
gentle ping |
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:
Of course, MITRE could remove this clause. |
@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:
It would be nice to make it easy on users by providing a proper license text in the repo. |
I submitted this PR #65 to add the missing current license text until that CC0 PR can be merged. |
Adding a license file to the repository