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

decide on license #2

Open
garu opened this issue May 22, 2023 · 2 comments
Open

decide on license #2

garu opened this issue May 22, 2023 · 2 comments
Labels
help wanted Extra attention is needed

Comments

@garu
Copy link
Collaborator

garu commented May 22, 2023

For scripts, I'm thinking "same as perl".

What about for the reports themselves?

RustSec, RubySec are CC0 (public domain), PHPSec is Unlicense (public domain), Go Vuln DB, PiPy, Github is CC-BY-4.0 (attribution). (more here).

For the advisory database, Github states in their license that "You agree to release your contributions to the GitHub Advisory Database under the Creative Commons Zero license." But that's an agreement with Github, not necessarily with everyone else.

So before we put any reports here, I wonder what should be our terms.

@garu garu added the help wanted Extra attention is needed label May 22, 2023
@sjn
Copy link

sjn commented May 22, 2023

I, for one, don't mind CC0. Do we have any upstream licenses to care about?

@garu garu moved this from Todo to In Progress in CPAN Vulnerability Index Jul 19, 2023
@timlegge
Copy link

@garu - discuss next meeting?

@timlegge timlegge moved this from In Progress to Stalled in CPAN Vulnerability Index Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Development

No branches or pull requests

3 participants