aboutcode-org / aboutcode-org/vulnerablecode

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

Ouverte
#1,018 0 commentaires 0 réactions 1 personne assignée Réclamée par @johnmhoran Voir sur GitHub
Data collection import-improver-migration
Langage dominant
Python
Étoiles
702
Forks
328
Merge moyen
3 j 8 h
PR mergées (30 j)
3

Description

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?

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.