Auto-PR pilot

A focused pilot for your dependency workflow.

ZeroPatch scans the dependency manifests configured for a repository and checks those listed dependencies for high-severity emerging CVEs. When an eligible patched version is available, it can open a pull request with the version change for your team to review.

The pilot flow

From configured scope to a patch proposal.

  1. 01

    Configured manifest

    The pilot scans the dependency manifests configured for a repository. Its scope is the dependencies listed there.

  2. 02

    Eligible emerging CVE

    The MVP checks listed dependencies for high-severity emerging CVEs and needs an eligible patched version to proceed.

  3. 03

    Reviewable pull request

    When a fix is eligible, ZeroPatch can open a pull request with the patched version for your team to review.

CI and merge control

CI may be skipped only for a low-risk change when the target workflow's skip mechanism has been verified. Otherwise, normal CI remains enabled. Pull requests are for your team to review and are not automatically merged.

Evaluate the fit with your security team.

Share the repository scope and review expectations you want to explore.

Talk through a ZeroPatch pilot