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

Offen
#392 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
56/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github, github-actions, python

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
17
Forks
3
Ø Merge
23 Std. 48 Min.
Gemergte PRs (30 T.)
3

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/Blender-Developer-Tools

Alle Issues in TMHSDigital/Blender-Developer-Tools

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.