(3398) Consider enabling GitHub Private Vulnerability Reporting (PVR)

未关闭
#684 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
45/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
github
领域
security

调研方向

从仓库的 Settings → Code security → Private vulnerability reporting 开始,并阅读链接的 GitHub 文档,了解配置步骤。当 Private Vulnerability Reporting 已启用,使未来的漏洞报告拥有安全渠道时,即表示完成。

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

描述

Hi,

I recently identified a security issue in jsdiff and wanted to report it through GitHub's Private Vulnerability Reporting feature, but it's not currently enabled on this repository.

I've reached out via email with the details (found via your public npm maintainer profile), but for future reports — from me or anyone else — PVR provides a secure, structured channel that:

  • Keeps vulnerability details private until a fix is ready
  • Lets you coordinate disclosure timelines with reporters
  • Automatically generates GitHub Security Advisories (GHSAs) and CVEs when you're ready to publish

You can enable it in Settings → Code security → Private vulnerability reporting. More info: https://docs.github.com/en/code-security/security-advisories/working-with-repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

Given jsdiff's download count (~397M/month) and dependent package count (4,153+), having a clear security reporting channel would benefit the entire ecosystem.

Thank you, truly, for maintaining this library!

Best,
Daniel Cervera

主要语言
JavaScript
星标
9.2k
派生
555
平均合并
1 天 9 小时
30 天内合并 PR
5

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

kpdecker/jsdiff 的其他 Issue

查看 kpdecker/jsdiff 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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