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

Add license scan report and status #696

Closed
wants to merge 1 commit into from

Conversation

fossabot
Copy link

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

Signed off by: fossabot <badges@fossa.com>
@fossabot
Copy link
Author

Your license scan is passing -- congrats!

Your badge status is now updated and ready to merge:

FOSSA Status

@ice1000 ice1000 closed this Nov 18, 2022
@imkiva
Copy link
Member

imkiva commented Nov 19, 2022

What is this?

@ice1000
Copy link
Member

ice1000 commented Nov 19, 2022

What is this?

Automatic license checker. I have managed to generate a report here: https://app.fossa.com/projects/custom%2b34509%2fgithub.com%2faya-prover%2faya-dev/refs/branch/main/4300c5a0f8033a7ffac0c05e0919a01c33c88dab

It explains some license things I conjecture. But most of these are our own GPL-2 or GPL-3 projects. I conjecture that we should change all of them to either Apache-2.0 or MIT.

@ice1000 ice1000 added the invalid This doesn't seem right label Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants