Skip to content

Commit 38174bd

Browse files
committed
docs: remove Node.js Ecosystem HackerOne program
Remove documentation related to the Node.js Ecosystem HackerOne program. closes: nodejs#788 see: nodejs/node#42144 Signed-off-by: Rifa Achrinza <[email protected]>
1 parent 7b53122 commit 38174bd

5 files changed

+0
-296
lines changed

README.md

-14
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,13 @@
1010
Table of Contents
1111

1212
- Vulnerability Management
13-
* [Responsible Disclosure Policy](./processes/responsible_disclosure_template.md)
14-
* [Third-Party Ecosystem Triage Process](./processes/third_party_vuln_process.md)
15-
* [Third-Party HackerOne Submission form](./processes/third_party_vuln_submit_form_hacker1.md)
1613
* [Vulnerability Database](./processes/vuln_db.md)
1714
* [Recognition for Security Researchers](./processes/recognition.md)
1815
- Processes for Security WG Members
1916
* [Security Team Membership Policy](./processes/security_team_membership_policy.md)
2017
* [On-boarding Team Members](./processes/wg_onboarding.md)
2118
* [Off-boarding Team Members](./processes/wg_offboarding.md)
2219
- [Node.js Bug Bounty Program](#nodejs-bug-bounty-program)
23-
- [Participate in Responsible Security Disclosure](#participate-in-responsible-security-disclosure)
2420
- [Charter](#charter)
2521
- [Code of Conduct](#code-of-conduct)
2622
- [Moderation Policy](#moderation-policy)
@@ -59,16 +55,6 @@ The Node.js project engages in an official bug bounty program for security resea
5955

6056
The program is managed through the HackerOne platform at [https://hackerone.com/nodejs](https://hackerone.com/nodejs) with further details.
6157

62-
## Participate in Responsible Security Disclosure
63-
64-
As a module author you can provide your users with security guidelines regarding any exposures and vulnerabilities in your project, based on a responsible disclosure policy [document](https://github.com/nodejs/security-wg/blob/e2c03e62d73635a766156c6ea4f9aefb35c04603/processes/responsible_disclosure_template.md) we've already put in place.
65-
66-
You can show your users you take security matters seriously and drive higher confidence by following any of the below suggested actions:
67-
68-
1. Adding a `SECURITY.md` file in your repository that you can copy&paste from [us](https://github.com/nodejs/security-wg/blob/e2c03e62d73635a766156c6ea4f9aefb35c04603/processes/responsible_disclosure_template.md). Just like having a contribution of code of conduct guidelines, a security guideline will help user or bug hunters with the process of reporting a vulnerability or security concern they would like to share.
69-
70-
2. Adding our Responsible Security Dislosure badge to your project's README which links to the `SECURITY.md` document.
71-
7258
## Current Project Team Members
7359

7460
* [ChALkeR](https://github.com/ChALkeR) - **Сковорода Никита Андреевич**

processes/responsible_disclosure_template.md

-21
This file was deleted.

processes/third_party_triage_guidelines.md

-51
This file was deleted.

processes/third_party_vuln_process.md

-156
This file was deleted.

processes/third_party_vuln_submit_form_hacker1.md

-54
This file was deleted.

0 commit comments

Comments
 (0)