-
Notifications
You must be signed in to change notification settings - Fork 121
Insights: nodejs/security-wg
Overview
-
- 0 Merged pull requests
- 1 Open pull request
- 3 Closed issues
- 2 New issues
There hasn’t been any commit activity on nodejs/security-wg in the last week.
Want to help out?
1 Pull request opened by 1 person
-
OpenSSF Scorecard Report Updated
#1341 opened
Jul 4, 2024
3 Issues closed by 4 people
-
spam
#1342 closed
Jul 4, 2024 -
Node.js Security team Meeting 2024-07-04
#1339 closed
Jul 4, 2024 -
Does .wasm module under --experimental-pemission protect?
#1168 closed
Jul 3, 2024
2 Issues opened by 2 people
-
Security Mailing List
#1343 opened
Jul 7, 2024 -
OpenSSF Scorecard Report Updated!
#1340 opened
Jul 4, 2024
4 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Requirement (Gold level): The project MUST have FLOSS automated test suite(s) that provide at least 80% branch and 90% statement coverage
#1188 commented on
Jul 4, 2024 • 1 new comment -
Requirement (Gold level): Secured delivery against man-in-the-middle (MITM) attacks
#1190 commented on
Jul 6, 2024 • 1 new comment -
Requirement (Gold level): The project MUST include a license and copyright statement in each source file
#1187 commented on
Jul 6, 2024 • 1 new comment -
Requirement (Gold level): Use basic good cryptographic practices
#1189 commented on
Jul 7, 2024 • 1 new comment