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
The @nodejs/security team is running an initiative to improve the OpenSSF Scorecard results at organization level (nodejs/security-wg#859). In the last security team meeting we had discussed about the current scoring for the nodejs/nodejs.org repository. Seems like there is a decrease of -1.7 points since the last review (2 weeks ago)
I kinda disagree with the reasoning imposed here. Yes, we are checking out code, but supposedly only the "base" refs for a given PR, which usually mean that the base branch of this repository is used.
Also I wonder if on forks it would checkout the base ref of the fork or our repository.
Anyhow, I need to understand the reasoning why checking out the base branch ref is unsafe, as it is actually the recommended approach by GitHub to stay safe.
Enter your suggestions in details:
The @nodejs/security team is running an initiative to improve the OpenSSF Scorecard results at organization level (nodejs/security-wg#859). In the last security team meeting we had discussed about the current scoring for the
nodejs/nodejs.org
repository. Seems like there is a decrease of -1.7 points since the last review (2 weeks ago)In this recorded video you can see the analysis from the team (relevant from 05:08 to 14:53). Also the relevant notes from the meeting.
Here are the highlighted parts from the Delta Analysis:
Code-Review
Determines if the project requires human code review before pull requests (aka merge requests) are merged
Dangerous-Workflow
Determines if the project's github action workflows avoid dangerous patterns
Next steps
The text was updated successfully, but these errors were encountered: