Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(processes): bug bounty program #532

Merged
merged 12 commits into from
Jun 28, 2019
35 changes: 35 additions & 0 deletions processes/bug_bounty_criteria.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Bug Bounty Criteria

The following document describes the criteria for eligibility of monetary reward for security researchers
lirantal marked this conversation as resolved.
Show resolved Hide resolved
who engage with the Node.js Security Working group through the Node.js Ecosystem
lirantal marked this conversation as resolved.
Show resolved Hide resolved
[bug bounty program](https://hackerone.com/nodejs-ecosystem/), as is currently running on HackerOne.
lirantal marked this conversation as resolved.
Show resolved Hide resolved

## Module Characteristics

1. **Module download count** - x >= 1000 downloads a month which accounts for 7% of npm packages
(courtesy of @ChALkeR here https://github.com/nodejs/security-wg/issues/151#issue-303209104)
2. **Approved Modules** - A list of modules where their maintainers approved to be included in the
lirantal marked this conversation as resolved.
Show resolved Hide resolved
bug bounty program

### Other Module Characteristics (WIP)

Work-in-progress to assess the following characteristics:

* **Module dependents count** - we don't have enough experience to gauge what this means
* **Vulnerability type** - Consider instead to have a criteria based on vulnerability severity rather than
type, so to match anything >= 4.0 which means Medium and higher.
lirantal marked this conversation as resolved.
Show resolved Hide resolved

## Modules list

The following is a list of modules which are eligible in the monetary reward due to their maintainers
explicitly confirming to collaborate with the working group and security researchers to receive and
resolve security reports.

* lodash
* jQuery
* node-red
* hapi (all packages under the GH org)
* Koajs (all packages under the GH org)
* Webpack
* ESLint
* socket.io
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably include links to the github organizations.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree although I'd be ok with the links being added in a follow on PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added links to the github repos