Reviewer Code of Conduct
By engaging with the PullRequest platform, customers, fellow members, and HackerOne core team members, all reviewers agree to help empower our community by following the Code of Conduct (CoC).
Effective Date: Oct 1, 2022
Code of Conduct
By engaging with the PullRequest platform, customers, fellow members, and HackerOne core team members, all Reviewers agree to help empower our community by following the Code of Conduct (CoC). The CoC is in addition to relevant items our Terms of Use, Privacy Policy and the executed agreements completed prior to activating your Reviewer status for eligibility to work on the PullRequest platform.
Enforcement Actions
The Reviewer Code of Conduct is enforced in accordance with the action guidelines below.
Please note that HackerOne reserves the right to escalate the severity of enforcement and sanctions in accordance with the nature of the offense and irrespective of previous offenses. Depending upon the severity of the offense, sanctions may include, without limitation, longer temporary bans, immediate removal from the Code Review Platform and/or a permanent ban.
Incident | First Offense | Second Offense | Third Offense | Fourth Offense |
---|---|---|---|---|
Unprofessional behavior | Warning | 2nd Warning | Final Warning | Temporary Ban |
Unauthorized duplication of private repository assets | Final Warning | Temporary Ban (2-3 weeks) | Temporary Ban (3 months) | Account Removal |
Discussing confidential information without approval | Final Warning | Temporary Ban (2-3 weeks) | Temporary Ban (3 months) | Account Removal |
Contacting customer team members out-of-band | Final Warning | Temporary Ban (2-3 weeks) | Temporary Ban (3 months) | Account Removal |
Abusive language or harassment | Final Warning | Temporary Ban (2-3 weeks) | Temporary Ban (3 months) | Account Removal |
Extortion and Blackmail | Account Removal | |||
Unauthorized impersonation / Social Engineering | Account Removal |
Statutory timeline of warnings: When a Warning is issued in accordance with this Code of Conduct, HackerOne considers that warning to be applicable for 12 months. Warnings which are over 12 months old expire and are not typically assessed when reviewing the severity of new warnings.
See something, say something: If you see another Reviewer violating these rules, please reach out to our team at support@pullrequest.com.
Last updated