Enhancement request: Allow managing vulnerabilities in the product itself
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
未指定任何檔案、測試或進入點。先整理現有的套件漏洞工作流程和產品關聯，然後檢視目前 CSAF VEX 匯出的運作方式。產品層級的漏洞工作流程、必要欄位和實作邊界達成共識後，即視為完成。
由索引模型根據 Issue 內容生成。
描述
Is your enhancement request related to a problem? Please describe.
Products may have vulnerabilities in their own source code, not just in their dependencies. The Cyber Resilience Act mandates that companies selling products on the EU market will have to perform vulnerability management, coordinated vulnerability disclosure and provide public security advisories for when they have fixed vulnerabilities in their products, regardless whether that is in their dependencies or the product itself.
Currently one would need a separate solution to manage vulnerabilities in the product itself. Thus the there would be a split between vulnerability management for third-party dependencies in DejaCode and vulnerabilities in the product on a different platform. More likely the vulnerability management feature in DejaCode would not get used because of this split.
What are the benefits of the requested enhancement?
It would allow to make DejaCode the one-stop-shop for license compliance and vulnerability management. The current feature is already very nice, but unfortunately does not cover the complete needs for vulnerability management. If extended it could really be great for fulfilling compliance requirements. Exporting CSAF VEX this way would be especially useful for providing machine readable information to users/customers.
Describe the solution you would like
The vulnerability management should be extended to allow the creation of own vulnerability entries that are associated with the product, rather than a package. This could perhaps be a separate section or tab. The general workflow can be the same as for vulnerabilities found in packages. Creation would require to provide all relevant information that would otherwise be pulled from VulnerableCode, but cannot be done there as this is company internal information at that point in time.
Additional notes
n.a.
- 主要語言
- Python
- 星號
- 52
- 分支
- 30
- 平均合併
- 4 小時 57 分鐘
- 30 天內合併 PR
- 21
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
aboutcode-org/dejacode 的其他 Issue
-
DOC: Document workflow between ScanCode.io and DejaCode可能已有人在做 @tdruez 於 1 天前認領。 未關閉documentation
難度 3/5 1-2 天 新手友好度 55/100
aboutcode-org/dejacode#606 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 45/100
aboutcode-org/dejacode#603 ·
維護者通常 1 天內回覆
-
design needed enhancement
難度 3/5 1-2 天 新手友好度 62/100
aboutcode-org/dejacode#561 · 3 則留言 ·
維護者通常 1 天內回覆
-
Enhancement request: Refine License Category - Copyleft Limited可能重新可做 @hesa 於 119 天前認領，目前沒有進行中的 PR。 未關閉design needed enhancement
aboutcode-org/dejacode#499 · 13 則留言 · 已指派 3 人 ·
維護者通常 1 天內回覆
-
BUG: Product overview page splits product with many versions across pages可能重新可做 關聯的 PR 已關閉且未合併。 未關閉bug design needed enhancement
難度 3/5 1-2 天 新手友好度 45/100
aboutcode-org/dejacode#460 ·
維護者通常 1 天內回覆
查看 aboutcode-org/dejacode 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 76/100
pytest-dev/pytest-html#1085 ·
-
難度 2/5 1-3 小時 新手友好度 90/100
pollen-robotics/reachy_mini#1527 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 66/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 1 天內回覆