aboutcode-org / aboutcode-org/vulnerablecode

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

Aperta
#1,018 0 commenti 0 reazioni 1 assegnatario Rivendicata da @johnmhoran Vedi su GitHub
Data collection import-improver-migration
Lingua principale
Python
Stelle
702
Fork
328
Merge medio
3g 8h
PR unite (30g)
3

Descrizione

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?

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.