chore: Set permissions for GitHub actions

Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions

https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs

[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)

Signed-off-by: nathannaveen <42319948+nathannaveen@users.noreply.github.com>
This commit is contained in:
nathannaveen 2022-06-09 01:05:21 +00:00
parent 8116903ba6
commit 4418fd38f1
7 changed files with 25 additions and 0 deletions

View File

@ -9,6 +9,9 @@ on:
schedule:
- cron: '0 0 * * *'
permissions:
contents: read
jobs:
generate-snapshots:
name: Generate ${{ matrix.version }} snapshots

View File

@ -8,6 +8,9 @@ on:
- master
- QA_**
permissions:
contents: read
jobs:
lint-node:
runs-on: ubuntu-latest

View File

@ -4,8 +4,13 @@ on:
schedule:
- cron: '0 0 * * *'
permissions:
contents: read
jobs:
lock:
permissions:
issues: write # for dessant/lock-threads to lock issues
runs-on: ubuntu-latest
steps:
- uses: dessant/lock-threads@v2

View File

@ -6,6 +6,9 @@ on:
pull_request:
branches: [master]
permissions:
contents: read
jobs:
tests:
name: Mutation tests with PHP ${{ matrix.php-version }}

View File

@ -8,6 +8,9 @@ on:
- master
- QA_**
permissions:
contents: read
jobs:
build-documentation:
runs-on: ubuntu-latest

View File

@ -11,6 +11,9 @@ on:
env:
php-version: "8.1"
permissions:
contents: read
jobs:
selenium:
name: "Selenium"

View File

@ -5,8 +5,13 @@ on:
schedule:
- cron: '0 0 * * 0'
permissions:
contents: read
jobs:
update-po:
permissions:
contents: write # for Git to git push
name: Update po files
runs-on: ubuntu-latest
# Source: https://github.community/t/do-not-run-cron-workflows-in-forks/17636/2?u=williamdes