Add clarity-based compliance support#1684
Closed
NucleonGodX wants to merge 1 commit into
Closed
Conversation
Signed-off-by: NucleonGodX <racerpro41@gmail.com>
NucleonGodX
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for evaluating license clarity scores against compliance policies. Now threshold-based policies for license clarity scores can be defined.
I've extended the policy system to handle both license and clarity policies in the same
policies.ymlfile and updated the summary generation to evaluate clarity scores against defined thresholds. Now aclarity_compliance_alertfield is injected into the summary output based on the evaluation results. Policies can be setup, like requiring a minimum clarity score of 95, with anything below triggering an error alert.This only works with the
scan_single_packagepipeline since that's the only one that generates clarity scores. The compliance alerts will show up in the summary.json file.