‹ NexaTechQuality report QR-26-00062
NexaTech
A ready-to-launch Laravel electronics store with an English/Arabic storefront and a full admin panel, for retailers.
- Product ID
- B0001-74510
- Builder
- Buildify
- Version reviewed
- 1.3.0 · released 23 Oct 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0 / MariaDB 10.6
- Built with
- Claude Code
- Review period
- 23 Oct 2026 – 23 Oct 2026
- ✓AI code audit6 checks · 23 Oct 2026
- ✓Installed & run23 Oct 2026
- ✓Demo vs delivered23 Oct 2026
- ✓Final sign-off23 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.
- !4 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 credentials found. The demo mode uses a weak default password ('password') that ships to buyers and is visible in factory files. Several .env.example entries use realistic-looking placeholders (sk_live_, whsec_) that could be mistaken for real values. The codebase correctly uses environment variables and encrypted storage for all production credentials. | 92 | Warning |
| Dependency vulnerabilities | Both composer.lock and package-lock.json are present with all versions pinned. Laravel 12.69.2 and all PHP dependencies are current stable releases with no known critical vulnerabilities. The npm packages are also pinned and current. A few packages like PHPUnit (11.5.56) and Vite (7.3.7) could be updated to their latest patch versions, but these are dev dependencies and pose no security risk. | 95 | Pass |
| Authorisation & access control | All admin routes require authentication and role-based authorization via AuthorizeAdminArea middleware. Mutating endpoints are properly guarded. However, several customer-facing read endpoints (order details, addresses, returns) lack explicit ownership checks—a customer could potentially view another's data by changing the ID in the URL. Password storage uses bcrypt correctly throughout. | 92 | Warning |
| Database access rules | No SQL injection or unscoped deletes found. All queries use parameter binding or Eloquent. Schema is complete and can be created from empty. Foreign keys are present with sensible cascades. However, several foreign key columns lack indexes (e.g. order_items.order_id, shipments.order_id), which will cause performance issues as data grows. | 92 | Warning |
| Code structure & duplication | The codebase follows Laravel conventions well with clear separation of concerns (Actions, Services, Controllers, Requests). However, some service classes are large and contain multiple responsibilities, and there is minor duplication in payment gateway implementations and validation logic. | 78 | Warning |
| Build reproducibility | All dependencies are pinned in composer.lock and package-lock.json. The setup document covers prerequisites and steps in order. Minor issues: Docker setup references DB_ROOT_PASSWORD without documenting it in .env.example comments, and the setup script in composer.json doesn't verify database connectivity before migrations. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
The codebase follows Laravel conventions well with clear separation of concerns (Actions, Services, Controllers, Requests). However, some service classes are large and contain multiple responsibilities, and there is minor duplication in payment gateway implementations and validation logic.
No SQL injection or unscoped deletes found. All queries use parameter binding or Eloquent. Schema is complete and can be created from empty. Foreign keys are present with sensible cascades. However, several foreign key columns lack indexes (e.g. order_items.order_id, shipments.order_id), which will cause performance issues as data grows.
No real credentials found. The demo mode uses a weak default password ('password') that ships to buyers and is visible in factory files. Several .env.example entries use realistic-looking placeholders (sk_live_, whsec_) that could be mistaken for real values. The codebase correctly uses environment variables and encrypted storage for all production credentials.
All admin routes require authentication and role-based authorization via AuthorizeAdminArea middleware. Mutating endpoints are properly guarded. However, several customer-facing read endpoints (order details, addresses, returns) lack explicit ownership checks—a customer could potentially view another's data by changing the ID in the URL. Password storage uses bcrypt correctly throughout.
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 23 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 23 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 23 Oct 2026 with 4 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.3.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.
Report history
| Report | Version | Date | Score | Status |
|---|---|---|---|---|
| QR-26-00062 | 1.3.0 | 23 Oct 2026 | 91 | Current |
| QR-26-00030 | 1.2.0 | 7 Oct 2026 | 94 | Replaced |
| QR-26-00004 | 1.0.0 | 4 Oct 2026 | 91 | Replaced |
Vibe96 FZ-LLC, Dubai, UAE. This report describes the product at the time of review and is not a warranty.