Vetoo

Approve. Comment. Vetoo.

Agentic AI code review for GitHub and GitLab. Tailored to your team.

Add refresh token rotation #482
OpenMergedlily wants to mergemerged 3 commits into main from feat/token-refresh
Conversation 4Commits 3Checks 1Files changed 1
src/auth/session.ts+9 −1
3636import { db } from '../db'
3737import { signToken } from './jwt'
3838
39+export async function refreshSession(token: string) {
40+ if (!token) throw new AuthError('missing token')
41+ const user = await db.query(`SELECT * FROM users WHERE token=${token}`) const user = await db.query('SELECT * FROM users WHERE token = $1', [token])
vetoo-reviewbotBlockingResolved · fixed in a1f3c9e
SQL injection on the refresh token.

String-interpolated SQL on token is injectable. A crafted token could read any row. Bind the value instead.

Suggested changeCommit suggestion
− const user = await db.query(`SELECT * FROM users WHERE token=${token}`)
+ const user = await db.query('SELECT * FROM users WHERE token = $1', [token])
L
lily · just now

@vetoo-review is this a real risk or theoretical?

vetoo-review bot

Real. This is the refresh path, so it is reachable without a valid session. Nothing upstream filters the token before line 41.

CancelComment
42+ const next = signToken(user.id)
43+ await cache.set(`session:${user.id}`, next)
vetoo-reviewbotNote
Token never expires.

The rotated token is cached without a TTL. Callers assume a 15 minute expiry.

44+ return next
45+}
vetoo-review requested changes · 1 blocking, 1 notevetoo-review approved these changes · SQL binding fixed, 1 note open
lily merged commit 7c2e9b1 into main
vetoo-reviewQueued
Merge pull requestConfirm mergeCancelWaiting for review
Pull request successfully merged and closed

You're all set. The feat/token-refresh branch can be safely deleted.

Delete branch
Works with
  • GitHub
  • GitLab
  • Linear
  • Notion
  • Slack
  • Jira soon

Top 4 in precision.

Independent Martian benchmark of 22 AI code reviewers on real, human-reviewed pull requests.

6thout of 22 tools
BeatingCodeRabbit, Greptile, Copilot, Bugbot, Macroscope, Claude, Gemini, Sourcery and many others
28/36groups won against CodeRabbit
See the full results

How it works

  1. It reads beyond the diff.

    Integrations and your other repositories.

  2. Multiple agents review your code from different angles.

    Signals merge and rank. The stricter call always wins.

  3. One verdict lands.

    Severity, reason and inline comments with fix proposals.

LinearAUTH-12Notiontoken RFCrepoweb-appSlack#auth-teamMemory · tomorrow+Security findings first+Tests on API routes−Tabs vs spaces nits·One-off rename: droppedAdd refresh token rotation #482src/auth/session.py+68 raw signals → 4 unique, rankedvetoo-review requested changes

Your code, your rules.

  1. Vetoo leaves comments.

  2. Give feedback by reacting to them.

  3. Feedback collected and evaluated.

  4. Learnings applied as rules.

Predefined rules in plain Markdown.

VETOO.md
1## Review rules
2
3- Block any PR that logs PII
4- Treat missing tests as nits
vetoo-review on #482
  1. Blocking

    logger.info prints the user email

    login.ts:27
  2. Nit

    New refresh path has no test

    session.ts
  3. Nit

    Prefer early return over nested if

    session.ts

Code review, not autopilot.

MANIFESTO.md+4 −4
  1. One model behind a proxy with an AI review sticker
  2. A coding agent let loose in your repo to write and ship
  3. Review bolted onto a do-everything platform
  4. Your source kept around to train a model
  5. A fresh review the moment a pull request opens
  6. Ranked findings, tailored to your team
  7. One job done best, with a mix of models, including frontier ones
  8. Your code deleted the moment the review ends

Code reviewed, then gone.

Kept

  • Pass, comment and block verdicts
  • Your votes as review preferences
  • Suppression rules you set
  • Repo and pull request identifiers

Never stored

  • Your source code
  • Secrets, tokens or env vars
  • File contents after the review
  • Anything used to train a model

Start free. Scale by the seat.

$20 bonus on sign-up

Free

$0per seat / month
Pay as you go
Seats
Up to 3
Support
Best effort
Start free

Hobby

$20per seat / month
2,200 credits / mo
Seats
Up to 5
Top-ups
30% off
Choose Hobby

TeamRecommended

$25per seat / month
2,875 credits / mo
Seats
6 to 25
Top-ups
30% off
Choose Team

Enterprise

Quotedtalk to us
Custom credits & BYOK
Seats
Your range
Support
SLA
Talk to sales

In every plan

  • Inline review comments
  • Review from every angle
  • Memory: learning from usage and feedback
  • Cross-repository checks
  • Interactive comments
  • Context enrichment with Notion, Linear and Slack
  • Review effort levels
  • PR checks
  • Unlimited repositories

1 credit = $0.01 Reviews from $0.70 Credits last 12 months

FAQ

How is Vetoo different from other AI code reviewers?

It adapts to your team, and it stays quiet unless it has something worth saying. Every reaction on a finding becomes part of your team's memory, alongside the rules you write in VETOO.md, so each review gets closer to how your team works. Multiple agents review every change from different angles and cross-check each finding before it posts, so what reaches your pull request is curated and verified: fewer comments, more of them worth acting on.

What is agentic AI code review?

Agentic AI code review uses autonomous agents that read a pull request, gather context and act on it, instead of a single model pass over the diff. Vetoo runs multiple agents in parallel, each reviewing the change from a different angle, and only a curated set of findings reaches your pull request.

Which AI models does Vetoo use?

Vetoo runs agents on a mix of models, including frontier ones, side by side, so no single model decides the review alone. Each one surfaces a different slice of issues, and only a curated set of findings reaches your pull request, not the verbose output of a single model.

Does Vetoo store my source code?

No. Vetoo only holds your code while the review runs, encrypted in transit and handled in isolation, and it is gone once the verdict lands. Review comments and their metadata are kept for a limited time so conversations and team memory keep working.

Can I ask Vetoo questions about its review?

Yes. Reply to any finding, or mention @vetoo-review in a comment, and it answers in the thread. Ask why something was flagged, push back on a finding you disagree with, or ask for a fresh review pass.

What programming languages does Vetoo support?

Vetoo is language agnostic. It reviews any language the underlying models understand, which covers every mainstream language and most niche ones. VETOO.md rules, conversations and team memory work the same in every language.

Can I self-host Vetoo?

Not today. Vetoo is a hosted service. Each review runs in an isolated sandbox, and your code is deleted once the verdict posts. On Enterprise you can bring your own model key, so reviews run on your own provider account.

Does it work with GitLab?

Yes, and all features are available.

Can we customise the review?

Yes. Commit a VETOO.md file to set severities, tone and focus. Votes on findings tune it further.

Clear the review queue before it forms.

Try for free

$20 in credits on sign-up.