Skip to content

ci: add pinned gitleaks secret scan - #4

Merged
FabioLeitao merged 1 commit into
mainfrom
ci/gitleaks-secret-scan
Oct 9, 2026
Merged

FabioLeitao merged 1 commit into
mainfrom
ci/gitleaks-secret-scan

Conversation

@FabioLeitao

@FabioLeitao FabioLeitao commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Publica o commit local 30d26ab (assinado, 2026-09-17 03:01:34 -0300), que ainda não estava no origin. A main local não foi alterada: o push foi 30d26ab:refs/heads/ci/gitleaks-secret-scan.

Um arquivo: .github/workflows/gitleaks.yml.

  • Repositório público (DataBoar/homebrew-databoar).
  • actions/checkout pinado pelo SHA df4cb1c069e1874edd31b4311f1884172cec0e10 (comentário no arquivo: v6.0.3). O binário gitleaks 8.30.1 e o gitleaks.toml upstream (83d9cd6) estão pinados por SHA-256 no próprio workflow.
  • O workflow não declara secrets e não lê secrets.*. Permissão: contents: read. persist-credentials: false.
  • O gate apaga .gitleaks.toml / .gitleaksignore do checkout e passa --ignore-gitleaks-allow, para um allowlist no PR não silenciar o scan.

Test plan

  • actionlint no arquivo: exit 0
  • zizmor v1.30.1, persona regular, modo offline: nenhum achado (1 auditoria suprimida por estar offline)
  • CI desta PR: o job Secret scan (Gitleaks) no pull_request

Closes the last gap found in today's org-wide hardening audit: this repo
had zero security scanning (homebrew-databoar#2). Same pinned-binary +
strict-config pattern already proven across the org (SHA256 pinned,
inline gitleaks.toml/gitleaksignore stripped before scan, no inline
allow comments honored) rather than the weaker self-referential-checksum
variant.
@FabioLeitao
FabioLeitao merged commit 6715bff into main Oct 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant