From 956944e0cdfe64f5e7c41e826fa3ad7c2e472604 Mon Sep 17 00:00:00 2001 From: Willie Date: Sun, 1 Nov 2026 03:01:36 +0800 Subject: [PATCH] docs: add a security policy for private vulnerability reports (#682) Vulnerabilities could only be reported in public issues, which exposes exploit details before a fix. Point reporters to GitHub's private advisory form, now enabled for the repository. --- SECURITY.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 000000000..33797a38b --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,9 @@ +# Security + +Report vulnerabilities privately through [GitHub's Report a vulnerability](https://github.com/runkids/skillshare/security/advisories/new). Don't post exploit details in a public issue. + +Include the skillshare version (`skillshare version`), your OS, what you found, steps to reproduce it, and the impact. A small proof of concept helps. Remove tokens, secrets and personal data from logs and configs. + +Only the latest release is supported. + +For how skillshare scans skills before installing them, see the [audit engine](https://skillshare.runkids.cc/docs/understand/audit-engine). For token and network rules of `skillshare mcp serve`, see [Serve skills over MCP](https://skillshare.runkids.cc/docs/reference/commands/mcp#serve-skills-over-mcp).