Skip to content

docs(security): publish SECURITY.md to enable GitHub private vulnerability reporting#207

Open
sirdeggen wants to merge 1 commit into
mainfrom
worktree-docs+publish-security-policy
Open

docs(security): publish SECURITY.md to enable GitHub private vulnerability reporting#207
sirdeggen wants to merge 1 commit into
mainfrom
worktree-docs+publish-security-policy

Conversation

@sirdeggen

Copy link
Copy Markdown
Contributor

What

Publishes the existing security / responsible-disclosure policy to .github/SECURITY.md so GitHub recognizes it.

Why

The policy already lived at plans/SECURITY.md, but that path is not one GitHub surfaces. As a result the repo showed no security policy and no "Report a vulnerability" button, so reporters had no visible way to disclose privately — a recent vulnerability was filed as a public issue for exactly this reason.

Copying it to .github/SECURITY.md:

  • Enables the "Report a vulnerability" entry point (private advisory intake)
  • Surfaces the policy on the repo's Security tab and community profile

Changes

  • Add .github/SECURITY.md — verbatim copy of plans/SECURITY.md. No policy content changes.

🤖 Generated with Claude Code

… policy

The security/responsible-disclosure policy already existed at plans/SECURITY.md
but was not at a path GitHub recognizes, so the repo showed no security policy
and no "Report a vulnerability" entry point. Reporters had no visible guidance
to report privately (a recent vuln was filed as a public issue as a result).

Copy the existing policy verbatim to .github/SECURITY.md, which enables the
GitHub "Report a vulnerability" button and private advisory intake. No policy
content changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

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.

1 participant