Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Improve EPSS Importer and Getting EPSS history data

Abierto
  • ¿Algo no está bien?
#2,435 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, data

Línea de trabajo

Start with the EPSS importer and the AdvisoryDataV2/VulnerabilitySeverity flow described here, then review PR #2433 and the historical daily dataset format. Define a bulk-import and time-series representation that avoids one advisory per CVE per day, and validate it against the stated multi-year history and import-time constraints.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

EPSS is currently represented as a VulnerabilitySeverity associated with an AdvisoryDataV2.

The importer creates one advisory for each CVE and stores the EPSS score and percentile as a vulnerability severity.

The current importer fetches the latest EPSS dataset for a single day, for example: epss_scores-2026-09-14.csv.gz, The pipeline then processes the entire dataset and creates a large number of advisory records. A single EPSS import currently takes approximately 3–12 hours.

This becomes a major problem when trying to import the complete EPSS history. The EPSS project provides historical daily datasets covering multiple years.

With approximately 2,190 daily files for roughly 6 years of history:

~365 days × 6 years = ~2,190 files
At an average of ~3 hours per import:
2,190 × 3 = 6,570 hours
6,570 / 24 = 273.75 days

Therefore, importing the complete history through the existing pipeline is not practical without implementing some form of bulk creation.
see:

There is also a second problem:

  • importing every historical file through the normal AdvisoryDataV2 workflow would generate a very large number of advisory records, even though EPSS is fundamentally time-series data where the score for a CVE changes over time.

I think we need a better way to handle EPSS data.

Lenguaje dominante
Python
Estrellas
716
Forks
347
Merge medio
12 h 15 min
PR fusionados (30 d)
9

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aboutcode-org/vulnerablecode

Todos los issues de aboutcode-org/vulnerablecode

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.