A dating app
for your patches.

For every finding, Depi generates a candidate patch and brings it to you. Swipe through them: it's a match, it's not, or ask for a different one. The matches ship themselves. Ten minutes a week, your upstream stays clean.

One card.
One decision.

Each finding shows up as a candidate: what's wrong, what the fix does, and the exact change. You don't write it. You don't research it. You just decide.

  • It's a match. The PR opens, CI runs, it merges.
  • Not for you. Pass, and Depi stops surfacing it.
  • Not quite. Ask for a different mitigation and get a new candidate.
Critical
Pin axios to 1.7.4Security · backend +3
8h

Why: A maintainer account upstream of axios is showing takeover signals. This pins you off the auto-update path while it gets investigated.

"dependencies": {
- "axios": "^1.7.0",
+ "axios": "1.7.4",
High
Restrict workflow permissionsPWN Request · class ACTION_PWN
8h

Why: release.yml runs pull_request_target with the default write token. This drops it to read-only, so a forked PR can no longer push to your repo.

pull_request_target:
+ permissions:
+ contents: read
+ pull-requests: read
Critical
Pin rollup transitive to 4.21.3TOCTOU · checkout-svc +1
10h

Why: The Rollup TOCTOU bug reaches this build through Vite. Public disclosure is days out; an override locks the fixed version in now.

"vite": "^5.4.0",
+ "overrides": {
+ "rollup": "4.21.3"
+ }

You review,
Depi does everything around it.

Generate

Every finding comes with a candidate patch already written, pinned versions, scoped names, the smallest change that closes the path. Linked to the finding that triggered it.

Swipe

Open the inbox, ten minutes a week. Match the ones you want, pass the ones you don't, ask for a different mitigation when it's close but not right.

Ship

Matches open as PRs in GitHub or GitLab, respecting your branch protection and reviewers. CI runs, you merge. Nothing bypasses your process.

The backlog that never piles up.

10min
A week is all the inbox asks for. No triage meetings, no ticket grooming.
1PR each
One finding, one patch, one rollback path. Never a 40-file dependency bump.
0research
You don't read the advisory or write the fix. You decide yes or no.

Stop triaging. Start swiping.

Book a demo and watch candidate fixes show up against your own dependency tree.