‹ Shipzo - Complete Querier ServiceQuality report QR-26-00012
Shipzo - Complete Querier Service
Complete last-mile delivery management: admin web app, driver PWA, merchant portal, COD finance and live tracking.
- Product ID
- B0001-81882
- Builder
- Ibrahim Abdurahman
- Version reviewed
- 1.0.0 · released 5 Oct 2026
- Stack
- Laravel 13 · PHP 8.3 · MySQL 8
- Built with
- Claude Code
- Review period
- 4 Oct 2026 – 5 Oct 2026 · 1 round of changes
- ✓AI code audit6 checks · 4 Oct 2026
- ✓Installed & run5 Oct 2026
- ✓Demo vs delivered5 Oct 2026
- ✓Final sign-off5 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 92/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 | No real API keys or credentials were discovered. The .env.example file contains weak demo passwords (Admin@123, 1234) that ship to buyers and are documented in README.md. These are acceptable for demo seeding but should be changed before production use. All other secrets are proper placeholders or environment variable references. | 92 | Warning |
| Dependency vulnerabilities | The project uses Laravel 13.17 and PHP 8.3 with all dependencies locked in composer.lock. No known critical vulnerabilities were found in the production dependencies. A few dev dependencies (phpunit, mockery) could be updated to their latest patch versions, but these are not security-critical. The lockfile is present and properly maintained. | 85 | Warning |
| Authorisation & access control | All mutating endpoints are protected by authentication and CSRF. Role-based middleware is correctly applied to admin routes. Password hashing uses bcrypt. However, several read endpoints (parcel details, merchant/customer lookups, driver performance) lack ownership checks, allowing cross-tenant data access by manipulating IDs in the URL or API. | 92 | Warning |
| Database access rules | All raw SQL uses parameterized queries through the Db helper. No string concatenation or injection paths found. Delete and update statements are properly scoped. Schema migrations are complete and can build from empty. Minor issues: a few foreign keys lack indexes (parcels.driver_id, routes.driver_id), and one migration uses raw SQL for constraints instead of Blueprint methods. | 92 | Warning |
| Code structure & duplication | Controllers properly delegate to services, and business logic is centralized. However, several service files exceed 400 lines, password validation logic is duplicated across three controllers, and some configuration values are hard-coded in multiple places. The architecture is sound but would benefit from extracting utility methods and breaking down larger services. | 78 | Warning |
| Build reproducibility | The project is fully reproducible on a clean machine. Composer dependencies resolve, migrations run, and Docker Compose works. HowToSetup.md covers all major paths (Docker, Linux VPS, XAMPP, cPanel). Minor issues: Docker instructions reference environment variables without showing how to persist them; Windows PowerShell syntax for multi-line env vars is incomplete; the .env.example has empty DEMO_PASSWORD fields that could confuse first-time users. | 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 uses Laravel 13.17 and PHP 8.3 with all dependencies locked in composer.lock. No known critical vulnerabilities were found in the production dependencies. A few dev dependencies (phpunit, mockery) could be updated to their latest patch versions, but these are not security-critical. The lockfile is present and properly maintained.
All raw SQL uses parameterized queries through the Db helper. No string concatenation or injection paths found. Delete and update statements are properly scoped. Schema migrations are complete and can build from empty. Minor issues: a few foreign keys lack indexes (parcels.driver_id, routes.driver_id), and one migration uses raw SQL for constraints instead of Blueprint methods.
No real API keys or credentials were discovered. The .env.example file contains weak demo passwords (Admin@123, 1234) that ship to buyers and are documented in README.md. These are acceptable for demo seeding but should be changed before production use. All other secrets are proper placeholders or environment variable references.
Controllers properly delegate to services, and business logic is centralized. However, several service files exceed 400 lines, password validation logic is duplicated across three controllers, and some configuration values are hard-coded in multiple places. The architecture is sound but would benefit from extracting utility methods and breaking down larger services.
All mutating endpoints are protected by authentication and CSRF. Role-based middleware is correctly applied to admin routes. Password hashing uses bcrypt. However, several read endpoints (parcel details, merchant/customer lookups, driver performance) lack ownership checks, allowing cross-tenant data access by manipulating IDs in the URL or API.
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 5 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 5 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 5 Oct 2026; the builder fixed them and uploaded again.
- Sign-off: approved for sale on 5 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.