‹ NexaTechQuality report QR-26-00030
This report has been replaced — a newer version of NexaTech was reviewed. See the current 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.2.0 · released 7 Oct 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0 / MariaDB 10.6
- Built with
- Claude Code
- Review period
- 7 Oct 2026 – 7 Oct 2026
- ✓AI code audit6 checks · 7 Oct 2026
- ✓Installed & run7 Oct 2026
- ✓Demo vs delivered7 Oct 2026
- ✓Final sign-off7 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.
- !14 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 96/100 with no failing check.
- !2 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 values are properly externalized to environment variables via .env. The .env.example file contains only placeholders (e.g., 'replace-with-a-strong-database-password', 'your_stripe_secret_key'). Database seeders generate random passwords at runtime. No API keys, private keys, or real credentials are committed. | 100 | Pass |
| Dependency vulnerabilities | Both composer.lock and package-lock.json are present and pin all dependencies to specific versions. No known critical vulnerabilities were found in the declared stack (Laravel 12.69, PHP 8.2+, MySQL 8.0). A few dependencies may be outdated but this is normal for production-ready code and does not pose immediate security risk. | 95 | Pass |
| Authorisation & access control | All admin routes require authentication and role checks. Mutating endpoints are properly guarded. Password reset uses Laravel's secure broker with throttling. Two minor gaps: order tracking allows any signed-in customer to view another's order if they know the number+email, and the invoice endpoint lacks an ownership check for authenticated users. | 95 | Warning |
| Database access rules | No SQL injection paths or unscoped destructive queries found. All user input is parameterized through Eloquent or query builder bindings. Schema is complete with proper foreign keys and cascades. However, several foreign key columns lack explicit indexes (MySQL creates them automatically, but explicit indexes are best practice for portability and clarity). | 92 | Warning |
| Code structure & duplication | NexaTech demonstrates good separation of concerns with Actions, Services, and Controllers properly isolated. Business logic is appropriately placed in Services and Actions rather than controllers. However, there is some duplication in password reset flows, email preview logic, and several hard-coded configuration values scattered across the codebase that should be centralized. | 82 | Pass |
| Build reproducibility | The project is fully reproducible with clear setup instructions, pinned dependencies in composer.lock and package-lock.json, and working Docker configuration. Minor issues: HowToSetup.md doesn't mention Node.js/npm versions needed for Vite build, docker-compose.yml references a Dockerfile not shown in the file tree, and the setup document could clarify the database seeding step order more explicitly. | 92 | Pass |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
All admin routes require authentication and role checks. Mutating endpoints are properly guarded. Password reset uses Laravel's secure broker with throttling. Two minor gaps: order tracking allows any signed-in customer to view another's order if they know the number+email, and the invoice endpoint lacks an ownership check for authenticated users.
No SQL injection paths or unscoped destructive queries found. All user input is parameterized through Eloquent or query builder bindings. Schema is complete with proper foreign keys and cascades. However, several foreign key columns lack explicit indexes (MySQL creates them automatically, but explicit indexes are best practice for portability and clarity).
Requirement list
What the builder agreed to deliver before uploading — 14 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)Partial
- 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 7 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 7 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 7 Oct 2026 with 2 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.2.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.