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

OSPS-DO-03.01 checks for a support file, but the requirement is release verification instructions

Abierto
#511 1 comentario 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

Start by reading the SupportDocumentation control in openssf-baseline.toml, then trace where that control is implemented and tested. Check how the project represents documentation checks and whether it can determine if a release exists. Done means the check assesses release-integrity instructions in project documentation, cannot pass on keywords alone, and is not assessed when there are no releases.

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

Descripción

module-baseline

OSPS-DO-03.01 (Maturity Level 3) reads:

When the project has made a release, the project documentation MUST contain instructions to verify the integrity and authenticity of the release assets.

The control is named SupportDocumentation in openssf-baseline.toml and checks for a support file (file_exists) followed by a keyword regex for support|help|issue|question. Neither measures the requirement: a SUPPORT.md passes, and a project that documents signature or checksum verification in its README or release notes does not.

Suggested direction:

  • rename the control and replace the steps with ones aimed at the requirement (look for verification instructions in the README, release docs, or SECURITY.md: cosign/gpg/sha256sum/slsa-verifier usage);
  • keep any keyword step unable to conclude PASS; the final say belongs to a judgment of the documentation content;
  • the requirement is conditional on a release existing, so the control should be N/A (or not assessed) when there are no releases.

Related: #508 (another control whose check does not match its requirement).

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
1 d 20 h
PR fusionados (30 d)
39

Preparar el entorno

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 darnitdevorg/darnit

Todos los issues de darnitdevorg/darnit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.