aboutcode-org / aboutcode-org/vulnerablecode

Should we use a different source of JSON advisory/CVE objects for the apache_httpd importer?

未关闭
#1,018 0 条评论 0 个 reaction 已指派 1 人 已被 @johnmhoran 认领 在 GitHub 查看
Data collection import-improver-migration
主要语言
Python
星标
702
派生
328
平均合并
3 天 8 小时
30 天内合并 PR
3

描述

Exploring the `json` URL we currently use in the `apache_httpd.py` `fetch_links()` function (https://httpd.apache.org/security/json/), if I navigate up 1 step to https://httpd.apache.org/security/, I see that:

* The date of the `json` folder is 2022-06-10. This folder contains the individual `.json` files currently parsed by `fetch_links()`. 1 file is dated 2022-06-10, and all others are dated 2022-06-08.
* There's also a link to https://httpd.apache.org/security/vulnerabilities-httpd.json, dated 2022-10-24, which is a list of `.json` advisory/CVE objects, possibly containing all of the individual CVE objects (and more?).

Should we explore this list of advisory/CVE objects, determine whether it contains all the objects contained in the `json` folder we're currently parsing, and if so parse that file instead, since it has a more recent date?

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。