From b10a351dbad7c3c5259fd8963e8fa88c5a3d7653 Mon Sep 17 00:00:00 2001 From: Xianpeng Shen Date: Wed, 11 Nov 2026 10:25:55 +0200 Subject: [PATCH] Link the private vulnerability report form in SECURITY.md Scorecard's Security-Policy check looks for links in the policy; the org policy had none. --- .github/SECURITY.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/SECURITY.md b/.github/SECURITY.md index 2a07d7e..eb2e55a 100644 --- a/.github/SECURITY.md +++ b/.github/SECURITY.md @@ -20,8 +20,11 @@ Please do not open a public issue, pull request or discussion for a security problem. Report it privately on GitHub instead: open the **Security** tab of the -affected repository and click **Report a vulnerability**. Include the package -and version, the steps to reproduce it, and what an attacker could do with it. +affected repository and click **Report a vulnerability**, for example + for +`mkdocs-ng`. Include the package and version, the steps to reproduce it, and +what an attacker could do with it. GitHub explains how private reporting works +in [Privately reporting a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). ## What to expect