Skip to content

docs: restore canonical security policy over bot-added SECURITY.md#1533

Open
WilliamBergamin wants to merge 1 commit into
mainfrom
restore-security-policy
Open

docs: restore canonical security policy over bot-added SECURITY.md#1533
WilliamBergamin wants to merge 1 commit into
mainfrom
restore-security-policy

Conversation

@WilliamBergamin

@WilliamBergamin WilliamBergamin commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

What & why

The Salesforce OSPO Service Bot committed a top-level SECURITY.md to this repo. But in fact we want to direct reporter to the Slack bug bounty program on HackerOne (https://hackerone.com/slack).

The fix

This PR moves .github/SECURITY.md to the repository root, which:

  • replaces the bot-added SECURITY.md with the maintained policy, and
  • removes the now-redundant .github/SECURITY.md.

Move .github/SECURITY.md to the repository root so it replaces the
top-level SECURITY.md added by the Salesforce OSPO Service Bot on
2026-06-02. GitHub resolves security policy with root taking precedence
over .github/, so the bot file had silently shadowed the maintained
policy. This restores the correct reporting channel.

Co-Authored-By: Claude <svc-devxp-claude@slack-corp.com>
@codecov

codecov Bot commented Jun 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.34%. Comparing base (03d4add) to head (3873490).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1533   +/-   ##
=======================================
  Coverage   91.34%   91.34%           
=======================================
  Files         228      228           
  Lines        7279     7279           
=======================================
  Hits         6649     6649           
  Misses        630      630           

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

@WilliamBergamin WilliamBergamin self-assigned this Jun 19, 2026
@WilliamBergamin WilliamBergamin added docs Improvements or additions to documentation security labels Jun 19, 2026
@WilliamBergamin WilliamBergamin marked this pull request as ready for review June 19, 2026 19:00
@WilliamBergamin WilliamBergamin requested a review from a team as a code owner June 19, 2026 19:00

@zimeg zimeg left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@WilliamBergamin Kind thanks for keeping these visible and current 🔐

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

Labels

docs Improvements or additions to documentation security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants