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

Aperta
  • Qualcosa non va?
#28 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
python
Ambito
security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Python
Stelle
2
Fork
2
Merge medio
11m
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ossf/python-secure-coding-guide

Tutte le issue di ossf/python-secure-coding-guide

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.