product
Secure Dependency Updates
Scheduled dependency updates, evaluated before they open.
customers
ubicloudevry healthdotenvxfirecrawlcapchasenangomastrapaperclip
why
most dependency bots open the pull request first and hope ci catches the rest. that still dumps a risky bump on your reviewers.
superagent generates the change, scores supported packages, and withholds anything that fails policy. the published pull request still gets a supply chain scan before merge.
what you get
schedule
daily, weekly, or monthly per repository. off by default.
isolated generation
pinned dependabot tooling runs in a sandbox with repository read access.
evaluate first
supported package changes are scored before a pull request opens.
scan again on the pr
the supply chain scan still runs after github opens the published update.
how it works
three steps
01 pick a schedule. open a repository in superagent and choose daily, weekly, or monthly.
02 we generate the update. manifest and lockfile changes are created in an isolated sandbox.
03 only approved proposals open. blocked updates stay unpublished. published ones still go through supply chain scanning.
get started
free for open source.
the whole suite, on any public repo. private usage starts free, with shared credits and self serve plans when you need more.