-
Notifications
You must be signed in to change notification settings - Fork 29
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
Addressing IllegalStateException in OssArtifactSecurityScore #822
Conversation
@@ -88,7 +88,9 @@ public ScoreValue calculate(Value<?>... values) { | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest in case of an unknown score (either artifact or project) to return to combined score as unknown.
Because the OssArtifactSecurityScore
take the project score and modify it based on the artifact version score.
If the project score is unknown it can not be modified and just returning the artifact version score is not correct (IMHO).
Other opinions?
As sample (which requires changes additional changes in line 91ff):
} | |
} else if (projectSecurityScore.isUnknown()) { | |
return scoreValue.withMinConfidence().makeUnknown(); | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with your argument. The artifact score should be co-dependent with the ProjectScore. @mibo please check the latest changes. It should reflect what we are discussing here.
…curityScore and OssSecurityScore
db21d36
to
e6bb4bb
Compare
fcb49bd
to
e5f68c9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #820