‹ NexaTechQuality report QR-26-00115
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.4.0 · released 11 Nov 2026
- Stack
- Laravel · PHP 8.x · MySQL 8.0 / MariaDB 10.6
- Built with
- Claude Code
- Review period
- 10 Nov 2026 – 11 Nov 2026
- ✓AI code audit6 checks · 10 Nov 2026
- ✓Installed & run11 Nov 2026
- ✓Demo vs delivered11 Nov 2026
- ✓Final sign-off11 Nov 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.
- !12 of 15 promised items delivered (setup guide, example config and the rest).
- ✓Security scored 82/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 | Every regex candidate is either a placeholder (.env.example, a project filee, docs), a config() lookup, or a PHP class reference such as Password:[hidden] No committed .env, private keys, or live API keys appear in the digest. Two items deserve a note: the demo admin password depends on an env value that ships empty, and 150 changed files were not visible in the digest. | 93 | Pass |
| 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 | The admin area has a layered guard: separate auth:admin guard, a fail-closed role middleware that refuses unmapped routes, throttled logins, and Owner-only demo data actions. The routes files (a project file, a project file) and most customer-facing controllers were not in the digest, so the ownership checks on order, return, address and tracking lookups by id/token could not be verified. Webhook endpoints and the storefront-password flow also need confirmation. | 80 | Warning |
| Database access rules | The files supplied show Eloquent and validated input: the demo-data controller whitelists groups with Rule::in and gates destructive actions behind owner permission, a typed 'REMOVE' confirmation, and a demo-mode guard. The key files for this check (DemoDataRemoval, DemoDataRun, ProductSearch, migrations, schema.sql, DatabaseBackup) were not included in the digest, so raw SQL, foreign keys, indexes and delete scoping could not be verified. | 72 | Warning |
| Code structure & duplication | The codebase splits concerns into Actions, Services, Support and Themes, and controllers delegate to services. The main weaknesses are a few long controllers and repeated Password broker calls, which cost points without making the product hard to maintain. | 84 | Pass |
| Build reproducibility | composer.json and package.json pin every dependency, lockfiles exist, a .env.example and Docker files are present, and build output is excluded. HowToSetup.md and the Docker files were not in the excerpts, so setup order, prerequisites and compose coherence could not be verified. The declared stack and a few documented references are inconsistent. | 80 | Warning |
Open warnings
Problems that did not stop the listing. They stay on the product page until a later version fixes them.
composer.json and package.json pin every dependency, lockfiles exist, a .env.example and Docker files are present, and build output is excluded. HowToSetup.md and the Docker files were not in the excerpts, so setup order, prerequisites and compose coherence could not be verified. The declared stack and a few documented references are inconsistent.
The admin area has a layered guard: separate auth:admin guard, a fail-closed role middleware that refuses unmapped routes, throttled logins, and Owner-only demo data actions. The routes files (a project file, a project file) and most customer-facing controllers were not in the digest, so the ownership checks on order, return, address and tracking lookups by id/token could not be verified. Webhook endpoints and the storefront-password flow also need confirmation.
The files supplied show Eloquent and validated input: the demo-data controller whitelists groups with Rule::in and gates destructive actions behind owner permission, a typed 'REMOVE' confirmation, and a demo-mode guard. The key files for this check (DemoDataRemoval, DemoDataRun, ProductSearch, migrations, schema.sql, DatabaseBackup) were not included in the digest, so raw SQL, foreign keys, indexes and delete scoping could not be verified.
Requirement list
What the builder agreed to deliver before uploading — 12 of 15 met.
- Complete source for every component Met
- No real credentials in the archive Met
- Builds from a clean machine Partial
- Database script or migrations Met
- Authentication and roles on every mutating endpoint Partial
- 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 11 Nov 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 11 Nov 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 11 Nov 2026 with 3 warnings shown publicly.
What this report covers — and what it doesn't
- It covers version 1.4.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-00115 | 1.4.0 | 11 Nov 2026 | 83 | Current |
| QR-26-00062 | 1.3.0 | 23 Oct 2026 | 91 | Replaced |
| 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.