Thank you for your interest in contributing. This is a curated list — we aim for high signal, not high volume.
Every submission must meet all of the following:
- Relevant — Directly related to Claude Code security, or strongly applicable to secure AI coding agent operations.
- Credible — From an official source, respected security firm, recognized researcher, or established open-source project.
- Practically Useful — A developer, security engineer, or platform owner would benefit from it in their work.
- High Signal — Contains real technical depth, actionable guidance, or novel insight. Not marketing fluff.
- Current — Updated within the last 18 months, or foundational enough to remain relevant regardless of age.
- Unique — Adds something not already covered by a stronger source in the list.
- Generic AI marketing content
- Shallow "top 10 tips" listicles without depth
- Repos with no maintenance, no stars, and no real value
- Duplicate coverage of topics already well-represented
- Self-promotional content without technical substance
- Content not related to Claude Code or closely adjacent tools
- Paywalled content (unless a meaningful free summary exists)
- Check for duplicates — Search the list to make sure the resource isn't already included.
- Fork the repository and create a new branch.
- Add your resource in the appropriate category, following the existing format:
- [Resource Title](URL) - Brief description (15-30 words) of what it is and why it matters. - Submit a pull request with:
- A clear title describing the addition
- A brief explanation of why the resource meets the inclusion criteria
- The category you're adding it to
- Use hyphens (
-) as list markers, not asterisks - Descriptions should be 15-30 words
- Descriptions start with a capital letter and end with a period
- No trailing slashes on URLs
- Link text should be the resource title, not a URL
- Keep entries alphabetically ordered within each category
- One resource per line
If you believe a new category is needed:
- Open an issue first to discuss the category name and scope
- Provide at least 3 resources that would belong in the new category
- Explain why existing categories don't cover the topic
- Broken links — Open an issue with the broken URL and suggested replacement if available
- Outdated resources — Open an issue explaining why the resource is no longer relevant
- Miscategorized items — Open a PR moving the resource to the correct category
Please review our Code of Conduct before contributing.
- Submissions are reviewed within 2 weeks
- We may ask for changes or additional context
- Rejections include a brief explanation
- Quality over speed — we'd rather take time than lower the bar