Senpy is in active development (currently 0.7.x). Security fixes are applied to the latest released minor version only.

Please DO NOT open public GitHub issues for security vulnerabilities.

Instead, report privately via one of these channels:

1. Go to https://github.com/Xilleet/senpy/security/advisories/new
2. Fill in the form:
   • Title: short summary (e.g. "Path traversal in unrpyc decompiler")
   • Description: what the vulnerability is, what component is affected
   • Steps to reproduce: minimal PoC (code snippet, .rpy file, command line)
   • Impact: what an attacker can achieve
   • Severity: your assessment (low / medium / high / critical)
3. Submit. The maintainer will be notified privately.

The maintainer is one person; please be patient. You will be credited in the advisory unless you request otherwise.

• The senpy/ Python package (CLI, LSP server, analyzer, formatter, plugins system).
• The senpy-vscode/ VS Code extension.
• The vendored senpy/vendor/unrpyc/ — but please also report upstream to https://github.com/CensoredUsername/unrpyc if the issue exists there.
• The bundled senpy.exe PyInstaller binary distributed via GitHub Releases.

• Vulnerabilities in Ren'Py itself — report to https://github.com/renpy/renpy.
• Vulnerabilities in third-party plugins installed via pip — report to the plugin author. Senpy's trust-on-first-use model (see examples/my_senpy_plugin/MY_SENPY_PLUGIN_README.md) is the primary mitigation; plugins run with full Senpy process privileges.
• Social engineering, DoS via huge input files, or issues requiring physical access to the user's machine.

Senpy has several built-in defenses; please familiarize yourself before reporting:

• SafeUnpickler with module blocklist (senpy/vendor/unrpyc/): .rpyc files are pickle-based; Senpy's unpickler rejects dangerous modules (os, sys, subprocess, socket, shutil, pathlib, builtins, ctypes, multiprocessing, pickle, marshal) even if added to the safe-list by accident. See tests/test_cache_security.py, tests/test_lsp_uri_security.py, tests/test_unrpyc_security.py, tests/test_vendored_unrpyc.py.
• UNRPYC_PINNED_SHA256 (senpy/cli/unrpyc.py): downloaded unrpyc zip is verified against a pinned SHA256 hash. Prevents supply-chain attacks on the unrpyc download endpoint.
• Plugin trust store (~/.senpy/trusted_plugins.json): trust-on-first-use model. CI environments (non-TTY) auto-skip untrusted plugins (fail-safe).
• HTML report CSP (senpy/formats/html_report.py): Content-Security-Policy: default-src 'none' + Mermaid securityLevel: 'strict' — prevents XSS in generated reports.
• LSP URI scheme validation + workspace containment (senpy/lsp/server.py, 0.6.2): _uri_to_path rejects non-file: URIs and (optionally) paths outside workspace root.
• execFile instead of exec (senpy-vscode/src/extension.ts, 0.6.2): VS Code extension uses array-args child_process.execFile, preventing shell injection via workspace paths.
• os.walk(followlinks=False) (0.6.2): explicit symlink-loop protection in all filesystem walks.

If you write a Senpy plugin, follow these guidelines:

1. Never exec() or eval() user input. Ren'Py source files are untrusted input.
2. No subprocess.run() from a plugin. If you need external tools, require them as separate dependencies and document the security model.
3. No network calls. Plugins should be deterministic and offline.
4. No file writes outside the project directory. Use Senpy's DiagnosticSink API, not direct file I/O.
5. Pin your dependencies. A plugin is only as secure as its deps.

• We follow Coordinated Disclosure. The reporter and maintainer agree on a disclosure timeline before public release.
• CVE numbers can be requested via GitHub Security Advisories.
• Credit is given in the release notes and the advisory, unless the reporter requests anonymity.

• Security advisories: https://github.com/Xilleet/senpy/security/advisories
• General questions (non-sensitive): https://github.com/Xilleet/senpy/discussions