Protostar is in active pre-1.0 development. Security updates are applied only to the main branch and the latest release tag. Previous releases do not receive backported security patches.

Please do not report security vulnerabilities in public GitHub issues, discussions, or pull requests.

Report all vulnerabilities privately through GitHub's Private Vulnerability Reporting.

When filing a report, please include:

• A clear description of the vulnerability and its potential impact.
• Step-by-step instructions or a minimal proof-of-concept (PoC) demonstrating how to reproduce the issue.
• Any relevant details regarding the environment, operating system, or flags used.

Reports will be acknowledged promptly and coordinated privately through GitHub Security Advisories before public disclosure.

Protostar scaffolds, manages, and executes project lifecycles, and executes external shell commands and filesystem transactions on user projects.

• Path Traversal / Archive Slip: Bypassing workspace boundaries (enforce_path_jail) or extracting archives that write outside the target workspace.
• Remote Trust Violations: Execution of unauthorized shell commands (system_tasks, post_install_tasks) from untrusted remote --from templates without displaying or requiring user consent.
• Binary Safelist Escapes: Bypassing subprocess execution boundaries (enforce_binary_safelist) during template execution.
• Secret Scanning Bypasses: Flaws or bypasses in credential detection that allow committed secret patterns past the variable safety net without --allow-secret.

• Vulnerabilities in third-party executables that Protostar coordinates (e.g., uv, git, ruff).
• Commands executed after a user has explicitly approved remote trust prompts or configured a template with trusted = true.
• Attack vectors requiring full local administrative access or arbitrary code execution capabilities already present in the user's local shell.