AI writes the code.We secure it.

Gitsentry reviews every pull request for security flaws and only posts what it can prove.

Free for public repos. Open source, MIT.

OpenAdd invoice download #128

src/routes/invoices.ts+6

12+router.get("/invoices/:id", requireAuth, async (req, res) => {

13+ const invoice = await db.invoice.findUnique({

14+ where: { id: req.params.id },

gitsentrybotCritical · IDOR

Any signed-in user can read any invoice by changing the ID.

where: { id: req.params.id, ownerId: req.user.id },

15+ });

16+ res.json(invoice);

17+});

Gitsentry Security Scan

1 security issue found

Reviews code written with

Everything happens in the pull request.

A second pass tries to disprove every finding. Only what survives reaches your PR.

Scan of #1285 candidates, 2 posted

Repos protected

Issues caught

Critical vulns stopped

Scans run

Categories that can't apply to your stack are skipped, so the ones that can get full attention.

See all 37 categories

Injection and taint: SQL · NoSQL · Command · Template · LLM prompt · SSRF · Path traversal · XSS · Open redirect · Unvalidated input
Access control: Missing auth · IDOR · Privilege escalation · Mass assignment · Password reset · Session management · CSRF
Secrets and exposure: Hardcoded secrets · Token leakage · Sensitive data · Insecure storage · Verbose errors · Crypto misuse
Logic and timing: Business logic abuse · Race conditions · Replay · Timing attacks · Cache poisoning · Missing rate limits
Platform and supply chain: CORS · Security headers · Debug exposure · Cloud config · Dependency risk · File upload · Deserialization
Composite: Attack chains spanning several files or commits

Install once. Every PR after that is covered.

Everything happens in the pull request.

A second pass tries to disprove every finding. Only what survives reaches your PR.

Scan of #1285 candidates, 2 posted