Skip to content

Potential fix for code scanning alert in pg-db-session Workflow #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kartykp
Copy link

@kartykp kartykp commented May 20, 2025

Potential fix for https://github.com/npm/pg-db-session/security/code-scanning/1

To fix the issue, we will add a permissions block at the root of the workflow to explicitly define the required permissions. Based on the workflow's functionality, it needs contents: read to access repository contents and packages: write to publish the npm package. These permissions are sufficient for the tasks performed in the workflow.

The permissions block will be added at the root level, applying to all jobs in the workflow. This ensures that no unnecessary permissions are granted to the GITHUB_TOKEN.


Ref: https://github.com/github/npm/issues/13757

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…n permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
@kartykp kartykp changed the title Potential fix for code scanning alert no. 1: Workflow does not contain permissions Potential fix for code scanning alert in pg-db-session Workflow May 20, 2025
@kartykp kartykp self-assigned this May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant