| Message ID | AS4P195MB1645496BED047F45D6B9247FEB632@AS4P195MB1645.EURP195.PROD.OUTLOOK.COM |
|---|---|
| State | New |
| Headers | show |
| Series | cve-check: add field "modified" to JSON report | expand |
On Thu, 2024-09-19 at 15:40 +0200, Katawann via lists.openembedded.org wrote: > cve-check: add field "modified" to JSON report > > Signed-off-by: Katawann <quent_55@hotmail.com> > --- > meta/classes/cve-check.bbclass | 1 + > 1 file changed, 1 insertion(+) Duplicating the shortlog isn't a great way to avoid the patchtest email. You had some good text in your 0/1 cover letter. I'd suggest putting that ("Added the "modified" field to the JSON export in the cve-check.class. This field captures the last modification date of each CVE, providing more detailed information on changes and updates within the exported data.") into the main commit message instead. Cheers, Richard
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass index a5104f210b..6245594dd7 100644 --- a/meta/classes/cve-check.bbclass +++ b/meta/classes/cve-check.bbclass @@ -534,6 +534,7 @@ def cve_write_data_json(d, cve_data, cve_status): cve_item["summary"] = cve_data[cve]["NVD-summary"] cve_item["scorev2"] = cve_data[cve]["NVD-scorev2"] cve_item["scorev3"] = cve_data[cve]["NVD-scorev3"] + cve_item["modified"] = cve_data[cve]["NVD-modified"] cve_item["vector"] = cve_data[cve]["NVD-vector"] cve_item["vectorString"] = cve_data[cve]["NVD-vectorString"] if 'status' in cve_data[cve]:
cve-check: add field "modified" to JSON report Signed-off-by: Katawann <quent_55@hotmail.com> --- meta/classes/cve-check.bbclass | 1 + 1 file changed, 1 insertion(+)