Skip to content

Commit dcd03ee

Browse files
authored
doc: add 2025-03-13 meeting notes (#1452)
1 parent 75c2400 commit dcd03ee

File tree

1 file changed

+73
-0
lines changed

1 file changed

+73
-0
lines changed

meetings/2025-03-13.md

+73
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Node.js Security team Meeting 2025-03-13
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=xzBqJSatnEs&ab_channel=node.js
6+
* **GitHub Issue**: https://github.com/nodejs/security-wg/issues/1444
7+
8+
## Present
9+
10+
* Michael Dawson (@mhdawson)
11+
* Nguyen Duc Thien (@iuuukhueeee)
12+
* Ulises Gascón (@UlisesGascon)
13+
* Marco Ippolito (@marco ippolito)
14+
* Rafael Gonzaga (@RafaelGSS)
15+
16+
## Agenda
17+
18+
## Announcements
19+
20+
*Extracted from **security-wg-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
21+
22+
- [X] Vulnerability Review - https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues
23+
- Nothing new
24+
25+
- [X] OpenSSF Scorecard Monitor Review
26+
- Report: https://github.com/nodejs/security-wg/pull/1450
27+
- Ulises will work on a PR to patch the scoring in node-gyp
28+
- Michael - recently created token as per - so maybe related, maybe we can add to docs to prevent in the future - https://github.com/nodejs/admin/blob/main/request-an-access-token.md
29+
- Clean up the tracking list: https://github.com/nodejs/security-wg/pull/1451
30+
31+
### nodejs/node
32+
33+
* src: add WDAC integration (Windows) [#54364](https://github.com/nodejs/node/pull/54364)
34+
* PR is getting close to be ready
35+
* Rafael, is being Windows only going to be an issue
36+
* Michael, since ability for client code to run across platforms is not affected, less of a concern
37+
in terms of Windows only implementation.
38+
39+
### nodejs/security-wg
40+
41+
* Remove nodejs-sec usage in favor of Node.js org RSS Feed [#1446](https://github.com/nodejs/security-wg/issues/1446)
42+
* Discussion, seems like we need to keep sending messages on nodejs-sec. Need to figure out
43+
how to automate.
44+
45+
* Update on CVEs for EOL Release Lines – MITRE Removal & Next Steps [#1443](https://github.com/nodejs/security-wg/issues/1443)
46+
* Have published blog post to explain next step
47+
* Marco has PR to update database maintained in security-wg
48+
* Marco talking to hacker 1 about how we update CVEs to include EOL versions . Going to
49+
provide csv with the updates needed. Will match what we land in the PR mentioned.
50+
51+
* OpenJS Security Compliance Checker [#1440](https://github.com/nodejs/security-wg/issues/1440)
52+
* Created issue to analyse how the Node.js project is doing against
53+
* Michael, Ulises has been working on tooling, should be try to use that?
54+
* Ulises, have been working on openpathfinder
55+
https://openpathfinder.com/docs/checklists/OpenJS-SCGv1.0-active
56+
* Sounds like it still work in progress so going through the docs manually still makes sense
57+
58+
* Node.js maintainers: Threat Model [#1333](https://github.com/nodejs/security-wg/issues/1333)
59+
60+
* Audit build process for dependencies [#1037](https://github.com/nodejs/security-wg/issues/1037)
61+
* Michael: Next step on my list is still to update amaro to ensure we can build from what is in
62+
deps
63+
64+
* Automate security release process [#860](https://github.com/nodejs/security-wg/issues/860)
65+
66+
## Q&A, Other
67+
68+
## Upcoming Meetings
69+
70+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
71+
72+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.
73+

0 commit comments

Comments
 (0)