Step 1
Tell the reviewer what to check
Add a security review to every pull request, or run it across the whole repository on a schedule. Write what it checks in plain words, from auth and injection to rules specific to your codebase.
SHIP reviews your code for vulnerabilities and tries each finding on a live preview before it reports it. Each confirmed finding comes back with proof and a pull request that fixes it.
Runs today: Run a security review on one pull request with ship delegate pr --prompt-file, or schedule the security advisory triage automation.
Answer 4 questions. SHIP emails you when it opens to you.
ship delegate pr SHIP-412 --prompt-file security-review.mdStep 1
Add a security review to every pull request, or run it across the whole repository on a schedule. Write what it checks in plain words, from auth and injection to rules specific to your codebase.
Step 2
The Tester tries each finding against a preview deployment of your app. A finding it can't reproduce is marked unconfirmed instead of reported.
Step 3
A Builder writes the patch for each confirmed finding. Your CI, a code review and the same exploit attempt run again before the pull request is ready.
The security advisory triage automation runs your package manager's audit. It checks whether your code reaches each advisory's vulnerable code, and patches the ones it reaches.
Pick the harness and model for the security review, so a second model reviews what the first one wrote.
Paste a scanner's findings into an issue and assign it to SHIP. The agents fix them in a tested pull request.
Agents run in isolated sandboxes with short-lived, scoped tokens. Your provider keys never enter them.
Every review reports how long it took and what it cost, priced on the model that actually answered.
| Devin |
|
|---|---|
| SHIP | In early access
|
Partly. A security review on every pull request, with each finding proven on a preview, is in early access. Today you can run a security review on one pull request with ship delegate pr --prompt-file, or schedule the security advisory triage automation.
No. SHIP catches and fixes what a code review and a live preview can show. Keep the penetration tests and audits your customers and certifications require.
No, unless a person asked for it. A change under .github/workflows is blocked before it is pushed, and every fix still has to pass your CI and a code review.
Devin fits a team that wants a dedicated security agent available today, as Devin's own page describes. It runs many investigation agents in parallel across the codebase and works with the scanners the team already has. SHIP fits when security review should run in the same loop as your other pull requests, on the harness and model you choose.
Join early access and decide what the security review checks.
Answer 4 questions. SHIP emails you when it opens to you.