You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can use permissions to modify the default permissions granted to the GITHUB_TOKEN, adding or removing access as required, so that you only allow the minimum required access.
Activity
mhdawson commentedon Jun 30, 2023
KevinEady commentedon Jul 5, 2023
node-addon-api (scorecard)
main(For GitHub, check out the steps here.)v2.x-staging,v1.x-stagingnode-addon-examples (scorecard)
mainnode-addon-api...?mhdawson commentedon Jul 12, 2023
Add branch protection for both node-addon-api and node-addon-examples.
mhdawson commentedon Jul 12, 2023
PR to add boilerplate files to node-addon-examples - nodejs/node-addon-examples#213
mhdawson commentedon Jul 12, 2023
@KevinEady can you expand a bit on
Make GitHub Actions CI workflow tokens read-onlymhdawson commentedon Jul 12, 2023
PR to add best practices to node-addon-api - nodejs/node-addon-examples#214
KevinEady commentedon Jul 12, 2023
Hi @mhdawson,
From Assigning permissions to jobs - GitHub Docs:
This is for the principle of least privilege, as discussed in the Token-Permissions Check documentation.
This was mostly addressed by the SecurityBot PR nodejs/node-addon-examples#214 , eg: nodejs/node-addon-examples@a05f82c#diff-e98936aa52a6dd7416e4296e9628456227d834f7245967383fd9ff80fd985dadR9-R11 but it skipped a workflow that I added to the PR in this commit.
So once this PR is merged, we can say that the Token-Permissions issue has been addressed and we will receive full points.
mhdawson commentedon Jul 14, 2023
@KevinEady I think I merged the PR you mentioned, so we should be able to close this now?