Help center
Five questions teams ask before adopting micropatches.
Get concrete answers about PR review, recovery after a regression, the public audit trail, change-control evidence, and the published ZeroPatch plans.
Control and recoveryEvidence and governancePricing
How to read this page
- Control and recovery — how an emerging-vulnerability PR is reviewed and how teams handle regressions
- Evidence and governance — what appears in pull requests and the public audit log
- Pricing — current monthly tiers, graph and package limits, and Enterprise terms
Control and recovery
Review changes and know how to recover.
The emerging-vulnerability PR stays reviewable, and your GitHub workflow remains the practical path for handling a regression.
Evidence and governance
Inspect the record and keep your controls.
Review the evidence in a pull request and the published audit log, while your team retains its existing change-control decisions.
Pricing
Match the published plan to your graph.
See current monthly rates and package/graph limits alongside the custom annual Enterprise plan.
Still on the fence?
If you want to discuss your dependency graph, review workflow, or plan fit, email us and we can talk through the documented ZeroPatch process.