| Version | Supported |
|---|---|
| 0.3.x | ✅ Current |
| 0.2.x | ✅ Security fixes only |
| 0.1.x | ❌ End of life |
If you discover a security vulnerability in this project — whether in the protocol itself, the templates, the skill files, or the repository infrastructure — please report it responsibly.
- Do NOT open a public issue. Security reports must be private.
- Email: Send a detailed report to security@affordance.design
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if you have one)
| Timeline | Action |
|---|---|
| 24 hours | Acknowledgment of your report |
| 72 hours | Initial assessment and severity classification |
| 7 days | Fix developed and tested (for critical issues) |
| 14 days | Fix released with credit (unless you prefer anonymity) |
This security policy covers:
- Protocol content — guidance that could lead to insecure practices if followed
- Template vulnerabilities — templates that could expose secrets or create attack vectors
- Skill file injection — skill files that could be manipulated to produce unsafe AI behavior
- Repository infrastructure — CI/CD, GitHub Actions, dependency supply chain
- Vulnerabilities in projects that use PWP (report those to the project maintainers)
- Theoretical attacks that require physical access to a developer's machine
- Social engineering attacks against contributors
The protocol itself enforces security standards:
protocol/00-mindset.md— No client secrets, sanitize input, enforce auth on backendskills/security-audit.skill.md— Comprehensive security audit checklist for AI agentsprotocol/09-dependency-management.md— Dependency evaluation and audit cadencetemplates/deployment-checklist.md— Pre-deploy security verification
We gratefully acknowledge security researchers who responsibly disclose vulnerabilities. With your permission, we will credit you in the CHANGELOG and in a SECURITY-ACKNOWLEDGMENTS.md file.
Thank you for helping keep PWP and its users secure.