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 摘要。