We actively support the following versions of Git Spark with security updates:
| Version | Supported |
|---|---|
| 1.3.x | ✅ |
| < 1.3 | ❌ |
We take security vulnerabilities seriously and appreciate your efforts to responsibly disclose your findings.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them using one of the following methods:
-
GitHub Security Advisories (Preferred)
- Visit https://github.com/markhazleton/git-spark/security/advisories/new
- This is the most secure and efficient way to report vulnerabilities
-
Email
- Send details to: mark@markhazleton.com
- Use subject line:
[SECURITY] Git Spark Vulnerability Report - Encrypt sensitive information using GPG if possible
Please include the following information in your report:
- Type of vulnerability (e.g., XSS, command injection, path traversal)
- Full paths of source file(s) related to the vulnerability
- Location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the vulnerability, including how an attacker might exploit it
- Initial Response: Within 48 hours of report submission
- Triage: Within 5 business days we'll provide an initial assessment
- Updates: Regular updates on our progress every 7 days
- Resolution: We aim to release patches within 30 days for critical vulnerabilities
- Acknowledgment: We'll acknowledge receipt of your report
- Validation: We'll work to validate the vulnerability
- Communication: We'll keep you informed of our progress
- Credit: With your permission, we'll credit you in the security advisory
- Disclosure: We'll coordinate public disclosure timing with you
When using Git Spark, follow these security practices:
- Keep Updated: Always use the latest version
- Input Validation: Be cautious when analyzing untrusted repositories
- Output Review: Review generated reports before sharing publicly
- Email Redaction: Use
--redact-emailsflag when sharing reports - Access Control: Limit who can access generated analytics reports
When contributing to Git Spark:
- Code Review: All code changes require review before merging
- Dependencies: Keep dependencies updated and audit regularly
- Input Sanitization: Always sanitize user inputs and Git output
- Path Validation: Validate file paths to prevent traversal attacks
- Command Injection: Never pass unsanitized data to shell commands
- Testing: Include security-focused test cases
- Secrets: Never commit API keys, tokens, or credentials
Git Spark includes several security features:
- Repository path validation and sanitization
- Git command output buffer limits (200MB default)
- File path traversal protection
- Email pattern validation and redaction
- Parameterized Git commands (no shell string interpolation)
- Read-only Git operations (no modifications to repositories)
- Timeout protection for long-running operations
- Process cleanup on interruption (SIGINT handling)
- HTML escaping for all user-generated content
- CSV injection prevention
- Safe JSON serialization
- Optional email redaction in reports
Git Spark executes Git commands using child_process.spawn() with proper argument arrays to prevent command injection. All Git operations are read-only.
Git Spark reads from Git repositories and writes report files. It validates all file paths and respects .gitignore patterns. Never run Git Spark with elevated privileges unless absolutely necessary.
Generated reports may contain:
- Author names and email addresses
- Commit messages
- File paths and names
- Code change statistics
Use the --redact-emails option when sharing reports publicly.
We regularly audit dependencies using:
npm auditfor known vulnerabilities- CodeQL for code analysis
- Snyk for dependency scanning
- Automated dependency updates via Dependabot
We follow coordinated vulnerability disclosure:
- Report is received and acknowledged
- Vulnerability is validated and assessed
- Fix is developed and tested
- Security advisory is prepared
- Fix is released
- Advisory is published after users have time to update
After a fix is released:
- We'll publish a GitHub Security Advisory
- CVE will be requested if severity warrants
- Details will be added to CHANGELOG.md
- Reporter will be credited (if desired)
Security updates are released as:
- Patch versions (1.0.x) for non-breaking security fixes
- Minor versions (1.x.0) if security fix requires minor breaking changes
- Emergency releases for critical vulnerabilities
Subscribe to releases and security advisories:
- Watch the repository: https://github.com/markhazleton/git-spark
- GitHub Security Advisories: https://github.com/markhazleton/git-spark/security/advisories
- npm security advisories: https://www.npmjs.com/package/git-spark
- Security Issues: mark@markhazleton.com
- GitHub Security: https://github.com/markhazleton/git-spark/security/advisories/new
- General Issues: https://github.com/markhazleton/git-spark/issues
We appreciate the security research community's efforts to keep Git Spark secure. Contributors who responsibly disclose vulnerabilities will be credited in our security advisories (with permission).
Last Updated: April 2026