Review your Laravel app code for security holes and bugs

A freelancer built your app a while ago, or your team grew it in a hurry. It works, but you're not sure what's hiding in it, and you'd like to find out before a customer or an attacker does.

I'll read through the code and send you a written report within 1 day.

What I check:
- Authentication and permissions: who can see or change what, and whether the server enforces it
- Common holes: SQL injection, XSS, CSRF, mass assignment, unsafe file uploads, open redirects
- Secrets committed to the repo, debug mode left on, error pages leaking data, an exposed .env file
- Outdated packages with known vulnerabilities (composer audit)
- Queries that will slow down as data grows (N+1 queries, missing indexes)
- Code structure that makes bugs likely

What you get:
- A report listing each issue, where it is (file and line), why it matters and how to fix it
- Priority labels: fix now, fix soon, nice to have
- A short summary for non-technical owners

I worked on a UK platform where we closed all 7 findings from an external security audit, and I wrote 485 automated API tests for it.

The fixed price covers apps up to about 30 controllers. I review the code only and don't run attacks against your live server. Fixes are not included, but I can quote for them from the report.