ci: pin actions e tripwire publish-watch (postmortem TanStack)#9
Merged
Conversation
- pin de todas as actions externas em SHA + comentário de versão (actions/*, pnpm/action-setup, terceiros conforme o repo) - novo publish-watch.yml: cron de 15 min que valida que toda versão publicada no npm tem tag git correspondente; abre issue de segurança em caso de divergência - renovate.json: preset helpers:pinGitHubActionDigests para que novas actions já entrem fixadas Motivação: postmortem do TanStack (2026-05-11) destacou refs flutuantes de actions e ausência de tripwire em registry como riscos de supply chain independentes da entrada original do ataque.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Endurecimento dos workflows após o postmortem do TanStack (2026-05-11). A entrada do ataque (
pull_request_target+ cache poisoning + extração de OIDC) não existe aqui, mas duas lições independentes do postmortem se aplicam:@vXagora apontam para SHA imutável + comentário de versão (formato suportado pelo Renovate para bumps).publish-watch.ymlroda cron de 15 min, comparanpm view <pkg> versioncontra as tags git locais e abre issuesecurity/publish-watchquando há divergência (publicação fora do fluxo).Mudanças
publish-watch.yml(novo, se o repo publica) — cron*/15 * * * *+workflow_dispatchrenovate.json—helpers:pinGitHubActionDigests+pinDigests: trueno grupogithub-actionsOrigem dos templates: PR Precisa-Saude/tooling#34. Após esse PR fazer release do
@precisa-saude/cli,precisa synctorna esta PR um no-op.Próximos passos pós-merge
npm-publishtem revisor requerido (gate já presente no_publish.yml).