Focused repository processing
ShipCheck reads the pull request change and may select relevant surrounding repository context to understand behavior. It is not designed to blindly send an entire repository to AI.
Your repository is notjust another upload.
ShipCheck is built around scoped GitHub access, explicit write actions, optional AI review, and clear control over which repositories the service can access.
You decide what ShipCheck can see.
ShipCheck uses a GitHub App rather than asking you to paste a personal access token into the product. Repository selection remains controlled through GitHub.
Installation tokens
ShipCheck creates GitHub App installation access tokens when repository access is needed.
Repository selection
Choose which repositories the GitHub App installation is allowed to access.
Revoke access
Remove individual repositories or uninstall the ShipCheck GitHub App through GitHub.
Verified installations
ShipCheck verifies that the installation belongs to the GitHub identity authorizing the connection.
What happens after you connect a repository?
AI is optional
AI Review is configurable per repository. Disable it and ShipCheck skips AI review while deterministic checks can continue operating.
No automatic code rewrites
A scan analyzes your change. Repository modifications happen through explicit actions such as Apply Fix or applying a generated regression test.
No full-repository mirror
ShipCheck is not designed to maintain a permanent clone of your entire repository. Scan artifacts may retain relevant evidence or generated code.
Server-side credentials
Privileged GitHub and service credentials stay on the server rather than being exposed to the browser.
Signed GitHub webhooks
Incoming GitHub webhook requests are cryptographically verified before ShipCheck processes supported events.
Know when your code touches AI.
ShipCheck uses OpenAI's API when AI Review is enabled. The setting is repository-specific, and the scanner checks it before invoking the AI review.
Relevant PR patches and selected supporting context may be sent for AI review.
ShipCheck limits how much code is included in an AI request.
Lock files, generated files, build outputs, snapshots, and similar low-value files are filtered from AI review in several cases.
Turning off AI Review prevents ShipCheck from invoking its AI reviewer for that repository.
OpenAI states that API data is not used for model training by default unless the API customer opts in.
Why does ShipCheck need write permissions?
Some ShipCheck features are intentionally interactive: you can ask ShipCheck to apply a suggested fix or generated regression test directly to a pull request.
Those capabilities require GitHub write access. They are separate from the normal scanning process.
The important part
ShipCheck does not silently rewrite your repository during a scan.
Scan your PR without applying anything.
Review a suggested fix before choosing to apply it.
Review a generated regression test before applying it.