Skip to content

Security: TMHSDigital/Blender-Developer-Tools

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security issue in this repository (e.g., a snippet that demonstrates an unsafe pattern, a template that ships an over-broad permission set, or a skill that recommends an insecure practice), please report it responsibly.

Report: Open a private security advisory on GitHub.

Please include:

  • Description of the vulnerability
  • Steps to reproduce
  • Which skill, rule, snippet, or template is affected
  • Any suggested fix

Scope

This repository ships Markdown skill files, MDC rule files, Python snippets, and three starter templates (a Blender extension add-on, a headless batch script, and a GLB-in engine-ready asset pipeline). The primary security concerns are:

  • Snippets or templates demonstrating insecure patterns (executing arbitrary code from .blend files, loading remote scripts without validation, leaking filesystem paths into logs).
  • The extension-addon template declaring over-broad permissions in blender_manifest.toml (e.g. network, files, clipboard, camera) without a documented justification.
  • Skills recommending insecure practices (running eval() on driver expressions from untrusted sources, disabling Blender's auto-execute-script protection in headless workflows, embedding credentials in .blend custom properties).
  • Headless batch scripts that pass user-controlled input to subprocess or os.system without sanitization.

Issues with the Blender Python API itself (bpy, bmesh, bpy_extras) belong upstream at https://projects.blender.org and are out of scope here.

Supported Versions

This is a content repository — Markdown, MDC, Python, and TOML files consumed directly by an AI agent. There is no installed runtime, no server, and no long-lived deployment to patch, so there are no maintenance branches and no backports.

Version Supported
Latest release (see VERSION) Yes
Any earlier release No

A confirmed fix lands on main and ships in the next release cut by release.yml. Consumers pin by tag or track main; the remedy in both cases is to move to the current release. Nothing older is patched in place.

Response Timeline

We aim to acknowledge reports within 48 hours and provide a fix or mitigation within 7 days for confirmed issues.

There aren't any published security advisories