Files
Victor KuznetsovandClaude Opus 5.5 72752feb33 Scan uv.lock in CI and add a security policy
Add a CI job running the maintain.sh uv-secure scan, pinned to the gate by
a parity test, and a SECURITY.md with private reporting and dependency
remediation. Refresh the security-gate block record for accelerate 1.15.0.

Closes #114

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02 10:33:50 -07:00

1.1 KiB

Security policy

Supported versions

Security fixes go into the latest release. Older releases are not patched; upgrade through the channel you installed from (PyPI or Homebrew).

Reporting a vulnerability

Report vulnerabilities privately through GitHub private vulnerability reporting. Do not open a public issue for an unpatched vulnerability. Include the affected version, the command or API call, and a minimal input that reproduces it.

Vulnerabilities in a dependency, such as a CVE in a package from uv.lock, can be reported as a regular issue when the advisory is already public.

Dependency vulnerabilities

Dependabot raises alerts and update pull requests for uv.lock and GitHub Actions, and CI scans uv.lock with uv-secure on every push and pull request. A vulnerable dependency is upgraded to a fixed release; advisories without one are tracked under Known security-gate blocks.