← 输入框|github.com|刷新
Skip to content

doc: remove stale bug bounty references in SECURITY.md - #66077

Open
ammar3040 wants to merge 1 commit into
nodejs:mainfrom
ammar3040:doc-fix-bug-bounty-references
Open

ammar3040 wants to merge 1 commit into
nodejs:mainfrom
ammar3040:doc-fix-bug-bounty-references

Conversation

@ammar3040

Copy link
Copy Markdown

What this fixes

PR #62590 updated the "Node.js bug bounty program" section to reflect that the bug bounty program was discontinued (see https://nodejs.org/en/blog/announcements/discontinuing-security-bug-bounties), but left several other "bug bounty" references unchanged elsewhere in the same file, creating an internal inconsistency.

This PR removes/rewords the remaining stale references:

  • "Forfeiture of any potential bug bounty." (redundant with "Rejection of the vulnerability report" above it)
  • "Temporary or permanent ban from the bug bounty program."
  • "eligible for a bug bounty" → "considered a valid vulnerability"
  • Two "Bug bounty rewards are not available for..." lines, since there are no bug bounty rewards at all anymore

No behavioral or policy change — purely a documentation consistency fix.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to Node.js documentation. label Sep 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

@ammar3040
ammar3040 force-pushed the doc-fix-bug-bounty-references branch from 8628b10 to f5e7042 Compare September 17, 2026 06:09
@ammar3040

Copy link
Copy Markdown
Author

Thanks for the review process info — happy to make any adjustments if needed!

@mcollina

Copy link
Copy Markdown
Member

I think we can keep those there for now... ;).

@ammar3040
ammar3040 force-pushed the doc-fix-bug-bounty-references branch 2 times, most recently from d80a165 to abae90a Compare November 4, 2026 23:26
@ammar3040
ammar3040 force-pushed the doc-fix-bug-bounty-references branch 3 times, most recently from a178de6 to 7ee263a Compare November 5, 2026 05:45
@MikeMcC399

Copy link
Copy Markdown
Contributor

@ammar3040

I would suggest to close this PR, since it was effectively rejected by #66077 (comment)

@MikeMcC399

Copy link
Copy Markdown
Contributor

GitHub has detected one or more conflicts in this PR. If you would like to keep this PR active, even though the comment suggests that it will not be accepted, please rebase the branch in this PR according to the Pull requests documentation.

Additionally, you would need to fix the commit message.

See Commit message guidelines according to the Pull requests documentation.

Your commit must contain the Signed-off-by line with your name and email address as an acknowledgement that you agree to the Developer Certificate of Origin.

@ammar3040
ammar3040 force-pushed the doc-fix-bug-bounty-references branch from 7ee263a to f7ca7c4 Compare November 5, 2026 09:21
@MikeMcC399

Copy link
Copy Markdown
Contributor

The last push does not fix the outstanding issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants