Caught a security hole
Someone could type a crafted search into the hours report and see other people's data. The Pass blocked the merge.
Every GitHub pull request reviewed by your AI panel, and fixed right in the PR.
Ready in about 20 minutes. No ops.
fix: apply tax after discountFrom our own demo app.
Someone could type a crafted search into the hours report and see other people's data. The Pass blocked the merge.
The Pass changed the code so the search can't be abused, added tests that try the attack, and reviewed the fix again before letting it through.
The team said a pattern was fine on purpose. On the next pull request, The Pass didn't bring it up again.
Real events from our own demo app, described in plain words.
Your panel of AI reviewers, any provider.
Pushes a fix commit, then re-checks it. You still merge.
lintunit testsYour existing checks, shown alongside the review.
Mark a finding "not a problem"; later reviews recall it.
| Question | Typical AI review tools | The Pass |
|---|---|---|
| Who runs it | Their shared service | Us, on your private server |
| Your models | Usually theirs; varies | Any provider, your keys |
| Fix in the PR + re-check | Varies; often suggestions | Yes |
| Shows your CI | Usually not | Yes, alongside the review |
GitHub only, today.
Changed code goes to the AI providers you connect. Security details
Plus your own AI usage, billed by your provider. Cancel any time.
The AI that wrote the code shouldn't be its only checker. You pick other reviewers, and fixes land in the PR.
From your private server to the AI providers you connect, under your keys. Never shared with other customers. Security details
You install our GitHub App on chosen repos. It reads code, posts reviews, and pushes fixes if auto-fix is on. It never merges. Full list
Yes, for any repo or single pull request.
Not yet. GitHub only, today.
That's coming. If you want it, talk to us: support@thepass.dev.