aboutcode-org / aboutcode-org/vulnerablecode

Provide more comprehensive options for possible upgrades

未關閉
#1,283 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Python
星號
702
分支
328
平均合併
3 天 8 小時
30 天內合併 PR
3

描述

The current VC UI shows one nearest non-vulnerable package and the latest non-vulnerable package for a given purl. Although, it is possible that neither of those version upgrades is suitable for me. Instead, I would like to upgrade to a vulnerable version with a low vulnerability severity because the development efforts in upgrading to the suggested versions are far too much than the risk (that I can accept) imposed by a low severity vulnerable upgrade.

Some sort of ordering like:
```
Worst upgrade candidate -> ... -> Ok-ish upgrade candidate -> Best upgrade candidate
```

The ordering could depend on:
1. Number of vulnerabilities for the upgrade candidate
2. Severity of those vulnerabilities

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。