nodejs
diff --git a/Collapse file
‎doc/contributing/security-release-process.md‎
Copy file name to clipboardExpand all lines: doc/contributing/security-release-process.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff b/Collapse file
‎doc/contributing/security-release-process.md‎
Copy file name to clipboardExpand all lines: doc/contributing/security-release-process.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
@@ -56,6 +56,9 @@ The current security stewards are documented in the main Node.js
     * Use the "summary" feature in HackerOne. Example [2038134](https://hackerone.com/reports/2038134)
     * `git node security --add-report=report_id`
     * `git node security --remove-report=report_id`
+  * Ensure to ping the Node.js TSC team for review of the PRs prior to the release date.
+    * Adding individuals with expertise in the report topic is also a viable option if
+      communicated properly with nodejs/security and TSC.
 
 * [ ] 3\. **Assigning Severity and Writing Team Summary:**
   * [ ] Assign a severity and write a team summary on HackerOne for the reports