Skip to content

Commit 51a5215

Browse files
doc: add meeting minutes 2023-04-13
Related: #961 ----------- Co-authored-by: RafaelGSS <[email protected]>
1 parent 6d54935 commit 51a5215

File tree

1 file changed

+82
-0
lines changed

1 file changed

+82
-0
lines changed

meetings/2023-04-27

+82
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
# Node.js Security WorkGroup Meeting 2023-04-27
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=6lpxKOL-PwQ&ab_channel=node.js
6+
* **GitHub Issue**: https://github.com/nodejs/security-wg/issues/961
7+
8+
9+
## Present
10+
11+
* Ulises Gascon: @ulisesGascon
12+
* Marco Ippolito: @marco-ippolito
13+
* Yagiz Nizipli: @anonrig
14+
* Michael Dawson: @mhdawson
15+
* Rafael Gonzaga: @RafaelGSS
16+
17+
## Agenda
18+
19+
## Announcements
20+
21+
*Extracted from **security-wg-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
22+
23+
- [x] Vulnerability Review - https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues
24+
* We’ll drop v14 support and include Node.js v20 to this action
25+
* There is a new OpenSSL low vulnerability
26+
27+
- [x] OpenSSF Scorecard Monitor Review - https://github.com/nodejs/security-wg/pull/965
28+
* Binary artifacts need to support whitelisting for the test fixtures case
29+
* New visualization tool in place, next release will include commit hash reference (immutability)
30+
* Many changes happened in Node.js but the total impact in the repo is -0.3 points
31+
* Ulises will invite the Scorecard maintainers to the next meetings to provide them feedback and share with the WG the next iteration planned with the scoring system
32+
* Ulises will include the link to the StepSecurity Beta Dashboard in the report for Node.js Org
33+
34+
### nodejs/security-wg
35+
36+
* Initiative for CII-Best-Practices for Nodejs Projects [#953](https://github.com/nodejs/security-wg/issues/953)
37+
* good discussion/sharing of existing answers - https://bestpractices.coreinfrastructure.org/en/projects/29#all
38+
* We’ll review all the three PR async
39+
* The entry-level might need a single adjustment (code static analysis), the rest looks good
40+
* Ulises will lead the initiative.
41+
* The documents will be relocated to the Node repository as soon as it is ready
42+
43+
* Assessment against best practices (OpenSSF Scorecards ...) [#859](https://github.com/nodejs/security-wg/issues/859)
44+
* No news
45+
46+
* Scorecard Review [#937](https://github.com/nodejs/security-wg/issues/937)
47+
* closed
48+
49+
* Improve Node.js Scorecard [#929](https://github.com/nodejs/security-wg/issues/929)
50+
* Published the updates in the issue
51+
52+
* Permission Model - Roadmap [#898](https://github.com/nodejs/security-wg/issues/898)
53+
* Possible some work on the relative paths in the C++ side next week
54+
55+
* Improve SecurityWG Scorecard [#884](https://github.com/nodejs/security-wg/issues/884)
56+
* Published the updates in the issue
57+
* It will great to have some community support for Fuzzing
58+
59+
* Automate security release process [#860](https://github.com/nodejs/security-wg/issues/860)
60+
* We are discussing it internally at Node.js TSC to get someone to work on this
61+
62+
* Discussion about policy-integrity integration on Windows [#856](https://github.com/nodejs/security-wg/issues/856)
63+
* PR created https://github.com/nodejs/node/pull/47609
64+
65+
* Automate updates of all dependencies [#828](https://github.com/nodejs/security-wg/issues/828)
66+
* The initiative is almost done.
67+
* Marco will work in the documentation in details for this process
68+
* Marco will start a discussion to backporting this process to other Node.js versions
69+
* Marco requested access to the Github Action team
70+
* It will be require to review if any dependency is missing from the list
71+
72+
## Q&A, Other
73+
74+
* Yagiz Nizipli will be in parental leave. He want to ensure that Ada can keep doing releases in cases that any urgent/security release is needed. We agreed to promote the Ada related issues in Node to the fastrack when needed.
75+
76+
77+
## Upcoming Meetings
78+
79+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
80+
81+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
82+

0 commit comments

Comments
 (0)