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

Usage of Basic Proprietary Commercial License #4364

Closed
Phani2811 opened this issue Mar 14, 2023 · 3 comments · Fixed by #4366
Closed

Usage of Basic Proprietary Commercial License #4364

Phani2811 opened this issue Mar 14, 2023 · 3 comments · Fixed by #4366
Assignees

Comments

@Phani2811
Copy link

Hi Team,
I have run a blackduck scan for scanning the keda packages to validate if there are any security or licence risks.
As part of this, dependency scan analysis was executed and it has shown a transitive dependency on the component "bouk/monkey" (Version: v1.0.1).

This component is mapped to a licence called "Basic Proprietary Commercial License". When i verified the licence info in github, it has shown below content:

**I do not give anyone permissions to use this tool for any purpose. Don't use it.

I’m not interested in changing this license. Please don’t ask.**

Git hub url for reference: https://github.com/bouk/monkey/blob/master/LICENSE.md

Can you please confirm if there is any workaround to use keda packages without using this component so that licence issues are sorted. Thank you!

@zroubalik
Copy link
Member

@Phani2811 thanks a lot for your message, we need to fix this. Seems like this dependency has been brought by this PR: #3804

@26tanishabanik FYI^

@JorTurFer
Copy link
Member

I'm asking in parallel to FOSSA (the tool we use for detecting this issues) about this case because in theory, we don't have any issue but obviously we have it

@zroubalik
Copy link
Member

I am working on a fix.

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

Successfully merging a pull request may close this issue.

3 participants