Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

No-workflows repositories: three controls report unexpected_exit instead of saying there is nothing to audit

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, python
Ambito
ci-cd, security

Direzione di ricerca

Start with the exec handler that turns a non-zero exit into unexpected_exit, and with the three controls OSPS-BR-01.01, OSPS-BR-01.02 and OSPS-AC-04.02, which are gated on when = { ci_provider = "github" }. Check how zizmor exit code 3 and grep exit code 2 are handled when .github/workflows/ is missing. Done when a repository without workflows still gets WARN from these controls, but the message says there are no workflow files to audit, and the proposed option of pointing at confirming ci_provider is either implemented or ruled out.

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

Descrizione

needs triage

Summary

Low priority, wording only, On a repository with no .github/workflows/ directory and no confirmed project context, three controls report WARN [unexpected_exit]:

WARNING: OSPS-BR-01.01: exec handler could not complete (error_class=unexpected_exit): Command exited with unexpected code 3: zizmor --format json --offline <repo>; stderr: ... fatal: no audit was performed ...
WARNING: OSPS-BR-01.02: exec handler could not complete (error_class=unexpected_exit): Command exited with unexpected code 2: grep -rln github.head_ref .github/workflows/; stderr: grep: .github/workflows/: No such file or directory
WARNING: OSPS-AC-04.02: exec handler could not complete (error_class=unexpected_exit): Command exited with unexpected code 3: zizmor --format json --offline <repo>; ...
  OSPS-BR-01.01: WARN [unexpected_exit] - Could not automatically verify - manual verification required

All three have when = { ci_provider = "github" }, the context has no ci_provider until a person confirms it, and running the control and reporting WARN is the cautious result.

The point is the reason shown. "Unexpected exit code 3" reads as a broken tool. What happened is well defined: zizmor exits 3 when it finds no inputs, and grep exits 2 when the directory is missing. A new user auditing a repository before adding CI sees three warnings that look like failures of darnit.

Possible direction

  • Recognize "no workflow files" for these steps and say so in the message, keeping WARN.
  • Or point the message at the ci_provider question: confirming it makes these controls not applicable.

Seen with zizmor 1.30.1 on main at 24a4fed.

Drafted with Claude; reviewed and filed by me.

Lingua principale
Python
Stelle
22
Fork
27
Merge medio
1g 20h
PR unite (30g)
39

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

Tutte le issue di darnitdevorg/darnit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.