Vibe code review
A senior review of an app built with AI coding tools, covering security, data, performance and deployment, with a ranked fix list.
Laravel services
Laravel code review and audit
Find out what you really have before you invest more in it. A senior Laravel engineer reviews your codebase and gives you a clear, ranked report on security, performance, architecture and the cost of change.
Security
Authentication, authorisation, input handling, secrets and vulnerable dependencies.
Performance
Query patterns, indexes, caching, queues and the slow paths your users notice.
Architecture
How the code is organised, how hard it is to change and where technical debt is building up.
Quality
Tests, static analysis, coding standards, documentation and deployment practices.
Why get a Laravel code review?
Most businesses only find out how healthy their codebase is when something goes wrong: a security incident, a supplier who disappears, or a simple feature that somehow takes three months. A code review gives you that answer up front, for a fixed price.
Common reasons clients ask for one:
- Before investing more. You are planning a big new phase and want to know whether the foundations will hold.
- Changing supplier. You want an independent view of what your current or previous developers delivered.
- Due diligence. An investor, acquirer or enterprise customer wants evidence that the product is sound.
- Something feels wrong. Bugs keep coming back, releases are scary or the app is getting slower.
What the report covers
The report opens with a one-page summary for managers and investors, covering overall health, key risks and recommended next steps. The detailed findings follow, each ranked by severity with the affected code, an explanation of the risk and a recommended fix with an effort estimate.
We cover:
- Versions and support. Your Laravel and PHP versions against the current support dates, with an upgrade path if needed.
- Security. Access control, authentication, mass assignment, injection risks, file handling, secrets and vulnerable packages.
- Performance. Query counts, indexes, caching, queue use and memory-heavy operations.
- Architecture. Separation of concerns, duplication, coupling and how hard common changes would be.
- Testing and tooling. What is tested, what is not, and whether static analysis, code style and CI are in place.
- Operations. Deployment, logging, error tracking, backups and environment configuration.
What happens next
You own the report and can act on it however you like. Many clients ask us to fix the critical items, plan an upgrade or take on ongoing support. Others hand the report to their own team. Either way, you will know exactly where you stand.
Scope
What's included
- A senior engineer's review of the whole codebase, supported by automated analysis
- Laravel and PHP version check against current support dates
- Dependency audit for known vulnerabilities and abandoned packages
- Security review of authentication, authorisation, validation and secrets
- Database and query review, including N+1 queries and missing indexes
- Test coverage and quality review
- Architecture and maintainability assessment
- A written report with ranked findings, effort estimates and recommendations
- A call to talk through the report
Not included
- Fixing the issues, which we can quote for separately
- Live penetration testing, which is part of our security review
Process
How it works
Access
You give us read-only access to the repository and a short briefing on what worries you.
Analyse
Automated tools map the codebase and flag issues, then a senior engineer reviews the code by hand.
Report
Within four working days you get a ranked report written for both managers and developers.
Discuss
We walk you through the findings and answer questions, with no obligation to hire us for the fixes.
FAQ
Frequently asked questions
How much does a Laravel code review cost?
A standard Laravel code review is a fixed £295 plus VAT, for codebases up to a typical business application size. Very large or multi-application estates are quoted before we start.
How is this different from a vibe code review?
A Laravel code review suits codebases written mainly by people, often over several years. A vibe code review is designed for apps written mostly with AI tools, and focuses on the gaps those tools tend to leave, such as missing authorisation and invented packages. If you are not sure which you need, ask us and we will recommend one.
What do you need from us?
Read-only access to the repository, a short description of the application and anything that worries you. Access to a staging environment helps but is not required.
Will you criticise our developers?
No. The report is about the code, not the people who wrote it. We explain the reasons behind each finding and recognise what has been done well. Many teams use our reports to argue for time to fix technical debt.
Can the report be used for due diligence?
Yes. Investors and buyers often ask for an independent view of a product's code. The executive summary is written for non-technical readers.
Keep exploring
Related services and guides
Laravel rescue and takeover
We take over struggling Laravel projects, whether written by people or AI, stabilise them quickly and get delivery back on track.
Laravel upgrades
Fixed-fee upgrades from any Laravel version to Laravel 13, with dependency fixes, test checks and a written report.
Talk to a senior Laravel engineer
Book a free 30-minute call. Tell us what you are building or what is worrying you, and we will tell you honestly what we would do, what it costs and how long it takes.