-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Improve Report UI #2
Comments
Hi @nprail, I have a suggestions for you:
|
Is someone still interested in working on this? I landed here because I was looking for a way to filter a table of just the high risk vulnerabilities. |
To be honest, is in my ToDo list in a while, but I didn't have time to see it yet. Feel free to open a PR, because i'm not part of the team. :P |
@giocodes I am planning on working on this at some point soon. But like @AdrianoCahete said, PRs are welcome! Are you looking for filtering after the report was generated or during? For example, you could achieve filtering by doing this: npm audit --json --audit-level=high | npm-audit-html |
Okay, so turns out that |
Aw too bad the flag does not work. Yeah, I'll be happy to help. 😃What do you all have in mind for the new UI to look like? I want to suggest a table where vulnerabilities can be sorted and users can choose the columns (information) they want to see. Similar to what Jira has for the issues view: For |
@giocodes Actually, determining what the improved look should be is most of why I haven't done it yet. So feedback like this is great! 👏👏👏 I like the idea of a sortable/filterable table that you can open collapses (or modals) to see more details for each vulnerability. @AdrianoCahete @giocodes |
If possible, everything (why not give the user that degree of customization?). But the most important ones are About the UI, my first idea was design an UI for this, but I'm with a lack of time this months. :( |
@AdrianoCahete Sure, giving the option to add any sortable columns to the table would be best. I just meant, what should the default columns be. The trouble with CVE is that it is an array of CVEs. There can be more than one. Would it make sense to group them all into one column? Example:
|
Is the palette easy to change? On my screen the green colors don't seem to have enough contrast. |
Yep, totally. I think I'll add a CLI option for dark or light mode. I'll definitely be making adjustments to the color palette too. |
Hope this will roll out soon. I have a small suggestion, It would be great if there is a breakdown of total no of issues based on the severity also. |
@nikhilgeo I'll be working on finishing this up and hopefully releasing a new version with it tomorrow! I'm probably going to make dark mode an option but not the default. |
Awesome, thank you for the new looks. Looking forward for the new release. |
🎉 This issue has been resolved in version 1.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The report UI doesn't look super great and could be better. Let's improve it.
To-Do
The text was updated successfully, but these errors were encountered: