pre-commit-uv is a pre-commit add-on that builds Python hook environments with uv in place of virtualenv and pip. This policy says how to report a security problem and how we decide whether a report is one.

Do not open a public issue for a security problem. Use GitHub's private vulnerability reporting. If you do not have a GitHub account, or you are a Tidelift subscriber, report through the Tidelift security contact instead; Tidelift coordinates the fix and the disclosure with us. If neither works for you, email gaborjbernat@gmail.com.

Include what the attacker controls and what they gain, the steps or a proof of concept, and the versions and platform you tested. Write the report yourself; unreviewed tool or model output takes longer to triage.

Volunteers maintain pre-commit-uv, with no on-call rotation. We aim to acknowledge a report within 5 working days and assess it within 15 working days. Fixes are developed in a private fork attached to the draft advisory, ship in a new release, and the advisory, with a CVE requested through GitHub, goes out with that release. The default embargo is 90 days from the report; we agree any change with the reporter. We credit reporters in the advisory under the name they choose, or not at all. There is no bug bounty.

Only the latest release receives fixes. Confirm the problem reproduces on it before reporting.

A report is a vulnerability when an attacker who controls only an input that the threat model lists as untrusted breaks a guarantee pre-commit-uv makes. A report that first needs control of something the threat model trusts, such as the .pre-commit-config.yaml, the hook repositories it pins, or the bundled uv, is a bug: we fix it in the open and publish no advisory. Classify by who supplies the dangerous input, not by how bad the outcome sounds.

In scope

• pre-commit-uv installing something other than what pre-commit asked for: a different hook repository, revision or additional_dependencies.
• pre-commit-uv running a uv other than the bundled uv package.
• The patch activating when DISABLE_PRE_COMMIT_UV_PATCH is set.

Out of scope

• Hooks and their dependencies: the config chooses them and pre-commit runs them; a malicious hook repository is trusted by the config that pins it.
• pre-commit's own behavior; report it to pre-commit.
• uv's resolution and downloads; report those to uv.

If you cannot tell which side a finding falls on, report it privately and we will decide.