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

Ouverte
#392 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
56/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
github, github-actions, python

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
17
Forks
3
Merge moyen
23 h 48 min
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/Blender-Developer-Tools

Toutes les issues de TMHSDigital/Blender-Developer-Tools

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.