aboutcode-org / aboutcode-org/vulnerablecode

[RFC] Advisory search api: access to unprocessed data

Abierto
#2,293 1 comentario 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
702
Forks
328
Merge medio
3 d 8 h
PR fusionados (30 d)
3

Descripción

VulnerableCode currently is one of the best data sources out there for vulnerabilities, although since our upstream data has a lot of inconsistencies/versioning issues/advisory quality issues etc, it makes it looks as though vulnerablecode is not exhaustive.

I'm proposing a VulnerableCode search engine that could search based on advisory's original text instead of purl or vulnerability/advisory. The output would contain all the unstructured advisories and the structured relationship among packages and vulnerabilities. In a sense, this will be Google for VulnerableCode.

For example, the package `grocy` has no matches in [current vulnerablecode deployment](https://public.vulnerablecode.io/packages/v2/search/?search=grocy), possibly because there was some problem parsing purl from the advisory. Although, we have multiple advisories fetched on `grocy` (12 in fact).
This is in no manner authoritative data source as VulnerableCode's default search since mere presence of a package name in the advisory does not prove that the package is vulnerable, but it does signal interest in the advisory if there's an interest in the package mentioned.

I've created a mock app that demonstrates this. For the above example, this is how it looks: https://advisory-search.hritik.sh/?q=grocy

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.