RFC: Proposing a standard and generic method of publishing Python packages

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

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start by reviewing the proposed SLSA level 3 risk matrix in the issue and the linked Trivy incident. The issue asks for group review of a generic standard for publishing and consuming Python packages, but does not define its requirements or implementation. Done would mean the group agrees on a PySCG norm that helps projects address the stated risks.

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

Descripción

This is a request for comments, in relation to the following topic that relates to publishing & consuming software in the Python language.

The subject was brought up during our today's meeting, and it has been about how to handle the situation that scanners themselves are problematic, as an example thinking of syft and trivy, the latter of which itself experienced trouble recently [1]. Using an LLM it was possible to narrow down the direction, but obviously this should now be put subject to review in the greater group.

Ultimately, the ask as regards a project like, say, qtop (ref. https://github.com/qtop/qtop) is merely the intent to implement SLSA level 3 against the following risk matrix - there is no desire to endorse any particular tool, merely to show the complementarity of risks and measures:

Image

Ideally, we could have a PySCG norm, that would allow Python projects to position themselves correctly in respect to said risks.

[1] https://www.digitec.ch/en/page/trivy-hack-millions-of-credentials-from-thousands-of-companies-leaked-43485

Lenguaje dominante
Python
Estrellas
2
Forks
2
Merge medio
11 min
PR fusionados (30 d)
2

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 ossf/python-secure-coding-guide

Todos los issues de ossf/python-secure-coding-guide

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.