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

License Policy and Compliance Alert not working with scan_codebase but working with scan_package #784

Closed
prakyathr opened this issue Jun 25, 2023 · 2 comments

Comments

@prakyathr
Copy link

prakyathr commented Jun 25, 2023

I am currently testing the functionality of Compliance Alert as it is one of the main requirements for OSS license scanning automation in my Organization. So, I was using the examples provided in the documentation using policies.yml and scan_codebase pipeline with cuckoo-filter package to test it out. However, I was never able to get the alerts configured in the policies.yml file.

license_policies:
  - license_key: mit
    label: Approved License
    compliance_alert: ""
  - license_key: mpl-2.0
    label: Restricted License
    compliance_alert: warning
  - license_key: gpl-3.0
    label: Prohibited License
    compliance_alert: error
  - license_key: cc-by-nc-sa-4.0
    label: Prohibited License
    compliance_alert: error

image
image

However, when I use scan_package pipeline for the same package, the License policy and Compliance alert is working as expected.
image

This is an expected output?

According to the documentation, license policy should be working for scan_codebase.

ScanCode.io: 32.3.0
ScanCode-toolkit: 32.0.4

tdruez added a commit that referenced this issue Jun 26, 2023
Signed-off-by: Thomas Druez <tdruez@nexb.com>
tdruez added a commit that referenced this issue Jun 26, 2023
Signed-off-by: Thomas Druez <tdruez@nexb.com>
@tdruez
Copy link
Contributor

tdruez commented Jun 26, 2023

@prakyathr Thanks for reporting the issue.

The fix #786 has been merged in the main branch.
Could you try again with the latest changes and confirm everything is now working as expected.
Thanks!

@prakyathr
Copy link
Author

@tdruez It is working now. Thanks for the fix..
image

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

No branches or pull requests

2 participants