Security
How we handle your code
What we access, where it runs, what leaves our machine, and what we keep. This page describes how Graft works today. It will change as Graft grows, and we'll update it when it does.
The path your code takes
We clone your fork read-only onto a machine Graft operates. The carry, the build and the tests run there. Only the files that conflict, with the context needed to merge them, go to the agents. You get a report and a branch, and we delete the working copy after delivery.
We never push to your repository unless you ask us to deliver there.
The details
- What we accessRead access to your fork, enough to clone it. For a private fork, a read-only deploy key or token, or a
git format-patchexport if you'd rather not grant access at all. We never ask for write access. - Where carries runOn a dedicated machine that Graft operates, not shared CI. Each carry gets its own working directory. Today Graft is run by one person, and so is that machine.
- Your build and testsWe run the build and test commands you give us, on the new release alone and with your changes on. They run on our machine with low priority and a time limit.
- What the agents seeFor each conflicting file: the file as it was, your version, upstream's new version, and the rest of that change as context. Agents run through Anthropic's Claude, with no tools, no shell, no settings and no access to anything else, each in a scratch folder. Your access token is never given to an agent.
- What leaves our machineThe agent inputs above, sent to Anthropic. The report and the branch, sent to you. Nothing else.
- What we keepYour request, the report, the decisions you made, and a record of the delivery, so we can carry your next release and answer questions about this one.
- What we deleteThe clone, the working trees and the build output, within 30 days of delivery or of a refund, or within 30 days of your free report if you don't go ahead. You can ask us to delete everything else at any time.
- Pushing to your repositoryNever, unless you ask us to deliver the branch there. Otherwise we deliver to a repository you choose or as a patch series.
- This websiteServed by Cloudflare over HTTPS. Report pages use long random links that aren't listed or indexed. The operator console needs a secret token. See privacy for what the site stores.
- CertificationsWe don't hold SOC 2, ISO 27001 or similar certifications. If you need a security questionnaire answered, ask and we'll answer it truthfully.
Report a vulnerability
If you find a security problem in graftfork.com or in how we handle code, email support@graftfork.com with "Security" in the subject. We'll reply within two business days and keep you updated until it's fixed. Please don't access other people's data or disrupt the service while testing.