-
Notifications
You must be signed in to change notification settings - Fork 34
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
Improve score on OpenSSF scorecard #450
Comments
|
node-addon-api (scorecard)
node-addon-examples (scorecard)
|
Add branch protection for both node-addon-api and node-addon-examples. |
PR to add boilerplate files to node-addon-examples - nodejs/node-addon-examples#213 |
@KevinEady can you expand a bit on |
PR to add best practices to node-addon-api - nodejs/node-addon-examples#214 |
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. |
@KevinEady I think I merged the PR you mentioned, so we should be able to close this now? |
https://deps.dev/project/github/nodejs%2Fnode-addon-api
https://deps.dev/project/github/nodejs%2Fnode-addon-examples
The text was updated successfully, but these errors were encountered: