Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Add the OpenSSF Scorecard GitHub Action and publish the results

Aberta Para iniciantes
  • Algo errado?
#1,332 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

@AdepuSriCharan já está trabalhando nisso.

Desde 22/10/2026.

  • #1341 de @AdepuSriCharan — aberto

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
78/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github-actions, python
Domínio
devops, security

Direção de pesquisa

Comece pelo README da action Scorecard e pelos workflows existentes em .github/workflows/; adicione um workflow que atenda aos requisitos listados de gatilhos, permissões, pinning das actions, publicação dos resultados e upload de SARIF. Execute actionlint .github/workflows/scorecard.yaml para verificá-lo. O trabalho estará concluído quando o workflow atender aos critérios de aceitação e a CI existente continuar verde.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

good first issue help wanted

Problem

python-sdk has no OpenSSF Scorecard results published. The public Scorecard API returns nothing for it today (curl -s https://api.securityscorecards.dev/projects/github.com/dapr/python-sdk is a 404), while dapr/dapr is already scanned. Running the official Scorecard action on a schedule gives users a public score for the project's supply-chain practices, and gives maintainers a list of concrete things to fix (pinned dependencies, token permissions, branch protection and so on) in the repo's code scanning alerts.

Proposed change

Add a workflow, for example .github/workflows/scorecard.yaml, using ossf/scorecard-action. The action's README has a starter workflow; the important parts are:

  • Triggers: push to main, a weekly schedule, and branch_protection_rule.
  • Top-level permissions: read-all, and on the job only what it needs: security-events: write (upload SARIF), id-token: write (publish results), contents: read, actions: read.
  • ossf/scorecard-action with results_format: sarif and publish_results: true.
  • Upload the SARIF with github/codeql-action/upload-sarif so findings appear under Security, Code scanning.
  • Optionally upload the SARIF with actions/upload-artifact too, for easy download.

Pin the actions in this new workflow to commit SHAs with the version as a trailing comment (for example uses: actions/checkout@<sha> # v7.0.0). Scorecard's own Pinned-Dependencies check expects it, and publish_results: true requires the workflow to follow the action's restrictions (see its README).

Optionally, add the Scorecard badge to README.md:

[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/dapr/python-sdk/badge)](https://scorecard.dev/viewer/?uri=github.com/dapr/python-sdk)

Acceptance criteria

  1. A Scorecard workflow runs on push to main, weekly, and on branch protection changes.
  2. It uses ossf/scorecard-action with publish_results: true, and uploads the SARIF to code scanning.
  3. The workflow's token has read-only permissions at the top level and only the job-level write permissions listed above.
  4. All uses: in the new workflow are pinned to full commit SHAs with a version comment.
  5. Existing CI stays green.

How to test

  1. Run actionlint .github/workflows/scorecard.yaml locally.
  2. After merge (or via workflow_dispatch if you add it), check the run succeeds and that results appear under Security, Code scanning.
  3. Confirm curl -s https://api.securityscorecards.dev/projects/github.com/dapr/python-sdk returns a JSON result.
  4. Before opening the PR you can preview the score locally with the scorecard CLI: scorecard --repo=github.com/dapr/python-sdk (needs a GITHUB_AUTH_TOKEN).
Linguagem predominante
Python
Estrelas
274
Forks
160
Merge médio
1d 23h
PRs com merge (30d)
70

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de dapr/python-sdk

Todas as issues de dapr/python-sdk

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.