Before any tool opens fix pull requests on your repositories, settle what it can read and write, how changes are reviewed, how they are tested, and how you turn it off. Start with a single low risk repository and review every change by hand.
Access
1. What permissions does it need? Ask for the exact scopes. Pull request creation does not require permission to merge or to change settings. Grant the minimum.
2. Can access be limited to chosen repositories? Avoid organisation wide grants on day one.
3. Where does the code go? Some tools clone to their cloud, some run in your CI. Match this to your data rules.
Behaviour
4. Does it ever merge on its own? The safe default is no. If auto merge exists, it should be a setting you control per category.
5. Can I set it to do nothing until I say so? An off by default option is a good sign. You should be able to enable it step by step.
6. How does it choose a fix? It should explain the version it picked and why, and say when no fix exists.
Safety
7. What runs against its pull requests? Your normal CI must run in full. If tests are thin, expect to review more by hand and do not rely on green checks.
8. How do I roll back and audit? Each change should be a normal commit you can revert, with a record of who or what approved it.
A cautious rollout
- One repository with good test coverage.
- Patch level fixes only, review required.
- Track for a month: merge rate, reverts, time saved.
- Widen scope based on those numbers, not on enthusiasm.
Where it is not worth it
If you merge only a handful of dependency changes a month, manual updates cost little. Automation pays off with volume.
Who owns the pull requests
Automated pull requests still need an owner. Decide which team reviews them and how quickly. Unreviewed fix pull requests pile up, go stale and conflict with each other, which is the same backlog problem in a new place. Assign a rotation, set a target such as review within two working days, and close stale pull requests rather than letting them linger.
Where Safeguard fits
Safeguard provides autonomous remediation with fix pull requests. It is off by default and every category starts on Manual, which matches the rollout above. Try the free scan to see candidate fixes first.
Quick check
Should a security tool have write access to my default branch?
No. Pull requests with required review are enough, and branch protection should stay on.
Last reviewed: 19 October 2026.
