Show patched version of dependency in the dependency review summary

[virangdoshi]

In the PR summary, it would be nice to have a fix/patched version of the dependency, when a vulnerability is identified. The summary has vulnerability details, severity, etc. And additional column for "Patched Version" can be included as well. When a developer is looking at the summary, the patched version would help save time and avoid context switching in locating the patched version of the dependecy. Today, I have to click on the "vulnerability" link that points to the Github advisory database, which then contains the information on patched version of the dependency. The patched version column can be next to the severity column

[jonjanego]

Hi @virangdoshi , thank you for the suggestion.

In the meantime, I suggest you consider enabling Dependabot alerts for your repositories, which will alert you to vulnerable package versions, as well as suggest fixes to them.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity for 180 days. You can: comment on the issue or remove the stale label to hold stalebot off for a while, add the Keep label to hold stale off permanently, or do nothing. If you do nothing, this issue will be closed eventually by the stalebot. Please see CONTRIBUTING.md for more policy details.