Skip to content

Commit 4c5dadb

Browse files
authored
doc: add 2024-04-25 meeting notes (#1295)
1 parent 93763ea commit 4c5dadb

1 file changed

Lines changed: 76 additions & 0 deletions

File tree

meetings/2024-04-25.md

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Node.js Security team Meeting 2024-04-25
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=nOd0dit-t80
6+
* **GitHub Issue**: https://github.com/nodejs/security-wg/issues/1286
7+
8+
## Present
9+
10+
* Thomas GENTILHOMME (@fraxken)
11+
* Michael Dawson (@mhdawson)
12+
* Rafael Gonzaga (@RafaelGSS)
13+
* Ulises Gascon (@UlisesGascon)
14+
* Robert - Microsoft
15+
* Lee Holmes - Microsoft
16+
* Carlos Espa
17+
18+
## Agenda
19+
20+
## Announcements
21+
22+
*Extracted from **security-wg-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
23+
24+
- [X] Vulnerability Review - https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues
25+
* Nothing new to discuss this week. An issues were opened asking about V8 vulns but those
26+
seem to be outside of the Node.js threat model.
27+
28+
- [X] OpenSSF Scorecard Monitor Review
29+
- PR: https://github.com/nodejs/security-wg/pull/1294 this includes the changes for 6w. Nothing actionable from the Security WG perspective.
30+
31+
### nodejs/node
32+
33+
* Remove --experimental-policy [#52575](https://github.com/nodejs/node/issues/52575)
34+
* Have been receiving lots of reports
35+
* Don’t have anybody who can maintain/keep up with the reports
36+
* Are starting down the path to remove the feature as its experimental
37+
* Lee Holmes, gave us an overview of why integrity is important.
38+
* Rafael, seems like main part is file integrity is the important part
39+
40+
* tools: change inactive limit to 9 months [#52459](https://github.com/nodejs/node/pull/52459)
41+
42+
### nodejs/security-wg
43+
44+
* Collaborators Inactivity Policy Review [#1282](https://github.com/nodejs/security-wg/issues/1282)
45+
* Added to potential initiatives list
46+
47+
* Can we have "unsecure" features in Node.js? [#1274](https://github.com/nodejs/security-wg/issues/1274)
48+
* General consensus that we should not have it. Answered in the issue asking aduh95 to join us to discuss further
49+
50+
* Discuss adding --security-revert to NODE_OPTIONS [#1262](https://github.com/nodejs/security-wg/issues/1262)
51+
* Michael gave overview and we had some discussion
52+
53+
* Initiative for CII-Best-Practices for Nodejs Projects [#953](https://github.com/nodejs/security-wg/issues/953)
54+
* Requested team review on https://github.com/nodejs/security-wg/pull/1185
55+
* Waiting for ownership transfer: https://github.com/nodejs/security-wg/issues/953#issuecomment-2049698350
56+
* We can reply “No” to the pending questions in gold and merge the PR: https://github.com/nodejs/security-wg/pull/956 ?
57+
* Remove from the agenda for now?
58+
59+
* Node.js Security Initiatives 2024 [#1255](https://github.com/nodejs/security-wg/issues/1255)
60+
61+
-- end of the meeting --
62+
63+
* Proposed approach for build steps in deps which are not in make node [#1236](https://github.com/nodejs/security-wg/issues/1236)
64+
* Security initiative in December 2023: fuzzing Nodejs: https://github.com/google/oss-fuzz/tree/master/projects/nodejs [#1159](https://github.com/nodejs/security-wg/issues/1159)
65+
* Audit build process for dependencies
66+
[#1037](https://github.com/nodejs/security-wg/issues/1037)
67+
* Permission Model - Roadmap [#898](https://github.com/nodejs/security-wg/issues/898)
68+
69+
## Q&A, Other
70+
71+
## Upcoming Meetings
72+
73+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
74+
75+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
76+

0 commit comments

Comments
 (0)