ataylorme / eslint-annotate-action

A GitHub action that takes ESLint results from a JSON file and adds them as annotated pull request comments
MIT License
88 stars 32 forks source link

GITHUB_TOKEN permissions used by this action #42

Closed step-security-bot closed 2 years ago

step-security-bot commented 2 years ago

At https://github.com/step-security/secure-workflows we are building a knowledge-base (KB) of GITHUB_TOKEN permissions needed by different GitHub Actions. When developers try to set minimum token permissions for their workflows, they can use this knowledge-base instead of trying to research permissions needed by each GitHub Action they use.

Below you can see the KB of your GITHUB Action.

name: "ESLint Annotate from Report JSON"
github-token:
  action-input:
    input: repo-token
  permissions:
    checks: write
    checks-reason: to create checks  #Checkout: https://github.com/ataylorme/eslint-annotate-action/blob/a1bf7cb320a18aa53cb848a267ce9b7417221526/src/eslint-action.ts#L82
    pull-requests: read
    pull-requests-reason: to get changed PR files #Checkout: https://github.com/ataylorme/eslint-annotate-action/blob/f92355332c64bc5c2d474cc6555edcb1315fdd12/src/get-pr-files-changed.ts#L14

If you think this information is not accurate, or if in the future your GitHub Action starts using a different set of permissions, please create an issue at https://github.com/step-security/secure-workflows/issues to let us know.

This issue is automatically created by our analysis bot, feel free to close after reading :)

References:

GitHub asks users to define workflow permissions, see https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/ and https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token for securing GitHub workflows against supply-chain attacks.

Setting minimum token permissions is also checked for by Open Source Security Foundation (OpenSSF) Scorecards. Scorecards recommend using https://github.com/step-security/secure-workflows so developers can fix this issue in an easier manner.