Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: ping nodejs/tsc for each security pull request
  • Loading branch information
RafaelGSS committed Mar 4, 2025
commit 7ed5b14cb89e01c7305f4adc735e40be80cc0d3a
3 changes: 3 additions & 0 deletions doc/contributing/security-release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down