The pull_request_target trap in GitHub Actions
Why it matters
pull_request_target runs with the repository secrets. Checking out and running the pull request’s code there hands those secrets to anyone who opens a pull request.
How to fix it
Does your repository pass this check?
Free for public GitHub repositories, no account needed. 50+ DevOps and security checks in about ten seconds.
Related checks
- How to find and remove secrets committed to a Git repository
- Why .env must be in .gitignore (and how to check it is not already committed)
- A .env file is committed to the repository: what to do
- Automated dependency updates with Dependabot or Renovate
- How to pin GitHub Actions to a commit SHA
- Least-privilege GITHUB_TOKEN permissions in workflows