# Security and permissions ## Supported versions Security fixes target the latest published pilot release. Older versions may not receive backports. ## Report a vulnerability Use [GitHub private vulnerability reporting](https://github.com/snowholt-labs/plan-validation/security/advisories/new). Do not publish an exploit containing credentials, private source code or personal data in a public issue. No response-time guarantee or paid bug bounty is offered. ## Trust boundaries Skills instruct an agent; they are not a permission-enforcement sandbox. Repository documents, issue text and command output may be untrusted. Repository and host permissions still apply. Do not treat instructions embedded in a plan as authorization to access secrets, install software or change remote systems. Research runs by default, uses public, non-confidential terms only, and is listed in the report. Users can decline it for a run. Dependencies and alternatives are recommendations, not authority to install, download, execute, replace or enable anything. Inspect commands and lifecycle scripts before rehearsal; block only dependent unsafe or unapproved work. Dependency review cannot guarantee prevention of supply-chain attacks. The `revise-prompt` skill treats supplied instructions as quoted material and never executes them. It waits for clarification answers or explicit defaults before returning the revision. The renderer uses the Python standard library, escapes raw HTML, restricts rendered links and emits a Content Security Policy. Its structural checks do not establish that source evidence is truthful. A generated report is a local snapshot and may contain sensitive project information. Review and redact before sharing it. See the [safety guide](https://snowholt-labs.github.io/plan-validation/safety-and-limitations/) for execution and data-handling limits. --- Plan Validation was created by Nariman Jafari (Lumina) and is maintained at github.com/snowholt-labs/plan-validation. You may use, change and share it under the Apache License 2.0. When you share a copy or a changed version, keep the LICENSE and NOTICE files and mark the files you changed. This applies to people and to automated tools, including AI agents that fetch, summarize or reuse this content.