Security & Trust
How IonWarp handles your code
By Ilya Volodarsky at Winding Labs · Updated
IonWarp reads your code through a GitHub App on the repositories you choose. Each review runs in its own sandbox session, wiped when the session ends, and review data is deleted 90 days after it was last updated.
If you have to approve IonWarp before your team installs it, this page says what a code review service can reach once it is connected. The answers come from the shipped product: the GitHub permissions it holds, the delete date on each record and how sessions are kept apart. IonWarp suits a team on GitHub that can let a hosted service read its code during a review. It won't suit a team whose code must stay on its own network, because IonWarp does not offer self-hosting, or a team on GitLab, Bitbucket or Azure DevOps, which it does not review.
What can IonWarp do with my code?
IonWarp has read-only code access on the repositories you choose, and it posts its review on your pull requests. It cannot change your code.
| Code access | Read-only, on the repositories you choose. |
|---|---|
| Changes to your code | None. IonWarp cannot push a commit, create a branch or merge a pull request. |
| What it posts | Review comments, suggested changes and a check on your pull requests. |
| Where reviews run | A sandbox container, separate from IonWarp's web app and from your infrastructure. |
| Language models | Third-party providers host the models that read the code under review. |
| Review data | Deleted 90 days after it was last updated. |
| Removing access | Uninstall the GitHub App from your organization's settings. |
| Code hosts | GitHub, plus GitHub Enterprise on the Enterprise plan. |
| Self-hosting | Not offered. |
What permissions does IonWarp need on GitHub?
IonWarp reads your code; it never writes to your repository. The GitHub App holds Contents: read-only, so it cannot push a commit, create a branch or merge a pull request. Its write access covers checks, issues and pull requests, which it uses to post its review.
IonWarp installs as a GitHub App on the repositories you choose — and only those. Access is scoped by GitHub's own permission model, visible in your organization's settings, and revocable at any time by uninstalling the app.
Every webhook from GitHub is checked against GitHub's signature before IonWarp reads it. A webhook without a valid signature is rejected.
| Permission | Access | What IonWarp uses it for |
|---|---|---|
| Contents | Read-only | Clones the repository for a review and reads its files. Commits, branches and merges all sit under this permission, so this read-only level is what keeps IonWarp from changing your code. |
| Metadata | Read-only | Reads repository names and basic details. |
| Pull requests | Read and write | Reads the pull request and its changed files, and posts inline review comments, replies and suggested changes. A suggested change stays a comment until someone on your team commits it. |
| Issues | Read and write | IonWarp's comment on a pull request and its reactions go through GitHub's issue-comment endpoints. |
| Checks | Read and write | Creates and updates IonWarp's check on the pull request. |
Where does my code go during a review?
A review reads your code in a sandbox container that IonWarp runs, and the diff and any file a reviewer reads go to that reviewer's language model. IonWarp does not host those models; third-party providers do.
That container is separate from IonWarp's web app and from your own infrastructure. Your repository is checked out into a directory private to that run.
Containers are kept running between sessions, and one container can run more than one session at a time, so isolation does not depend on a container being new or empty. Every session — a review, a repository scan or a chat — gets its own environment, holding only that session's credentials, and its own directories for the checkout and the output, which only that session's system user can open. When the session ends, all of it is wiped, so one customer's code, credentials or output never reaches another customer's session.
What does IonWarp store, and for how long?
IonWarp stores what you see in the dashboard: findings, pull request details, scorecard results and run logs.
Review data is deleted 90 days after it was last updated. Every record we keep about a review — the run, its findings, scorecards, learned rules, screenshots, notes about the repository and support tickets — is marked with its delete date when it is written, and a nightly job deletes whatever is past it.
Deleting a project deletes its review data with it.
The checkout is not one of those records, because it is wiped when the session ends. A finding can quote the lines it points to and carry a suggested fix, so what we store can include excerpts of your code.
What does the Enterprise plan add for security?
The Enterprise tier adds SSO/SAML, audit logs, GitHub Enterprise support, a custom security review of your setup, and an SLA — the same list published on our pricing page.
How do I report a vulnerability or send a security questionnaire?
Security questionnaires, compliance questions, or a vulnerability to report — reach us through the support page and we'll route it to the right person. Preparing your own SOC 2 audit? SOC 2 code review covers what a pull request can show an auditor. See who builds IonWarp.