‹ Torqly — Auto Repair Workshop & Garage Management SystemQuality report QR-26-00068
Torqly — Auto Repair Workshop & Garage Management System
Auto repair shop management: job cards, parts inventory, invoices & appointments for independent garages.
- Product ID
- B0651-35845
- Builder
- Artfall Studio
- Version reviewed
- 1.0.0 · released 27 Oct 2026
- Stack
- Laravel 13 · PHP 8.3 · MySQL 8.0+ / MariaDB 10.6+ / SQLite 3.35+
- Built with
- Claude Code
- Review period
- 23 Oct 2026 – 27 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run27 Oct 2026
- ✓Demo vs delivered27 Oct 2026
- ✓Final sign-off27 Oct 2026
At a glance
- ✓Installed and run from the delivered code — 8 of 8 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 88/100 with no failing check.
- !5 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 | The demo seed file contains weak default passwords ('password') for test accounts. While these are clearly marked as demo data and not production credentials, buyers deploying without changing them could expose their installation. No real API keys, private keys, or production credentials were found in the codebase. | 92 | Warning |
| Dependency vulnerabilities | The project uses Composer (PHP) and npm (JavaScript) with lockfiles present. Laravel 13.17 and PHP 8.3 dependencies are current. Several npm packages are outdated (Vite 8.0.0, Tailwind 4.0.0 are pre-release versions) but no known critical vulnerabilities were found. The demo uses SQLite which is appropriate for testing. | 85 | Warning |
| Authorisation & access control | All mutating routes require authentication and role checks are enforced via middleware. Admin, advisor and mechanic roles are properly segregated. Password hashing uses bcrypt. Minor issue: customer and vehicle show/edit endpoints lack ownership checks—any authenticated user can view any customer/vehicle by changing the ID in the URL. | 95 | Warning |
| Database access rules | No SQL injection vulnerabilities found—all queries use parameter binding or Eloquent. However, several foreign key columns lack indexes (customer_id, vehicle_id, mechanic_id, part_id), which will cause performance issues as data grows. Two delete operations lack proper scoping checks (Customer and Part controllers), though they have existence checks. The schema is complete and can be created from empty. | 78 | Warning |
| Code structure & duplication | The codebase follows Laravel conventions well with business logic properly isolated in Services. However, there is moderate duplication in validation rules across controllers, some large controller methods, and configuration values scattered in multiple places. The architecture is sound but could benefit from extracting shared validation and reducing controller method sizes. | 78 | Warning |
| Build reproducibility | The project is fully reproducible. All dependencies resolve, framework versions are consistent (Laravel 13, PHP 8.3), and build output is properly excluded. HowToSetup.md covers all deployment paths but could be clearer about the order of npm build vs migration steps and SQLite file creation timing. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The demo seed file contains weak default passwords ('password') for test accounts. While these are clearly marked as demo data and not production credentials, buyers deploying without changing them could expose their installation. No real API keys, private keys, or production credentials were found in the codebase.
All mutating routes require authentication and role checks are enforced via middleware. Admin, advisor and mechanic roles are properly segregated. Password hashing uses bcrypt. Minor issue: customer and vehicle show/edit endpoints lack ownership checks—any authenticated user can view any customer/vehicle by changing the ID in the URL.
The project uses Composer (PHP) and npm (JavaScript) with lockfiles present. Laravel 13.17 and PHP 8.3 dependencies are current. Several npm packages are outdated (Vite 8.0.0, Tailwind 4.0.0 are pre-release versions) but no known critical vulnerabilities were found. The demo uses SQLite which is appropriate for testing.
The codebase follows Laravel conventions well with business logic properly isolated in Services. However, there is moderate duplication in validation rules across controllers, some large controller methods, and configuration values scattered in multiple places. The architecture is sound but could benefit from extracting shared validation and reducing controller method sizes.
No SQL injection vulnerabilities found—all queries use parameter binding or Eloquent. However, several foreign key columns lack indexes (customer_id, vehicle_id, mechanic_id, part_id), which will cause performance issues as data grows. Two delete operations lack proper scoping checks (Customer and Part controllers), though they have existence checks. The schema is complete and can be created from empty.
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 27 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 | Yes | |
| 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 | Yes | |
| Branding and company details can be changed without code | Yes |
Stage 2 — Live demo compared with the delivered code
Completed 27 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
- None — approved on the first round.
- Sign-off: approved for sale on 27 Oct 2026 with 5 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.