‹ Car Rental Manager: Fleet, Bookings & ReturnsQuality report QR-26-00079
Car Rental Manager: Fleet, Bookings & Returns
Fleet, bookings, handover and returns for small car rental companies
- Product ID
- B0344-31655
- Builder
- Infymerce
- Version reviewed
- 1.0.0 · released 28 Oct 2026
- Stack
- Laravel 13.17 + Filament 5.10 · PHP 8.4+ · MySQL 8.0+ or MariaDB 10.6+
- Built with
- Claude Code
- Review period
- 25 Oct 2026 – 28 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 24 Oct 2026
- ✓Installed & run28 Oct 2026
- ✓Demo vs delivered28 Oct 2026
- ✓Final sign-off28 Oct 2026
At a glance
- !Installed and run from the delivered code — 6 of 7 checks answered yes.
- ✓Live demo compared with the delivered code — 7 of 7 checks answered yes.
- ✓15 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 95/100 with no failing check.
- !3 open warnings — explained in part 1.
AI code audit
The full source archive was read by our AI auditor against each check. It reads the code — it does not run it; running it is part 2.
| Check | What we found | Score | Result |
|---|---|---|---|
| Secrets & credentials | All sensitive credentials are properly externalized to environment variables. The .env.example file contains only placeholders and instructions. Database passwords, admin passwords, and demo credentials all require explicit configuration via environment variables with clear documentation. | 100 | Pass |
| Dependency vulnerabilities | All production dependencies are pinned in composer.lock (402 KB) and package-lock.json. No known critical vulnerabilities detected in Laravel 13.17, Filament 5.10, or other packages. A few dev dependencies could be updated but pose no security risk. | 95 | Pass |
| Authorisation & access control | All admin routes are protected by Filament's authentication and policies. Public booking creation is rate-limited with honeypot protection. The signed URL for viewing a booking does not verify the customer owns it (anyone with the link can view), and the demo login endpoints lack CSRF protection on POST requests. | 92 | Warning |
| Database access rules | No SQL injection risks or unscoped destructive queries found. All queries use parameter binding or Eloquent. Schema is complete with proper foreign keys and cascades. However, several foreign key columns lack indexes (car_id, customer_id, branch_id, category_id), which will cause performance issues as data grows. | 92 | Warning |
| Code structure & duplication | The project has clear separation between controllers, services, and models following Laravel conventions. However, some service classes are large and contain multiple responsibilities, and there is minor code duplication in validation and query patterns. Configuration is mostly externalized but a few hard-coded values remain. | 78 | Warning |
| Build reproducibility | The project is fully reproducible with Docker or manual setup. All dependencies resolve correctly, framework versions are consistent (Laravel 13, PHP 8.3+), and build artifacts are properly excluded. HowToSetup.md provides clear instructions but could be more explicit about Node.js version requirements and the order of environment variable setup. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The project has clear separation between controllers, services, and models following Laravel conventions. However, some service classes are large and contain multiple responsibilities, and there is minor code duplication in validation and query patterns. Configuration is mostly externalized but a few hard-coded values remain.
No SQL injection risks or unscoped destructive queries found. All queries use parameter binding or Eloquent. Schema is complete with proper foreign keys and cascades. However, several foreign key columns lack indexes (car_id, customer_id, branch_id, category_id), which will cause performance issues as data grows.
All admin routes are protected by Filament's authentication and policies. Public booking creation is rate-limited with honeypot protection. The signed URL for viewing a booking does not verify the customer owns it (anyone with the link can view), and the demo login endpoints lack CSRF protection on POST requests.
Requirement list
What the builder agreed to deliver before uploading — 15 of 15 met.
- Complete source for every component Met
- No real credentials in the archive Met
- Builds from a clean machine Met
- Database script or migrations Met
- Authentication and roles on every mutating endpoint Met
- Pinned dependencies without critical CVEs (nice)Met
- Documentation set (nice)Met
- Working live demo Met
- README.md Met
- HowToSetup.md Met
- CLAUDE.md (or AGENTS.md) (nice)Met
- CHANGELOG.md (nice)Met
- .env.example Met
- a project file Met
- a project file (nice)Met
Human review
Reviewers from the Vibe96 team in Dubai worked through each question below; a final reviewer signed it off.
Stage 1 — Installed and run from the delivered code
Completed 28 Oct 2026A reviewer installed the product on a clean machine, following only the guide that ships with it.
| Question | Answer | Reviewer's note |
|---|---|---|
| Packages restored without errors | No | |
| Solution builds clean | Yes | |
| Database created from the shipped script or migrations | Yes | |
| First sign-in works with the documented steps | Yes | |
| Setup guide is accurate and complete | Yes | |
| Every module in the feature list opens and works | Yes | |
| No real secrets in the archive | N/A | |
| Branding and company details can be changed without code | Yes |
Stage 2 — Live demo compared with the delivered code
Completed 28 Oct 2026A second reviewer checked that what the listing and demo show is what the buyer receives.
| Question | Answer | Reviewer's note |
|---|---|---|
| Demo URL is reachable | Yes | |
| Demo credentials work | Yes | |
| Demo runs the same version as the archive | Yes | |
| All five differentiators are visible in the demo | Yes | |
| Screenshots match the demo | Yes | |
| Nothing in the demo is missing from the code | Yes | |
| Datasheet claims are accurate | Yes |
Changes asked for during review
- Round 1: changes requested on 26 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 28 Oct 2026 with 3 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.0.0 exactly as the buyer downloads it: the source archive, the setup guide and the live demo on the dates above.
- It is not a penetration test, a performance or load test, or a legal review of third-party package licences.
- Scores are a point in time. Libraries age; a later version is audited again and gets its own report.
- Your setup matters. Hosting, configuration and changes made after purchase are outside this review.
- How the score is made: each AI check is scored 0–100 and weighted (security counts most). A listing needs 75 or more, no failing check, and the human review passed.
- Always try the live demo before buying, and ask the builder questions from the product page.
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.