Skip to content

Improve score on OpenSSF scorecard #450

Closed

Activity

  1. added this to the Milestone 11 milestone on Apr 13, 2023
  2. mhdawson commented on Jun 30, 2023

    @mhdawson
    MemberAuthor
    • Kevin mentioned branch protection in the last meeting.
  3. KevinEady commented on Jul 5, 2023

    @KevinEady
    Contributor

    node-addon-api (scorecard)

    node-addon-examples (scorecard)

    • Add branch protection on main
    • Add LICENSE file
    • Make code reviews mandatory (as well as for administrators)
    • Make GitHub Actions CI workflow tokens read-only
    • Add CodeQL scanning similar to node-addon-api...?
    • Add fuzzing...?
  4. mhdawson commented on Jul 12, 2023

    @mhdawson
    MemberAuthor

    Add branch protection for both node-addon-api and node-addon-examples.

  5. mhdawson commented on Jul 12, 2023

    @mhdawson
    MemberAuthor

    PR to add boilerplate files to node-addon-examples - nodejs/node-addon-examples#213

  6. mhdawson commented on Jul 12, 2023

    @mhdawson
    MemberAuthor

    @KevinEady can you expand a bit on Make GitHub Actions CI workflow tokens read-only

  7. mhdawson commented on Jul 12, 2023

    @mhdawson
    MemberAuthor

    PR to add best practices to node-addon-api - nodejs/node-addon-examples#214

  8. KevinEady commented on Jul 12, 2023

    @KevinEady
    Contributor

    Hi @mhdawson,

    ... can you expand a bit on Make GitHub Actions CI workflow tokens read-only

    From Assigning permissions to jobs - GitHub Docs:

    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.

    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.

  9. mhdawson commented on Jul 14, 2023

    @mhdawson
    MemberAuthor

    @KevinEady I think I merged the PR you mentioned, so we should be able to close this now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions