Potential fix for code scanning alert no. 6: Workflow does not contain permissions #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/qdequippe-tech/pappers-php-api/security/code-scanning/6
In general, the fix is to explicitly set GitHub Actions
permissionsto the minimal required level instead of inheriting repository defaults. This can be done either at the workflow root (affecting all jobs) or per job. Here, there is a single job (check-cs) that only reads code, so we can safely restrict contents to read-only.The best minimal fix without changing behavior is to add a
permissionsblock at the workflow root, right after theon:block and beforejobs:. We will setcontents: read, which is sufficient foractions/checkoutto fetch the repository content. No other scopes (likepull-requestsorissues) are needed because the workflow does not interact with those APIs. Concretely, in.github/workflows/ci.yml, we’ll insert:aligned with the existing indentation so that it applies to all jobs in the workflow. No imports or additional methods are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.