Add a SECURITY.md and enable private vulnerability reporting

未关闭 适合新手
#552 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
github
领域
security

调研方向

首先检查仓库现有的 README 和 GitHub 安全设置。添加 SECURITY.md,说明如何报告漏洞、受支持的分支(staging 和 prod)以及预期的回复时间;在仓库设置中启用漏洞私密报告。完成标准是该政策可从 GitHub 的 Security 选项卡访问,且私密报告已启用。

由索引模型根据 Issue 内容生成。

描述

Is your feature request related to a problem? Please describe.
The repository has no SECURITY.md and GitHub's private vulnerability reporting is turned off, anyone who finds a security problem has no private way to report it, so they either open a public issue (which exposes it before a fix) or dont report it at all. I have a potential security issue Id like to share privately.

Describe the solution you'd like

  • Enable private vulnerability reporting (Settings -> Code security -? Private vulnerability reporting) so reports go to gitHub security advisories
  • add a SECURITY.md that says how to report which branch is supported (staging/prod), and roughly how soon reporters can expect a reply

Describe alternatives you've considered
A contact email in the README, but a SECURITY.md is what GitHub links from the Security tab and the "new issue" page

Additional context
GitHub's guide: https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository

主要语言
TypeScript
星标
22
派生
66
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

CodeChefVIT/papers-codechef 的其他 Issue

查看 CodeChefVIT/papers-codechef 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。