Always-on Fixboxes by CRACI
Fix vulnerabilities automatically, without breaking your build
CRACI sees everything your builds run and everything they pull in, down to the last dependency. So when one turns out to be vulnerable, a Fixbox automatically opens a pull request to fix it and verifies the fix with a new build. No guessing.
- Fix pull requests
- Verified by a new build
- Transitive dependencies
- Replaces update bots
Security teams are drowning in vulnerabilities
The security advisories and CVEs never stop, and every year there are more of them (see our CVE publication trends). Each one that touches your dependencies becomes a chore for someone: to determine which repositories are affected, find a patch that fixes it, update or replace the dependency, rebuild, and get the change reviewed.
That someone has often been the security team, and they are outnumbered. They find the vulnerability, chase the team that owns the code, and that team of course has a roadmap of its own. None of the steps are hard; the problem is the volume. Across dozens of repositories, the list of pending alerts grows faster than anyone can work through it, and after a while it becomes an overwhelming pile of work that no one dares to touch.
It used to take months for attackers to exploit a vulnerability. Now, on average, they exploit it a week before a patch exists. Fixing by hand can’t keep up. An automated fix can.
Picture a team with 30 repositories. If 10 new advisories a week touch their dependencies and each one takes an hour to work through, that is more than a full working day every week spent on dependency fixes before anyone builds a feature. Skip a few weeks and the backlog is in the dozens.
Fixboxes take the most repetitive part of that job off the security team’s plate. When CRACI finds a vulnerable dependency in your builds, Fixboxes open a pull request that fixes it. Your team reviews and merges it like any other change.
How it works
- Your builds run on CRACI. GitHub Actions jobs run on CRACI runners after a one-line change to
runs-on: craci. Runs still appear in GitHub. - CRACI records what each build pulled in. A package-aware proxy observes what the job downloads from package sources, including transitive dependencies and packages restored from CI caches. The result is an SBOM for that build, with a completeness state per job and per cache.
- CRACI finds the vulnerabilities in it. Packages from your builds are matched against known vulnerabilities, aggregated across builds and repositories, and re-evaluated as new advisories appear.
- Fixboxes open a pull request. For each vulnerable dependency, Fixboxes open a pull request in the affected repository to fix it.
- CRACI verifies the fix. CRACI runs a new build of the change, tests included, and checks that the vulnerability is no longer present.
- You review and merge. The pull request goes through your usual review and checks.
Illustration of a pull request opened by the CRACI GitHub App for a Fixbox. Title: Upgrade next to 15.2.3 to fix CVE-2025-29927. The description says the Fixbox found CVE-2025-29927, a critical vulnerability, in next 15.2.2 in the build of web-portal, and upgraded next to 15.2.3. The diff changes next from 15.2.2 to 15.2.3 in package.json and package-lock.json. The pull request's own CI runs on CRACI runners and passes, and the description then adds that the new build's SBOM no longer contains CVE-2025-29927. The pull request is ready for review.
Why start from the build
Most dependency tooling reads the manifests and lockfiles in a repository. That is a good start, but a build often pulls in more than the manifest says: a tool downloaded by a script, a package restored from a cache, a dependency of a dependency. A vulnerability in something the build fetched is a vulnerability that may flow into what you ship.
Because CRACI records the build itself, the vulnerabilities it reports come from what was really built, guiding the fixes Fixboxes propose. Read more about build-time SBOMs and vulnerability tracking.
Why Fixboxes replace update bots
Dependabot and Renovate are widely used automation tools for updating your dependencies. Here is what they do, according to their own documentation:
- Dependabot version updates are “automated pull requests that keep your dependencies updated, even when they don’t have any vulnerabilities.”
- Dependabot security updates open pull requests when a Dependabot alert is raised for a vulnerable dependency in your repository’s dependency graph. GitHub notes that they are “triggered only for dependencies that are specified in a manifest or lock file.”
- Renovate keeps dependencies up to date according to your configuration and schedule. It can also raise vulnerability-fix pull requests from GitHub’s Dependabot alerts, or from the OSV database for direct dependencies.
Fixboxes start from a different input: the vulnerabilities CRACI found in the packages your builds actually pulled in, including transitive dependencies and packages restored from caches. Every pull request is tied to real exposure in what you built, and a new build verifies it. That is why you can switch your update bot off and let Fixboxes do the job.
Details
- Supported ecosystems: the same ones CRACI records in your builds: npm, PyPI, RubyGems, Cargo, Go, Nix, OCI, Debian and Ubuntu (apt), Alpine (apk), Git sources, Yocto, and OpenEmbedded.
- Transitive dependencies: yes. CRACI maps which upstream package pulls in the vulnerable transitive dependency, and Fixboxes fix it there.
- Severity: fix everything, or only critical- and high-severity vulnerabilities if you prefer.
- Pull requests: the CRACI GitHub App opens them with commits GitHub signs, and they run through your usual CI on CRACI runners. Nothing is merged automatically: your team reviews and merges every fix.
Fixboxes and the CRA
The Cyber Resilience Act requires manufacturers to address and remediate vulnerabilities without delay, including by providing security updates. A fix pull request is where that work starts in the code. CRACI keeps the evidence around it: the build record, the SBOM, and the vulnerabilities found in it. CRACI automates a significant part of the supply chain visibility and evidence gathering that companies need for their wider CRA compliance process; it does not make a product compliant on its own. Read what the CRA requires.
Fixboxes: frequently asked questions
How are Fixboxes different from Dependabot?
Dependabot security updates open a pull request when GitHub raises an alert for a dependency in a manifest or lockfile, and version updates keep dependencies current even when nothing is vulnerable. Fixboxes start from what your builds actually pulled in, including transitive dependencies and packages restored from caches, and a new build verifies every fix. See CRACI vs Dependabot.
How are Fixboxes different from Renovate?
Renovate keeps dependencies current according to rules and schedules you write, and raises vulnerability fixes from GitHub’s alerts or from OSV, which its documentation says covers direct dependencies only. Fixboxes need no configuration file: they fix the vulnerabilities CRACI finds in your builds, and for a vulnerable transitive dependency they fix the upstream package that pulls it in. See CRACI vs Renovate.
Can I switch off Dependabot or Renovate?
Yes. Fixboxes replace the update bot for vulnerable dependencies in builds that run on CRACI. What you give up is routine version updates for dependencies with no known vulnerability. See Dependabot alternatives and Renovate alternatives for the wider comparison.
Will a Fixbox break my build?
A Fixbox fix is checked like any other change before anyone merges it. CRACI runs a new build of the change, tests included, and checks that the vulnerability is no longer in it. The pull request also runs your usual CI on CRACI runners. If a fix breaks a test, you see it in the pull request before anything is merged.
Does a Fixbox merge anything on its own?
No. Your team reviews and merges every fix, through the same review and checks as any other pull request. Nothing reaches your default branch until a person merges it.
Who opens the pull request?
The CRACI GitHub App opens it, with commits GitHub signs. An AI agent writes the change, the title and the description, based on the vulnerability CRACI found in your build.
Can I trust a fix written by AI?
An AI agent writes each Fixbox change, but it starts from data, not a guess: the vulnerabilities CRACI recorded in what your build actually pulled in. Every fix then follows the guardrails AI fixes need. A new build, tests included, checks that the vulnerability is gone, the build records every package the change pulls in, and your team reviews and merges every fix. See AI vulnerability remediation for what AI fixes do well and where they go wrong.
Can I limit Fixboxes to the most serious vulnerabilities?
Yes. Fixboxes can fix everything, or only critical- and high-severity vulnerabilities if you prefer.
Which plans include Fixboxes?
Fixboxes are part of the Secure and Enterprise plans. See pricing.
See Fixboxes on one of your repositories
Book a demo and we will run one of your GitHub Actions workflows on CRACI and show what it finds and what it would fix.
Book a demo