-
Notifications
You must be signed in to change notification settings - Fork 64
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
What is the license ? #5
Comments
FWIW this is tracked on our side in aboutcode-org/vulnerablecode#487 and aboutcode-org/vulnerablecode#795 |
@williballenthin @jhsmith @RonnieSalomonsen and team: gentle ping... if there is no license the data cannot be reused at all. |
@aaronc100 do you have a preference or insights here? |
I'd suggest referring to our general council.
Aaron
…On Tue, Oct 11, 2022 at 1:25 PM Willi Ballenthin ***@***.***> wrote:
@aaronc100 <https://github.com/aaronc100> do you have a preference or
insights here?
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4EJKHYZY5IE6KITXUPJ33WCWWILANCNFSM53IEO24Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@aaronc100 given that you maintain this repo, can I ask that you take lead on this? |
Absolutely. Please assign the ticket to me.
…On Tue, Oct 11, 2022 at 2:21 PM Willi Ballenthin ***@***.***> wrote:
@aaronc100 <https://github.com/aaronc100> given that you maintain this
repo, can I ask that you take lead on this?
—
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4EJKBAVOV2Q62LY5OUMCLWCW43VANCNFSM53IEO24Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@aaronc100 Thank you in advance: anything you will select as a license will work and be a good choice. |
Some examples:
|
I have updated our readme and source files (*.cpp). CVE information is CC BY-SA 4.0 and source files are MIT. Please let me know if this resolves this issue to satisfaction. Thanks! --Aaron |
@aaronc100 and team: this is awesome and you rock. Thanks! |
Licensing updated on repo. |
Just for the record, since code and data are mixed in the files with the exception of these few PoC files in https://github.com/mandiant/Vulnerability-Disclosures/search?l=C%2B%2B&q=include , I will treat the effective resulting license of the collection as |
I am trying to import the Mandiant in vulnerablecode as part of my GSoC project. it will be great if we get the license
@pombredanne
The text was updated successfully, but these errors were encountered: