3 Commits

Author	SHA1	Message	Date
Ninette Adhikari	34edaea7f6	cve-report: Reformat txt recipe list per branch ... Yocto gathers the amount of CVEs per branch at the top of their metrics view. However, the presentation of this information is not descriptive enough and it’s spread across several files. This change adds collapsible, nested lists to show all cve information. Show current CVE count per release, parse txt files with CVE lists to group them by project and display their total CVE count. Inline this data on the matrics-page in details elements so there’s no need to navigate away. The current output includes the count of cve's and the cve-urls. No data is lost here, it looks like: CVE counts by recipes: linux-yocto: 134 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 ... bluez5: 2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3637 ... Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>	2024-05-02 11:35:21 +01:00
Richard Purdie	9131fbeab5	cve-report: Add summary counts of CVEs by recipe ... It is often helpful to know how many CVEs are open against a given recipe. Add a summary table of this to the end of the CVE listing. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>	2024-01-24 10:24:15 +00:00
Richard Purdie	2aad3d2c6d	config.json/scripts: Update to handle CVE checks for meta-oe ... Backport the recent CVE script changes from the master branch and add in cvelayer.bbclass as a way to exclude specific paths from the CVE check. Master can use the layer overrides to do this but these are not present on kirkstone. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>	2023-11-03 12:55:39 +00:00