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

Abierto
#392 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
56/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, github-actions, python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
17
Forks
3
Merge medio
23 h 48 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/Blender-Developer-Tools

Todos los issues de TMHSDigital/Blender-Developer-Tools

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.