security: private vulnerability reporting is disabled, so every advertised private channel (SECURITY.md, CoC, issue templates) is a dead end

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
56/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, github-actions, python

调研方向

Start by checking SECURITY.md, CODE_OF_CONDUCT.md, and the three cited files under .github/ISSUE_TEMPLATE; verify the reporting endpoint with the gh api command in the issue. Enable private reporting, provide a separate monitored CoC contact, and correct the plugin pinning guidance. Done means the endpoint reports enabled, non-collaborators can open the advisory form from all four links, and the CoC has its own contact.

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

描述

community documentation priority: high security stale

Why it matters

SECURITY.md, the Code of Conduct and the issue templates all send reporters to …/security/advisories/new and forbid public issues. With private reporting off, people outside the repo can't open a draft advisory there. A vulnerability reporter, or someone reporting harassment, has no private channel at all.

Evidence

  • gh api repos/TMHSDigital/Blender-Developer-Tools/private-vulnerability-reporting returns {"enabled":false}.
  • The only advertised channel, in four places:
    • SECURITY.md:7
    • .github/ISSUE_TEMPLATE/config.yml:4
    • .github/ISSUE_TEMPLATE/bug.yml:8
    • CODE_OF_CONDUCT.md:58-60 (the CoC enforcement contact)
  • config.yml sets blank_issues_enabled: false, and there is no email fallback anywhere.
  • A related inaccuracy: SECURITY.md:~38-40 says "Consumers pin by tag or track main". Claude Code users actually install from the force-pushed orphan plugin-dist branch, which has no tags.

Suggested approach

  • Enable private vulnerability reporting (Settings → Code security, or gh api -X PUT repos/TMHSDigital/Blender-Developer-Tools/private-vulnerability-reporting).
  • Also give CODE_OF_CONDUCT a non-security contact path, such as a monitored address. Security advisories are the wrong channel for conduct reports anyway.
  • Correct the pinning sentence for plugin users.
  • Optionally add a scheduled check that warns if reporting becomes disabled.

Done when

The endpoint returns enabled:true, a non-collaborator can open the advisory form from all four links, and the CoC has its own contact.

主要语言
Python
星标
17
派生
3
平均合并
23 小时 48 分钟
30 天内合并 PR
3

环境准备

从这里开始

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

TMHSDigital/Blender-Developer-Tools 的其他 Issue

查看 TMHSDigital/Blender-Developer-Tools 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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