You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a branch in the trusty evaluator that checks if we managed to fetch a score for a package at all:
if resp.Summary.Score == 0 {
logger.Info().
Str("dependency", dep.Dep.Name).
Msgf("the dependency has no score, skipping")
continue
}
but if we can't fetch any packages we just say that no packages with low scores were found. We should at the very least change the summary in case no scores can be fetched or even provide a separate table with dependencies that couldn't be fetched so that the maintainers can check those themselves.
To Reproduce
unsure, I managed to hit this in combination with a trusty bug
What version are you using?
v0.0.24+ref.aa6a2170
The text was updated successfully, but these errors were encountered:
@evankanderson - I'm not sure, I haven't tested it yet, so I'll suggest to plan it for the next sprint. Best case scenario is we confirm it's fixed and close it.
Describe the issue
We have a branch in the trusty evaluator that checks if we managed to fetch a score for a package at all:
but if we can't fetch any packages we just say that no packages with low scores were found. We should at the very least change the summary in case no scores can be fetched or even provide a separate table with dependencies that couldn't be fetched so that the maintainers can check those themselves.
To Reproduce
unsure, I managed to hit this in combination with a trusty bug
What version are you using?
v0.0.24+ref.aa6a2170
The text was updated successfully, but these errors were encountered: