OWASP / OWASP/SecurityShepherd
ci: least-privilege GITHUB_TOKEN and no long-lived tokens
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 515
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
PR #864 added a workflow-level permissions: contents: read block to .github/workflows/test.yml
.github/workflows/release.yml still has no permissions: block, but we might change how things are released. IF this stays it needs to be hardened. However, any release should use OIDC, no long lived tokens
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review .github/workflows/release.yml and compare its token permissions with the existing permissions block in .github/workflows/test.yml. First determine whether the current release workflow remains in use; done means any retained release path uses least-privilege permissions and OIDC rather than long-lived tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100