-
Notifications
You must be signed in to change notification settings - Fork 18
Time for a bounty program? #345
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
Comments
+1, although it would mean that we would no longer use GitHub in the future to report security issues (see expressjs/security-wg#30), right? |
Not really, We include it as a valid way to report vulnerabilities in https://github.com/expressjs/.github/blob/master/SECURITY.md#reporting-a-bug. |
@UlisesGascon I think might be worth reaching out to [email protected] to get this sponsored by the Internet Bug Bounty Program |
I see that several projects from the foundation are included here, I think it's great to request inclusion. (https://hackerone.com/ibb/policy_scopes) |
@marco-ippolito @RafaelGSS can you tell us about your experience in the program with Node.js? How was your experience so far (day to day, reports quality, tricks...)? 🙏 |
I don't see it mentioned here, but it looks like the STF also has a program for bug bounties which we should assess. I don't have a strong opinion in general here, but just wanted to drop this note since it was only mentioned so far in an email with @UlisesGascon and I on it. |
As discussed on last week's working session, this discussion is moving to the @expressjs/security-wg. So removing the agenda label. |
In the past we had mention the option to run a bounty program (ref) to engage with more security researches. Also other Open Source project within the foundation engaged with this programs too.
I was thinking that Hacker One (H1) is a great option for us as they have a Community Edition that fits well with our approach.
Even if we don't have enough economical resources to reward for bounties this program will provide reputation to the researches.
I already sent them an email to see if they want to accept us in their program (exploring not confirming).
Note that this was part of the objectives that we set for the milestone 3 in STF:
It also worth mention that we are actively working on defining better the process on how to handle security reports (expressjs/security-wg#56) and manage expectations (expressjs/.github#15)
WDYT @expressjs/express-tc @expressjs/security-wg @expressjs/security-triage?
The text was updated successfully, but these errors were encountered: