git-parsec 0.3.0

# Security Policy

## Supported Versions

| Version | Supported          |
|---------|--------------------|
| Latest  | :white_check_mark: |
| < Latest | :x:               |

Only the latest released version of git-parsec receives security updates.

## Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please report it responsibly.

**Do NOT open a public issue for security vulnerabilities.**

### How to Report

1. Go to the [Security tab](../../security/advisories/new) of this repository
2. Click **"Report a vulnerability"**
3. Fill in the details of the vulnerability

Alternatively, you can use [GitHub's private vulnerability reporting](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) feature.

### What to Expect

- **Acknowledgment**: Within 48 hours of your report
- **Assessment**: We will evaluate the severity and impact
- **Fix timeline**: We aim to address confirmed vulnerabilities within 90 days
- **Disclosure**: We will coordinate disclosure with you after a fix is available

### Scope

This policy applies to the git-parsec CLI tool and its published crate.

## Thank You

We appreciate the security research community's efforts in helping keep git-parsec and its users safe.