-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Node.js Security WorkGroup Meeting 2023-03-16 #905
Comments
Hello, I am a co-founder of StepSecurity and plan to attend the next Node.js Security WG meeting. I want to demo a solution to automate remediations to increase Scorecard score using a pull request if there is time. This has already been used by many open-source repositories and is also being used by the Eclipse Foundation. Looking forward to the meeting! Thanks! |
I won't be around to discuss flags for MS integration tomorrow. |
arf missed the meeting, didn't see that the time changed 😅 |
Oh no, it's DST in some timezones now 🤦♂️ |
Sorry, I should have pinged in the #nodejs-security-wg slack channel |
I wanted to follow up on a few things discussed in today's meeting.
Thanks! |
Time
UTC Thu 16-Mar-2023 14:00 (02:00 PM):
Or in your local time:
Links
Agenda
Extracted from security-wg-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/security-wg
nodejs/nodejs-dependency-vuln-assessments
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
security-wg-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
https://zoom.us/j/92309450775
The text was updated successfully, but these errors were encountered: