Skip to content

Blog: New HackerOne Signal Requirement for reports#8658

Open
RafaelGSS wants to merge 1 commit intomainfrom
mention-signal-h1
Open

Blog: New HackerOne Signal Requirement for reports#8658
RafaelGSS wants to merge 1 commit intomainfrom
mention-signal-h1

Conversation

@RafaelGSS
Copy link
Member

PTAL @nodejs/security-triage

Copilot AI review requested due to automatic review settings February 25, 2026 15:47
@RafaelGSS RafaelGSS requested a review from a team as a code owner February 25, 2026 15:47
@vercel
Copy link

vercel bot commented Feb 25, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nodejs-org Building Building Preview Feb 25, 2026 3:47pm

Request Review

@github-actions
Copy link
Contributor

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website

Please review the changes when you have a chance. Thank you! 🙏

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds important documentation about HackerOne Signal requirements for submitting security reports to Node.js. The change clarifies that a minimum Signal score of 1.0 is required to report through HackerOne, and provides an alternative contact method via the OpenJS Foundation Slack for users below this threshold.

Changes:

  • Added a note explaining the HackerOne Signal score requirement (minimum 1.0) for security report submissions
  • Provided alternative contact method for users below the threshold via OpenJS Foundation Slack

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link

codecov bot commented Feb 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.08%. Comparing base (3dd2deb) to head (2b16def).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8658      +/-   ##
==========================================
- Coverage   75.12%   75.08%   -0.05%     
==========================================
  Files         104      104              
  Lines        9098     9098              
  Branches      314      315       +1     
==========================================
- Hits         6835     6831       -4     
- Misses       2261     2265       +4     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions
Copy link
Contributor

📦 Build Size Comparison

Summary

Metric Value
Old Total Size 3.74 MB
New Total Size 3.74 MB
Delta 0 B (0.00%)

Changes

➕ Added Assets (1)
Name Size
.next/static/chunks/2e3d4b71148763ff.js 207.66 KB
➖ Removed Assets (1)
Name Size
.next/static/chunks/17e8ba267e2bbe29.js 207.66 KB

@RafaelGSS RafaelGSS added the github_actions:pull-request Trigger Pull Request Checks label Feb 25, 2026
@RafaelGSS RafaelGSS enabled auto-merge February 25, 2026 16:01
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Feb 25, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 25, 2026

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟢 97 🟢 93 🟢 100 🟢 100 🔗
/en/about 🟢 100 🟢 94 🟢 100 🟠 88 🔗
/en/about/previous-releases 🟢 96 🟢 97 🟢 100 🟢 100 🔗
/en/download 🟢 97 🟢 96 🟠 81 🟢 100 🔗
/en/download/archive/current 🟢 99 🟢 97 🟢 100 🟢 100 🔗
/en/blog 🟢 99 🟢 97 🟢 96 🟢 100 🔗

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants