Security fixes go to the newest 1.3.x release only. Forks and older releases are not supported.
Do not report security vulnerabilities through public GitHub issues.
Use GitHub's private vulnerability reporting instead:
Include as much detail as possible:
- Description of the vulnerability and what it affects
- Steps to reproduce
- Potential impact and attack scenarios
- Any suggested mitigations
What to expect:
- Acknowledgment within 48 hours
- Status update within 7 days
- Resolution within 90 days for confirmed vulnerabilities
CCGS is a local development tool — it installs shell hooks and coordinates AI agents that run directly on your machine. Security issues are primarily about contributed code that executes in users' environments without their awareness.
- Hooks (
.claude/hooks/*.sh) that execute malicious or undisclosed shell commands on user machines - Skills or agents that exfiltrate environment variables, API keys, or secrets
- Prompt injection via skill or agent definitions that causes Claude to bypass safety measures or take unauthorized destructive actions
- Contributions that silently alter behavior in ways users cannot audit
- Skills that make undisclosed outbound network requests
- Agent definitions that escalate permissions or bypass user confirmation prompts
- Hook patterns that behave differently across platforms to conceal behavior
- Skills that write outside their documented scope without an explicit user approval step
- The behavior of Claude or the Claude Code CLI itself (report to Anthropic)
- Bugs in the user's Claude Code installation or editor extension
- Theoretical vulnerabilities with no realistic attack path
- Issues requiring physical access to the user's machine
When contributing hooks, skills, or agents:
- Hooks must be POSIX-compatible — use
grep -E, notgrep -P; avoid platform-specific syntax that behaves differently across operating systems - No silent network calls from hooks or skills unless explicitly documented and opt-in by the user
- No reading secrets or environment variables beyond what is minimally required and clearly documented in the skill's header
- Skills must not write outside their documented scope without an explicit user confirmation step
We follow a 90-day coordinated disclosure timeline:
- You submit the vulnerability privately
- We acknowledge within 48 hours
- We confirm and assess severity within 7 days
- We develop and test a fix
- We notify you before any public disclosure
- Public disclosure happens after the fix ships, or at 90 days — whichever comes first
We credit reporters in release notes unless you prefer to remain anonymous.