security: private vulnerability reporting is disabled, so every advertised private channel (SECURITY.md, CoC, issue templates) is a dead end
還沒有人認領這個 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 內容生成。
描述
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-reportingreturns{"enabled":false}.- The only advertised channel, in four places:
SECURITY.md:7.github/ISSUE_TEMPLATE/config.yml:4.github/ISSUE_TEMPLATE/bug.yml:8CODE_OF_CONDUCT.md:58-60(the CoC enforcement contact)
config.ymlsetsblank_issues_enabled: false, and there is no email fallback anywhere.- A related inaccuracy:
SECURITY.md:~38-40says "Consumers pin by tag or trackmain". Claude Code users actually install from the force-pushed orphanplugin-distbranch, 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
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
TMHSDigital/Blender-Developer-Tools 的其他 Issue
-
bug ci priority: high
難度 2/5 1-3 小時 新手友好度 55/100
-
content-integrity priority: low showcase stale
難度 5/5 一週以上 新手友好度 45/100
TMHSDigital/Blender-Developer-Tools#499 · 1 則留言 ·
-
feature marketing priority: high stale testing
難度 5/5 一週以上 新手友好度 25/100
TMHSDigital/Blender-Developer-Tools#373 · 1 則留言 ·
-
distribution documentation priority: high stale
難度 4/5 1-2 天 新手友好度 62/100
TMHSDigital/Blender-Developer-Tools#348 · 1 則留言 ·
查看 TMHSDigital/Blender-Developer-Tools 的全部 Issue
相似的 Issue
-
hive size:simple
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未關閉
難度 2/5 1-3 小時 新手友好度 68/100
-
難度 2/5 1-3 小時 新手友好度 70/100
painted-porch/marcus#977 ·
維護者通常 1 天內回覆
-
llm translation
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
維護者通常 1 天內回覆