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

Aberta
#392 2 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
56/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github, github-actions, python

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
17
Forks
3
Merge médio
23h 48min
PRs com merge (30d)
3

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/Blender-Developer-Tools

Todas as issues de TMHSDigital/Blender-Developer-Tools

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.