Skip to content

Security: destination/claude-code-templates

Security

SECURITY.md

Security Policy

Thank you for helping us keep Claude Code Templates and the systems they interact with secure.

Reporting Security Issues

This project is maintained by Daniel Avila.

The security of our CLI tool and the templates it generates is our top priority. We appreciate the work of security researchers acting in good faith in identifying and reporting potential vulnerabilities.

How to Report a Vulnerability

If you discover a security vulnerability in Claude Code Templates, please report it to us in one of the following ways:

GitHub Security Advisories (preferred)

Use Report a vulnerability. It keeps the report private, lets us work on the fix with you in a private fork, and gives you credit when the advisory is published.

Email

Send details of the vulnerability to daniel@aitmpl.com with the subject line "SECURITY: Claude Code Templates Vulnerability Report"

Please do not open a public issue, pull request or discussion for a vulnerability.

Supported Versions

Only the latest minor release of the claude-code-templates npm package receives security fixes. Fixes ship as a new release, and npx claude-code-templates@latest always runs it. Components in the catalog are fixed in place on main; reinstall a component to get the fixed version.

Version Supported
Latest minor (see npm) Yes
Older releases No

What Happens After You Report

Step Target
Acknowledge the report 3 business days
Triage: confirm, ask for details, or explain why it is not a vulnerability 7 days
Fix released, or a plan with a date shared with you 30 days (90 days at most for complex issues)
Advisory published with a CVE and credit to you When the fixed release is on npm

We keep the report private until the fix is released. If we miss one of these targets, you are welcome to send a reminder by email. Duplicates of an already reported issue are credited to the first reporter.

What to Include in Your Report

To help us understand and resolve the issue quickly, please include:

  • Description: A clear description of the vulnerability
  • Impact: What an attacker could achieve by exploiting this vulnerability
  • Steps to Reproduce: Detailed steps to reproduce the vulnerability
  • Affected Versions: Which versions of the CLI tool are affected
  • Environment: Operating system, Node.js version, and any other relevant details
  • Proof of Concept: If possible, include a minimal example demonstrating the vulnerability

Security Best Practices

When using Claude Code Templates:

For Users

  • Keep Updated: Always use the latest version via npx claude-code-templates@latest
  • Review Templates: Check generated files before committing to your repository
  • Audit Hooks: Review automation hooks before enabling them
  • Secure Environment: Use the tool in a secure development environment

For Contributors

  • Dependency Scanning: Run npm audit before submitting changes
  • Input Validation: Validate all user inputs and file paths
  • Secure Defaults: Choose secure defaults for all template configurations
  • Code Review: All changes undergo security-focused code review

Contact Information

Legal

This security policy is designed to encourage responsible security research. We will not pursue legal action against researchers who:

  • Act in good faith
  • Follow responsible disclosure practices
  • Do not access or modify user data
  • Do not perform testing on systems they do not own
  • Report vulnerabilities through the channels described above

Thank you for helping keep Claude Code Templates secure!

There aren't any published security advisories