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

The format of vulnerability scanning result report should be refactored and improved to avoid confusions. #4567

Closed
steven-zou opened this issue Apr 2, 2018 · 4 comments · Fixed by #5965

Comments

@steven-zou
Copy link
Contributor

Currently, we summarize info based on package. Maybe it should be displayed directly with CVE counts of different severities.

@reasonerjt
Copy link
Contributor

Summarize the based on packages are for rendering the status bar.
I believe the confusion was due to misleading text messages on UI, if we can clarify the number are the number of packages, not actual CVE vulnerabilities, there won't be issues.

@zhoumeina
Copy link
Contributor

I will asign this UI changes to the new comer to familiar with the code.

@zhoumeina zhoumeina added this to the Sprint 43 milestone Sep 10, 2018
@zhoumeina
Copy link
Contributor

@lweitzman , I agree. It do lead misunderstanding of Vulnerabilities number. Could you help to give a new design about this? What about show "XX Vulnerabilities in XX packages."

@zhoumeina zhoumeina assigned pureshine and unassigned zhoumeina Sep 19, 2018
@zhoumeina zhoumeina modified the milestones: Sprint 43, Sprint 44 Sep 19, 2018
@lweitzman
Copy link

do we have the number of vulnerabilities for each package? is it useful at this point to know the number of vulnerabilities per package or just that XX packages have vulnerabilities?
also, could we align the number (right align) and the text (left allign) on the page?

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

Successfully merging a pull request may close this issue.

5 participants