| Version | Supported |
|---|---|
| 1.x | Yes |
Do not open a public GitHub issue for security vulnerabilities.
Report security issues by emailing: biuro@softspark.eu
Include in your report:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if you have one)
You will receive a response within 48 hours. We will:
- Confirm receipt of your report
- Investigate and validate the issue
- Release a fix and disclose the vulnerability (with credit to you unless you prefer anonymity)
The toolkit enforces a 5-article safety constitution via PreToolUse hooks. Article 1 (Safety First) blocks:
rm -rfand mass deletion commandsDROP TABLEand destructive database operations- Any command that could cause irreversible data loss without explicit confirmation
Hooks execute in the user's local environment. They do NOT:
- Phone home or send telemetry
- Execute network requests
- Store or transmit any code or data externally
All bundled scripts (scripts/*.py, scripts/*.sh) use stdlib only — no external dependencies, no network calls. Review them directly: they are short and readable.
install.sh creates symlinks only. It does NOT:
- Execute arbitrary code from the network
- Modify system files outside of the target project's
.claude/directory - Request elevated permissions
For confirmed vulnerabilities, we use GitHub Security Advisories to:
- Coordinate private disclosure and fix development
- Request a CVE identifier when applicable
- Publish the advisory alongside the patched release
If you believe a vulnerability warrants a CVE, mention it in your report email — we will initiate the process.
In scope:
- Command injection in hook scripts
- Privilege escalation via agent definitions
- Unsafe default permissions in settings templates
- Constitution bypass vectors
Out of scope:
- Issues in Claude Code itself (report to Anthropic)
- Social engineering attacks
- Denial of service