Customers
Teams building on CRACI
These teams moved their GitHub Actions builds to CRACI runners, and every build now records what it pulls in.
Updated
What these teams have in common
-
They kept GitHub and GitHub Actions. Moving a workflow to CRACI is one line:
runs-on: craci. - Every build now produces an SBOM from what the job actually pulled in, with a completeness state that says how far to trust it.
- Vulnerabilities are tracked across the builds and repositories that share a dependency, so one question answers where a package is used.
Want to be the next story?
If you are running CRACI and want to share what changed for your team, named or anonymous, we would like to hear from you. Get in touch.
Tell us about your pipeline
Book a demo and we will run one of your real workflows on CRACI and look at what it pulls in together.
Book a demo