◐ Shell
clean mode source ↗

doc: ping nodejs/tsc for each security pull request · nodejs/node@e178acf

Original file line numberDiff line numberDiff line change

@@ -56,6 +56,9 @@ The current security stewards are documented in the main Node.js

5656

* Use the "summary" feature in HackerOne. Example [2038134](https://hackerone.com/reports/2038134)

5757

* `git node security --add-report=report_id`

5858

* `git node security --remove-report=report_id`

59+

* Ensure to ping the Node.js TSC team for review of the PRs prior to the release date.

60+

* Adding individuals with expertise in the report topic is also a viable option if

61+

communicated properly with nodejs/security and TSC.

5962
6063

* [ ] 3\. **Assigning Severity and Writing Team Summary:**

6164

* [ ] Assign a severity and write a team summary on HackerOne for the reports